On Monday 03 January 2011 17:12:11 fe...@crowfix.com wrote: > On Mon, Jan 03, 2011 at 09:37:23AM +0000, Mick wrote: > > KMS won't work with framebuffer modules like vesa/uvesa/radeonfb/etc. > > unless you also add nomodeset at the kernel line in GRUB. > > I'm not using those modules. Unless KMS actively breaks because those > modules exist but aren't loaded, I don't see how framebuffer modules > are the problem. > > > http://www.gentoo.org/doc/en/xorg-config.xm
I don't know because on my boxen I had the framebuffer modules built in the kernel. Therefore I had to recompile the kernel with all the KMS settings as suggested in the article above and remove the framebuffer modules completely. > I added VIDEO_CARDS and remerged xorg-server and xorg-drivers. This > made no difference; the log file is exactly the same other than a > minor Mhz change. > > > http://www.gentoo.org/proj/en/desktop/x/x11/xorg-server-1.8-upgrade-guide > > .xml > > It tells how to set up a config file for 1.8, which I had working > without a config file, so this particular upgrade guide seems rather > useless. My only problem is that 1.9.2 doesn't set the right screen > size. That probably does point to KMS in some manner, but a 1.8 > upgrade guide doesn't deal with it. I think that the solution is probably to go for the full KMS approach and remove the framebuffer modules as already suggested. Then come back if it doesn't work. The xorg-server-1.8 migration is necessary if you need to configure particular devices. HAL and its fdi files are no longer used. In absence of any other configuration files under /etc/X11/*, xorg will use the files in /usr/share/X11/xorg.conf.d/* which may or may not agree with your hardware. That's what the xorg-server-1.8 migration URL is for. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
