Stephen Varga <blacklab@darkambient.org> writes:

Andreas wrote:

...

So, it always hangs when cpufreq is started? Then you have either a broken BIOS or hardware :-(.

...

Please remove cpufreq, e.g.: Use the rescue option and remove /etc/init.d/cpufreqd (hope that's the right path) and try again.

Yes, to follow up my previous post: I have reinstalled Suse 9 pro (AMD64) and was able to remove "cpufreqd" from the /etc/init.d/ directory. This definitely solved the problem. Suse boots up normally. I also noticed that this process was skipped during the initial installation startup procedures. So yes "cpufreqd" was causing the problem. Everything seems nice here, and I actually have the opportunity to relax and admire your beautiful gnome desktop. Very well done. Hmm the "cpufreqd" problem you say, is associated with a messed up motherboard / bios? What exactly does this service do? I do know that I have a 350 watt power supply inside my case, which should be enough to power the Athlon 64 (it's not an FX). Anyways I am glad this is cleared up. Any feedback about why this possibly went wrong would be appreciated. I don't know it could just be a problem with cpufreqd. But I am really a non technical user. Thanks to all and Andreas.

The modern AMD CPUs have frequency scaling. You can use a low frequency in idle time to use less power and therefore make less noise (less power-> less temperature -> less fan usage). The cpufreqd looks at your system load and gives you highest frequency (and therefore a fast cpu) when you need it - and otherwise saves energy... Glad to hear that your problem is solved. Let's discuss off-list the real problem... Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126