Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 153176 - forcedeth nForce driver not selectable when manually choosing a network module
Summary: forcedeth nForce driver not selectable when manually choosing a network module
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
Depends On:
Blocks: FC4Blocker
TreeView+ depends on / blocked
Reported: 2005-04-01 23:32 UTC by Jesse Keating
Modified: 2015-01-04 22:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-04-28 02:58:24 UTC

Attachments (Terms of Use)
pci.c from kudzu 1.1.95-10 (RHEL4) (deleted)
2005-05-24 23:01 UTC, Jay Hilliard
no flags Details

Description Jesse Keating 2005-04-01 23:32:14 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2

Description of problem:
Using noprobe option to start an install, or a network method and forcedeth not automatically detected, one will get prompted to manually choose a network driver.  forcedeth driver is not one of these options.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.  Start installer w/ noprobe
2.  Browse list of network drivers

Actual Results:  Forcedeth not found.

Expected Results:  forcedeth 'nForce Ethernet Driver' should be available

Additional info:

Related to this bug, the network chip on the MSI K8N Neo Platinum/SLI is not automatically detected.  I do not have the PCI ID as of yet to add to initrd, I will file a seperate bug on this issue.

Comment 1 Jesse Keating 2005-04-02 00:00:16 UTC
Upon closer look, it appears that the driver DOES load automatically, however
the driver is unable to see the hardware device.  Perhaps this is a kernel bug
instead.  Installing from CD to see what happens once OS is installed.

Comment 2 Jesse Keating 2005-04-02 00:16:01 UTC
Module DOES seem to function inside the installed os.  Seems like the problem is
that it doens't work during the installer.  Not sure where this bug goes then.

Comment 3 Jeremy Katz 2005-04-02 16:28:05 UTC
The problem is that the device doesn't show up as a network device according to
it's PCI device class.

Comment 5 Bill Nottingham 2005-04-28 02:58:24 UTC
Hacked around in kudzu-1.1.115-1. Yuck.

Comment 6 Jay Hilliard 2005-05-20 22:57:45 UTC
(In reply to comment #5)
> Hacked around in kudzu-1.1.115-1. Yuck.

May I ask what that hack was? I'd like to try in on RHEL4 and FC3

Comment 7 Bill Nottingham 2005-05-21 00:51:08 UTC
Index: pci.c
RCS file: /usr/local/CVS/kudzu/pci.c,v
retrieving revision 1.121
retrieving revision 1.123
diff -u -r1.121 -r1.123
--- pci.c       22 Apr 2005 22:05:18 -0000      1.121
+++ pci.c       29 Apr 2005 15:42:12 -0000      1.123
@@ -903,6 +905,10 @@
                        dev->driver = strdup("8139cp");
+               /* nForce4 boards show up with their ethernet controller
+                * as a bridge; hack it */
+               if (dev->vendorId == 0x10de && dev->deviceId == 0x0057)
+                           devtype = PCI_CLASS_NETWORK_ETHERNET;
                dev->pcidom = p->domain;
                dev->pcibus = p->bus;
                dev->pcidev = p->dev;

You can also put a pci quirk in the kernel to change the class there (to make it
appear correctly to *all* userland tools); I don't have that patch in front of me

Comment 8 Jay Hilliard 2005-05-24 17:55:50 UTC
Thanks!  I was hoping to implement this change in anaconda so loader/init in my
pxe initrd can use the nForce network device to install via nfs.  Will this fix
make anaconda work right if I patch/rebuild/install kudzu, then rebuild
anaconda-runtime and use the new loader and init in my initrd?  I'm curious how
anaconda uses kudzu in a pxe boot to anaconda environment.  Thanks again!

Comment 9 Bill Nottingham 2005-05-24 19:01:54 UTC
Correct. (You only need the loader, not init)

Comment 10 Bill Nottingham 2005-05-24 19:02:38 UTC
You probably want the new kudzu python module in stage2 as well.

Comment 11 Jay Hilliard 2005-05-24 19:40:43 UTC
I couldn't find a pci.c in the anaconda src to apply the patch to.  I guess I'd
need some sort of python workaround to do the same thing you did in pci.c. 
Suggestions are welcome as I am not well versed in python.  

Comment 12 Bill Nottingham 2005-05-24 20:09:20 UTC
The pci.c is in kudzu; you'd need to apply/build/install that before rebuilding
the loader.

Comment 13 Jay Hilliard 2005-05-24 22:58:48 UTC
Sorry to keep on with this....
I applied the patch to kudzu, built it and then installed the kudzu
and kudzu-devel rpms that were created.  I then built anaconda, then
installed the newly created anaconda and anaconda-runtime rpms.

Next put /usr/lib/anaconda/loader/loader into my initrd that I pxe boot with.
No joy. forcedeth loads and eth0 is bound to 0000:00:0a.0, but keep getting the
"no driver found" window where I can use a driver disk.

* getting kickstart file
* no network devices in choose network device!
* no network drivers for doing kickstart

I'll attach my pci.c from kudzu.  Maybe I put the patch in the wrong place?

Comment 14 Jay Hilliard 2005-05-24 23:01:02 UTC
Created attachment 114806 [details]
pci.c from kudzu 1.1.95-10 (RHEL4)

Comment 15 Bill Nottingham 2005-05-24 23:06:49 UTC
It looks ok. Note that the RHEL 4 U1 kernel will have the pci quirk for this,
solving this that way.

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