Very Computer

I've decided to take an old 486 and move it from Windoze 3.11 over to
RH7.1 or RH7.2 . I swapped out the RTL8009 based NIC for a D-Link
DE-220P and ran the DOS program to set its I/O address and IRQ.

This machine has a CD-ROM, but the RH7.1 boot floppy does not find it.
It's a Mitsumi plugged into a sound card. Perhaps someone can direct
me on getting THAT to work.

I then tried an FTP install using the boot-net floppy. That works up
to the point where it askes what kind of NIC you have, and lists a few
possibilities, but not the one I have. Googling around, I found that
this NIC uses the NE2000 driver, which, I believe is ne.o . I
downloaded it from another machine running RH7.1 (from
/lib/modules/2.4.2-2/kernel/drivers/net/ne.o) and stuck it on a DOS
floppy (and that may be where my problem is). The boot-net program
says "The floppy disk you inserted is not a valid driver disk for this
release of Red Hat Linux." I imagine the problem might be that I
copied it to the floppy on a dos machine. If that's so, is there an
image I can use rawrite to make this disk with? If that's not the
problem... what am I doing wrong?

Eventually, it'd be nice to also have the CD running, but at this
point, I consider the NIC more important.

THANKS!

Harold

Answering my own questions...

I found the NIC driver image on my RH 7.2 disk#1 in images, so I was
able to create the driver disk and get my D-Link DE-220P working.

I also tried the oldcdrom image, but none of those would talk to the
Mitsumi CD plugged into the sound card in this OLD 486 machine. So,
I'm doing an FTP install, which takes a while, but it works.

Harold

If the machine in question is about the approximate age I think it is,
dump the CD drive. I had experiences with several Mitsumi CD drives
during that period and every one of them was a piece of shit. Can't say
anything about more recent Mitsumi models, though, as I avoided that
brand like the plague since then.

Pete

Just for future reference and for the reference of others:

Installable kernel modules have to be compiled for the particular
kernel that is to use them.

So, you need to get your modules from your own system or from the
install disk that came with the system or from an RPM package
explicitly recited as being for your kernel.

If the module is not available from these sources, then download the
source code tarball and compile using the compiler on the system that
will use the module.