https://bugzilla.novell.com/show_bug.cgi?id=719034 https://bugzilla.novell.com/show_bug.cgi?id=719034#c0 Summary: first boot of install, black screen, hung, AFAIK, NOT infinite loop issue, empty /var/log/messages, klogd missing but nodeps, HDIO_GET_IDENTITY failed Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 5 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: Pemberton.John.M@gmail.com QAContact: jsrain@suse.com Found By: --- Blocker: --- Created an attachment (id=451801) --> (http://bugzilla.novell.com/attachment.cgi?id=451801) bzip2'd contents recursive tar of /var/log and hwinfo.txt file, output of hwinfo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 Downloaded the ISO described by the following output, at the illustrated time. # file /mnt2/toes/openSUSE-DVD-Build0250-x86_64.iso/openSUSE-DVD-Build0250-x86_64.iso /mnt2/toes/openSUSE-DVD-Build0250-x86_64.iso/openSUSE-DVD-Build0250-x86_64.iso: # ISO 9660 CD-ROM filesystem data 'openSUSE-DVD-x86_640250 ' (bootable) # ll /mnt2/toes/openSUSE-DVD-Build0250-x86_64.iso/openSUSE-DVD-Build0250-x86_64.iso -rw-r--r-- 1 1000 users 4534042624 Sep 17 02:50 /mnt2/toes/openSUSE-DVD-Build0250-x86_64.iso/openSUSE-DVD-Build0250-x86_64.iso MD5 sum matched, burned DVD, verified burn. Went through first "phase" of install, selected KDE. Install procedure tried to reboot the system; attempt hung with underscore in upper left corner of black screen. KBD shortcuts to restart X server, or reboot machine, would not work. Cold rebooted from install DVD; forced update, hoping during the process, the install might complete. Install procedure tried to install 1 RPM. This time reboot got to lizard in middle of green "corduroy" background, hung about midway through progress bar. Tried same thing again hoping things might get further, but similar result, install still ried to install 1 RPM. I can boot the system in fail safe mode which appears to fallback to he nouveau driver. In boot.msg I see: HDIO_GET_IDENTITY failed for '/dev/sdd' which is the root drive, even though the corresponding drive is specified by-id in GRUB's menu.lst, and somehow facilities during boot time can fsck the drive successfully using the designation /dev/sdd as base name for drive partitions, rather by-id. /var/log/messages is empty, in boot.msg there are messages such as: /sbin/klogd is not installed some of the start up scripts appear to be trying to run klogd, yet both yast and the rpm command, seem to indicate that nothing depends on the klogd package. The klogd package is not installed. How can there be scripts installed, trying to run klogd, but those things do not show dependencies on klogd? If a script tries to run klogd, doesn't that script depend on klogd? Is this something that got lost in the weeds on the way to systemd? Unless there's something worth investigating, some reason to leave the system in its current condition, I'll probably install klogd manually and see where that gets me. Especially since there were some repeated messages that looked like complaints. They flew by so fast I couldn't quite catch them. With the broken logging situation, it seems they weren't caught in a file. AFAIC, debugging should be done in the simplest context possible, to minimize the number of variables that can affect things. I almost care how sophisticate technology gets, I want a gosh RS232 port so I can use have a serial console in a simple way. But Hewlett Packard, in their "infinite wisdom" :-O decided this machine should have no RS232 serial port, so no serial console. Unless the serial console mechanism has evolved enough so someone can show me how to directed it to a virtual RS232 port over USB, using one of those modules, something over USB, or some kludge, I may be stuck with log files, unless I can catch the messages with a video camera as they fly by. Reproducible: Always Steps to Reproduce: 1. Do the install as I've suggested above, on identical hardware. 2. After the first attempt at causing install to go further, by forcing update rather than new install, every time it boots in standard, non- failsafe mode, it seems to behave as described, every time. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.