Am Freitag, 27. Januar 2006 01:47 schrieb Carl Hartung:
Hi Martin,
Hi Carl,
At this point, I think it's reasonable to conclude that the PSU {insert an underlying cause here} is unable to cope with the greatly accelerated boot process in SUSE 10.0.
Well, currently I'm a little reluctant to change the PSU or look into hardware and I would like to know your thoughts about my theory:
It could be getting tired from age...
The machine is only 10 months old so I tend to exclude "tired from age" for now.
or newly added hardware is demanding too much at cold boot...
There has been no additional hardware since the Suse 9.3 times...
In particular, optical drives (DVD/CD) are notoriously high power consumers after cold boots. When old and marginal, they can even pull enough extra current during extended initializations to 'starve' surrounding circuitry during POSTs.
Well, that may be, BUT: - The problem occured during "restarts" (no cold boot) as well. - The CD/DVD-Drives are as well 10 months "young" (as the rest of the box) - IF circuits are starved during POST, then there should (to my understanding) be NO difference regarding their behaviour, no matter which Runlevel I boot to. Even with booting to Lv 3 and then switching to 5 the hardware should then be out of normal operating and cause a hang on KDE startup. Shouldn't it? I mean: POST is WAY before and whatever would go wrong there should remain so, regardless of the initial runlevel...
3: Pull the high end graphics card, boot to run level 3 and, as root, run SaX2 to configure the on-board graphics. Test booting directly to run level 5. If the problem goes away, reinstall your graphics card and **upgrade the PSU.**
ATI x300 is a passively cooled low level entry card that should be one of the easiest to handle for the PSU - I think. So I still think it is a race condition between KDE and the not comlpletely startet modules like ALSA, ACPI, HAL daemon, keymap or something like these. Therefor I am still looking for a way to serialize the process of loading modules making sure, that even with default runlevel 5 KDE only starts, when everything else has finished. Do you have an idea about how to schieve this? Regards, Martin