Bug 114904 - Installation hangs when loading YAST on Dell D610 laptop
Summary: Installation hangs when loading YAST on Dell D610 laptop
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 4
Hardware: x86 SUSE Other
: P5 - None : Major
Target Milestone: ---
Assignee: Hubert Mantel
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-02 05:49 UTC by dante bly
Modified: 2005-10-04 08:20 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dante bly 2005-09-02 05:49:22 UTC 
After booting to first CD in beta 4, the linux kernel is loaded and the
installation continues until the line "starting yast" is reached. At this point
the system hangs with a blinking cursor. This same bug occurs with standard
installation, acpi disabled, and safe setting modes of installation. This bug
did not occur in beta 3.

A few of the messages previous to starting yast are listed below:

Idconfig: /usr/lib/libk5crypto.so.3.0 is not an ELF file - it has the wrong
magic bytes at the start.

Idconfig: /usr/lib/libk5crypto.so.3 is not an ELF file - it has the wrong magic
bytes at the start.

Idconfig: File /usr/lib/libgssapi_krb5.so.2.2 is empty, not checked.

Idconfig: File /usr/lib/libgssapi_krb5.so.2 is empty, not checked.

starting syslogd (logging to /dev/tty4)... ok

starting klogd... ok

starting yast ...
Comment 1 Steffen Winterfeldt 2005-09-02 09:12:28 UTC 
the messages are unrelated. yast does not use kerberos libs.
Comment 2 Hubert Mantel 2005-09-02 11:59:16 UTC 
Can you provide a little bit more information? Any messages on console 3 or 4?
Comment 3 Michael Gross 2005-09-06 08:50:22 UTC 
This looks like a broken image (which resultet in at least one corrupted file).
Run the md5sum(1) command on your image and compare it with the md5sums listet
in the file MD5SUMS on the download-mirror. If they differ, download the image
again and retry it.

Until proven otherwhise, I reduce the status of this bug to `major'.
Comment 4 Hubert Mantel 2005-10-04 08:20:49 UTC 
No news, assuming INVALID now.