Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
I have an old 486 - toshiba techra, a square grey box of significant size. I installed debian onto it no problem and seems to be running fine. I want to get the ethernet card (and, very wishfully thinking, the wifi card). They are both pcmcia cards, the ethernet card being and SMC ez pca card 10/100 model SMC8040TX.
I have googled a bit and not been able to find anything. I am sure the card works as I have tried it in another computer. Also when I installed the lights lit up, when I did a previous install I managed to install debian from a netinst image - it went and grabbed everything from the net with no problems. Now that I have the distro installed the card is refusing to work.
ifconfig -a shows only the loop back device, lspcmcia shows nothing and dmesg also shows nothing on insertion.
Can anyone give me a pointer about how to get this setup
Thanks for your replies. Pcmciautils was already installed, I had to install sysfsutils. Modprobing the suggested drivers and a subsequent lsmod confirms that they were installed. Unfortunately the card still isn't showing any life.
After a reboot and modprobing again, dmesg and igconfig -a shows nothing different than previously.
does anyone have any more suggestions that I could try? Since this card installed on this computer with this os on install I have no reason to believe that it won't work
I just wonder if you are running into an issue because the system hardware is so old.. Have you been able to get ANY pcpmcia cards to work in that laptop ?
did you look at the rest of the info in the link I provided in my previous post ?
Quote:
Known problems
applying / removing socket power
These are covered at an extra page:
* cs: pcmcia_socket0: unable to apply power
* cs: pcmcia_socket0: *** DANGER *** unable to remove socket power
Unable to suspend Thinkpad T.22
This Thinkpad does not like us placing the Yenta bridge into PCI D3 state.
cs: unable to map memory
Try issuing
pcmcia-socket-startup
CardBus (sometimes also PCMCIA) cards not found
On several, especially new systems the Yenta bridge is not on the root PCI bridge, but behind a PCI-to-PCI bridge. On some x86 or x86_64 systems, these bridges aren't correctly set up by the BIOS, which may cause CardBus and even PCMCIA devices not to show up in lspci or in pccardctl ident correctly. If you suspect that this may be the cause, issue this command:
Let's decode the first line: bus 0 (primary) is bridged to busses 2 (secondary) to 4 (subordinate) by a bridge. The second and the third line state that bus 2 is bridged to busses 3-6, and 7-10. However, the CPU (which itself is connected to bus 0 through the root bridge) needs to be able to access all these busses. If you try to walk the tree to bus 7, for example, you see that the CPU can't get there, as bus 0 is only bridged to busses 2 to 4.
If this is the case, or you find a message stating "try pci=assign-busses" in the dmesg log, append the following to the kernel boot line:
pci=assign-busses
Additional information, and a proposed workaround can be found at bug #5557.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.