I don't know about Redhat 7.1, but my FA311 card works fine with Mandrake 8.0.

i would use 6.2 but it is incompatible with my mobo. I would use 7.0 but it stinks. so...im trying 7.1 again, and if it doesnt work, then im going for slak or maybe Debian.

just installed 7.1, rebooted from install prog. turned PNP (plug and play) OS off in BIOS booted into linux, and it worked! i dont know if they are related...but it may be worth a shot jfd118

Unforunately, my PnP Bios option
was already set to "off".

So, it worked with no tweaking?

j

yes....but i this is my linksys card...it was doing the same thing as the netgear though..i did nothing different

is the fa311 the same as the fa312? I wonder if I will have these problems.. I plan on installing mandrake v8 and getting a web server, mail, ftp, etc. going soon..

Hi,

In the event that anyone cares I thought I might
update on my progress to get a fa311 working.

I have tried various things to ensure the
problem is not something other than the card.
My machine is connected to a linksys cable/DSL
router.

So, I
1) switched cables
2) switched router ports
3) moved the NIC to a different
PCI slot

all of which did not improve the extremely
slow transfer rates I am experiencing
(as a refesher I can ping the outside world
but cannot ftp data, for instance)

This morning I did an experient in which I
installed RH6.2 which is what the machine
was running before i installed RH7.1.
Once this was done, I copied the pci_scan.c
and natsemi.c files (from scyld.com) over
from a disk, compilied them per donald's
directions, installed them, insmod'ed them,
set up the network, used ifconfig and route to
configure the network, and mananged to ping
the outside world again.

However, after all this the transfer rate on web pages and ftp files (and even file copied over from /gonzo/s2) was pathetic and netstat -i still indicated signficant packet loss. So, now I am convinced I have a card problem (and am hoping it is not a mother board problem). Needless to say,
I will be buying a new card today.

This is all very interesting to me. I moved
from PA to VA about 2 months ago. Before
the machine was put back in its box everything
was working (i.e. the fa311 ) without problems.
When it came out of the box again after the
move, it was experiencing the above problems.
Nothing strange happened in between.
Oh, well.

Thanks for reading,

jfd118

Hello all,

I had the same open issues with SuSE.
I had fa311 driver on floppy delivered with the card (fa311.o, fa311.c and makfile for redhat)
because that didn't work I downloaded natsemi.c from http://www.scyld.com/network/ethercard.html.
I had the same problems compiling the things.
Now I found the right driver on www.netgear.com.
Without any compilation cp the file to the right position and with "/sbin/insmod natsemi" I started the module. After that I did the hardware configuration of the card.

good luck

Ramon

heh:< im new in Linux, i have VERIZON ONLINE DSL and i try to configure it with NETGEAR FA311 for madnrake 8.0, it finds ethernet card, but it doenst determine what kind of card it is nor it shows it in MADNRAKE CONTROL CENTER. I tried to download your drivers, but im sorry, i dont know how to install it

I would be very thankful if u would reply to the email adress, Leniu@marihuana.com

If you have the fa311.o driver already, just make sure it's under your /lib/modules/ directory. Depending on your kernel version, the directory name may be different, but it should like like: /lib/modules/2.4.8-26mdk/kernel/drivers/net/
Put fa311.o there. While in that directory, gzip the file by typing "gzip fa311.o" Then, edit /etc/modules.conf to add the line "alias eth0 fa311". Then restart your network interface by typing "service network restart".

Thanks for help, I'll try

still... it doesnt work

is your name really willard smythe....
you're kiddin' rit?

Running Redhat 7.2 and using netgears drivers no probs ever. And I am no install expert what so ever. So if I can do it you can too. Not using a shared pci slot are you?


-bigmouse

bigmouse:

*psst!*

>read the dates on the threads before you respond; you've just awakened a perfectly dead 4 month old topic.