On Fri, 2003-09-19 at 20:44, Jason Stubbs wrote: > > > > It hanged here for more than 45 minutes compelling me to switch off the > > PC. From 'Running "make dep"' to 'Running "make bzImage"' and then to > > 'Running "make modules"' it was very slow. Each took at least 30 > > minutes or even more. > > Depending on your machine, this sounds completely normal. "make modules" will > be the longest process as most drivers are built as modules with genkernel. > If there is _any_ hard disk activity at all, just wait until it completes. My > favourite test to see if a machine has locked up is to see if Num Lock still > works. If it does, in most cases you just need to wait until the computer's > finished whatever it's doing. > Jason's correct. This could be normal.
<Alt><Ctrl><F2> to a second console, log in, and then use 'top' or something to see what the machine is doing. If the above key sequence isn't working, then you may have a problem, but always try to get control of the machine somehow before power cycling. - Mark -- [EMAIL PROTECTED] mailing list
