SlackwareThis Forum is for the discussion of Slackware 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 a Cisco Aironet 350 Series PCMCIA wireless card. I just installed Slackware 9 on an old laptop and I can't figure out how to get the wireless card setup. Could anyone either point me to a good place to start or perhaps give a breif eplenation?
Thanks, I wasn't sure if Slack was initiazling the card or not. I've used this card a little under Windows, but for the most part I'm new to wireless networking.
What does "lo no wireless extrension" mean? The card is not picking up any wireless connections?
By the way, would I have to update the firmware for the card to be compatible with Linux?
Pcmcia should intialize the card as long as pcmcia started, which is Slack default on all installs... Is there a pcmcia bus read in "dmesg" at all? It'll look like:
Code:
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Intel PCIC probe: not found.
Databook TCIC-2 PCMCIA probe: not found.
PCI: Assigned IRQ 9 for device 00:0a.0
Yenta IRQ list 0008, PCI irq9
Socket status: 30000010
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x378-0x37f 0x388-0x38f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
hermes.c: 5 Apr 2002 David Gibson <hermes@gibson.dropbear.id.au>
orinoco.c 0.11b (David Gibson <hermes@gibson.dropbear.id.au> and others)
orinoco_cs.c 0.11b (David Gibson <hermes@gibson.dropbear.id.au> and others)
eth0: Station identity 001f:0001:0008:000a
eth0: Looks like a Lucent/Agere firmware version 8.10
eth0: Ad-hoc demo mode supported
eth0: IEEE standard IBSS ad-hoc mode supported
eth0: WEP supported, 104-bit key
It should have registered a device as eth0... if not, post back with the output of:
Socket 0:
product info: "Cisco Systems", "350 Series Wireless LAN Adapter"
manfind: 0x015f, 0x000a
function: 6 (network)
Socket 1:
no product info available
Is there a difference between firmware for Linux and Windows? The card currently has the firmware for Windows flashed into it.
Theoretically no, not as far as I know, if it doesn't even load the card though, this may be an issue with pcmcia instead of the card itself, there's an exact matching bind line in /etc/pcmcia/config:
Code:
card "350 Series Wireless LAN Adapter"
manfid 0x015f, 0x000a
bind "airo_cs"
so its doubtful that there's anything wrong with the card, what's "dmesg" say about it? Also, is Slack happy with other pcmcia cards?
So there is no configuration for an eth1 after that, it looks partially like it succeeded and partly like it failed, the airo_cs module looks to have loaded though, its definately not listed in "/sbin/lsmod"?
Doof, I just did some poking around and evidently you will need to set-up the card with cisco's own utilities the first time out, whcih evidetly doesn't mess with anything on the windows side, you can download the package from here:
Thanks, I'll give that a try as soon as I have time. I should have done that before I even came to this board. Hehe, woops. Well I've learned alot, thanks.
The installer requires the Linux source under /usr/src/Linux.Blah.Blah, but I dont have the source. I didn't install it, and according to the slackware site, the source software set is K. Yet I can't find any set named K on the slack 9 cd. How else could I get the source into my /usr/src dir?
Forget that last post, I got a hold of the source package. But I think the problem with the Cisco driver/utility package is that it's missing a shell script. Has anyone else had any probelms getting the latest Cisco Aironet driver/utility for the 350 installed and working?
In my case, using Windows version of the Cisco ACU, I discovered that the 350 had firmware version 5.02.19. I'm running RedHat 9.0, and it would simply not recognize the card. I downloaded the firmware version 4.25.30 from the cisco website and used the Windows box to downgrade the 350, and now it seems to work fine on Linux. It's not Slackware, but the firmware downgrade might be relevant to all distributions.
In my case, using Windows version of the Cisco ACU, I discovered that the 350 had firmware version 5.02.19. I'm running RedHat 9.0, and it would simply not recognize the card. I downloaded the firmware version 4.25.30 from the cisco website and used the Windows box to downgrade the 350, and now it seems to work fine on Linux. It's not Slackware, but the firmware downgrade might be relevant to all distributions.
Hope this helps,
john
Thanks a lot! That got my Aironet detected on boot. I had a feeling it might be a firmware problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.