> Yes. After an evening of kernel compiling (not on the 386!), I have
> narrowed down the point at which my MCA machine stopped working. My
> computer has no weird drivers. The only thing of note about this computer
> is that it's MCA, has ESDI, and has 6 MB of RAM.
>
> 2.1.57 Works
> 2.1.62 Works
> 2.1.69 Works
> 2.1.74 Works
> 2.1.75 Kernel doesn't compile (line 614 in arch/i386/kernel/ptrace.c)
> 2.1.76 Kernel doesn't compile (same problem as above, hard_math undeclared)
> 2.1.77 Kernel panic: No init found.
> 2.1.78 Kernel panic: No init found.
I can offer a me-too but the machine is different.
I am using an old 80386 to test new kernels on. It is an ancient GW2K
with 16 megabyte of RAM and an old UltraStor drive which was from the
pre-IDE days. Here is how hdparm describes what it finds:
Model=UltraStor Ultra-12, FwRev=0.08, SerialNo=
Config={ HardSect NotMFM Fixed DTR>5Mbs TrkOff }
RawCHS=1224/15/34, TrkSize=20880, SectSize=614, ECCbytes=7
BuffType=2(DualPort), BuffSize=32kB, MaxMultSect=8, MultSect=off
DblWordIO=no, maxPIO=0(slow), DMA=no
CurCHS=0/0/0, CurSects=0, LBA=no
IORDY=no, tPIO={min:0,w/IORDY:0}, PIO modes:
I compiled 2.1.78 with the newest 2.7.2.3 of gcc and the latest
binutils. The boot sequence proceeds normally, mounts the ext2 root
filesystem and than complains that it cannot find init.
The 2.0.33 kernel boots and runs flawlesslly. I used it to compile
the 2.1.78 kernel on the said machine.
I will back off to 2.1.74 and see if I can locate a failure point.
> Gilbert Ramirez Jr. gram@merece.uthscsa.edu
Greg
}-- End of excerpt from Gilbert Ramirez Jr.
As always,
Dr. G.W. Wettstein Enjellic Systems Development - Specialists in
4206 N. 19th Ave. intranet based enterprise information solutions.
Fargo, ND 58102 WWW: http://www.enjellic.com
Phone: 701-281-1686 EMAIL: greg@wind.enjellic.com
------------------------------------------------------------------------------
"Linux is a movement, a philosophy, where programmers and technical
people take control of their own destiny."
-- Tim Bass