Skip to Content.
Sympa Menu

baslinux - Re: [BL] Can't compile 486 kernel

baslinux AT lists.ibiblio.org

Subject: Baslinux mailing list

List archive

Chronological Thread  
  • From: sindi keesan <keesan AT sdf.lonestar.org>
  • To: baslinux AT lists.ibiblio.org
  • Subject: Re: [BL] Can't compile 486 kernel
  • Date: Mon, 16 May 2005 13:30:04 +0000 (UTC)

The floppy disk which scandisk said was damaged could be reformatted and is 100% good.

I just attempted to use the parport zip drive boot disk with the kernel that I compiled for 486DX on an older 486 laptop (which is probably sx not dx) and it said process halted 'ran out of input data'. I will try with 386 kernel (fpu support).

(And external keyboard - I keep forgetting the internal one is dead).

The 386 kernel worked better, insmod imm worked, busybox is slowly .... loading from zip disk. Press Enter to activate this console.

The Compaq Elite 486DX laptop also worked booting the parport zip drive with the 386 kernel, though it did not work with my or Steven's 486 DX kernel. It gave a different error message than the 486SX when I tried to boot with 486DX kernel, because it is a DX. The problem appears to be in the 486 kernel as it interacts with a 486 (since it does work on a pentium). I could try compiling for 486SX but the 386 kernel works.

I don't know if the POSIX problem is specific to my Compaq Elite. I might test it on a desktop 486DX some day.

So for a foolproof (I hope) floppy boot disk for parport zip drive, I will post a variant for 386 that works on a 486 where the 486 kernel did not work.

Unrelated info: The compact flash PCMCIA adaptor is hdc1 even though this laptop has no hdb (like sda4 for zip disk even though no sda1-3).
I will also post my config file that supports this adaptor, with function 4 and ide_cs module (also needed in /etc/pcmcia/start).

On Mon, 16 May 2005, sindi keesan wrote:

I suppose I could try the BL1 kernel but it may not support parport zip drives.

I substituted the bare.i kernel from SW4.0 and of course it did not work because the modules were wrong, not only that, it completely messed up the floppy disk. Scandisk found hundreds of things wrong after e2fsck fixed things and I just deleted a bunch of .chk files but I also seem to have damaged a large area in the middle of the disk - how did this happen?

Since the floppy drive I am scandisking on is the worn-out one in the 486 laptop this may be an artifact. How does one format for DOS in linux?

I did a Ctrl-Alt-Del when the boot process crashed - would this have damaged the disk?

I just downloaded the blimmz.gz file and gunzipped and wrote to disk and replaced the pentium kernel with my 486 kernel again, on a known good floppy disk.
_______________________________________________
BasLinux mailing list
BasLinux AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/baslinux


keesan AT sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org




Archive powered by MHonArc 2.6.24.

Top of Page