On Thursday 03 August 2006 19:16, Jerry Feldman wrote:
On Thursday 03 August 2006 12:46 pm, Paul Neuwirth wrote:
I can boot all runlevels, but theres no X installed. Maybe "hangup" is the wrong word (English is not my mother language). The system stands completely still, the text-curser doesn't blink anymore, even num-lock isn't working. Some actions in YaST cause that, i even could not install with graphics mode, the install of 10.1 failed every time (i think because of the zen-daemon).
Ok. When you boot into single user mode (run level 1 or s), can you log in as root? Or does your system freeze up once the boot ins complete. Single user mode only has your root file system mounted, and no daemons. At this point, only the kernel, kernel daemons, init(8) and bash should be running. You should have a login prompt. It is very important to know if your system is locked up in single-user mode or not.
If you are locked out in single user mode, then the problem could be with your keyboard. I've seen this happen with USB keyboards being locked out after switching from a PS/2 keyboard to a USB.
What I am trying to do here is to go back to the most basic setting. We can assume that your memory is ok.
If you can work in run level 1, then lets try to run fsck: make sure your root file system is mounted read-only. I've seen the mount command lie, so just test by creating a garbage file: touch foo If you get a permission denied, then root is mounted read-only. If this succeeds and foo is created, then force a read-only mount: mount / -o ro,remount
Then run 'fsck -sA" This will run fsck through all your file systems serially.
Once this succeeds, then go to run level 2 manually. Keep an close watch on kernel messages. Let's see what happens in run level 2.
-- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
it's wired... the problem doesn't seem to be existent anymore... but i think to know what the problem is/was. When the problem occured, the room temperatures were very high (about 40°C and some more), in recent i already had problems at high temperatures with the mainboard's chipset (for example POST errors, BIOS data deleted, BIOS not loading or even such system freezes), the chipset is not actively cooled... now at about 22°C room temperature the system works fine... i would never buy an elitegroup motherboard again... thanks for all the help