I credit this to "malweth" for posting the url in the first place. Awesome!!! I'm glad to hear that it works for you.

Is there any way to automate that prosess on startup?? I have to cd to /lib/modules....thne insmod fa311.0 and then sh/etc/rc.d/init.d.....Kind of a pain. can i make it do it automatically?

Yes, I agree that is a pain to enter those commands every time you boot up. And yes, there is a way you can configure your system so your fa311 module is automagically loaded at boot time: use the "/etc/modules.conf" file. That is, in that file, add the line: alias eth0 fa311
That's it! This will automatically load /lib/modules/2.whatever/net/fa311.o at boot time.

well. that is already there. The weird thing is. when i boot up, it says ***unknown symbols in /lib/modules/2.2.16-22/net/fa311.o. pretty weird. and then it delays eth0. so i thought if there was a way to enter those commands exactly, i would be all set.

I'm not sure on this one. I didn't need to re-load each time I reboot. Unfortunately, I can't tell you what my setup was because I wiped out my drive already.

not sure what i did. I installed 62 instead for the heck of it to see if it would work. but after i finished installing it i said: "I can get 7.0 to work right, and im not quitting til I do". so i reinstalled 7.0 and lo and behold, it starts up eth0 on startup . now i just need to get ssh and all the good stuff working. any good howtos?

in RedHat 7.0 for dummies, I start it by using the CD. but it doesn't recognize my network card.
How can I get it to recognize this card. I have tried entering expert mode and it asks for the drivers disk, but it says that my disk isn't for this version of linux.

I went to netgears site. downloaded there driver for RedHat 7.0 and put it on a disk. but it says the same thing, this disk isn't for this version of Linux.

Any help???

Spanky,

The RH7 installer didn't recognize my Netgear card as well. You can configure it afterwards, read this thread starting from the mid-section on page 2. Try to follow some of the step-by-step procedure to see if they work for you. Good luck.

Yee

OK, well I have RH 7.0 (2.2.16-22 kernel) and I've managed to build the FA311.o module, and eth0 is recognised OK. Indeed the ifconfig shows the rx and tx counts incrementing so I guess the module is working.

There are only two machines on the net - Linux as 192.168.1.3 and a Win95 as 192.168.1.2

If I ping the Linux machine from Win95 ifconfig shows both the RX and TX counts increase by 4 but Win95 says the request timed out.

If I ping Win95 from Linux, ifconfig only shows the tx count increment, and nothing else happens - I have to CTRL-C to stop the ping.

The hardware is all working OK in both machines, because if I boot both machines in MSDOS mode, I can run the NetGear diagnostics, and that shoves data back and forth without problems.

So what is going on ? Is it a problem with the FA311 driver or something else ?

I have winsock2 on the Win95 machine if that is significant.

I would recommend getting the precompiled fa311.o from http://www.sonnik.com/fa311/ . Or, do what I did, install 6.2 7.0 has too many bugs for me. Plus 7.1 is coming out shortly.

Ok, I finally got this card to work with a custom build kernel in suse7.1 by choosing the natsemi driver. However, when I ping from the fa311 machine i get the following

PING 192.168.0.2 (192.168.0.2): 56 data bytes
64 bytes from 192.168.0.2: icmp_seq=0 ttl=255 time=0.752 ms
64 bytes from 192.168.0.2: icmp_seq=1 ttl=255 time=0.586 ms
64 bytes from 192.168.0.2: icmp_seq=2 ttl=255 time=0.578 ms
64 bytes from 192.168.0.2: icmp_seq=3 ttl=255 time=0.579 ms
64 bytes from 192.168.0.2: icmp_seq=4 ttl=255 time=0.579 ms
64 bytes from 192.168.0.2: icmp_seq=5 ttl=255 time=0.579 ms
64 bytes from 192.168.0.2: icmp_seq=6 ttl=255 time=0.579 ms
64 bytes from 192.168.0.2: icmp_seq=11 ttl=255 time=0.561 ms
64 bytes from 192.168.0.2: icmp_seq=16 ttl=255 time=0.557 ms
64 bytes from 192.168.0.2: icmp_seq=21 ttl=255 time=0.554 ms
64 bytes from 192.168.0.2: icmp_seq=26 ttl=255 time=0.552 ms
64 bytes from 192.168.0.2: icmp_seq=31 ttl=255 time=0.562 ms
64 bytes from 192.168.0.2: icmp_seq=36 ttl=255 time=0.551 ms
64 bytes from 192.168.0.2: icmp_seq=41 ttl=255 time=0.564 ms
64 bytes from 192.168.0.2: icmp_seq=46 ttl=255 time=0.565 ms
64 bytes from 192.168.0.2: icmp_seq=51 ttl=255 time=0.555 ms
^M--- 192.168.0.2 ping statistics ---
68 packets transmitted, 17 packets received, 75% packet loss
round-trip min/avg/max = 0.551/0.576/0.752 ms

and so on, the icmp_seq seems to skip 5 after the first 7 pings and reports the packet loss. Any tcp/ip experts or anyone for that matter have a clue whats going on?

BTW, pinging from 192.168.0.2 to the fa311, 192.168.0.10, machine does not skip sequence and reports 0% loss with slightly less round-trip averages.

Dave

Hi All,

I recently installed RH7.1 and seem to be having
some problems with my netgear fa311 NIC. My machine passes data, but it is extremely slow
and "netstat -i" shows substantial packet loss.

From what I have read in this thread, kernel
2.4 includes support for this device, and
infact a "lsmod" shows that natsemi is being used.

In looking at the scyld.com site they
suggest that pci_scan should be "insmod"ed
before natsemi is. There is no indication
I am running pci_scan.

So, a first question:
Has anyone succesfully used fa311 without problems
in RH7.1 (or 7.0)?
Reading this thread, it looks like some
people have switched from RH to another
dist and then all worked.

What does fa311.o do that natsemi.o does not?

Can the fa311.o, described above, be installed
in RH7.1?

Thanks,

jan

weird...after building a new, faster linux box, i decided to go with redhat again, 7.1, i LOVE the look of it. and it is very fast. i have a linksys LNETX 10/100 NIC and also a spare netgear fa311. The linksys would take about 5 minutes to initiate on startup and wouldnt even get on line . i tried the fa311 and even the smallest page (www.google.com) took about 5 mins, no images coming. I got frustrated and put windows on it (yuk) but now i have 2 days off in a row, so i will have time to figure it out.. i want to use the linksys...i was just about to post for getting some help, when i got this email about someone replying .

I have the exact same symptom. I also
tried transferring files from another
machine on my network and it was
very slow.

I can ping machine on the outside world
and on my network, but the NIC is
definitely not working correctly.

jfd118

i pinged my linux box also and it was fine....what is going on here?