Bugzilla – Bug 120567
Nvidia MCP-04 ethernet not detected in installation
Last modified: 2005-10-06 09:52:49 UTC
I have a new Gigabyte GA-8N-SLI Pro motherboard with the NVIDIA nForce 4 chipset with the MCP-04 south bridge. This chipset has a gigabit Ethernet port built-in, attached to a Marvell PHY. When installing OpenSUSE 10.0 RC1 from CDs, this ethernet adaptor is not auto-detected, and the system is not set up for it. If I manually select the "sk98lin" device driver, it works as expected. Here's some lines from dmesg: NFORCE-MCP04: IDE controller at PCI slot 0000:00:0f.0 ACPI-0212: *** Warning: Device is not power manageable NFORCE-MCP04: chipset revision 162 NFORCE-MCP04: not 100% native mode: will probe irqs later NFORCE-MCP04: 0000:00:0f.0 (rev a2) UDMA133 controller forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.35. eth0: forcedeth.c: subsystem: 01458:e000 bound to 0000:00:0e.0 ACPI-0212: *** Warning: Device is not power manageable
Please, attach output of 'hwinfo --netcard'
Ok, here it is: 27: PCI 0e.0: 0680 Bridge [Created at pci.277] UDI: /org/freedesktop/Hal/devices/pci_10de_38 Unique ID: rBUF._nK_faGuTv5 SysFS ID: /devices/pci0000:00/0000:00:0e.0 SysFS BusID: 0000:00:0e.0 Hardware Class: bridge Model: "Giga-byte MCP04 Ethernet Controller" Vendor: pci 0x10de "nVidia Corporation" Device: pci 0x0038 "MCP04 Ethernet Controller" SubVendor: pci 0x1458 "Giga-byte Technology" SubDevice: pci 0xe000 Revision: 0xa2 Driver: "forcedeth" Device File: eth0 Memory Range: 0xd8003000-0xd8003fff (rw,non-prefetchable) I/O Ports: 0xcc00-0xcc07 (rw) IRQ: 193 (2328861 events) HW Address: 00:14:85:0e:86:33 Module Alias: "pci:v000010DEd00000038sv00001458sd0000E000bc06sc80i00" Driver Info #0: Driver Status: forcedeth is active Driver Activation Cmd: "modprobe forcedeth" Config Status: cfg=no, avail=yes, need=no, active=unknown
Hmm, hwinfo reports "forcedeth" for the device but is looks like "sk98lin" would be the right one (see comment #0)
The nforce 4 problems were (hopefully) fixed in rc4. You can verify that with the final 10.0, which should be available by now (or very soon) or with the already released 10.1 alpha.