Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi there - thanks for all of your help so far.
I try to answer all of your questions as good as I can:
* Kind of card:
Netgear FA411 10/100 16-bit pcmcia ethernet card (recommended driver: pcnet_cs or 8310 module)
* What shows ifconfig:
loopback device (lo) only - no eth0
* What shows dmesg (thx for assistance for this command) - as there is no eepro or eth0 entry I try to give you hopefully other (strange) relevant boot messages:
...
PCI: PCI BIOS revision 2.10 entry at 0xfd8a0
PCI: Using configuration type 1
PCI: Probing PCI hardware
...
scsi: <fdomain> Detection failed (no card)
NCR53c406a: no available ports found
sym53c416.c: Version 1.0.0
Failed initialization of WD-7000 SCSI card!
IBM MCA SCSI: Version 3.2
IBM MCA SCSI: No Microchannel-bus present --> Aborting.
This machine does not have any IBM MCA-bus
or the MCA-Kernel-support is not enabled!
...
3w-xxxx: tw_findcards(): No cards found.
...
Intel PCIC probe:
Cirrus PD6729 rev 00 PCI-to-PCMCIA at slot 00:13, port 0x3e0
host opts [0]: [ring] [1/6/16] [1/20/16]
host opts [1]: [ring] [1/6/16] [1/20/16]
ISA irqs (default) = 3,4,5,7,9,10,12 polling interval = 1000 ms
cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x3b8-0x3e7 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0x0d0000-0x0dffff: clean.
Originally posted by trickykid Have you checked out any of the howto's at www.tldp.org for any information that help you ?
yeah, cause as far as i know, redhat doesn't like to auto-detect pcmcia nics. i had to set mine up manually back in the days when i used redhat. you might wanna check your sys init scripts in /etc/rc.d
Yes, I read both HOWTOs many times, but unfortunately I couldn't find help.
Because of the many errors while booting (unfortunately I don't really understand what they mean) I guess that the failure is much closer to thy system (init).
Maybe I should set up my laptop new - with the pcmcia-card plugged in (if there is something like a "autodetect" during setup).
Debian, which I think it still uses 2.2.x kernel. You need to check if your card is supported within the system. If it is not, probably you have to upgrade your current kernel and refer to the pcmcia-howto for more config options.
This could be true because on one of my 3 laptos I use a 2.0.38 kernel.
But on the other 2 laptops I use 2.2.19 which shouldn't have problems with eth0.
On the other hand a "linux-on-a-floppy-disk" (tomsrtbt) I tried works perfect (eth0, dhcp).
So I guess I have a basic problem (how to define/install the eth0 interface) which most other linux user still have soved.
I'm close to give up to connect a computer to a LAN with linux (and switch after one year playing with linux back to Window$)
Straight modprobing of a pcmcia module doesn't work as cardmgr needs to know to bind it to pcmcia_core, and through that, the kernel.
If this is Debian 2.2r4 or 5 you're looking at about pcmcia-cs 3.30? right? Also, don't switch to RH or SuSe as they switched to in-kernel pcmcia and yenta_socket doesn't work well (or at all) with those old 16-bit cirrus bridges.
This may sound like voodoo, but after the machine is running, upon card insertion, does the machine make 2 identical beeps, or one beep and a low toned bonk? The first means something is bound to the card, the second means cardmgr saw a card there (there can be silence), but failed to load the right thing.
My guess is you've got a beep-bonk situation and a goofy network card, which probably means we'll just tweak /etc/pcmcia/config or get a newer pcmcia-cs. What is the dmesg right after you insert the card?
Hi Finegan - you are the guide trough my darkness - you give me new hope.
All your guesses are right:
* I have the beep-bonk situation - to say it more accurate I have a silence-bonk tone while inserting my card
* A closer look to my /etc/pcmcia/config doesn't show a Netgear FA411 card
* I run pcmcia-cs-3.1.22 (deb-package) and there is a newer version (3.1.33) in the net
So 3 questions occure:
* Does it mean anything if I have one bonk-tone only (no beep first)?
* How can I "tweak" /etc/pcmcia/config (that for I would need foolproof instructions)
* I tried to install pcmcia-cs-3.1.33 but as it depends on a newer perl-version I have problems to install all necessary deb-packages (the old perl can't be removed) - but this seems to be my weekend-game
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.