| View previous topic :: View next topic |
| Author |
Message |
adammc
Apprentice
Joined: 07 Oct 2003
Posts: 230
Location: Europe
|
 Posted: Thu Dec 25, 2003 11:02 pm Post subject: PCMCIA Ethernet configuration |
 |
|
A friend of mine got a PCMCIA ethernet card for christmas, and is trying to get it set up. I'm a little confused as to how to get it to work; I'm not even sure if it's been detected correctly. The module for the card (8139too) has been loaded, as has pcmcia_core; however, there is no beep when the card is inserted as there should be.
Any help/guidance would be greatly appreciated.
_________________
There'd better be fudge when I get home... |
|
| Back to top |
|
 |
silverter
Guru
Joined: 10 Apr 2002
Posts: 491
Location: Ulm, DE
|
| Posted: Fri Dec 26, 2003 11:55 am Post subject: |
|
|
What kernel version are you using? The pcmcia setup is different depending on the kernel version you are using.
regards
_________________
-- A Guru was once a Beginner -- |
|
| Back to top |
|
|
adammc
Apprentice
Joined: 07 Oct 2003
Posts: 230
Location: Europe
|
| Posted: Fri Dec 26, 2003 6:12 pm Post subject: |
|
|
he's using 2.4.20-gentoo-r7
in what way is the setup different? I had no problems with that when upgrading my own laptop to 2.6.0...
_________________
There'd better be fudge when I get home... |
|
| Back to top |
|
|
silverter
Guru
Joined: 10 Apr 2002
Posts: 491
Location: Ulm, DE
|
| Posted: Fri Dec 26, 2003 7:55 pm Post subject: |
|
|
| adammc wrote: | | he's using 2.4.20-gentoo-r7 |
Then using the pcmcia documentation at the gento site would suffice to set it up correctly, if the card is getting recognized correctly by the pcmcia-cs tools. Check out the documentation at the gentoo site.
| adammc wrote: | | in what way is the setup different? I had no problems with that when upgrading my own laptop to 2.6.0... |
In 2.4 kernel you use the pcmcia drivers whereas in 2.6 you have to use the kernel pcmcia drivers. For example on my system when I switche from 2.4 to 2.6 I have to stop loading the module i82?? something that I used to load in the 2.4 kernel series; instead I needed to load yenta_soket module. And I still needed to compile the pcmcia-cs utils for my 16 bit network card whereas for my cardbus card it sufficed to used the hotplug system. Those are the difference on my side between 2.4 and 2.6.
HTH
regards,
_________________
-- A Guru was once a Beginner -- |
|
| Back to top |
|
|
adammc
Apprentice
Joined: 07 Oct 2003
Posts: 230
Location: Europe
|
| Posted: Fri Dec 26, 2003 8:58 pm Post subject: |
|
|
I can't seem to find any pcmcia-related docs...are there instructions buried inside another document or something?
_________________
There'd better be fudge when I get home... |
|
| Back to top |
|
|
silverter
Guru
Joined: 10 Apr 2002
Posts: 491
Location: Ulm, DE
|
| Posted: Sat Dec 27, 2003 11:26 am Post subject: |
|
|
| adammc wrote: | | I can't seem to find any pcmcia-related docs...are there instructions buried inside another document or something? |
IIRC it's in the installation guide for x86 under network related. Basically after compilng your kernel you should then issue a | Code: | | rc-update add pcmcia boot |
. *If* your card is detected correctly it should work out of the box, otherwise, there need some tweaking to be done. What is the type of the card again? Not the module getting loaded. What do you get with (you need to be root to run this)?
HTH
regards
_________________
-- A Guru was once a Beginner -- |
|
| Back to top |
|
|
adammc
Apprentice
Joined: 07 Oct 2003
Posts: 230
Location: Europe
|
| Posted: Wed Dec 31, 2003 8:34 pm Post subject: |
|
|
ok...I sorted the problem with getting the card detected by compiling the drivers into the kernel, instead of using modules. This works perfectly, and when plugged into the router the laptop is detected.
however, I am still unable to use the network. I can't give any exact errors, as I'm not at that machine any more, but trying to ping the router results in something like "destination host unreachable". Also, running "route" to list the routing table takes a long time (a lot longer than on my machine).
That is when using manual static config, I also tried DHCP (since the router has this built in) - this causes the rc script to stop at "Bringing up eth0" (presumably waiting for a responce or for a timeout).
I can't see anything wrong with the config, so I'm really confused as to why this doesn't work 
_________________
There'd better be fudge when I get home... |
|
| Back to top |
|
|
FreeFly42
l33t
Joined: 03 Nov 2003
Posts: 848
Location: Houston, TX
|
| Posted: Sat Jan 10, 2004 6:47 pm Post subject: |
|
|
The reason route it taking so long is it is trying to get names for the route points. Try running route -n instead.
Your router should be configured to be on your local network, else I'm not sure you will be able to ping it. You can try adding a static route to it:
route add -host <router-ip-address> eth0
and try to ping it then, but it seems you still have a problem with your driver.
If you know which module should be loaded you can teach pcmcia to recognize your card. Insert the card, and run 'cardctl ident'
You will get something like:
| Code: | Socket 0:
product info: "Wireless Network CardBus PC Card", "Global", "", ""
manfid: 0x0097, 0x8402
Socket 1:
product info: " LEXAR ATA FLASH CARD ", "TWISTER", "TTE01"
manfid: 0x4e01, 0x0200
function: 4 (fixed disk) |
Edit /etc/pcmcia/config and add an entry for your network card in the network section. It should look something like:
| Code: | card "D-Link Systems Texas Instruments ACX 100 22Mbps Wireless Interface"
manfid 0x0097, 0x8402
bind "acx100_pci" |
This entry corresponds to the Wireless card in the ident above. You copy the manfid retrieved from cardctl ident to the manfid line, and add the module name in the "bind" entry. Card is just String to identify the card.
This will let cardmgr automatically insert the proper kernel module, and call the proper /etc/init.d/net script.
_________________
Kent
Planes are dangerous, get out of 'em quick |
|
| Back to top |
|
|
adammc
Apprentice
Joined: 07 Oct 2003
Posts: 230
Location: Europe
|
| Posted: Sun Jan 11, 2004 2:23 pm Post subject: |
|
|
thanks for the help, but after some testing I'm pretty sure the problem is with the card and not the software. I tried the wireless card from my laptop in his laptop, which worked perfectly, and also tried his card in my laptop with the same results as before. I also tried it in a windows laptop to see if it was the driver; the windows machine also had problems using it. he's going to get a replacement card and try that instead; hopefully that'll work 
_________________
There'd better be fudge when I get home... |
|
| Back to top |
|
|
|
Networking & Security
