Boot failure with video corruption

Bug #95370 reported by Kissake
2
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I can't find a boot option that will cause Feisty Fawn beta to boot.

Symptoms (regardless of booting normal, graphical safe mode, video resolution set to minimum)

As soon as I hit enter, the small window with progress bar comes up. While initially the progress bar progresses with blue squares, at the same time there is video corruption (extra pixels changing, immediately under and around the progress bar)

After the progress bar fills, there is additional delay, with additional corruption. Note that the initial boot screen / menu is still visible in the background.

Then the screen clears. There is a short change, and the sound my monitor makes when it changes video modes. There may be a very brief flash of text, followed by nothing. After a short pause, the caps lock and scroll lock lights on the keyboard begin flashing in unison.

This could be a problem in the boot loader (I have no idea what you use for a boot loader) or _very_ early in the kernel boot process.

Potentially pertinent details:
 MB: Asus SK8V
 CPU: Opteron 148
 Memory: 1GB
 Video: ATI x800, 256M video RAM

I have five HD's installed, 3SATA(2 mirrored RAID, 1 standalone), 2PATA (master/slave), and two optical drives. USB mouse, PS2 keyboard. I can't think of anything else potentially relevant, so I'll leave it at that.

Note that this behavior or similar also exists for Ubuntu 6.10 and 6.06. I have not been able to get Ubuntu on this machine at all. Prior versions of Ubuntu would get to the second progress bar before failing.

Revision history for this message
Kissake (kissake) wrote :

I was able to boot with the following kernel commandline (two of the options, fb= and BOOT_DEBUG= I got from one or the other of the older installers):

BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.gz quiet splash fb=false BOOT_DEBUG=3 -- vga=0x376

I also chose the 1600x1200x32 video mode. This still caused graphic corruption on the boot screen (loading kernel progress bar), but only minor corruption on the ubuntu logo progress/activity bar that appears immediately afterwards (The bar leaves a smidgeon of itself on the left side when it first bounces off of it.)

Revision history for this message
Nanley Chery (nanoman) wrote :

Does this still happen in 7.04 final? It's good to follow up on reports...

Changed in casper:
status: New → Incomplete
Revision history for this message
Robert Hrovat (robi-hipnos) wrote :

I have some video corruption issue if I don't select anything when starting Live CD and just press enter with first option. It happened in Feisty and now in Gutsy Tribe 5. Attached is a video file to show you how it goes because I don't know how to explain it :-)
Whole video was 2,5 minutes long, so I cut out delays or blank screens.

I have nVidia GeForce 6200 PCI Express video card and AMD Athlon 64 CPU. Live CD was 32-bit version so I can't confirm it for 64-bit.

Revision history for this message
Nanley Chery (nanoman) wrote :

I can't see your video in its current format (I may have to look at it when I get on a XP machine). Do you still have this problem in the final Gutsy release?

Changed in casper:
assignee: nobody → nanoman
Revision history for this message
Tormod Volden (tormodvolden) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Nanley Chery (nanoman)
Changed in casper (Ubuntu):
assignee: Nanley Chery (nanoman) → nobody
Revision history for this message
rusivi2 (rusivi2-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 casper (Ubuntu):
status: Incomplete → Invalid
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.