• Post Reply Bookmark Topic Watch Topic
  • New Topic

Linksys EtherFast 10/100 PC Card not working  RSS feed

 
Marek Zale
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm running RH 7.1 on Dell Inspiron 4000. All's good, except Linksys PCMPC100 Card. cardmgr recognizes it as NE2000, which I guess is OK, but it never gets initialized. I keep getting "delaying initialization eth0 -- can't read base network address 0x300". I believe this is the address for that card. It's a dual boot machine 'n' the card works under windows. ifconfig shows only localloop, no eth0 at all. I'm new to linux and after about a week of trials I'm sort of out of ideas on that one. I'd really apprieciate any help!
 
Greg Harris
Ranch Hand
Posts: 1012
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
i am having the same problem! i was running RedHat 7.0, but now i have 7.1 on a machine that i built last year. i have the same Linksys card running on a dual (triple, really) boot machine and it works fine with win2000 and win98.
i have installed Samba and configured it correctly as far as running it locally, but it never seems to recognize the network. i am about to start my final exams, so i am not going to put much more effort into this until after december 13. after that i will spend a couple days trying to figure out the network problem.
i will let you know what i find out... (or, let me know if you fix it before then).
 
Guy Allard
Ranch Hand
Posts: 776
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Some thoughts:
I have this card working flawlessly on a Sony Vaio, RH 7.1.
I do get the message 'startup delayed', but it does not say anything about 0X300. What happens is that networking initialization tries to start eth0, but the card manager drivers are not yet up. However on my card manager automatically starts eth0 OK later during the boot.
The card manager stuff uses I/O address 0x300.
Do a 'cat /proc/ioports' to find out what is using that base I/O.
Don't know if this will help, but hope it does ......
Later, Guy
 
Frank Carver
Sheriff
Posts: 6920
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
There's a fairly well-known situation with "plug-n-play" cards when used with Windows and Linux: The card is set to plug-n-play, and Windows aska it to change it's address, but Linux still thinks it is set to the default address.
Check the IO port mappings, interrupts and so on in Windows, then try overriding the defaults in Linux to match the Windows settings. It's not a particularly simple process, but once you have the right module parameters set up, then it should carry on working.
 
Greg Harris
Ranch Hand
Posts: 1012
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
> There's a fairly well-known situation with "plug-n-play" cards when used with Windows and Linux:
leave it to windows to screw things up!
thanks for the tip, Frank.
 
Guy Allard
Ranch Hand
Posts: 776
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Greg - glad you got it going.
The "look at it in Win/device manager" trick is great! *If* Win is on the box.
Otherwise, you need to use some different diagnostic tools.

Regards, Guy
 
Tim Holloway
Saloon Keeper
Posts: 18797
74
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm using LinkSys cards, but I believe that they all use the "tulip" driver, not NE2000.
 
Guy Allard
Ranch Hand
Posts: 776
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Tim - I think that is true for PCI bus cards, but not for PCMCIA cards ..... you should probably check me on that.
Guy

[This message has been edited by Guy Allard (edited November 28, 2001).]
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!