Re: Re: [Nolug] Kernel panic - Correction

It turned out to be a memory problem. I had already eliminated one module because there were three beeps during boot. Found another one wasn't working or giving a signal, and a third one had only 32Mb usable - v - e - r - y s - l - o - w! Got a new one at Best Buy for $23 after rebate (mail-in).

============================================================
From: <jdtiede@bellsouth.net>
Date: 2003/08/05 Tue AM 01:14:56 EDT
To: <nolug@joeykelly.net>
Subject: Re: Re: [Nolug] Kernel panic - Correction

Correction--the AD11, etc., is the box I reloaded but lost /home. The one that won't boot now but did earlier but wasn't running right is a Gigabyte GA-7ZXE with Athlon 1600+ and 2x250 PC-133, GeForce 2 MX and an old CTX monitor, Dlink 530TX.
============================================================
From: <jdtiede@bellsouth.net>
Date: 2003/08/05 Tue AM 12:56:43 EDT
To: <nolug@joeykelly.net>
Subject: Re: Re: [Nolug] Kernel panic

It worked before this reload of RH8.
============================================================
From: "Andrew S. Johnson" <andy@asjohnson.com>
Date: 2003/08/05 Tue AM 12:11:15 EDT
To: nolug@joeykelly.net
Subject: Re: [Nolug] Kernel panic

On Monday 04 August 2003 09:32 pm, jdtiede@bellsouth.net wrote:
> FIC AD11 mobo, Athlon 1600+, 2x256Mb PC2100 RAM, Sony Multiscan420GS, VGA card (can't remember name, but isn't AGP)

According to ftp://ftp.fic.com.tw/motherboard/cpu_table/socketa/AD11.pdf,
the Athlon 1600+ isn't supported on certain MB revs and BIOS versions.
Are you sure this CPU is supported on your board?

Andy

> ============================================================
> From: "Andrew S. Johnson" <andy@asjohnson.com>
> Date: 2003/08/04 Mon PM 10:27:57 EDT
> To: nolug@joeykelly.net
> Subject: Re: [Nolug] Kernel panic
>
> On Monday 04 August 2003 08:10 pm, jdtiede@bellsouth.net wrote:
> > I got a new CPU (Athlon) for my "spare" system. I could boot it but not do anything beyond that, so I reloaded RH8. Now I get the following during boot:
> > Code: 39 66 28 89 de 75 f1 86 44 24 20 39 83 94 00 00 00 75 25 86
> > <0> Kernel panic: [can't read my writing] to kill the idle task
> > In idle task - not syncing
> >
> > Does anyone know what this means and how to fix it?
> >
>
> How about some hardware particulars?
>
> Andy
>

___________________
Nolug mailing list
nolug@nolug.org
============================================================

___________________
Nolug mailing list
nolug@nolug.org
============================================================

___________________
Nolug mailing list
nolug@nolug.org
============================================================

___________________
Nolug mailing list
nolug@nolug.org
Received on 08/05/03