Anyone know of a good linux distribution that will work with the nf7-s ethernet port. I cant seen to find any that work to well, or have driver support for it.
0
Comments
Straight_ManGeeky, in my own wayNaples, FLIcrontian
edited February 2004
Unfortunately, you are correct there. One way for now would be to use an Intel NIC PCI card, which Linux DOES work very well with. (Change what is used for Networking, for now, until NVIDIA and the Linux kernel dev folks work out how to use the embedded NIC circuits in the Nforce2 chipset.).
Yeah, I know NVIDIA has NForce2 drivers out, but they are not completely working for that board yet, and one of the hangups is Networking-- specifically that Linux does NICS one way and NVIDIA does this chipset's networking routing another way. Linux only will let Network cards be used if they have certain IRQs, and NVIDIA chose to hard code a different IRQ for NIC circuits than one of the ones Linux likes.
i never needed to worry about that because i've got a nic that is supported in my pci slot. but i'll keep an eye out for ya since i have the same board.
i tried the nvnet for redhat, and it didnt do anything for me... but ill give forcedeth a try .. but i appreciate it guys.
0
Straight_ManGeeky, in my own wayNaples, FLIcrontian
edited February 2004
One other thing:
If you want to know some of what is going on, try this, which will give you some feedback (actually lots, but I will get into that later in this post...)
There is a linux command called modprobe. If you are not sure if Linux has a driver module running that conflicts with what you are trying to install, or you in fact are not sure if Linux is even trying to use the driver module you want it to use, try this:
login or sudo root
(give it the root password)
modprobe -aq > modproberesults.txt
cat modproberesults.txt | less
(note that less is a file reader module, you can use pageup, pagedown and arrow keys, and unlike more you can move backwards to beginning of file if wanted or to any place backwards as well as forwards)
The reason I did this is some of us might be able to make sense of errors linux shows when doing this device driver probe-- please cut-n-paste errors only here, or if you notice more than one device, the entries and comments for the devices that use same IRQ, for instance, AS WELL. This call tells it to query use of all modules available for kernel, and tell the person running it what the query results are. IF you run it directly in a pure console, you will get 4-10 screens of output that scroll very fast, from a file and using a file reader you can read online and if you want to print you need a file to print from. The file name does not have to be modproberesults, you can use any name thta will make sense for you to find it later. Extension does not have to be .txt, but it will easier to find if you lose the thing if you DO use .txt.
If you have questions about this, please ASK... And, 'man modprobe' is a good idea also.
Is the intel nic pci card a good choice? because i may end up purchasing one of them, for emergency reasons and whatnot. And which intel nic pci card should i go about purchasing, i see that there is a wide variety on newegg.
Comments
Yeah, I know NVIDIA has NForce2 drivers out, but they are not completely working for that board yet, and one of the hangups is Networking-- specifically that Linux does NICS one way and NVIDIA does this chipset's networking routing another way. Linux only will let Network cards be used if they have certain IRQs, and NVIDIA chose to hard code a different IRQ for NIC circuits than one of the ones Linux likes.
John D-- who also wants to add: Sorry, not YET.
forcedeth ABIT
or
nvnet RPM
If you want to know some of what is going on, try this, which will give you some feedback (actually lots, but I will get into that later in this post...)
There is a linux command called modprobe. If you are not sure if Linux has a driver module running that conflicts with what you are trying to install, or you in fact are not sure if Linux is even trying to use the driver module you want it to use, try this:
login or sudo root
(give it the root password)
modprobe -aq > modproberesults.txt
cat modproberesults.txt | less
(note that less is a file reader module, you can use pageup, pagedown and arrow keys, and unlike more you can move backwards to beginning of file if wanted or to any place backwards as well as forwards)
The reason I did this is some of us might be able to make sense of errors linux shows when doing this device driver probe-- please cut-n-paste errors only here, or if you notice more than one device, the entries and comments for the devices that use same IRQ, for instance, AS WELL. This call tells it to query use of all modules available for kernel, and tell the person running it what the query results are. IF you run it directly in a pure console, you will get 4-10 screens of output that scroll very fast, from a file and using a file reader you can read online and if you want to print you need a file to print from. The file name does not have to be modproberesults, you can use any name thta will make sense for you to find it later. Extension does not have to be .txt, but it will easier to find if you lose the thing if you DO use .txt.
If you have questions about this, please ASK... And, 'man modprobe' is a good idea also.
John D.
as simple as:
emerge nforce-net
modprobe nvnet
then edit your "/etc/modules.autoload.d/kernel" and add nvnet in there so it loads on startup'
if you are using the 2.5 kernel or above, you need to install the patch before the src will emerge.