I can only give observations I'm afraid, and hope they pan out. One, is that the most up to date pcmcia-cs is 3.1.29, and two is that my dlink uses prism2 which I had to dig around to find, since it wasn't part of the official pcmcia-cs package. On that line, it assigns it to eth1 instead of wlan0? My dlink isn't 'wavelan' but it still takes a wlan0 name (though I presume this is the drivers doing) - seems to me that most if not all wireless cards would attempt to assign it to that, presuming it's "wireless lan" as eth is "ethernet". A problem I often run into is that rebuilding the pcmcia source likes to overwrite my config - which has some custom options since it never seems to acknowledge the existance of the majority of my cards! I often have to "cardctl ident" to get the manfid and throw the appropriate driver in the config file. -Martin -- Subscription/unsubscription/info requests: send e-mail with subject of "subscribe", "unsubscribe", or "info" toWear-Hard Mailing List Archive (searchable): http://wearables.blu.org please, Please, *PLEASE* don't subscribe through a forward/false domain
From Wear-Hard Mailing list Archive (WH)
Maintained by R. Paul McCarty
Archive created with babymail