I finally "stole" a few minutes here at home to try and chase down the
cause of e-smith not networking the for-the-moment Win98 box here.
Looks as though e-smith fails to identify the 3Com 905-tx nic. Don't
know if the problem is with e-smith or RH 7.0 but it has stopped the
network server from doing the job with this nic!
I chased down the location of a driver but am confused as to how I
appropriately add it to e-smith 4.1.2 ... which is based on RH 7.0
(I believe)
Sounds as though RH really made some poor choices in 7.0 which
make for additional complexity for users when generic setups do not
fly.
Thanks! Doc
http://www.scyld.com/network/updates.html
Using the Source RPM Package
The updated drivers are best installed by using the source RPM to create
a custom binary RPM with kernel modules for your system:
ftp://ftp.scyld.com/pub/network/netdriver-2.1.src.rpm
Use the following commands to install and test the driver pack: # Transfer
the Scyld PCI Netdriver package # Perhaps use ncftpget
ftp://ftp.scyld.com/pub/network/netdriver-2.1.src.rpm rpm -i
ftp://ftp.scyld.com/pub/network/netdriver-2.1.src.rpm # Build the binary
version for your kernel cd /usr/src/{redhat,TurboLinux,packages}/ rpm -bb
SPECS/netdriver*.spec # Now install it your newly built package.
rpm -i --force
RPMS/i386/netdriver-2.1-*.i386.rpm
The --force option is needed because the new drivers may conflict with the
existing drivers installed by the kernel package. If this occurs you will
see a
warning message for each driver that has been updated.
Special instructions for Red Hat 7.0
Red Hat 7.0 has a flawed configuration with their default install. The
symptom
is a variety of errors when trying to compile the driver update source RPM.
The
easiest work-around is to use a precompiled RPM for Red Hat 7.0 running the
x86 uniprocessor kernel from
ftp://ftp.scyld.com/pub/network/netdrivers-rh70.i386.rpm
Red Hat 7.0 uses the header files from an unreleased 2.3.99 kernel, rather
than
installing the header files from the kernel that is actually running. This
was an
attempt to make user-level binaries independent of the specific kernel
version,
but it makes it impossible to automatically build kernel modules.
A second problem is that 7.0 provides an experimental version of gcc that
was
not intended for public release. The stable version of gcc needed to
correctly
compile the kernel has been renamed to kgcc.
The work-around is to substitute kgcc for gcc and to
add -I/usr/src/linux/include
on the compile command line when compiling by hand. The Makefile in the tar
file
and RPM automatically include this compile flag, however they cannot
automatically
use 'kgcc'.
To repeat: this is a flaw that was introduced with Red Hat 7.0. It is a Red
Hat
configuration problem, not a driver update distribution bug. The symptom of
this
bug is compile error messages such as tulip.c: In function `tulip_open':
tulip.c:1437:
structure has no member named `tbusy' tulip.c:1438: structure has no member
named `start'
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:08:02 EDT