[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: fried(?) computer hangs on boot



Vikki Roemer wrote:

Pigeon wrote:

I wouldn't be surprised if time was involved: that if you deliberately
put some delay in early on in the boot process, it wouldn't get so far
before it hung.

Prolly. But I noticed that merely deleting symlinks (not the smartest thing in the world, but I figured it couldn't hurt at this point) didn't make a significant amount of difference; I'm not sure that doing that made much difference in the boot time, though, either. So that's why I'm not *entirely* sure that the hanging is time-dependent, but I've a hunch it is.

So boot into single-user mode, or start Linux from the lilo prompt with something like:
   boot: linux single init=/bin/bash
or
   boot: linux -b
(see man init)
to start a minimalist system (-b = "emergency"), and see if the machine lasts for any length of time.


Tried booting from tomsrtbt, and it runs like a charm.


Then the hardware is probaby okay, and you've just got some file corruption or something similar. The "linux -b" option at the lilo prompt should allow you to then start running the startup scripts manually to find out which ones are causing you grief.

--
Kent West (westk@acu.edu)





Reply to: