[Bug 21575] framebuffer blank/corrupted unless "splash" used with "vga="

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=21575
Ubuntu | linux





------- Additional Comments From a.parseg at gmail.com  2005-12-28 16:11 UTC -------
(In reply to comment #1)
> The likely reason is that with vga= and no splash argument, is that vesafb does
> not get loaded and it is trying to use just vga text mode switching.
> 
> Try adding vesafb to /etc/modules and boot with vga=791 and no splash argument.

Edit: in first report, behavior is compared to Breezy, not Hoary (initial Hoary
install, dist-upgraded to Breezy later on ; Dapper on separate partition of its
own). The vga= option already worked as expected in Hoary anyway.

vesafb added to /etc/modules as the first line. Now the framebuffer behaves
normally : Alt+Fn works fine, no display corruption. However it only starts
displaying the boot lines partway through (when the vesafb module loads,
obviously). 

Breezy on the same machine activates the framebuffer right at the beginning of
the boot process, without having vesafb in modules. 

It would seem there's no in-kernel framebuffer support (only as module), whereas
previous versions had it ?


-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.