http://bugzilla.novell.com/show_bug.cgi?id=593568 http://bugzilla.novell.com/show_bug.cgi?id=593568#c0 Summary: i686 GNOME LiveCD w/Fresh HDD stops after Wallpaper Displayed Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Live Medium AssignedTo: coolo@novell.com ReportedBy: jimomura@pathcom.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2 (.NET CLR 3.5.30729) I have recently bought an HP Compaq dc5850 SFF running an AMD Athlon dual-core 5800B processor (same as 5800+ but more heavily tested). It came with a 160GB HDD which I decided to replace immediately with a Seagate Barricuda 250 GB drive (ST3250318AS). Using this completely fresh HDD, I tried to start up the 32-bit GNOME LiveCD. It got to the Wallpaper and then just hung there. I think the mouse was working, but I am not certain now. I waited a very long time and then unplugged the computer (there is no reset button) and tried again. After that I gave up. After installing 32-bit XP Pro, I had no problem with the GNOME LiveCD. It only happened on a completely fresh HDD. Reproducible: Always Steps to Reproduce: 1. Start computer 2. Put LiveCD in the drive 3. Reboot Actual Results: Stopped with Wallpaper showing but no objects being drawn on the screen to click on. Expected Results: I expected it to continue to boot and put icons and such on the screen. Sadly, I will not be able to help further than this posting. I cannot wipe the drive and start over again because it is a "work" computer. My best guess is that it is somewhere in the HAL hardware search. It might be that it is trying to read a disc label (which would be MSDOS for most situations) or a partition table, neither of which would exist at that point. Or something like that. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.