On Monday 09 January 2006 4:17 pm, Martin Soltau wrote:
Hi all,
I am new to this mailing-list so please be patient ;-) OK, I have a boot-problem with SUSE 10 on my computer:
The Hardware: Dell Dimension 5000, Bios-Version A07 P4@3.0 GHz, 3GB RAM, Onboard LAN, ATI X300, Creative Soundblaster Live 24bit 2* Seagate (80 GB + 300 GB)
The issue: I was able to install SUSE 10 from DVD (I bought the package). Even with that installation (Online Updates installed, no Packman or other additional software) the system hangs during boot every 5th-6th time. it hangs while the KDE-Login screen is showing, or alternatively JUST before it is about th show (when you see the KDE-Clock) or just immediately after login, while KDE is starting up and loading the user-session.
I searched the web and found hints about ACPI-Problems. So I added the boot-option ACPI=OFF. <snip> So I ended up having the following additional boot parameters (besides the SUSE 10 standard ones): ACPI=off, APM=power-off, NOAPIC, NOLAPIC.
I believe the kernel boot command line parameters should all be lower case, no CAPS. I've always used lower case. acpi-off apm=off noapic nolapic
Result: It still hangs on every 5th-6th boot. That may be an immediate reboot, or one with cold motherboard... just no rules to see. WinXP works fine, SUSE 9.3 did so as well.
IF (big if there) I'm right about case sensitivity that would explain the no change in symptoms. Since it seems to be happening in a GUI intense environment I'd double check your video card driver setup. <snip>
So: Does anybody have an idea about where to look at? Which logfile would be interesting? SUSE asked for /var/log/boot.msg but has not responded and that's 5 weeks in the past. I#m not sure, which version of the log is the one to look for, because when I reboot there is a new file written, isn't ist? And the old one (where the system hangs) is gone or reorganised?
/var/log/messages is cumulative. dmesg and any logs in the /var/log directory. You could also flip to Ctrl+Alt+F10 to monitor some system messages as the GUI is coming up. You won't see what it is freezing on but you may see a pattern that indicates what the last thing it reported was before the lock-up and then we may be able to help determining what the next step should be in the GUI start up... Looking for clues.
Kind regards, Martin Soltau
Stan