I installed the driver and its update, but i still cant get it to work....
0
Straight_ManGeeky, in my own wayNaples, FLIcrontian
edited February 2004
Will someone tell me what the chip(or circuit brand used) is for ethernet on the NF7-S??? I do not have mine yet....
I can tell you that the drivers for RH, so far, are for the NF2 chipset, overall, and not the NF3 RELIABLY yet. Part of this is the kernel and not purely the drivers.
Unless Fedora adopted the 2.6 since I last looked, the solution to get the latest NF chipset completely running might be a case of needing to compile a 2.6 kernel to fit your box.
2.4 kernel is limited as to what IRQs it will allow the NICs to be set at. And how it likes NICs to be almost always on and not IRQ stacked with other things. Linux needs tight drivers that address the hardware precisely right and can access it often, especially for ethernet cards. See. linux was first deved for servers, and those need reliable NICs that can be accessed at random any time and respond fast. If you stack IRQs, witht eh 2.4 kernel and back, you get a situation where it takes longer for the NIC to know it and only it has to respond, and you get the Linux kernel disabling it if it lags too often. If Linux does not know what the chip really is, since it talks more to hardware from kernel for networking than for some other things(on my Linux box the South Bridge ID is wrong, but the box works fine, but the NIC ID had to be right for the networking to work), then the drivers report errors and the kernel and scripts fail the NIC too often.
I WOULD expect the 2.6 kernel to be alot more likely to work than a 2.4 kernel, though, for Linux distros as they work it into the mainstream of what is out there as a canned set, but some NICs and Linux do not get along well.
Easiest "instant" fix, is a good PCI card NIC (Intel PCI NICs of mid-grade and up models work if embedded NIC can be disabled, ditto many 3COM NICs) and to disable onboard NIC for right now until drivers are firmed up.
Comments
2) nVidia Chipset Drivers for RH 9 (Kernel Upgrade)
Enjoy
you also need the chipset drivers park linked
I can tell you that the drivers for RH, so far, are for the NF2 chipset, overall, and not the NF3 RELIABLY yet. Part of this is the kernel and not purely the drivers.
Unless Fedora adopted the 2.6 since I last looked, the solution to get the latest NF chipset completely running might be a case of needing to compile a 2.6 kernel to fit your box.
2.4 kernel is limited as to what IRQs it will allow the NICs to be set at. And how it likes NICs to be almost always on and not IRQ stacked with other things. Linux needs tight drivers that address the hardware precisely right and can access it often, especially for ethernet cards. See. linux was first deved for servers, and those need reliable NICs that can be accessed at random any time and respond fast. If you stack IRQs, witht eh 2.4 kernel and back, you get a situation where it takes longer for the NIC to know it and only it has to respond, and you get the Linux kernel disabling it if it lags too often. If Linux does not know what the chip really is, since it talks more to hardware from kernel for networking than for some other things(on my Linux box the South Bridge ID is wrong, but the box works fine, but the NIC ID had to be right for the networking to work), then the drivers report errors and the kernel and scripts fail the NIC too often.
I WOULD expect the 2.6 kernel to be alot more likely to work than a 2.4 kernel, though, for Linux distros as they work it into the mainstream of what is out there as a canned set, but some NICs and Linux do not get along well.
Easiest "instant" fix, is a good PCI card NIC (Intel PCI NICs of mid-grade and up models work if embedded NIC can be disabled, ditto many 3COM NICs) and to disable onboard NIC for right now until drivers are firmed up.
John D.
It's a Realtek 8201BL but branded as "NVIDIA nForce MCP Networking Controller" by drivers in Windows.