LNE100TX and FA311 problems
In short:
I did LFS, wanted my networking to work. I had a linksys LNE100TX that I wanted to do. I found that when I did: insmod tulip ifconfig eth0 up my console generated errors like this, one after another, at the rate of about 30 per second: eth0: (NNN) System Error occured (0) so I took it out and put in my FA311 when I did: insmod natsemi ifconfig eth0 up it generated eth0: PCI error 00800000 and repeated at about the rate of once every two seconds. I would like a solution if possible, or will go and get a 3COM card... ANY suggestions, comments, or questions would be greatly appreciated. (Sorry about the brevity of this, I messed up after writing it the first time and had to write it again in a hurry.) |
Yikes, those are weird errors regardless of card. You might want to try and recompile net-tools. Something wonky might have happened in your LFS build. I kept having seg faults while using "su" until I re-compiled whatever that was in, unix-utils I think. Also, you may want to rake through your kernel config, although I doubt anything that insane would be happening.
Beekman would be the best to query about this, if a straight recompile of net-tools doesn't do the trick, you may want to try re-posting this... man I hate suggesting it, in the LFS sub-forum of Distros, but re-print those errors out verbatim. If its choking on a tulip and a national semi, then it'll probably hork over a golden 3com too. Luck, Finegan |
given up (almost)
I tried the kernel config stuff - spent several hours and made a few kernels (fun stuff eh?), but I am having doubts as to whether or not a recompile of anything would help as I had the same exact problem with Red Hat, but I expect that I will try recompiling too. But, In the mean time I would just like to get the machine on the network, and as I know that the card works reliably, I just want to disable logging, so I am semi-continuing this in the LFS forum.
P.S. sorry for the really late reply, I've been busy. |
All times are GMT -5. The time now is 11:12 AM. |