Intel: usplash must be uninstalled to achieve usable consoles with vga=0x120

Bug #150797 reported by Felix Miata
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
usplash (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: usplash

I installed from kubuntu-7.10-beta-alternate this AM, then immediately upgraded to whatever state is on the mirrors.

On all Intel video chips that I've used (i810, i815, 845G), none of the common framebuffer vga= modes (785, 788, 791, 0x31a, etc.) work. The only functional mode I've found other than normal 80x25 is 0x120, which is 25 row by 132 column. Setting splash=0 and vga=0x120 on the kernel lines in menu.lst causes bootup video to initialize correctly, but after usplash finishes and I return to any of the consoles from X, the characters on screen have been reset to the 80x25 size, but are laid out as if there were still 25 rows of 132 columns, with chars >80 spilling onto subsequent rows, and new rows appended where previous rows end. As a result, the consoles are unusable. The last rows and columns seem to be off the bottom of the screen. The only fixes I have found are suffering to keep 80x25, or apt-get remove usplash. I did the latter before booting after the upgrade, so don't know if a newer version than 0.5-5 might have behaved differently.

Upstream kernel bug http://bugzilla.kernel.org/show_bug.cgi?id=7513 might be related.

Revision history for this message
Felix Miata (mrmazda) wrote :

I've since determined that with 845G a BIOS upgrade may provide support for standard framebuffer vga= modes.

Revision history for this message
Saivann Carignan (oxmosys) wrote :

Can you look in your BIOS options to see if you can apply a similar workaround as the one described in bug 68012 description?

Changed in usplash:
assignee: nobody → saivann
status: New → Incomplete
Revision history for this message
Felix Miata (mrmazda) wrote :

That's basically what https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/150797/comments/1 means IIRC. Newer BIOS may have a 1MB/8MB option while older BIOS have only .5MB/1MB options. IIRC, my GX150 i815 with Hardy has a BIOS with .5/1 option set to 1, while my Intel DLVA 845G with Hardy has the 1/8 option set to 8. I don't believe the other bug describes a workaround as much as it does full VESA support vs. partial VESA support in the motherboard BIOS, with full VESA support available only when there is an 8M BIOS option. On the systems with the 8M option available, the 0x120 mode does not work but the standard VESA modes do work; while on those with only .5/1 options, no standard VESA modes work, and 0x120 does.

see also https://bugzilla.novell.com/show_bug.cgi?id=259577 and https://qa.mandriva.com/show_bug.cgi?id=39837

Changed in usplash:
assignee: saivann → nobody
status: Incomplete → New
Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in usplash (Ubuntu):
status: New → Incomplete
Revision history for this message
Felix Miata (mrmazda) wrote :

I no longer use *buntu on any systems where the standard VESA modes do not work as expected. It's possible http://bugzilla.kernel.org/show_bug.cgi?id=7513 may have provided a fix. The Novell bug noted earlier has been marked fixed as well. I do still have a working i810 system, so I need to try a 9.04 live CD when I get a chance, if someone else doesn't get to it and comment here first.

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

No problem Felix, I shall leave this bug as Incomplete for now in the hope that yourself or someone else can provide that information. Thank you.

Revision history for this message
xteejx (xteejx-deactivatedaccount) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in usplash (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Felix Miata (mrmazda) wrote :

This is worksforme as of 9.10.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.