D-Link DWL -650 vP pcmcia card will not load.
D-Link DWL -650 vP pcmcia card will not load.
Hi,
Very new to Linux and Puppy. I have installed Puppy on a toshiba sattelite
1715. I bought a D-Link DWL 650 pcmcia card and tried to install it using the wizard. No luck, searched the forums and found out that I needed a frimware up date (Thanks tempestuous ) and followed the manual install directions. I instaled the frimware pet for hostap_cs tried to get the card to work,
#Modprobe hostap_cs #as root no messages,
#ifconfig wlan0
#wlan0: unknown interface:No such device.
any places to look at for answers?
Thanks joewilly
Very new to Linux and Puppy. I have installed Puppy on a toshiba sattelite
1715. I bought a D-Link DWL 650 pcmcia card and tried to install it using the wizard. No luck, searched the forums and found out that I needed a frimware up date (Thanks tempestuous ) and followed the manual install directions. I instaled the frimware pet for hostap_cs tried to get the card to work,
#Modprobe hostap_cs #as root no messages,
#ifconfig wlan0
#wlan0: unknown interface:No such device.
any places to look at for answers?
Thanks joewilly
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
The firmware is not an update. It needs to be loaded into the device's onboard RAM each and every time the device is powered up.
After loading the hostap_cs module, a network interface "wlan0" will be created, but this interface is not yet active, and cannot be made active until the firmware is loaded. So these are the commands -
modprobe hostap_cs
hostap_fw_load wlan0
ifconfig wlan0 up
iwconfig wlan0 mode managed
ifconfig wlan0 up
Notice that the interface is brought up twice with "ifconfig wlan0 up". This information was given to me by another forum member who explained that the default mode of the hostap driver is "master" (as an access point). We need to force it into "managed" mode, and this brings down the interface.
I believe an alternative approach would be specify "managed" mode when loading the module (iw_mode=2). So, in theory, this sequence of commands should also work -
modprobe hostap_cs iw_mode=2
hostap_fw_load wlan0
ifconfig wlan0 up
After loading the hostap_cs module, a network interface "wlan0" will be created, but this interface is not yet active, and cannot be made active until the firmware is loaded. So these are the commands -
modprobe hostap_cs
hostap_fw_load wlan0
ifconfig wlan0 up
iwconfig wlan0 mode managed
ifconfig wlan0 up
Notice that the interface is brought up twice with "ifconfig wlan0 up". This information was given to me by another forum member who explained that the default mode of the hostap driver is "master" (as an access point). We need to force it into "managed" mode, and this brings down the interface.
I believe an alternative approach would be specify "managed" mode when loading the module (iw_mode=2). So, in theory, this sequence of commands should also work -
modprobe hostap_cs iw_mode=2
hostap_fw_load wlan0
ifconfig wlan0 up
Hi tempestuous,
trided out the comands you listed
Loaded hostap_frimware pet
loaded hostap_cs in the wireless
#modprobe hostap_cs
no messages
#hostap_fw_load wlan0
Host AP driver data for device wlan not found in procfs
#ifconfig wlan0 up
SIOCGIFFFLAGS: No such device
#iwconfig wlan0 mode managed
ERROR for wireless request "Set Mode" (8B06) :
SET failed on device wlan) : No such device.
#ifconfig wlan0 up
SIOCGIFFFLAGS: No such device
It seems that wlan0 can not be found, any idea of how I messed up?
Thanks
joewilly
trided out the comands you listed
Loaded hostap_frimware pet
loaded hostap_cs in the wireless
#modprobe hostap_cs
no messages
#hostap_fw_load wlan0
Host AP driver data for device wlan not found in procfs
#ifconfig wlan0 up
SIOCGIFFFLAGS: No such device
#iwconfig wlan0 mode managed
ERROR for wireless request "Set Mode" (8B06) :
SET failed on device wlan) : No such device.
#ifconfig wlan0 up
SIOCGIFFFLAGS: No such device
It seems that wlan0 can not be found, any idea of how I messed up?
Thanks
joewilly
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
A number of possibilities.
1. Check if the PCMCIA system recognises your device with these 2 commands -
cardctl status
cardctl ident
If you can't see the card listed, try resetting the PCMCIA interface, as explained here -
http://www.murga-linux.com/puppy/viewto ... 1707#31707
2. You didn't mention what TYPE of installation you have. If it's a full HD install, you may have the all-too-common problem of not being able to access the full set of kernel modules.
WhoDo gave instructions on how to uncompress the zdrv file (modules) here -
http://www.murga-linux.com/puppy/viewto ... 1735#91735
3. There might be one extra step involved: after "modprobe hostap_cs" try "ifconfig wlan0 up"
1. Check if the PCMCIA system recognises your device with these 2 commands -
cardctl status
cardctl ident
If you can't see the card listed, try resetting the PCMCIA interface, as explained here -
http://www.murga-linux.com/puppy/viewto ... 1707#31707
2. You didn't mention what TYPE of installation you have. If it's a full HD install, you may have the all-too-common problem of not being able to access the full set of kernel modules.
WhoDo gave instructions on how to uncompress the zdrv file (modules) here -
http://www.murga-linux.com/puppy/viewto ... 1735#91735
3. There might be one extra step involved: after "modprobe hostap_cs" try "ifconfig wlan0 up"
Last edited by tempestuous on Sun 06 Jul 2008, 13:55, edited 2 times in total.
Hey tempestuous,
Well have some more info. The #cardctl ident and staus came back showing the right card. When I ejected the card the computer froze up in term, had to do a hard boot. I watch as Puppy (2.14) booted up and it found the card identified it as the right one and loaded hostap_cs. When I tried to #hostap_fw_load wlan0 got the device not in procfs error message. I unloaded# hostap_cs using the wizard, I was going to reload it to see if it made a difference, and the computer froze up again, had to hard boot by cycling power.
Physically ejected card and started Puppy, everything work with out freezing the computer, it looks like the card is interfering with my hardware? I did try just using the CD boot and had the same results. I could not mount the zdrv_212.sfs file, were not located on any of the drives, thinking 212 might be a version number I tried 214 also with out success. I plan on downloading the newest stable version of Puppy and try to get every thing working before a HD install. This is a steep cliff I want to thank you for helping a newbie.
Thanks Joe Willy
Well have some more info. The #cardctl ident and staus came back showing the right card. When I ejected the card the computer froze up in term, had to do a hard boot. I watch as Puppy (2.14) booted up and it found the card identified it as the right one and loaded hostap_cs. When I tried to #hostap_fw_load wlan0 got the device not in procfs error message. I unloaded# hostap_cs using the wizard, I was going to reload it to see if it made a difference, and the computer froze up again, had to hard boot by cycling power.
Physically ejected card and started Puppy, everything work with out freezing the computer, it looks like the card is interfering with my hardware? I did try just using the CD boot and had the same results. I could not mount the zdrv_212.sfs file, were not located on any of the drives, thinking 212 might be a version number I tried 214 also with out success. I plan on downloading the newest stable version of Puppy and try to get every thing working before a HD install. This is a steep cliff I want to thank you for helping a newbie.
Thanks Joe Willy
Hi all,
I re install Win 98 and the drivers for the D Link card. It worked so the card and interface should be good. Rebooted toshiba satellite 1715 with Puppy 2.16 live CD, no luck on getting the the card to work. Right now I am using a Netopia 3D Reach USB worked right out of the box with driver rt2570 and the wizard. I plan to down load some pets and then wok some more on the D Link card. I wanted to learn Linux I am going to do some reading and see if I can get an idea. tempestuous I really thank you for your help if you can think of anything I should do I would be very thankful.
Joewilly
I re install Win 98 and the drivers for the D Link card. It worked so the card and interface should be good. Rebooted toshiba satellite 1715 with Puppy 2.16 live CD, no luck on getting the the card to work. Right now I am using a Netopia 3D Reach USB worked right out of the box with driver rt2570 and the wizard. I plan to down load some pets and then wok some more on the D Link card. I wanted to learn Linux I am going to do some reading and see if I can get an idea. tempestuous I really thank you for your help if you can think of anything I should do I would be very thankful.
Joewilly
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
The DWL-650 Rev.P card definitely contains the Prism3 SSF chipset, supported by hostap_cs.
Forum member iscove reported success with this device/driver combintation here -
http://www.murga-linux.com/puppy/viewtopic.php?t=14249
and from his results, I revised the hostap-firmware.pet package.
... but maybe I missed a few files. I will check shortly.
Forum member iscove reported success with this device/driver combintation here -
http://www.murga-linux.com/puppy/viewtopic.php?t=14249
and from his results, I revised the hostap-firmware.pet package.
... but maybe I missed a few files. I will check shortly.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Well I just checked my hostap-firmware.pet package and all files seem to be correct.
/proc/net/hostap/wlan0/
but it appears that this is not happening.
I suggest you first use Rox to browse and confirm that this directory does not exist.
If true, try to run the command "cardmgr" and see if that creates the directory.
If successful, now you can try the main commands again.
This is our problem. When the PCMCIA system launches, it should read /etc/pcmcia/hostap_cs.conf and create this directory -joewilly wrote:#hostap_fw_load wlan0
Host AP driver data for device wlan not found in procfs
/proc/net/hostap/wlan0/
but it appears that this is not happening.
I suggest you first use Rox to browse and confirm that this directory does not exist.
If true, try to run the command "cardmgr" and see if that creates the directory.
If successful, now you can try the main commands again.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Re: D-Link DWL -650 vP pcmcia card will not load.
I see what might have gone wrong -
or hostap-firmware.pet from http://dotpups.de/dotpups/Wifi/drivers- ... 2-to-2.14/
"hostap-extras.pup" is ONLY for versions of Puppy earlier than 2.12. The utilities are in conflicting locations to those of recent Puppy versions, and the firmware is in a slightly different location. I will probably remove this dotpup soon.
In recent versions of Puppy you MUST use hostap-firmware.pet. Make sure that these files exist -
/etc/pcmcia/hostap_cs.conf
/etc/pcmcia/PM010102.HEX
/etc/pcmcia/RF010802.HEX
And also make sure that this file DOES NOT EXIST -
/usr/local/bin/hostap_fw_load
If it does exist, delete it.
Did you install hostap-extras.pup from http://dotpups.de/dotpups/Wifi/wifi-driver-firmware/joewilly wrote:I installed the firmware pet for hostap_cs
or hostap-firmware.pet from http://dotpups.de/dotpups/Wifi/drivers- ... 2-to-2.14/
"hostap-extras.pup" is ONLY for versions of Puppy earlier than 2.12. The utilities are in conflicting locations to those of recent Puppy versions, and the firmware is in a slightly different location. I will probably remove this dotpup soon.
In recent versions of Puppy you MUST use hostap-firmware.pet. Make sure that these files exist -
/etc/pcmcia/hostap_cs.conf
/etc/pcmcia/PM010102.HEX
/etc/pcmcia/RF010802.HEX
And also make sure that this file DOES NOT EXIST -
/usr/local/bin/hostap_fw_load
If it does exist, delete it.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Hi all,
I checked the files and all three files were there, the one file in /user/localwas not there. I ran dmesg after # modprobe hostap_cs and got alot information. It is rather long but here are the messages about the card.
pccard: PCMCIA card inserted into slot 0
cs: memory probe 0xa0000000-0xa0ffffff: clean.
pcmcia: registering new device pcmcia0.0
ieee80211_crypt: registered alogrithm 'NULL'
hostap_cs: 04.4.-kernel (Jouni Malinen <jkmaline@cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
Checking CFTABLE_ENTRY 0X01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0047, io.base=0x0000. len=128
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: , irq3, io 0x0200-0x027f
wifi0: init command completed too quickley - retrying
wifi0: __hfa384x_cmd_no_wait(6) - timeout- reg=0x816c
hostap_cs: first command failed - aussming card does not have primary firmware
prism2_hw_init: initialized in 10 ms
wifi0: prism2_enable_aux_port -timeout-reg=0x816c
wifi0: prism2_enable_aux_port -timeout-reg=0x9108
wifi: valid PDA not found
SWSUPPORTED write/read failed: FFFF ! =8A32
hostap_cs: Initialization failed
prism2_config () failed
hostap_cs: probe of 0.0 failed with error 1
Joe Willy
I checked the files and all three files were there, the one file in /user/localwas not there. I ran dmesg after # modprobe hostap_cs and got alot information. It is rather long but here are the messages about the card.
pccard: PCMCIA card inserted into slot 0
cs: memory probe 0xa0000000-0xa0ffffff: clean.
pcmcia: registering new device pcmcia0.0
ieee80211_crypt: registered alogrithm 'NULL'
hostap_cs: 04.4.-kernel (Jouni Malinen <jkmaline@cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
Checking CFTABLE_ENTRY 0X01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0047, io.base=0x0000. len=128
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: , irq3, io 0x0200-0x027f
wifi0: init command completed too quickley - retrying
wifi0: __hfa384x_cmd_no_wait(6) - timeout- reg=0x816c
hostap_cs: first command failed - aussming card does not have primary firmware
prism2_hw_init: initialized in 10 ms
wifi0: prism2_enable_aux_port -timeout-reg=0x816c
wifi0: prism2_enable_aux_port -timeout-reg=0x9108
wifi: valid PDA not found
SWSUPPORTED write/read failed: FFFF ! =8A32
hostap_cs: Initialization failed
prism2_config () failed
hostap_cs: probe of 0.0 failed with error 1
Joe Willy
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
This looks OK. The error messages relate to the fact that your device does not yet have firmware loaded.
The next step will be the important one. After "modprobe hostap_cs" do this -
ifconfig wlan0 up
hostap_fw_load wlan0
dmesg
and report the output.
If you get some sort of error message that wlan0 does not exist, you could try instead -
hostap_fw_load wifi0
since I see in your dmesg output that the "wifi0" interface seems to have been created. It's a longshot, because I think that "wifi0" is a virtual interface, not the true interface.
The next step will be the important one. After "modprobe hostap_cs" do this -
ifconfig wlan0 up
hostap_fw_load wlan0
dmesg
and report the output.
If you get some sort of error message that wlan0 does not exist, you could try instead -
hostap_fw_load wifi0
since I see in your dmesg output that the "wifi0" interface seems to have been created. It's a longshot, because I think that "wifi0" is a virtual interface, not the true interface.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
I just discovered the problem -
http://hostap.epitest.fi/bugz/show_bug.cgi?id=197
the pci id's for the hostap_cs module in the kernel source code are wrong.
So I just compiled the fixed version of the module, compatible with Puppy 2.17 up.
I also patched the driver to support packet injection with aircrack, and included the other hostap variants, too.
The firmware loading command still needs to be run -
EDIT: this is for Puppy 2.17 ONLY.
For Puppy 3.x see here -
http://www.murga-linux.com/puppy/viewto ... 918#144291
Puppy4 should be OK.
http://hostap.epitest.fi/bugz/show_bug.cgi?id=197
the pci id's for the hostap_cs module in the kernel source code are wrong.
So I just compiled the fixed version of the module, compatible with Puppy 2.17 up.
I also patched the driver to support packet injection with aircrack, and included the other hostap variants, too.
The firmware loading command still needs to be run -
Code: Select all
hostap_fw_load wlan0
For Puppy 3.x see here -
http://www.murga-linux.com/puppy/viewto ... 918#144291
Puppy4 should be OK.
- Attachments
-
- hostap_cs-k2.6.21.5-aircrack.pet
- for Puppy 2.17 ONLY
- (133.6 KiB) Downloaded 424 times
Last edited by tempestuous on Fri 09 May 2008, 07:10, edited 1 time in total.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
The hostap-utilities are also needed.
- Attachments
-
- hostap-utils-0.4.7.pet
- (46.4 KiB) Downloaded 450 times