Corrupt display and machine hang when booting Lucid Beta ISO in Dell Inspiron 6400

Bug #539579 reported by Colin Ian King on 2010-03-16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)

Bug Description

ISO testing, AMD64 test: ISO image


After ISOLINUX has booted, I get a Ubuntu logo and a keyboard icon at bottom of the screen. I wait and then the system starts to boot. After ~25 seconds or so, the screen display changes and then I get a corrupt image and the machine gets hung. The image is attached.

However, if switch consoles to VT1 and then back after I see the Ubuntu logo and keyboard icon before the screen changes, I skip over this hang. This looks like a possible virtual terminal / X race condition bug.

Hardware: Dell Inspirion 6400, Video: ATI Technologies Inc M52 [Mobility Radeon X1300]

Colin Ian King (colin-king) wrote :
Colin Ian King (colin-king) wrote :

Also booting from the ISO and pressing ENTER and selecting "Install Ubuntu" from the ISOLINUX boot menu works around this hang.

summary: - Corrupt display when booting Lucid Beta ISO
+ Corrupt display and machine hang when booting Lucid Beta ISO in Dell
+ Inspiron 6400
Colin Ian King (colin-king) wrote :

Still occurs on today's Lucid ISO when ISO testing:

Steve Langasek (vorlon) wrote :

Hi Colin,

Does pressing Alt+SysRq+K have any effect when this corruption occurs?

Do you have Lucid installed on the HD of this system, by chance? If so, is the problem reproducible there?

If you drop 'splash' from the kernel commandline, what happens?

affects: ubuntu → plymouth (Ubuntu)
Changed in plymouth (Ubuntu):
status: New → Incomplete

I've similar problems when i reboot lucid beta from my regular hd-installation - see attached pic.

Like Christian I also get a black screen with red artifacts when rebooting my regular hd-installation. (Dell Inspiron 6400, Lucid Lynx 10.04 AMD64)

My graphics adapter is an ATI Mobility Radeon X1400. Adding radeon.modeset=0 to the GRUB command line seemed to avoid this problem.
See also

I can't remember where, but I read that this option is a workaround needed until Kernel version 2.6.34.

Launchpad Janitor (janitor) wrote :

[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.]

Changed in plymouth (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers