You are not logged in.
today read that Xorg 7.4 moves to extra, and update, after that finally can use opengl with kwin, before can only use xrender and can watch videos at fullscreen without problems and the effects looks really nice now
and dont understend hotplug so disable with the help of the wiki.
only one thing about the update: libdrm looks like still is in testing and have to compile from abs, the same about xproto.
Offline
Since this update I cannot use keytouch as always, that is, my keys are not working
I am googling about that right now...
Heeeeeey cat!!!
Offline
you can disable hotplug, just read the wiki.
Offline
Now to get catalyst working with it. Currently, X won't even start.
Offline
Xorg fails to start with the RgbPath set. You should comment this in your xorg.conf:
Section "Files"
# RgbPath "/usr/lib/X11/rgb"
EndSection
Also, for me, the keyboard is horribly broken. Arrow keys, delete key, etc. all don't work. Keyboard layouts as chosen in KDE via system settings do not work, either.
Haha, the systray in KDE is broken, too. I have eight batteries.
Last edited by mutlu_inek (2008-11-30 17:52:11)
Offline
Xorg fails to start with the RgbPath set. You should comment this in your xorg.conf:
Section "Files" # RgbPath "/usr/lib/X11/rgb" EndSection
I've tried that, it just doesn't start. I'll make a thread.
Offline
And for catalyst some time you need to remove /etc/ati/amdpcsdb and run aticonfig to recreate it. If you got some seg. faults on start for me removing Text.*Render and Text.*2D solved (I dont remember the options name)...
Offline
Also, for me, the keyboard is horribly broken. Arrow keys, delete key, etc. all don't work. Keyboard layouts as chosen in KDE via system settings do not work, either.
Actually, it was due to the KDE settings. You need to choose "Evdev-managed keyboard" as the keyboard model in the keyboard layout KCM.
Offline
Haha, the systray in KDE is broken, too. I have eight batteries.
Ok, solved. Even better, now I don't have any systray artifacts any more. This concerns the intel driver.
I had to comment
Section "Device"
# Option "MigrationHeuristic" "greedy"
EndSection
See http://bugs.kde.org/show_bug.cgi?id=170283
Edit:
Oh, nice! For me, for the first time xorg runs just as well without an xorg.conf. Including all the compositing bling. This just means less potential errors.
Edit2:
Any 3D on my intel is horribly broken since TTM is not supported and GEM will only be in the 2.6.28 kernel:
$ glxgears
Failed to initialize TTM buffer manager. Falling back to classic.
229 frames in 5.0 seconds = 45.673 FPS
2D compositing works fine, though.
Last edited by mutlu_inek (2008-11-30 19:18:15)
Offline
you can disable hotplug, just read the wiki.
It works now, but is there any way to get keytouch working again with hotplug?
Heeeeeey cat!!!
Offline
After that xorg update, I had to remove xorg.conf, because it didin't work at all. I managed to get it work after command: "Xorg -configure", but I lost my keyboard layout totally. I edited layout options for xorg.conf, but it didin't solve the problem.
After editing GNOME layout-settings, I managed to get it work better, but it still won't work properly: ä's (a with dots, if can't see) don't work.
Last edited by Eboy (2008-11-30 19:25:09)
Offline
I edited layout options for xorg.conf, but it didin't solve the problem.
Did you read: http://wiki.archlinux.org/index.php/Xor … otplugging ?
If you want to set the keyboard in Gnome, this may help you: http://bbs.archlinux.org/viewtopic.php?id=59931
Offline
It works now, but is there any way to get keytouch working again with hotplug?
Yes, there is. You must:
1. remove or comment all input device configuration in xorg.conf
2. configure hal so that it can inform X correctly. This is the though part. For my case (abnt2 keyboard, Brasil), i used the following files:
-- /etc/hal/fdi/policy/10-keymap.fdi -- don't include this line
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keymap">
<append key="info.callouts.add" type="strlist">hal-setup-keymap</append>
</match>
<match key="info.capabilities" contains="input.keys">
<merge key="input.xkb.rules" type="string">base</merge>
<!-- If we're using Linux, we use evdev by default (falling back to
keyboard otherwise). -->
<merge key="input.xkb.model" type="string">keyboard</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.xkb.model" type="string">evdev</merge>
</match>
<merge key="input.xkb.layout" type="string">br</merge>
<merge key="input.xkb.model" type="string">abnt2</merge>
</match>
</device>
</deviceinfo>
-- end of file --
You must configure your keyboard correctly. Your current xorg.conf will be the right reference for you.
For the synaptics touchpad:
-- /etc/hal/fdi/policy/11-x11-synaptics.fdi --
<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.touchpad">
<match key="info.product" contains="Synaptics TouchPad">
<merge key="input.x11_driver" type="string">synaptics</merge>
<!-- Arbitrary options can be passed to the driver using
the input.x11_options property since xorg-server-1.5. -->
<!-- EXAMPLE:
-->
<merge key="input.x11_options.AlwaysCore" type="string">true</merge>
<merge key="input.x11_options.Protocol" type="string">auto-dev</merge>
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
<merge key="input.x11_options.SHMConfig" type="string">false</merge>
<merge key="input.x11_options.LeftEdge" type="string">1700</merge>
<merge key="input.x11_options.RightEdge" type="string">5300</merge>
<merge key="input.x11_options.TopEdge" type="string">1700</merge>
<merge key="input.x11_options.BottomEdge" type="string">4200</merge>
<merge key="input.x11_options.FingerLow" type="string">25</merge>
<merge key="input.x11_options.FingerHigh" type="string">30</merge>
<merge key="input.x11_options.MaxTapTime" type="string">180</merge>
<merge key="input.x11_options.VertEdgeScroll" type="string">true</merge>
<merge key="input.x11_options.HorizEdgeScroll" type="string">true</merge>
<merge key="input.x11_options.CornerCoasting" type="string">true</merge>
<merge key="input.x11_options.CoastingSpeed" type="string">0.30</merge>
<merge key="input.x11_options.VertScrollDelta" type="string">100</merge>
<merge key="input.x11_options.HorizScrollDelta" type="string">100</merge>
<merge key="input.x11_options.MinSpeed" type="string">0.10</merge>
<merge key="input.x11_options.MaxSpeed" type="string">0.60</merge>
<merge key="input.x11_options.AccelFactor" type="string">0.0020</merge>
<merge key="input.x11_options.VertTwoFingerScroll" type="string">true</merge>
<merge key="input.x11_options.HorizTwoFingerScroll" type="string">true</merge>
<merge key="input.x11_options.TapButton1" type="string">1</merge>
<merge key="input.x11_options.TapButton2" type="string">2</merge>
<merge key="input.x11_options.TapButton3" type="string">3</merge>
</match>
<match key="info.product" contains="AlpsPS/2 ALPS">
</match>
<match key="info.product" contains="appletouch">
</match>
<match key="info.product" contains="bcm5974">
</match>
</match>
</device>
</deviceinfo>
-- end of file --
3. Restart hal
4. Restart X
Everything should be working. Hope that helps.
Satisfied users don't rant, so you'll never know how many of us there are.
Offline
I did the steps above -edited /etc/hal/fdi/policy/10-keymap.fdi file, restarted hal and X- but the problem persists. My multimedia stop key acts like if it was the volume down key, and so :'(
My keyboard is an English one.
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keymap">
<append key="info.callouts.add" type="strlist">hal-setup-keymap</append>
</match>
<match key="info.capabilities" contains="input.keys">
<merge key="input.xkb.rules" type="string">base</merge>
<!-- If we're using Linux, we use evdev by default (falling back to
keyboard otherwise). -->
<merge key="input.xkb.model" type="string">keyboard</merge>
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.xkb.model" type="string">evdev</merge>
</match>
<merge key="input.xkb.layout" type="string">us</merge>
<merge key="input.xkb.model" type="string">pc105</merge>
</match>
</device>
</deviceinfo>
Last edited by BinkyTheClown (2008-11-30 21:53:52)
Heeeeeey cat!!!
Offline
Since this update I cannot use keytouch as always, that is, my keys are not working
I am googling about that right now...
That happened to me however, X started to recognized my functions keys as actual keys! Run xev and see if a keycode appears when you hit one of your function keys (Fn + F10 or w/e)
Offline
BinkyTheClown wrote:Since this update I cannot use keytouch as always, that is, my keys are not working
I am googling about that right now...That happened to me however, X started to recognized my functions keys as actual keys! Run xev and see if a keycode appears when you hit one of your function keys (Fn + F10 or w/e)
xev reports a keycode Thanks for the idea.
Heeeeeey cat!!!
Offline
Had no problem at all. Just read the messages when you use pacman, for example stuff like this:
[2008-11-25 21:43] Input device handling has changed in xorg-server 1.5.
[2008-11-25 21:43] Please read http://wiki.archlinux.org/index.php/Xorg_input_hotplugging.
It's a bug planet!
Offline
Well, I am using xbindkeys for the moment, but I miss the nice keytouch's OSD when changing volume
Heeeeeey cat!!!
Offline
I wont be updating until i resolve the driver issues, nvidia-71xx isn't supported by the new xorg, so I'm SOL without using the open source drivers or vesa.
Offline
Guys, how about configs usb mouse?
Offline
Guys, how about configs usb mouse?
Plug it in.
Offline
Guys, how about configs usb mouse?
Well I'm using hotplugging and my xorg section looks like this:
Section "InputDevice"
Identifier "Mouse0"
Driver "evdev"
Option "SendCoreEvents"
EndSection
Does anyone know if that is even needed?
Offline
Does anyone know if that is even needed?
It is not needed. Moreover, you can probably even run X without xorg.conf... but don't just delete it.
Offline
pyther, thank you!
Offline