Re: Why the heck does 'tar -xvzf linux-2.0.{30,27,29}.tar.gz' lock up my 486??

Jeff Wiegley (jeff@w3-design.com)
Wed, 27 Aug 1997 21:49:18 -0700

Alan Cox wrote:
>
> > but even if I compile a 2.0.30+pre-patch-7 or even a 2.0.29 or 2.0.27
> > kernel on another machine and then use that kernel on the 486DX-100
> > machine
> >
> > tar -xvzf linux-2.0.30.tar.gz
> >
> > still locks the whole machine up solid.
>
> Sounds like the hardware. A solid lock sounds more like an interrupt
> controller or IDE problem than anything else, but you might want to try
> heavy I/O low CPU tasks (dd if=/dev/hda of=/dev/zero), and high CPU/memory
> low disk usage stuff and see what dies
>
> > PC/104 company tomorrow to see if linux will run on there hardware but
> > it'll be a waste of my time if linux just locks up again. (And it will
> > look bad for linux :-(
>
> Perhaps you should go meet a different PC/104 manufacturer.

Thanks Alan, I will try the heavy I/O stuff.

I have met with several different PC/104 vendors. In general my
perception
is:

PC/104 "standard": isn't, everybody stuff differs and everybody's stuff
has
weird quirky things that make it not 100% PC compatible.

PC/104 is second rate when compared to notebook hardware and other
well established hardware industries.

I can't get PCMCIA running on any PC/104 platform and if these damn
things
are supposed to be so damn compatible this should be a no-brainer for me
since I've got it working on dozens of different platforms and laptops.

Oh, well thanks for the IDE I/O idea, it always seems to happen right
during a heavy disk burp if memory suits me.

- Jeff

-- 

J E F F  W I E G L E Y

W 3 - d e s i g n,  I n c.

 phone: (310) 815-1177 x 307 fax:(310) 815-1133