On Fri, 16 Feb 2001, João Paulo Legat wrote:
> I'm using a 3c905b PCI and had no problems with RH7+XFS.
> In theory the NIC's chip is the same or similar to your adapter.
>
> Also, the support is compiled in the kernel and not lodaded as module.
>
> 3c59x.c:LK1.1.11 13 Nov 2000 Donald Becker and others.
> http://www.scyld.com/network/vortex.html $Revision: 1.102.2.46 $
> See Documentation/networking/vortex.txt
> eth0: 3Com PCI 3c905B Cyclone 100baseTx at 0x6800, PCI: Found IRQ 10 for
> device 00:10.0
> 00:10:4b:c8:83:2c, IRQ 10
> 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
> MII transceiver found at address 24, status 786d.
> MII transceiver found at address 0, status 786d.
> Enabling bus-master transmits and whole-frame receives.
>
> Regards,
>
> JP
> >
> > Hello,
> >
> > We are trying to install Linux + XFS using the SGI pre-release installation
> > CD on a Dell Precision 420 system. It contains an integrated 3com 3c90x
> > ethernet adapter. For some reason, the adapter is not identified at all
> > during installation (installation does not ask for IP address, subnet mask,
> > etc.), and after installation, Linux does not recognize any eth0 device. We
> > tried adding the device through linuxconf, but after rebooting the system
> > declares, "Delaying eth0 configuration". The command `ifconfig eth0` returns
> > that the device could not be found. The card itself is enabled in the BIOS,
> > and was fully functional under RedHat 6.2. Has anyone else had problems
> > getting such a 3com network card to work with RedHat 7 + XFS, or have any
> > suggestions on how to do so?
> >
> > Thank you,
> > Ken
I have a system that used a network card that wasn't supported with the
limited number of drivers included in the network installation (although
I'm almost certain that the 3c90x is one that *is* included in that
limited number of drivers) that was installed over a network connection
with the xfs prerelease. The trick is to know that there is an option to
use an additional driver disk during installation (enter "linux dd" at the
boot: prompt when you first boot the installer). There is such a driver
disk image available in the images directory that you would have
downloaded the bootnet.img image from. The problem after installation is
that the installation doesn't make the entry for you in the modules.conf
file to identify that driver for eth0. If you have the installation
finished, you just need to add the following line to your
/etc/modules.conf file so the kernel knows what driver coresponds to the
eth0 device:
alias eth0 3c90x
Russ
--
---------------------------------------------------------------
"Bill Gates and Microsoft have ruined the computer industry for
a long time to come by creating a class of ignorant and lazy
computer users." --Russel Ingram
"Mommy ... can I go out and ... KILL TONIGHT!?"
--Glen Danzig, The Misfits
---------------------------------------------------------------
Russ Ingram
Gargoyle Computer Consulting
(307)742-1361
www.gargoylecc.com
|