No, the upstream changes in viafb won't help the problem you are experiencing and it is unknown whether viafb and/or openchrome (which should not rely on the output configuration to be correct) will ever be fixed as this would require an amount of documentation that is not yet released by VIA, especially for older IGPs like CLE266. However you can likely make it work with some module parameters as described in viafb.txt: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/fb/viafb.txt;h=f3e046a6a987a685910bafc171c2cc9cf243df1b;hb=HEAD If you also hit some acceleration bugs that where fixed in 2.6.33 you can use viafb_accel=0 This bug is similiar/identical to this one I think https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-via/+bug/538430 I do not object blacklisting viafb for this release as there exists also an even more serious problem: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539020
However blacklisting vga16fb sounds like a bad idea but that's not something I work on. (but even balcklisting it wouldn't be that much of a problem but it really should simply work) Perhaps it would be a good idea to do one seperate bugreport only for the vga16fb bug which gives a more verbose description of what the screen looks like? -- [KM400] Black screen after boot, no text console possible https://bugs.launchpad.net/bugs/518623 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
