Red Hat Bugzilla – Bug 130208
kernel 2.6.7-1.494.2.2 Nforce 2 ethernet driver problem
Last modified: 2015-01-04 17:08:55 EST
Description of problem:
Installing kernel 2.6.7-1.494.2.2 kills the Nvidia Nforce 2 ethernet
drivers on Shuttle SN41G2-V2 chip set machines, but not on earlier
SN41G1 version 1 machines. Also there are video driver timing changes
and the LCD monitor loses sync, but auto reset of LCD monitor recovers.
Version-Release number of selected component (if applicable):
only kernel 2.6.7-1.494.2.2
Always (three installs of above kernel, but 2.6.6-1 .435.2.3 and
earlier work fine.
Steps to Reproduce:
1.Every install of kernel 2.6.7-1.494.2.2 on a Shuttle SN41G2-V2 from
the up2date, and reboot.
2. Eth0 not found during boot
Ethernet eth0 is not found at reboot, so there is no ethernet
connection. Also video driver scan rates change, but work with an
auto reset of the monitor.
Working ethernet as with kernel 2.6.6-1 .435.2.3 and earlier
Unique to the new Nvidia chipset used in the Shuttle SN41G2-V2 (AMD
3000XP), and does not occur for two SN41G2 original versions we tried.
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
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
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.