On kernel 2.0.27, we compiled in support for our network card with
the following option:
CONFIG_NET_ETHERNET=y
CONFIG_NET_VENDOR_3COM=y
# CONFIG_EL1 is not set
# CONFIG_EL2 is not set
# CONFIG_ELPLUS is not set
# CONFIG_EL16 is not set
# CONFIG_EL3 is not set
CONFIG_VORTEX=y
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_ISA is not set
# CONFIG_NET_EISA is not set
# CONFIG_NET_POCKET is not set
# CONFIG_TR is not set
# CONFIG_FDDI is not set
# CONFIG_ARCNET is not set
And on boot-up, we get:
Apr 16 20:40:33 ns kernel: 3Com EtherLink III: Overriding PCI latency timer (CFLT) setting of 64, new value is 255.
Apr 16 20:40:33 ns kernel: eth0: 3Com 3c900 Boomerang 10baseT at 0xf0c0, 00:60:97:29:a9:c8, IRQ 10
Apr 16 20:40:33 ns kernel: Internal config register is 10302d8, transceivers 0xe108.
Apr 16 20:40:33 ns kernel: 8K word-wide RAM 3:5 Rx:Tx split, autoselect/10baseT interface.
Apr 16 20:40:33 ns kernel: 3c59x.c:v0.28c-all 9/22/96 becker@cesdis.gsfc.nasa.gov
...
Apr 16 20:40:33 ns kernel: eth0: Initial media type 10baseT.
Apr 16 20:40:33 ns kernel: eth0: vortex_open() InternalConfig 010302d8.
Apr 16 20:40:33 ns kernel: eth0: vortex_open() irq 10 media status 88c0.
Apr 16 20:40:34 ns kernel: eth0: Media selection timer tick happened, 10baseT.
Apr 16 20:40:34 ns kernel: eth0: Media 10baseT has link beat, 88c0.
Now, the strange thing is that, with the same network driver (CONFIG_VORTEX)
and the same exact system, on kernel 2.0.30, the network card was not
detected. In fact, as far as I know, the /usr/src/linux/.config were just
about identical for the two kernels...
So, for now, we are just using 2.0.27 and things are working well...
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Kirk Bauer Georgia Tech gt5918a@prism.gatech.edu or
Finger for PGP Key --> kirk@kaybee.gt.ed.net
http://www.kaybee.gt.ed.net/~kirk/html/index.html
Resnet RTA (Residence Technical Advisor) GTRI Co-Op