Lost all graphics on "Jaunty" after last update.

Bug #327230 reported by res1b3uq
90
This bug affects 4 people
Affects Status Importance Assigned to Milestone
usplash (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

 I am at present on 7.10-same machine. I have nothing but a black screen on Jaunty. I had no problem getting the machine up this morning, then I added the last updates- still no problem. I cut the machine off, left the house , and when I came back and tried to restart the machine, I got a "no graphics" message. I rebooted the machine, and now there is no message, just a totally black screen. Sorry I don't have more info to give you.

Related branches

Revision history for this message
res1b3uq (res1b3uq) wrote :

I got back into Jaunty by booting from a different kernel in GRUB.

Revision history for this message
pablomme (pablomme) wrote :

I can confirm this. The kernel update leaves me with a blank screen too. Everything works, though: the welcome sound is played back and I can restart the computer using the power key, the cursors and pressing Enter. Even the backlight control works fine to tune the screen to your favourite shade of black.

I've also noticed that in the screen mode change between the grub menu and the splash screen, for a split second the BIOS splash screen can be seen, which had never happened before. Perhaps this has to do with graphics modesetting?

I have an Intel 945GM chip, in case it's relevant.

Revision history for this message
pablomme (pablomme) wrote :

The problem doesn't seem to be with the kernel. I don't get anything on the screen with either 2.6.28-6 or 2.6.28-7.

Other possible culprits are initramfs and usplash, which were also updated today. However the old packages are not in my /var/cache (I guess because they were distribution updates?), so I can't easily revert the changes. I'll try to get them from the Alpha 4 squashfs image and report back.

But in any case - does anyone know if these older packages live anywhere online?

Revision history for this message
pablomme (pablomme) wrote :

I haven't reverted any package changes, but it seems that the problem is with usplash.

If I boot normally, independently of kernel version, I end up on a blank screen or with the X failing to load at all. However, if I choose 'recovery mode' at the grub menu, independently of kernel version, and pick "resume normal boot" at the recovery menu, everything works fine. I assume, given the recent updates, that the relevant difference is that in recovery mode usplash is bypassed, and in normal mode it's not.

So it appears that usplash 0.5.28 is to blame because it leaves the graphics driver in some funny state, which 0.5.27 didn't. I'm changing the package associated with this bug to reflect this.

Revision history for this message
res1b3uq (res1b3uq) wrote :

My chip is a 945GC. Are we the only ones affected?

Revision history for this message
Gianfranco Liporace (dr.kabuto) wrote :

Hi all,
I'm affected with this bug too, and probably the following list are duplicate of this bug report:

#327610
#327505
#327498
#327444
#327286

Removing "splash" from menu.lst i can have a login screen again.

Bryce Harrington (bryce)
Changed in usplash:
importance: Undecided → Critical
milestone: none → jaunty-alpha-5
Revision history for this message
swmike (ubuntu-s-plass) wrote :

For me everything works as normal when I boot 2.6.28-6, but it doesn't work with 2.6.28-7 (This is on Lenovo Thinkpad X200 (Intel Centrino2 with GMA 4500 graphics).

Revision history for this message
Bryce Harrington (bryce) wrote :

I can confirm seeing this problem after a recent upgrade. Each of the following made the issue go away:

  * Removing the 'splash' parameter from the bootloader
  * Booting to an earlier kernel
  * Downgrading to usplash 0.5.27

Revision history for this message
Bryce Harrington (bryce) wrote :

Here's the corresponding lib in case that's needed (I had installed both this and the usplash deb above)

Revision history for this message
Christopher (soft-kristal) wrote :

My system (also a 945G) works after choosing the 'attempt to fix graphic' in recovery mode. It flashes by very quickly but it seems to use a backup of xorg.config in /etc/X11.

Revision history for this message
Kees Cook (kees) wrote :

Here are builds corresponding to each bzr commit made between 0.5.27 and 0.5.28 releases:
http://people.ubuntu.com/~kees/usplash-testing/

Please try them in order: 242 242.1.1 242.1.2 242.1.3 242.1.4 243 244 Both usplash and libusplash0 debs for your architecture need to be installed.

242 is 0.5.27 and 244 is 0.5.28. I've personally been unable to reproduce this bug, so any feedback on which commit breaks graphics would go a long way to sorting out the origin of the problem.

Thanks!

Revision history for this message
Tommaso R. Donnarumma (tawmas) wrote :

I have the same on intel 915 (eee 900). I tried the first two workarounds proposed by Bryce Harrington above and they fix the problem for me too. I'll see if I can test the builds linked to by Kees Cook later today.

Revision history for this message
nyarnon (cabal) wrote :

It has to be a kernel issue as reverting to an older kernel gives normal access. I'm running .20 on a Intel Mobile 945GME on a eeepc 1000h The problem seems to start at the moment GDM kicks in as I do get my splash bar.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package usplash - 0.5.29

---------------
usplash (0.5.29) jaunty; urgency=low

  * libusplash.c: Revert signal handler changes which seem to have caused
    problems with Xorg initialization in some situations (LP: #327230).

 -- Kees Cook <email address hidden> Tue, 10 Feb 2009 11:27:11 -0800

Changed in usplash:
status: Confirmed → Fix Released
Revision history for this message
Christopher (soft-kristal) wrote :

This afternoon's (UTC -5) update of usplash fixed my display.

Revision history for this message
nyarnon (cabal) wrote :

Yes mine too, Thanx Kees.

Revision history for this message
Yannick Defais (sevmek) wrote :

MSI Wind fixed too.

Revision history for this message
res1b3uq (res1b3uq) wrote :

Hokay, everthing seems to be working again. Thank You.

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.