[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#279648: kernel-source-2.6.9: Boot : console vga mode problem



B. Zhang wrote:

I have just tested the kernel source 2.6.9 from http://www.kernel.org
with the same .config.
No problem, I can have vga=791 and console.


Sorry about not providing further debug info, I only intendend the follwing as a note that might help. (The affected machines are not ready at hand, but please ask if more info is needed)

I did experience this problem using 2.6.9 with a statically built rivafb module, and
using 2.6.10-rc1 with a statically compiled viafb driver (from patch).

When the drivers are compiled statically and the vga option is given then there IS a video mode switch at boot time (wich might come from grub as well which is in grapnic mode displaying a 640x480 splash)
but the screen remains blank.

If I compile the drivers into a module and boot without the vga option the drivers initialize properly when i load them with insmod. (Although they clear the screen with white, wich is not a problem, but annoying, and as far as I know this artefact is present since long time..)

I use vga=0x318, and I give all the explicit mode, depth, refresh, etc
information with a video=viafb:... video=rivafb:... option the driver can parse (I looked them up in the kernel sources). I'm sure these options are OK since they work well
when passed to insmod.

Note: both kernels has the DirectFB fusion patch on them, which is standalone character device
and im quite sure they do not affect the fb drivers.

Hope this helps. I'm quite fine with using modules, but having the display properly set from the start of the boot would be nice.



Reply to: