ethernet card
Adam McDougall
mcdouga9@egr.msu.edu
Tue, 22 May 2001 12:13:52 -0400 (EDT)
On 22 May 2001, Ben Pfaff wrote:
> "Clint Thayer" <clint@thayernet.com> writes:
>
> > nope, it's a PCI card
> >
> > "Clint Thayer" <clint@thayernet.com> writes:
> >
> > > Now I'm having trouble getting the ethernet card to work... here is what I
> > > know...
> > >
> > > 1.) It's a kensington brand card
> > > 2.) I think it uses the tulip drivers
> > > 3.) It's on IRQ 5
> > > 4.) I've turned all PnP off in BIOS
> ^^^^^^^^^ this applies only to ISA/PnP
> cards, hence my question
I disagree about this one! If it thinks your OS supports PNP then the
BIOS wont initialize non-boot device PCI devices as completely as if it
thinks your OS is non-PNP. I've seen turning pnp-os off solve many cases
on FreeBSD mailing lists where the network card could not map memory or
something similar because the BIOS had not initialized the card
completely. This may be different in Linux as I am not familiar with the
PCI code but it may apply for NT4 and DOS and other oses cannot yet
completely initialize a PCI card.
>
> > > 5.) looked in /etc/modules.conf to confirm the eth0 setting
> >
> > Is it an ISA card?
>
> Okay, in that case, then you want to get to a root prompt and
> type `ifconfig eth0'. Does anything useful show up, like this?
>
> pfaffben:~# ifconfig eth0
> eth0 Link encap:Ethernet HWaddr 00:D0:59:10:4C:D4
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Interrupt:11 Base address:0x1000
>
> If not, then check whether an Ethernet driver is loaded. First
> check for a module with `lsmod'; is `tulip' listed? Show us the
> list of modules. You can also check whether a nonmodular driver
> is loaded with something like `dmesg | grep -3i ethernet'. Show
> us the result, if any.
>
> If no driver is loaded, try loading the Tulip driver with
> `modprobe tulip'. Any luck? If not, show us a list of the PCI
> devices you get by running `lspci'; e.g., I get:
>
> pfaffben:~/linux-2.4.5pre1# lspci
> 00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03)
> 00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03)
> 00:04.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)
> 00:04.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)
> 00:05.0 CardBus bridge: Texas Instruments PCI1131 (rev 01)
> 00:05.1 CardBus bridge: Texas Instruments PCI1131 (rev 01)
> 00:07.0 Bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
> 00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
> 00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
> 00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 03)
> 00:08.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
> 00:09.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100] (rev 09)
> 00:09.1 Serial controller: Lucent Microelectronics LT WinModem
> 00:0d.0 SCSI storage controller: BusLogic BT-946C (BA80C30) [MultiMaster 10]
> 00:0e.0 Ethernet controller: 3Com Corporation 3c905C-TX [Fast Etherlink] (rev 74)
> 00:0f.0 Network controller: Compaq Computer Corporation Integrated NetFlex-3/P (rev 10)
> 00:14.0 ISA bridge: Compaq Computer Corporation MIS-E (rev 05)
> 00:14.1 IDE interface: Compaq Computer Corporation Triflex Dual EIDE Controller (rev 03)
> 01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage P/M Mobility AGP 2x (rev 64)
>
> where devices 9.0, e.0, and f.0 are my first, second, and third
> Ethernet controllers on this box (don't ask).
> --
> "doe not call up Any that you can not put downe."
> --H. P. Lovecraft
> _______________________________________________
> linux-user mailing list
> linux-user@egr.msu.edu
> http://www.egr.msu.edu/mailman/listinfo/linux-user
>