Next-in-Thread Next Message

Ok Problem Solved! 

Forum: PCMCIA Wireless Network Adapter Issues
Re: Question Wavelan IEEE problems... (Avijit Banerjee)
Re: Sad wvlan_cs vs wavelan2_cs (Jean Tourrilhes)
Re: Feedback Here's more info... (Avijit Banerjee)
Re: None You should not insmod the driver by hand (David Hinds)
Date: 2000, Jun 02
From: Avijit Banerjee avi

> You can't just insmod the wvlan_cs driver.  You have to modify
> /etc/pcmcia/config to indicate that wvlan_cs should be bound >to your

That particular file was fine, it *did* say that the card was bound to the wvlan_cs driver. However, the culprit seems to be a little file in /etc/pcmcia. It's called wavelan2_cs.conf. Upon removal and running /etc/rc.d/rc.pcmcia restart, the card was recognized properly and the driver installed and wvlan0 interface showed up using ifconfig! (sorry for the run-on sentence).

To check that this was indeed the culprit, what I actually did was to rename the wavelan2_cs.conf file (without that .conf part basically) and restarted the card services. Everything worked all peachy. Then I changed the name back to the original and restarted card services. Bingo! I got a high then a low beep.... Then I decided to delete the file altogether, and restart card services, and again, everything was all peachy.

> The way PCMCIA modules work... loading the module by itself has no
> effect.  When a card is inserted, the cardmgr daemon looks it up in
> the config file and tells the PCMCIA subsystem that "card X needs
> driver Y", so when driver Y is loaded, the PCMCIA subsystem tells it
> to deal with card X.

Makes sense.

Thank you to Jean and David for your help! This problem had been perplexing me for a little while now... I should've come here much earlier.

Again, Thank you,


Next-in-Thread Next Message

Add Message to: "Problem Solved!"

Members Subscribe Admin Mode Show Frames Help for HyperNews at 1.10