Red HatThis forum is for the discussion of Red Hat 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.
Well I've given up on the 2635. I got my Orinoco Gold in the mail today, but it appears the support for this card isn't any better. I read so many things say how well this card worked in linux and I'm finding that it doesn't.
sadly, no. literally, the only card I ever stuck in the slot and had come on and work without any intervention from me was a revision 1 d-link dwl-650 (the one with the "axe-head" looking antenna housing sticking out) that I borrowed from a visiting friend just to test. all 4 other wireless pcmcia/cardbus cards I own, (and I'm sure the pci card coming in the mail) required a fair amount of work to get going, but it was a great learning experience and now they all work well.
I ended up with so many different cards for the same reason, I read that they worked w/linux, unfortunately the cards being talked about *did* work until the manufacturer changed the internal chipset, added the new drivers for the chipset to the windows driver cd in the box and still tagged the same model number to it, after all windows users will never know the chipset changed, they'll just stick in the cd and go, we have a different scenario...go to d-link's site and act like you need drivers for a dwl-650, they'll show you a bunch of pictures and ask you to id your card from them, they all got different chipsets and the same freakin' model number!! (this still get's me fired up, heh)
Well thanks for the help guys. I was able to get the Orinoco up and running last night. It took some work and a lot of learning, but it finally works.
I rebuilt the pcmcia services with the beta drivers which in turn broke my network configurator. I ended up needing to use the wvlan_cs module. When I loaded everything manually and restarted the pcmcia service things were ok. So now I need to rebuild the pcmcia service to get it working properly again.
Now my question for you guys is this: (actually 2 ?s)
1.) Because the driver is already built in will I need to do anything else to get the card to work automagically upon booting?
2.) I have wireless at home and at school, therefore I need two profiles for each location. What is the best way to go about this?
Once again, thank you very much for all the help thus far.
if your card is a 16bit model, (ie: not a 32bit cardbus card handled by the hotplug system) then you may be interested in browsing /etc/pcmcia/wireless.opts, wireless.opts has commentary in it on setting up "schemes" invoked via cardctl for a particular card to accomodate using the card in different environments. This may be doing things the hard way, might be worth a look though.
and installed the correct rpms but still am not able to get it up and working.
I am not giving up on WPC11, but want to know if there is any card ut there that will work as soon as i insert it on my laptop with redhat 9?...without tweaking anything..well not as much as i am doing for wpc11?
I get the following error when i do /etc/init.d/network restart
Bringing up interface wlan0: Error for wireless request "Set
Encode" (8B2A) :
SET failed on device wlan0 ; No such device.
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wlan0 ; No such device.
Determining IP information for wlan0...SIOCSIFADDR: No such device
The "no such device" error means just that: the device that the module(driver) is supposed to enable that you're trying to insert into the running kernel does not exist. So, either you're trying to use the wrong module(driver) for that device, or your pcmcia sub-system is not working, which is unlikely with a stock redhat 9 install. Do a search here on your device, I think it's been covered several times.
I just bought a SMC 2635W wirelss card and tried to install it on my Redhat 8.0 (on a Toshiba laptop).
I downloaded the driver for Redhat 8.0 from http://www.admtek.com.tw/download/ADM8211.htm and
installed it (as a Cardbus). But it does not recognize the
card. Then I added the following lines into the file /etc/pcmcia/config:
device "8211"
class "network" module "8211"
and added the following line right after the "Ethernet adapter definitions"
card "SMC 2635W"
manfid 0x1317,0x8201
bind "8211"
Still get no success. At some point though, the network configuration could recognise a network adaptoer at eth1
but I couldn't get any network device to work with it.
I deleted it and tried to add one manually but nothing works. Any help is appreciated!
I just bought a SMC 2635W wirelss card and tried to install it on my Redhat 8.0 (on a Toshiba laptop).
I downloaded the driver for Redhat 8.0 from http://www.admtek.com.tw/download/ADM8211.htm and
installed it (as a Cardbus). But it does not recognize the
card. Then I added the following lines into the file /etc/pcmcia/config:
device "8211"
class "network" module "8211"
and added the following lines right after the "Ethernet adapter definitions"
card "SMC 2635W"
manfid 0x1317,0x8201
bind "8211"
Still no success. At some point though, the network configuration could recognise a network adaptoer at eth1
but I couldn't get any network device to work with it.
I deleted it and tried to add one manually but nothing works. Any help is appreciated!
Before going any further, reboot your machine and use whatever key to get into the bios setup routine, then check the settings for the pcic, do not have it set to "auto" use the other one: something like "16bit pcmcia/cardbus", linux doesn't like that "auto" setting at all.
>Before going any further, reboot your machine and use whatever key to >get into the bios setup routine, then check the settings for the pcic, do not >have it set to "auto" use the other one: something like "16bit >pcmcia/cardbus", linux doesn't like that "auto" setting at all.
After installing ADMtek driver (Install_RH80_103_0304.tar.gz) with miniPCI/PCI option and then again with Cardbus there is a change:
The Network configuration recognizes a new hardware:
I tried to add a new Device (first page of Network Configuration) under eth1 but it cannot bring up eth1.
Also, when I insert the card (and during boot if it is inserted) I get the following:
PCI: Failed to allocate resource 1(ffc00000-ff9fffff) for 05:00.0
PCI: Failed to allocate resource 6(ffc00000-ff9fffff) for 05:00.0
PCI: Enabling device 05:00.0 (0000 -> 0003)
PCI: Unable to reserve mem region #2:ffe00000@ffc00000 for device 05:00.0
Trying to free nonexistent resource <ffc00000-ff9fffff>
PCI: Unable to reserve mem region #2:ffe00000@ffc00000 for device 05:00.0
Trying to free nonexistent resource <ffc00000-ff9fffff>
PCI: Unable to reserve mem region #2:ffe00000@ffc00000 for device 05:00.0
Trying to free nonexistent resource <ffc00000-ff9fffff>
PCI: Unable to reserve mem region #2:ffe00000@ffc00000 for device 05:00.0
Trying to free nonexistent resource <ffc00000-ff9fffff>
PCI: Unable to reserve mem region #2:ffe00000@ffc00000 for device 05:00.0
Trying to free nonexistent resource <ffc00000-ff9fffff>
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.