The nforce nic is definitely running as: --- 0000:00:05.0 Bridge: nVidia Corporation: Unknown device 00df (rev a2) ---
on your PC. I was confused by the same thing, but it works very well. later, Steve Christian T. Steigies wrote: > On Tue, Nov 02, 2004 at 07:18:32PM -0500, Joey Hess wrote: > >>Christian T. Steigies wrote: >> >>>There was nothing hooked up to the firewire, but the NIC was connected to a >>>switch. So I guess it is a bug in the link detection code. Could there be >>>anyhting in the installer log files? I could try to retrieve them tomorrow. >>>I also tried a knoppix 3.6 (i386), it did not detect the network either. >> >>Yes there should be some info in there about the link info it reported. >>We probably need that and the model of nic card to do more. > > > Since I installed with the old CD after this, it seems the log files where > overwritten, and I can not install again just for testing, this will have to > wait until we get the next AMD64, which will probably have the same MB. > > As for the onboard nic (which died after less than a days usage), I don't see > it in lspci, I think it is one of the unknown devices, I am guessing one of > the Bridges: > > 0000:00:00.0 Host bridge: nVidia Corporation: Unknown device 00e1 (rev a1) > 0000:00:01.0 ISA bridge: nVidia Corporation: Unknown device 00e0 (rev a2) > 0000:00:01.1 SMBus: nVidia Corporation: Unknown device 00e4 (rev a1) > 0000:00:02.0 USB Controller: nVidia Corporation: Unknown device 00e7 (rev a1) > 0000:00:02.1 USB Controller: nVidia Corporation: Unknown device 00e7 (rev a1) > 0000:00:02.2 USB Controller: nVidia Corporation: Unknown device 00e8 (rev a2) > 0000:00:05.0 Bridge: nVidia Corporation: Unknown device 00df (rev a2) > 0000:00:06.0 Multimedia audio controller: nVidia Corporation: Unknown device 00ea (rev a1) > 0000:00:08.0 IDE interface: nVidia Corporation: Unknown device 00e5 (rev a2) > 0000:00:0a.0 IDE interface: nVidia Corporation: Unknown device 00e3 (rev a2) > 0000:00:0b.0 PCI bridge: nVidia Corporation: Unknown device 00e2 (rev a2) > 0000:00:0e.0 PCI bridge: nVidia Corporation: Unknown device 00ed (rev a2) > 0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > 0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > 0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > 0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > 0000:01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1) > 0000:02:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) > 0000:02:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) > 0000:02:0c.0 RAID bus controller: Silicon Image, Inc. (formerly CMD > Technology Inc) SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02) > > It is supported by the forcedeth driver: > > forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.28. > ACPI: PCI interrupt 0000:00:05.0[A] -> GSI 11 (level, low) -> IRQ 11 > PCI: Setting latency timer of device 0000:00:05.0 to 64 > eth2: forcedeth.c: subsystem: 01043:80a7 bound to 0000:00:05.0 > > It has eth2 now, since we had to plug in another NIC, which is detected as > eth0, before the builtin firewire and the builtin nforce3. > > Christian > >
