On Tuesday 09 September 2003 11:25 pm, Jack Coates wrote:
> On Tue, 2003-09-09 at 16:23, Glenn Johnson wrote:
> > Hi folks. Question about MDK 9.1. I've been running 9.1 since it came
> > out, with few major problems. However, when I've booted my computer the
> > last 2 nights it makes it's way to the graphical login screen with no
> > noticeable problems, but the mouse won't move and the caps lock and
> > scroll lock lights are flashing as I'm prompted to log in. The numlock
> > light is not flashing nor is it lit at this time. Oh yeah, keyboard
> > doesn't work either.
>
> that's a kernel panic. If you had access to a console, it would be
> saying "AIIEE!!! killed interrupt handler at " and a whole bunch of
> illegible stuff.
>
> > Now, since I'm
> > the consumate Linux genius I hit the reset button to reboot (can't get to
> > another terminal). System wants to run fsck, you know, "press Y in 5
> > seconds". So I press Y and after a few minutes I'm left at a term window
> > because system says "can't fix file system". No graphics or X.
>
> if you have ext3 or one of the other journalling filesystems, you do not
> need to say Y here.
I do have ext3.
>
> > I wonder what
> > I should have done. I ran drakxconf and checked the display config.
> > Everything seems ok, so get out of there and reboot again. This time all
> > is well and I make it to KDE. No prob for the rest of the night. Tonight
> > the same thing, i.e., mouse frozen, lights flashing, no keyboard, hit
> > reset. Computer reboots, sez to hit "Y" again to run fsck, but I pass on
> > the offer. Again all is well and here I am in KDE land.
> >
> > Any ideas what causes this behavior guys and gals? The computer's
> > behavior, not mine. :)
>
> well, something is causing the kernel to panic, and that's usually a
> sign of flaky hardware. The first time you boot, are you a) rebooting
> from Windows or b) cold-booting from power-off? If so, flaky hardware
> goes way high on the list of possibilities.
>
> less /var/log/messages and look for the stuff that you see when it
> reboots, then scroll up from there and you'll see if there was anything
> troublesome logged. Usually bad hardware just pulls the rug out before
> Linux can write anything to the log, but sometimes you get lucky and
> there'll be warning messages there.
Thought occured to me this morning re hardware. I've been having a lot of
trouble with the cd burner lately. That's secondary master. Put it into
another computer and it worked perfectly. Also bought a new hard drive
because I was SURE that I lost the 20 gig to failure. That was/is primary
slave. Here's one message I'm seeing very often in /var/log/messages:
DriveReady SeekComplete Error. That's for /dev/hdd which is my cdrom.
And another: SCSI Error: host 0 id 0 lun 0 return code = 8000002
Sense class 7, sense error 0, extended sense 0
That's in there many many times.
And another: I/O error: dev 0b:00; sector xxxxxx
More: "unknown group video" and "caught SIGHUP" and "defaulting to GID=0".
The list goes on..... This is a huge /var/log messages. Some 20,000 lines.
--
Glenn Johnson
[EMAIL PROTECTED]
Powered by Mandrake Linux v9.1
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
