In mt previous experience with frame buffer (2.4 kernel and not Gentoo), I was able to load the frame buffer modules (matrox) after boot and could do frame buffer things (enable the tvout on my Mystique).
I am now using 2.6 (test8) and Gentoo. If I don't enable "G100/G200/G400/G450/G550 support", then it is not enough for me to load the usual modules (i2c_matroxfb and matroxfb_*). By "not enough" I mean that I do not get get the /proc/fb or /dev/fb/0 entries). If I enable the above option, then the devices get created, but at some point in the boot process my screen gets all garbled. I can remotely log in and run startx fine (except for a warning "(WW) MGA(0): Failed to set up write-combining range (0xe3000000,0x1000000)"). I tried to pass different arguments to lilo at boot time to set the video (video=<blah:blah:etc> to no avail). Where in the boot process does this frame buffer initialization occur? How can I control it? Thanks, John -- [EMAIL PROTECTED] mailing list
