--- Begin Message ---
Package: linux-image-2.6.22-3-amd64
Hardware: Motherboard is ASUS M2N-VM DVI, which has an nvidia nforce
chipset with integrated network controler.
OS: Debian etch, kernel replaced by the above (from 'testing')
(apparently the same malfunction happens with the standard 'etch'
kernel (linux-image-2.6.18-5-amd64) and with linux-2.6.23-1-amd64 from
'unstable')
Output of 'uname -a': Linux olaf 2.6.22-3-amd64 #1 SMP Mon Nov 12
10:28:43 UTC 2007 x86_64 GNU/Linux
Description of bug: forcedeth module seems is inserted without error
messages, but eth0 still seems not to be present
Output of 'dmesg | grep forcedeth':
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.g0.
forcedeth: using HIGHDMA
eth0: forcedeth.c: subsystem: 01043:82b3 bound to 0000:00:0a.0
The system fails to configure the network and 'ifconfig' shows only
interface 'lo', not 'eth0'.
Then, while forcedeth is still inserted, output of
'ifconfig eth0 up':
eth0: ERROR while getting interface flags: No such device
Remarks: The 'linux from scratch' distribution has a 'liveCD' (version
x86-6.3.r2145) with a kernel called linux-2.6.22.5. Running this CD,
forcedeth is also inserted (with the same output of 'dmesg | grep
forcedeth'), and ifconfig eth0 up works, as well as networking. The
only difference in 'forcedeth.c' is line 554, where they have
#define PHY_OUI_REALTEX 0x01c1
instead of
#define PHY_OUI_REALTEX 0x0732
But with this difference applied to the debian linux-source-2.6.22,
the compiled forcedeth.ko, after inserting it, still shows the same
bug as described. I could not get the 'linux from scratch' kernel
source 2.6.22.5 as a whole compiled and running on my 'etch' (though I
applyed the configuration of debians 2.6.22-3-amd64 --- kernel says
something about devfs not present while booting and panics).
Output of 'lspci':
00:00.0 RAM memory: nVidia Corporation Unknown device 0547 (rev a2)
00:01.0 ISA bridge: nVidia Corporation Unknown device 0548 (rev a2)
00:01.1 SMBus: nVidia Corporation Unknown device 0542 (rev a2)
00:02.0 USB Controller: nVidia Corporation Unknown device 055e (rev a2)
00:02.1 USB Controller: nVidia Corporation Unknown device 055f (rev a2)
00:04.0 USB Controller: nVidia Corporation Unknown device 055e (rev a2)
00:04.1 USB Controller: nVidia Corporation Unknown device 055f (rev a2)
00:06.0 IDE interface: nVidia Corporation Unknown device 0560 (rev a1)
00:07.0 Audio device: nVidia Corporation Unknown device 055c (rev a1)
00:08.0 PCI bridge: nVidia Corporation Unknown device 0561 (rev a2)
00:09.0 IDE interface: nVidia Corporation Unknown device 0550 (rev a2)
00:0a.0 Ethernet controller: nVidia Corporation Unknown device 054c (rev a2)
00:0b.0 PCI bridge: nVidia Corporation Unknown device 0562 (rev a2)
00:0c.0 PCI bridge: nVidia Corporation Unknown device 0563 (rev a2)
00:0d.0 PCI bridge: nVidia Corporation Unknown device 0563 (rev a2)
00:0e.0 PCI bridge: nVidia Corporation Unknown device 0563 (rev a2)
00:0f.0 PCI bridge: nVidia Corporation Unknown device 0563 (rev a2)
00:10.0 PCI bridge: nVidia Corporation Unknown device 0563 (rev a2)
00:11.0 PCI bridge: nVidia Corporation Unknown device 0563 (rev a2)
00:12.0 VGA compatible controller: nVidia Corporation Unknown device 053b (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
Regards, Olaf
--- End Message ---
--- Begin Message ---
On Tue, Jan 15, 2008 at 12:33:56PM +0100, Olaf Till wrote:
>
> The interface name was indeed eth2. I did not think this is possible,
> since the messages of forcedeth.ko while inserting explicitely said
> 'eth0'; maybye they should not say that ...
>
> It works now for me, even with 2.6.22 --- thank you.
>
cool, so closing bug report.
--
maks
--- End Message ---