wireless card can't detect after reboot

hello everyone:
i use damnsmalllinux(the kernel is 2.4.26) in a flash.the
system already contains
the driver prsim2_usb.My wireless card is linksys WUSB11 . 
i add the command: 
    'modprobe prism2_usb prism2_doreset=1'
    'wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable' 
    'wlanctl-ng wlan0 lnxreq_autojoin ssid=default
authtype=opensystem'
    'pump -i wlan0'(the pump is the same as dhcp in
damnsamlllinux)
when the system start ,the wireless card works very well.

But! when reboot the system .the system can't not detect
the device. 
i use lsmod to show the modules. the kenerl don't load the
prism2_usb modules.
so I don't know what's wrong?

And if i disconnect the usb wireless card and plug it .then
start the system .
everything is ok.

Thanks!



_______________________________________________
Linux-wlan-user mailing list
Linux-wlan-userlists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-w
lan-user

Just a thought, have you tried doing an ifstate=disable
before the 
reboot, to see if that makes any difference?

I'm guessing either the USB bus or device isn't being
properly reset on 
reboot, and the WUSB11 is either already in a non-sane state
that it 
isn't coming out of, or is being put there by the
re-addressing being 
done post-warm-boot... the same sort of thing you may have
experienced 
where the WUSB11 detects as simply "USB Device"
under Wi***ws instead of 
being recognized as a network interface.

Check your kernel logs for both cold-start and warm-reboot
USB 
messages-- I'm guessing you might see something like the
following:

[cold boot; good init]
May 26 19:50:36 kardbord kernel: usb 1-2.3: new full speed
USB device 
using uhci_hcd and address 6
May 26 19:50:36 kardbord kernel: usb 1-2.3: configuration #1
chosen from 
1 choice
May 26 19:50:36 kardbord kernel: prism2usb_init:
prism2_usb.o: 0.2.4 Loaded
May 26 19:50:36 kardbord kernel: prism2usb_init: dev_info
is: prism2_usb

[warm boot; storm front comin']
May 26 19:50:36 kardbord kernel: usb 2-1: device descriptor
read/64, 
error -110
May 26 19:50:36 kardbord kernel: usb 2-1: device descriptor
read/64, 
error -110
May 26 19:50:36 kardbord kernel: usb 2-1: new full speed USB
device 
using ohci_hcd and address 3
May 26 19:50:37 kardbord kernel: usb 2-1: device descriptor
read/64, 
error -110
May 26 19:50:37 kardbord kernel: usb 2-1: device descriptor
read/64, 
error -110
May 26 19:50:37 kardbord kernel: usb 2-1: new full speed USB
device 
using ohci_hcd and address 4
May 26 19:50:37 kardbord kernel: usb 2-1: device not
accepting address 
4, error -110
May 26 19:50:37 kardbord kernel: usb 2-1: new full speed USB
device 
using ohci_hcd and address 5
May 26 19:50:37 kardbord kernel: usb 2-1: device not
accepting address 
5, error -110

(That's actually my fried USB 2.0 PCI card crapping out on
me.)

If it is the case that the WUSB11 is failing because it
doesn't like the 
"re-init" being done to it on a warm boot, then
shutting it down with 
ifstate=disable prior to reboot may solve the problem. The 
"prism2_doreset" module parameter can only help
if the system actually 
recognizes the USB device as a Prism2 unit, which it sounds
like yours 
is failing to do... in which case it'll never know it needs
to load that 
module in the first place.

-FeRD

moxsh04st.lzu.edu.cn wrote:
> hello everyone:
> i use damnsmalllinux(the kernel is 2.4.26) in a
flash.the system already contains
> the driver prsim2_usb.My wireless card is linksys
WUSB11 . 
> i add the command: 
>     'modprobe prism2_usb prism2_doreset=1'
>     'wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable' 
>     'wlanctl-ng wlan0 lnxreq_autojoin ssid=default
authtype=opensystem'
>     'pump -i wlan0'(the pump is the same as dhcp in
damnsamlllinux)
> when the system start ,the wireless card works very
well.
>
> But! when reboot the system .the system can't not
detect the device. 
> i use lsmod to show the modules. the kenerl don't load
the prism2_usb modules.
> so I don't know what's wrong?
>
> And if i disconnect the usb wireless card and plug it
.then start the system .
> everything is ok.
>
> Thanks!
>
>
>
> _______________________________________________
> Linux-wlan-user mailing list
> Linux-wlan-userlists.linux-wlan.com
> http://lists.linux-wlan.com/mailman/listinfo/linux-w
lan-user
>
>   
_______________________________________________
Linux-wlan-user mailing list
Linux-wlan-userlists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-w
lan-user

FeRD wrote:

> Just a thought, have you tried doing an ifstate=disable
before the
> reboot, to see if that makes any difference?
>
> I'm guessing either the USB bus or device isn't being
properly reset
> on reboot, and the WUSB11 is either already in a
non-sane state that
> it isn't coming out of, or is being put there by the
re-addressing
> being done post-warm-boot... the same sort of thing you
may have
> experienced where the WUSB11 detects as simply
"USB Device" under
> Wi***ws instead of being recognized as a network
interface.

Apparently there is a firmware problem that inhibits a
proper warm
reset. The problem seems to cause the 2.6 kernel a bit of a
consternation as well. A cold reset is always recommended
with Netgear's
Prism2USB devices. Removing power forces a proper or at
least a decent
reset. Sometimes a hub will power down all the ports when
the system
reboots, which is adequate as well.

This seems to work with 2.4 & 2.6 kernels:

On cold boot:
#!/bin/bash
wlanctl-ng [Prism2USBdevice] lnxreq_ifstate ifstate=disable
sleep 1
wlanctl-ng [Prism2USBdevice] lnxreq_ifstate ifstate=enable
...
continue other configuration stuff...

On warm boot:

 1. disable interface with wlanctl-ng $prism2usbdevice
lnxreq_ifstate
ifstate=disable
 2. unplug prism2usb device
 3. rmmod prism2_usb module
 4. rmmod p80211 module
 5. plug device back in
 6. wait a sec or 2
 7. modprobe prism2_usb (in case hotplug fails to do it)
(might need to
wait a sec after)
 8. disable interface with wlanctl-ng $prism2usbdevice
lnxreq_ifstate
ifstate=disable
 9. enable interface with wlanctl-ng $prism2usbdevice
lnxreq_ifstate
ifstate=enable
10. continue with configuration stuff.

The above was handled here by shell scripts with ugly tk
front ends so
there are buttons to click instead of commandline stuff. It
could also
be handled fairly well with a sigle expect script w/ tk
front end or
expectk script.

Bad antennae and a new wifi router have retired the prism2
devices I have.

==
jd
jdebert_at_garlic_dot_com
_______________________________________________
Linux-wlan-user mailing list
Linux-wlan-userlists.linux-wlan.com
http://lists.linux-wlan.com/mailman/listinfo/linux-w
lan-user