Bug 130208
Summary: | kernel 2.6.7-1.494.2.2 Nforce 2 ethernet driver problem | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Donald L. Walters <dlwalters> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | kevin.russell, pfrields, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-04-16 05:28:10 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Donald L. Walters
2004-08-18 01:16:09 UTC
I have a similar problem that may be related. After upgrading from kernel 2.6.6-1.435.2.3 to either 2.6.7-1.494.2.2 or 2.6.8-1.521, the installation of NVIDIA's binary nForce ethernet driver fails (using NFORCE-Linux-x86-1.0-0283-pkg1.run). /var/log/nvidia-nforce-installer.log reports errors such as [...] /tmp/selfgz2641/NFORCE-Linux-x86-1.0-0283-pkg1/nvnet/nvenet.c:1720: error: request for member `lock' in something not a structure or union [...] Upon further investigation, CONFIG_DEBUG_SPINLOCK has been enabled on both the new kernels which in turn, tickles a compilation bug in NVIDIA's use of spin_lock(). Rebuilding the 2.6.8-1.521 with CONFIG_DEBUG_SPINLOCK disabled allows NVIDIA code to compile and the system is able to recognize eth0. Of course, this is comletely unrelated if you use the forcedeth driver. mass update for old bugs: Is this still a problem in the 2.6.9 based kernel update ? Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you. |