pcmcia network adapter doesn't work
pcmcia network adapter doesn't work
Hello, I've installed Puppy Linux 4.2.1 on an old notebook (compaq armada e500). It works well but I'm not able to connect to the internet. The pcmcia card's model is: superlan by roper pcmcia 100-32 bit. I've installed the module by ndiswrapper and wlan0 is correctly found and configurated (dhcp), but browser doesn't work. If I type ifconfig the last message for wlan0 is Interrupt:11. If I try to ping I've got the following message: Network is unreachable. Have you got any ideas? Thank you. Bye
Do you have an IP address?
Having flicked around on Google, i came across a couple of posts from Suse and another distro. They seemed to think it is the driver. I dont know what chipset is in the card. any clues as to what the chipset is, i am assuming that Puppy doenst pick it up without NDISWRAPPER
Having flicked around on Google, i came across a couple of posts from Suse and another distro. They seemed to think it is the driver. I dont know what chipset is in the card. any clues as to what the chipset is, i am assuming that Puppy doenst pick it up without NDISWRAPPER
Seems likely that Puppy would have a native Linux driver for
that card....if this site is up to date.
http://linux-wless.passys.nl/query_part ... name=Roper
that card....if this site is up to date.
http://linux-wless.passys.nl/query_part ... name=Roper
Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs
First, thank you for your reply. I think is the driver because I've tried to install puppy linux on another old laptop (geo) and internet works well. I haven't written that the pcmcia card is not wireless but ethernet. Do you think that it works if I try to install the driver listed in the web site?
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
ndiswrapper doesn't work very well with ethernet devices, and it's more likely that one of Puppy's native Linux drivers will work better anyway.mo_70 wrote:The pcmcia card's model is: superlan by roper pcmcia 100-32 bit. I've installed the module by ndiswrapper
It would help if you could positively identify the exact model of your PCMCIA card, since this will determine the correct Linux driver. Please run this command -
Code: Select all
pccardctl status
Code: Select all
pccardctl ident
Last edited by tempestuous on Tue 09 Jun 2009, 07:43, edited 1 time in total.
I have 2 slots in my pc, one is empty.
The message of the command 'pccardctl status' is:
Socket 0:
3.3V 32-bit PC Card
Socket 1:
no card
The message of the command 'pccardctl ident' is:
Socket 0:
no product info available
Socket 1:
no product info available
I've extracted the card, the model is:
SUPERLAN BY ROPER PCMCIA 100-32-BIT
No product code available
The message of the command 'pccardctl status' is:
Socket 0:
3.3V 32-bit PC Card
Socket 1:
no card
The message of the command 'pccardctl ident' is:
Socket 0:
no product info available
Socket 1:
no product info available
I've extracted the card, the model is:
SUPERLAN BY ROPER PCMCIA 100-32-BIT
No product code available
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Clearly there's a problem with your PCMCIA interface, and yours is currently one of three problems on the forum concerning PCMCIA interfaces.
I have a suspicion that the fault may be with 4.2.1, but I'm really not sure, and I don't have a copy of 4.2.1 to check.
I suggest you boot with "pci=biosirq".
I have a suspicion that the fault may be with 4.2.1, but I'm really not sure, and I don't have a copy of 4.2.1 to check.
I suggest you boot with "pci=biosirq".
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Good. As I said before, you shouldn't be using ndiswrapper.mo_70 wrote:When I reboot the pc it doesn't keep the interface wlan0 loaded by ndiswrapper
Wow, that's good. Puppy can only create a network interface once it detects your network device.mo_70 wrote:and interface eth0 is loaded again.
I suggest you clear ndiswrapper from the Network Wizard, reboot, and configure the Network Wizard to use the module which it automatically selects. I suspect that will be r8169.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Well a large part of the battle is to recognise the device, load a compatible module, and create a network interface.
Since eth0 exists, you have succeeded to this point.
Now you need to do some diagnosis.
When you run the "dmesg" command, what do you see about how the 8139too module loaded? Does it look OK?
Is your router set up for DHCP? Maybe you need to configure the Network Wizard with a static IP address?
Since eth0 exists, you have succeeded to this point.
Now you need to do some diagnosis.
When you run the "dmesg" command, what do you see about how the 8139too module loaded? Does it look OK?
Is your router set up for DHCP? Maybe you need to configure the Network Wizard with a static IP address?