[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problems installing on AMD Athlon 64 system



On Wed, Dec 21, 2005 at 08:54:18AM -0500, Aaron Stromas wrote:
> Output of lspci:
> 0000:00:00.1 Memory controller: nVidia Corporation: Unknown device 005e (rev
> a3)
> 0000:00:01.0 ISA bridge: nVidia Corporation: Unknown device 0050 (rev a3)
> 0000:00:01.1 SMBus: nVidia Corporation: Unknown device 0052 (rev a2)
> 0000:00:02.0 USB Controller: nVidia Corporation: Unknown device 005a (rev
> a2)
> 0000:00:02.1 USB Controller: nVidia Corporation: Unknown device 005b (rev
> a2)
> 0000:00:04.0 Multimedia audio controller: nVidia Corporation: Unknown device
> 0059 (rev a2)
> 0000:00:06.0 IDE Interface: nVidia Corporation: Unknown device 0053 (rev f2)
> 0000:00:07.0 IDE Interface: nVidia Corporation: Unknown device 0054 (rev f3)
> 0000:00:08.0 IDE Interface: nVidia Corporation: Unknown device 0055 (rev f3)
> 0000:00:09.0 PCI Bridge: nVidia Corporation: Unknown device 005c (rev a2)
> 0000:00:0a.0 Bridge: nVidia Corporation: Unknown device 0057 (rev a3)
> 0000:00:0b.0 PCI Bridge: nVidia Corporation: Unknown device 005d (rev a3)
> 0000:00:0c.0 PCI Bridge: nVidia Corporation: Unknown device 005d (rev a3)
> 0000:00:0d.0 PCI Bridge: nVidia Corporation: Unknown device 005d (rev a3)
> 0000:00:0e.0 PCI Bridge: nVidia Corporation: Unknown device 005d (rev a3)
> 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:01.0 VGA compatible controller: nVidia Corporation: Unknown device
> 0141 (rev a2)
> 0000:05:0b.0 FireWire(IEEE 1394): Texas Instruments TSB43AB22/A
> IEEE-1394a-2000  Controller (PHY/Link)

Any chance ethernet is disabled in the bios?

Try manually just doing 'modprobe forcedeth'.  Some boards the nvidia
ethernet doesn't appear in the pci list with certainly 2.6 kernel
versions (of which 2.6.8 is certainly one) but the driver still works
and detects it.

Len Sorensen



Reply to: