From: Ed W <lists@wildgooses.com>
To: linux-kernel@vger.kernel.org
Subject: Ethernet not functioning on Nvidia MCP51 in 2.6.21
Date: Sat, 14 Jul 2007 17:35:23 +0100 [thread overview]
Message-ID: <4698FB4B.8000508@wildgooses.com> (raw)
Hi, I am renting a root server which uses an nvidia motherboard and
currently has a functioning 2.6.16 kernel. Unfortunately taking the
same .config file (make oldconfig) in 2.6.21.6 is apparently not
spotting the ethernet controller correctly (for various reasons I need a
newer kernel, eventually with some other patches also)
As near as I can find it should be the forcedeth driver being used
here. Comparing dmesg on the working kernel and the non-working kernel
shows no obvious differences. The working kernel uses no special
command line options. Can someone please help me to debug this further?
Symptoms are that dmesg suggests that the driver is being asked to load,
but ifconfig does not show any eth0 device?
Relevant chunks of dmesg on the non working kernel are below, full dmesg
and lspci and kernel .config are in the links at the end. Grateful for
any help debugging this? How do I find out why the driver is finding my
hardware, but no eth0 device is being created?
Ed W
...
loop: loaded (max 8 devices)
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
sk98lin: driver has been replaced by the skge driver and is scheduled
for removal
Marvell 88E1101: Registered new driver
Marvell 88E1111: Registered new driver
Marvell 88E1145: Registered new driver
Davicom DM9161E: Registered new driver
Davicom DM9131: Registered new driver
Cicada Cis8204: Registered new driver
Cicada Cis8201: Registered new driver
LXT970: Registered new driver
LXT971: Registered new driver
QS6612: Registered new driver
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.60.
ACPI: PCI Interrupt Link [LNKL] enabled at IRQ 23
ACPI: PCI Interrupt 0000:00:14.0[A] -> Link [LNKL] -> GSI 23 (level,
high) -> IRQ 16
PCI: Setting latency timer of device 0000:00:14.0 to 64
forcedeth: using HIGHDMA
eth0: forcedeth.c: subsystem: 01734:10c6 bound to 0000:00:14.0
...
00:14.0 Ethernet controller: nVidia Corporation MCP51 Ethernet Controller (rev a3)
Subsystem: Fujitsu Siemens Computer GmbH Unknown device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 16
Memory at f2202000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 8c38 [size=8]
Capabilities: [44] Power Management version 2
http://www.wildgooses.com/downloads/config
http://www.wildgooses.com/downloads/dmesg.txt
reply other threads:[~2007-07-14 16:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4698FB4B.8000508@wildgooses.com \
--to=lists@wildgooses.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox