The natsemi driver included in beta-3 has some problems. The natsemi driver in beta-2 did not have these problems. The network card in question is a Netgear FA-312. All *appears* to work, but when I try to use the card, I get dropped packets without any complaint in dmesg or /var/log/messages. Another network card (w/ tulip driver) in the same machine works without any problems, so I know this is a natsemi driver problem.
This defect is considered MUST-FIX for Florence Gold release
I have purchased one of these cards for testing.
I just bought one, and it seems to work just fine with the Wolverine kernel (and with the current AC kernels).
Ok, I'll mark this one as closed rawhide; ekuns, please reopen if the wolverine kernel doesn't fix it for you.
With Wolverine, this driver still has problems. Intermittent connections, slow connections. I have a natsemi and a tulip network card in the test machine. FTP'ing to kilroy (the machine from which I type this) works perfectly on the tulip card ... but doing so with the natsemi card works on rare occasion for small files, but pulling a kernel over hangs partway through the kernel. I *think* the natsemi driver hung the machine due to my killing the ftp sessions and starting over and over. During this experimentation, my machine hung, locked solid. Yes, when switching from one network device to the other, I swap their network addresses (192.168.1.11 and 192.168.2.11) and the network cable by appropriate means. (Deactivate both, edit both, activate both.) FYI, with my current arrangement of PCI cards, the natsemi card is sharing its IRQ with the two USB devices on the motherboard and with my SCSI card ... but neither is in use with my current test configuration. "/boot" is the only partition on a SCSI device, and I have no USB devices connected.
Forgot to mention ... 46% lost packets on a ping test. With the tulip card, 0% lost packets pinging the same host.
I have 0 packet loss, successful install and no problems... What does the relevant lines of "lspci -v" say?
00:0d.0 Ethernet controller: National Semiconductor Corporation: Unknown device 0020 Subsystem: Netgear: Unknown device f312 Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at a000 [size=256] Memory at df001000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at <unassigned> [disabled] [size=64K] Capabilities: [40] Power Management version 2 It is detected fine, installs fine, but runs poorly.
Can you try the latest kernel from Rawhide?
No luck. With that kernel, I get "destination host unreachable" trying even to ping. Pinging from the other end results in 100% packet loss. And again, swapping eth0/eth1 addresses and then swapping the cable gives me 100% functional connection from both directions. I swapped back and forth several times testing this, identical results each time. Sorry.
I'm also having problems with this card (kern=2.4.2-0.1.28): # ifup eth5 Determining IP information for eth5... eth5: Transmit timed out, status 358a2b60, resetting... eth5: Transmit timed out, status 358a2b60, resetting... # ifconfig eth5 ... RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:4 dropped:0 overruns:0 carrier:0
If you do setpci -d 100b:0020 0x45=0 as root, does the network card start working ?
Did the final release of 7.1 work for you? What about the errata kernel 2.4.3-12?