Ok, thanks. However, my problem is that they didn't include either one on the
livecd iso image so I can't connect to the internet to download my stage 1 tar
file and start the compile process. I tried to compile a driver to use on a
separate system using the 2.4.19 source tree. However, it didn't work (and I
tried both drivers). Probably due to the fact that it's an xfs-r1 modified
kernel and I have no idea what kinds of patches they have applied to the running
kernel on the iso image. The only way I got the compiled drivers to even attempt
to load was to edit the version.h file and make it say '2.4.19-xfs-rc1'. Even
after I did this, I get the 'init_module: No such device' error from insmod. So
my problem is I need _compiled_ drivers for the 2.4.19-xfs-r1 kernel that is on
the livecd-ut2003-i586-1.4.1.iso image for my Intel Pro/100 S NIC... any ideas?

> -----Original Message-----
> From: Duane Attaway [mailto:dattaway@attaway.net]
> Sent: Monday, September 23, 2002 7:26 PM
> To: Jeremy Fowler
> Cc: Kclug@Kclug. Org
> Subject: Re: Gentoo NIC drivers
>
>
> On Mon, 23 Sep 2002, Jeremy Fowler wrote:
>
> > Trying to get Gentoo installed, but the 1.4.1 version on the UT2003 ISO
> > image doesn't have eepro100 drivers!!! I compiled some using the default
> > 2.4.19 source tree and I get 'init_module: No such device' errors. Damn,
> > if I can't get this to work. The livecd-basic-1.4_rc1 is the same, no
> > eepro100 drivers. Now I know that the Pro/100 NICs are popular, why
> > didn't they include them? Anyone able to get this to work or know where
> > I can download drivers for my NIC that will work with the 2.4.19-xfs-r1
> > kernel?
>
> I have the same NIC.  There are two versions of this driver, one is by
> Donald Becker, the other is from Intel.  Both are included with the new
> kernels, but you can use either one.  Due to my hardware on my new Toshiba
> laptop, I've had problems with buffer mismatches, causing random timeouts.
> Compiling the other driver works.  Both drivers have done it at one time
> or another.
>
> You can use either:
>
> e100      <--Intel's driver
> eepro100  <--from NASA's Donald Becker
>
>
>