Svante Signell wrote:
>Thank you for your advices. The problem was not the CPU
>fan/temperature or IRQ conflicts, it was a RAM memory failure. Solved
>by append="mem=128M" in lilo.conf, disabling the last 64Megs of
>memory. No problems after that, with either kernel. Two follow-up
>questions, though:
>
>1. Using the append feature in lilo.conf, which part of memory is
>shut off, upper or lower part?
>
>2. Is there any tool for checking RAM memory available? The BIOS does
>not seem to support memory checking. I've heard of some DOS utility ;-(
>but what about a linux tool?
>
Yes, there are.
Search in freshmeat.net, I don't remember the name.
The other option is to buy a new 128MB PC100 DIMM. Here they are
really cheap, like 13$ per 128MB PC133.
Cheers
Oliver
>
>Gary Sandine writes:
> > On Sat, Nov 10, 2001 at 07:07:57PM -0300, Oliver Schulze L. wrote:
> > > How about hardware issues?
> > > Did you check your CPU fan/temperature with lm_sensors?
> > >
> > > When Linux freezes, usually is a hardware problem.
> >
> > I have also seen freezing when devices are sharing IRQs, while their drivers
> > can't deal with this; or freezing related to PCI card driver problems. It
> > might be useful to have a look at /proc/pci, or lspci -vv, and do your best
> > to eliminate IRQ sharing. Some BIOS allows the user to assign IRQs to PCI
> > slots; with others, the way to change IRQs is to physically move the cards,
> > and then choose "Reset Configuration Data" or "Update ESCD" in BIOS.
> >
> > Regards,
> > Gary S.
>
>
>
>_______________________________________________
>Redhat-devel-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/redhat-devel-list
>
--
Oliver Schulze L.
[EMAIL PROTECTED]
Asuncion-Paraguay
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
