Red Hat Bugzilla – Bug 167387
sk98lin gigabit ethernet driver does not work in kernel-smp 2.6.12 1.1447_FC4
Last modified: 2007-11-30 17:11:12 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6
Description of problem:
Since the update to 1447 the network interface (Marvell yukon onboard ASUS P5P800) driven by sk98lin can't get a connection. Driver is loaded without errors, but interface can't get address via dhcp, manually assigned address does not work either.
Older kernel and knoppix both work fine, so the issue is neither hardware nor network infrastructure.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.install kernel-smp 2.6.12 1.1447_FC4
2.try to use network for anything
Actual Results: failed miserably
Expected Results: seen a website, downloaded some pictures, pinged some computers
no error messages whatsoever, except for the failure to obtain IP address at boot.
Tested on P4 with hyperthreading and smp kernel, not tested on uniprocessor kernel.
network card is connected to a TP/Fiber trnsceiver
does the skge driver work better ?
sk98lin is an older driver, and will eventually be obsoleted by skge.
I have uninstalled the kernel in question, and I have little occasion to test
anything on that machine, because it is in production use. Nevertheless I will
try to test this during the course of this week.
If skge is the better module, shouldn't this be the one that is loaded
automatically by whatever package detects the Hardware?
as of fc5, it will use skge by default.
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (188.8.131.52). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.
Please retest with this update, and update this bug if necessary.
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
Closed due to lack of response. Please reopen when the requested information