From: Oncaphillis <oncaphillis@snafu.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: forcedeth trouble in 2.6.34.6 ?
Date: Wed, 29 Sep 2010 10:40:28 +0200 [thread overview]
Message-ID: <4CA2FB7C.5010509@snafu.de> (raw)
Hi,
I'm running a 2.6.34 (64bit) with Fedora 13 using the forcedeth
network driver. Sometimes a ǵo I noticed that the driver fails
to initialize the network connection properly. The HUB tells me
I have a connection and ifconfig and ethtools seem to report
the card as being properly set up. But nothing goes over the lines.
No DHCP or any other communication. Removing and inserting the
driver (sometimes more then once) solves the problem.
Since the hardware is rather old I thought the NIC is broken
and I added another card. Now I have set up a new computer with
another nvidia chipset and have to find out that
it seems to be a driver issue.
I found some random complains about the NIC and the driver in the
net which seem to report similar issues (NIC dead on boot etc..)
but all of these seem to refer to older kernels like 2.6.27 and
such. There also didn't come up much under bugzilla.kernel.org
for 2.6.24 when I search for forcedeth
Is that a known issue ?
Cheers
O.
== lspci -v ==
Old Mainboard AMD Althlon 642X
00:05.0 Bridge: nVidia Corporation CK8S Ethernet Controller (rev a2)
Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device a551
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23
Memory at fdffc000 (32-bit, non-prefetchable) [size=4K]
I/O ports at fc00 [size=8]
Capabilities: [44] Power Management version 2
Kernel driver in use: forcedeth
Kernel modules: forcedeth
New MainBoard Intel Quad Core
00:0a.0 Ethernet controller: nVidia Corporation MCP79 Ethernet (rev b1)
Subsystem: ZOTAC International (MCO) Ltd. Device 0ae5
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22
Memory at fe02b000 (32-bit, non-prefetchable) [size=4K]
I/O ports at fc00 [size=8]
Memory at fe02a000 (32-bit, non-prefetchable) [size=256]
Memory at fe029000 (32-bit, non-prefetchable) [size=16]
Capabilities: [44] Power Management version 2
Kernel driver in use: forcedeth
Kernel modules: forcedeth
reply other threads:[~2010-09-29 9:08 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=4CA2FB7C.5010509@snafu.de \
--to=oncaphillis@snafu.de \
--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