Re: dead NIC, or ...?
I'm copying the results of 'cat /proc/pci' below. It seems not to be seeing the
card at all.
On boot I *know* I'm seeing a message about modprobe not being able to find the
3c59x module scroll by ... is modprobe not finding the because the card isn't
being recognized, or is the card not being recognized because of the module not
being found? Sorry for the lo-level questions, I'm trying to understand. I did
search the message archive a bit.
Thanks to anyone who may be able to help.
Here's the output of 'cat /proc/pci' :
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: Intel Corp. 440BX/ZX - 82443BX/ZX Host bridge (rev 3).
Master Capable. Latency=64.
Prefetchable 32 bit memory at 0xf8000000 [0xfbffffff].
Bus 0, device 1, function 0:
PCI bridge: Intel Corp. 440BX/ZX - 82443BX/ZX AGP bridge (rev 3).
Master Capable. Latency=64. Min Gnt=132.
Bus 0, device 7, function 0:
ISA bridge: Intel Corp. 82371AB PIIX4 ISA (rev 2).
Bus 0, device 7, function 1:
IDE interface: Intel Corp. 82371AB PIIX4 IDE (rev 1).
Master Capable. Latency=64.
I/O at 0x1440 [0x144f].
Bus 0, device 7, function 2:
USB Controller: Intel Corp. 82371AB PIIX4 USB (rev 1).
IRQ 9.
Master Capable. Latency=64.
I/O at 0x1400 [0x141f].
Bus 0, device 7, function 3:
Bridge: Intel Corp. 82371AB PIIX4 ACPI (rev 2).
IRQ 9.
Bus 0, device 14, function 0:
VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 1).
IRQ 11.
Non-prefetchable 32 bit memory at 0xf4000000 [0xf5ffffff].
Prefetchable 32 bit memory at 0xfc000000 [0xfdffffff].
I/O at 0x1000 [0x10ff].
Bus 0, device 16, function 0:
Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 7).
IRQ 9.
Master Capable. Latency=64. Min Gnt=2.Max Lat=20.
I/O at 0x1420 [0x143f].
Bus 0, device 16, function 1:
Input device controller: Creative Labs SB Live! (rev 7).
Master Capable. Latency=64.
I/O at 0x1450 [0x1457].
Bus 0, device 17, function 0:
Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 1).
IRQ 10.
I/O at 0x1458 [0x145f].
> Glen,
>
> Try cat /proc/pci - that'll tell you how the kernel sees your card (or
> if it sees it at all) and that may help you in figuring out which
> module to load. It may be that the new version of this card uses a
> different module than the old. This is sometimes the case when the
> manufacturer changes chipsets, but keeps naming conventions the same or
> similar.
>
+----------------+
http://www.burningclown.com
"Everyone's Portal to Nothing At All"
+----------------+
Reply to: