2009/1/3 Volker Armin Hemmann <[email protected]>: > On Samstag 03 Januar 2009, Beso wrote: >> 2009/1/2 Volker Armin Hemmann <[email protected]>: >> > On Freitag 02 Januar 2009, Beso wrote: >> >> 2009/1/1 Sebastian Redl <[email protected]>: >> >> > Hi, >> >> > >> >> > When my hard-disk made suspicious noises recently, I decided to >> >> > replace it - be safe rather than sorry - and use the opportunity to do >> >> > a complete, fresh install of my system. The new system is up and >> >> > running (OpenOffice troubles aside), with the added advantage that I >> >> > finally managed to get to the most recent ATI binary driver version >> >> > instead of that stone-age version that happened to not hang my system >> >> > under the old setup. >> >> > >> >> > With the new driver, I want to use its AIGLX capabilities. However, >> >> > I'm having trouble getting XComposite to work. I have it enabled in >> >> > xorg.conf: >> >> > >> >> > Section "Extensions" >> >> > Option "Composite" "Enable" >> >> > EndSection >> >> >> >> you need also to enable damage and render extension in the extensions >> >> section. here's what >> >> ity should look like: >> > >> > NO >> > >> > he does not. In fact he does not have to enable anything of this. >> >> when i've last been with fglrx you would need to enable that manually or >> they won't start. as i've said it has been about 6-8 months that i haven't >> been using fglrx. >> >> > Here is a close to perfect xorg.conf, with composite/aiglx working: >> > >> > Section "ServerLayout" >> > Identifier "Layout0" >> > Screen 0 "aticonfig-Screen[0]-0" 0 0 >> > InputDevice "Keyboard0" "CoreKeyboard" >> > InputDevice "Mouse0" "CorePointer" >> > EndSection >> > >> > Section "Files" >> > EndSection >> > >> > Section "Module" >> > Load "evdev" >> > Load "v4l" >> > EndSection >> > >> > Section "InputDevice" >> > Identifier "Mouse0" >> > Driver "evdev" >> > Option "CorePointer" >> > Option "Name" "Logitech, Inc. MX610 Laser Cordless Mouse" >> > Option "evBits" "+1-2" >> > Option "keyBits" "~272-287" >> > Option "relBits" "~0-2 ~6 ~8" >> > EndSection >> >> this doesn't work anymore. for the use of evdev (2.0.5 if i remember >> well) with new hal versions >> you have to put these options inside >> /etc/hal/fdi/policy/10-x11-input.fdi or evedev would throw >> out warnings and errors and the devices would not have full >> functionality. the other option would >> be to put the ignore flag inside xorg.conf. i don't see you having >> this flag enabled and this >> leads me to think that you're not using the 1.5.x xorg-server. > > hal: > 0.5.11-r4 > evdev: > 2.1.0 > xorg-server: > 1.5.3 > > and for some reasons I have full functionality. > well, i've had some issues with this new way of configuration and spent some hours to fix up hal rules. either i have been very unlucky or you've been lucky.
>> >> here's what colin guthrie said about this functionality in a >> discussion about xorg >> allowing non hal devices inside xorg.conf on the xorg mailing list: >> >> Yes. Some platforms that Xorg is on do not support hal. But that said, >> there are lots of things in Gnome/KDE that just don't work without HAL, >> so more and more you will need it for correct operation. Is there any >> reason you have a problem using hal? > > there are many reasons. Like hal breaking every version. hal config being a > pain in the ass. keyboard with non us layouts are almost unusable with hal - > except somebody hhacks a fdi together. > In short: hal is a POS and forcing it down everybody's throat does not help. > well, this discussion went one long on the mailing list. i've been following it a little and i tend to agree with xorg devs: if there's one way of handling devices outside or the configuration and with something that just recognizes it and automatically plugs it on without the user to do anything is far better. i agree that the layout config isn't working, or at least not in a simple way (there has been a long discussion about this issue too on the mailing list), but you alreay know that the keyboard config is set to us by default at x login. setting the right layout in your desktop env then fixes localization inside the desktop environment. >> >> At the moment, Xorg will automatically disabled kbd/mouse devices unless >> you set the AllowEmptyInput flag in the server. > > not for me. > i've had to force it manually to have it loading the options. maybe your's working because you don't use the other particular settings that a driver might have, like synaptics touchpad gestures. well, again, either you've been lucky or i've been unlucky. sometimes xorg is just doing strange things. >> >> if you use xaa you'll also most probably will need also the >> Option "XAANoOffscreenPixmaps" "True" >> >> to eliminate xaa corruption on the screen. i don't know if this issue >> has already > > there are no xaa corruption. > i'm glad to hear that the bug of the pixel corruption around the pointer and around moving windows has been fixed. as i've said when i was still using fglrx it had this corruption issue (sometimes also video was getting corrupted) that i've had to set the removal of offscreen pixmaps to true. i know it was happening mostly with igp boards, like the ones in laptops. >> >>you'll also need to enable texturedrender in your device section to >> >>enable the Xv. i've been not >> >>using fglrx for some months now (the xf86-video-ati is quite enough >> >>for my needs) and i don't >> >>remember all the hacks that are available for fglrx driver. look at >> >>the phoronix forums for more >> >>detailed configuration infos about fglrx. >> > >> > no, he does not. >> >> what does he do not? to add configuration options or to see phoronix >> forums?! is not very clear from your answer. > > he does not need to add that option. On installation the driver will put the > right option into amdpcsdb - and everything there overrides xorg.conf. > so there's now an override in the amd personal configuration file. at the time i've been using fglrx this file had just appeared. by the way, it seems that this file is being overwritten after each update. is it the one for the permanent fglrx configuration or is there another file for this? i think it's a little stupid to overwrite this file every time, removing old settings, so that the end user to have to run again the amd config center. -- dott. ing. beso
