Bug 196115 - nforce4 ethernet stopped working after latest kernel update
nforce4 ethernet stopped working after latest kernel update
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-06-21 03:43 EDT by Klaasjan Brand
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-11-21 18:49:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Klaasjan Brand 2006-06-21 03:43:52 EDT
Description of problem: after installation of the latest FC5 update kernel on a
system with an Asus A8N-SLI (nforce4-based) motherboard, the on-board nforce4
ethernet port stopped working (did not get an IP address using DHCP, no visible
activity on switch or ethernet port tx/rx leds).
Booting the previous kernel just worked, so it's no hardware problem. Could be
related to bug 191441.

Version-Release number of selected component (if applicable):
kernel 2.6.16-1.2133
Comment 1 Dave Jones 2006-10-16 16:36:47 EDT
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.
Comment 2 Klaasjan Brand 2006-10-30 13:48:59 EST
Sorry for the late reply. It's working for me with the current FC5 kernel.

Note You need to log in before you can comment on or make changes to this bug.