I appreciate all help and advice receieved. I recompiled the magical new 2.2._ kernel my friend just gave me and *poof* the driver fought off the linksys demons. It works. Another victory, credited to the unknown mysteries of the black box... --Chris Johnson Adam Rogoyski wrote: > > Hi Chris. What exactly is the problem? You have the card detected and > configured? You wrote way too much in that message. I've got two > machines using the tulip driver without any problems, but I do have > different cards. > > Adam > > On Fri, 9 Apr 1999, Johnson, Christopher M. wrote: > > > Reader beware: > > The linksys card challenge has been before enjoined, but > > the pitfalls are numerous and the rewards dubious. > > > > Many months ago I posted a question about how to get my > > linksys EtherFast 10/100mbit PCI plug'n'pray card to work > > with my linux. Through many agonizing hours of reading > > installation instructions from linksys, resnet, and > > Becker himself, I have arrived at nothing. That's not > > to say that the driver hasn't been correctly installed, > > it has, and that the card *isn't* working, as it talks in > > windoze95, and my helful linux wizard friend and I got it > > to communicate with his box once over spring break while > > in linux. > > > > No, nowadays if the UT network is temporarily down for a few > > minutes to a few hours, my attempts to make my card work are > > likely to blame, as my card wants to stay in 100Mbit mode and > > therefore causes the network much distress, according to the > > network admins who have contacted me (and have physically > > disconnected my system when I left it running and left for a > > few hours). > > > > Additional info: I have upgraded recently to 2.2.1 kernel, > > which actually allowed my card to speak with my friend's > > computer over spring break. We had to configure a route to > > his computer before the pinging would work, and we probably > > did several other things which are lost to my memory now. > > One important fact is that when we had it booting, an extra > > line describing the card's status would appear that doesn't > > appear now (and therefore I can't recall it). As it is now, > > the tulip.c driver line comes up and then an eth0 ... irq > > line comes up, which are correct and fine. But the problem > > is that the card is not talking correctly with the network > > again, and therefore it never gets to the point of doing the > > dhcpcd thing. And it hangs the network. > > > > I'm sending this mail from windows, using the same card and > > the same resnet. I have heard from the resnet info page that > > linksys cards are "notorious;" now I wish that whoever wrote > > that page and/or knows that info would speak with me and help > > me sort this out. > > > > Before I go out this afternoon and get a nice, expensive, 3Com > > or such. Any suggestions (including which new card to buy) > > are appreciated. I know that after reading this, you must > > be ready to rest your eyes and lie down, so I apologize for > > the length. > > > > --Chris Johnson > > At this point, because I'm somewhat still > > unfamiliar with linux, if someone who knows exactly what I'm > > talking about or knows someone who does doesn't come out of > > the woodwork, I need to just get a new card and move on in life. > > Long live the linux revolution, where technical writers and > > documenters are even more poorly paid than the programmers, > > who work for free (and glory). > > --------------------------------------------------------------------------- > > Send administrative requests to [EMAIL PROTECTED] > > --------------------------------------------------------------------------- Send administrative requests to [EMAIL PROTECTED]
