w35und driver unusable
hello, I'm trying to run Slackware-current on my AMTEK T700 UMPC box. and from:
http://ubuntuforums.org/showthread.php?t=664458
I know that the my box's wifi is WinBound's products.
I'm currently running kernel 2.6.28.7 now and have modprobed w35und. and I also have a linksys usb wireless card on the USB port.
Now, the situation is Linksys's card can just work well. and the Winbound card can't .
wlan1 is the WinBound card:
root@t700:~# dmesg |grep wlan1 udev: renamed network interface wlan0 to wlan1 ADDRCONF(NETDEV_UP): wlan1: link is not ready
root@t700:~# iwlist wlan1 scan wlan1 No scan results
root@t700:~# iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:1B:FC:7E:57:51
ESSID:"default"
Mode:Master
Channel:5
Frequency:2.432 GHz (Channel 5)
Quality=56/100 Signal level:-22 dBm
Encryption key:off
IE: Unknown: 000764656661756C74
IE: Unknown: 010882848B968C929824
IE: Unknown: 030105
IE: Unknown: 0406000200000000
IE: Unknown: 2A0100
IE: Unknown: 3204B048606C
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=00000035772ec17e
Extra: Last beacon: 52ms agodoes this mean that the winbound drivers in the kernel tree is not ready for use ? or do we have any idea for make it work ?
Quoted 42 lines · luoyi
hello, I'm trying to run Slackware-current on my AMTEK T700 UMPC box. and from:
http://ubuntuforums.org/showthread.php?t=664458
I know that the my box's wifi is WinBound's products.
I'm currently running kernel 2.6.28.7 now and have modprobed w35und. and I also have a linksys usb wireless card on the USB port.
Now, the situation is Linksys's card can just work well. and the Winbound card can't .
wlan1 is the WinBound card:
root@t700:~# dmesg |grep wlan1 udev: renamed network interface wlan0 to wlan1 ADDRCONF(NETDEV_UP): wlan1: link is not readyroot@t700:~# iwlist wlan1 scan wlan1 No scan resultsroot@t700:~# iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 00:1B:FC:7E:57:51 ESSID:"default" Mode:Master Channel:5 Frequency:2.432 GHz (Channel 5) Quality=56/100 Signal level:-22 dBm Encryption key:off IE: Unknown: 000764656661756C74 IE: Unknown: 010882848B968C929824 IE: Unknown: 030105 IE: Unknown: 0406000200000000 IE: Unknown: 2A0100 IE: Unknown: 3204B048606C Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Extra:tsf=00000035772ec17e Extra: Last beacon: 52ms ago
Quoted 2 lines
does this mean that the winbound drivers in the kernel tree is not ready for use ? or do we have any idea for make it work ?
The driver is known to be broken in 2.6.28. You might want to try out 2.6.29-rc8 which carries fixes for the driver. Note that the driver is in the staging directory which means it is not of production quality.
Hi!
Quoted 40 lines
Quoted 40 lines
http://ubuntuforums.org/showthread.php?t=664458
I know that the my box's wifi is WinBound's products.
I'm currently running kernel 2.6.28.7 now and have modprobed w35und. and I also have a linksys usb wireless card on the USB port.
Now, the situation is Linksys's card can just work well. and the Winbound card can't .
wlan1 is the WinBound card:
root@t700:~# dmesg |grep wlan1 udev: renamed network interface wlan0 to wlan1 ADDRCONF(NETDEV_UP): wlan1: link is not readyroot@t700:~# iwlist wlan1 scan wlan1 No scan resultsroot@t700:~# iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 00:1B:FC:7E:57:51 ESSID:"default" Mode:Master Channel:5 Frequency:2.432 GHz (Channel 5) Quality=56/100 Signal level:-22 dBm Encryption key:off IE: Unknown: 000764656661756C74 IE: Unknown: 010882848B968C929824 IE: Unknown: 030105 IE: Unknown: 0406000200000000 IE: Unknown: 2A0100 IE: Unknown: 3204B048606C Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Extra:tsf=00000035772ec17e Extra: Last beacon: 52ms ago
Quoted 6 lines
Quoted 2 lines
does this mean that the winbound drivers in the kernel tree is not ready for use ? or do we have any idea for make it work ?
The driver is known to be broken in 2.6.28. You might want to try out 2.6.29-rc8 which carries fixes for the driver. Note that the driver is in the staging directory which means it is not of production quality.
Winbond driver only supports channel 1, for now.
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Wow, thanks for your advice. and I can get it work now after I set my wireless AP's channel to 1 and mode to "b/g auto".
3 problems:
1. it can only work with 802.11b mode
2. rmmod w35und
modprobe w35und
Kernel Panic
3. after it get IP address with dhcpcd, if I execute iwlist scan, then it will lose the connection and never restore again, the only way make it work again is to restart my computer.
2009/3/17 Pavel Machek <[email protected]>:
Quoted 3 lines
Winbond driver only supports channel 1, for now.
Pavel
Hi!
Quoted 3 lines · luoyi
2. rmmod w35und
modprobe w35und
Kernel Panic
Can you please post the exact oops so we can figure out what is going on? Sandro, can you see this as well?
A message that is not in the archive (sent off-list or not yet received): [email protected]
just rmmod and modprobe it will trigger the oops.
I've just upload a oops snapshot picture onto flickr:
http://www.flickr.com/photos/21260339@N03/3364812089/
hope it will help for you.
2009/3/18 Pekka Enberg <[email protected]>:
Quoted 25 lines
Hi!
(off-list)
Quoted 7 lines · luoyi
Wow, thanks for your advice. and I can get it work now after I set my wireless AP's channel to 1 and mode to "b/g auto".
3 problems:
1. it can only work with 802.11b mode
Quoted 7 lines
2. rmmod w35und
modprobe w35und
Kernel Panic3. after it get IP address with dhcpcd, if I execute iwlist scan, then it will lose the connection and never restore again, the only way make it work again is to restart my computer.
Just to let you know, I am traveling right now and dont have my laptop with me. I wont be able to look at the issues until next week but please do post the oops as requested in the other email so other people can take a look at it meanwhile.
Hi!
Quoted 7 lines · luoyi
just rmmod and modprobe it will trigger the oops.
I've just upload a oops snapshot picture onto flickr:
http://www.flickr.com/photos/21260339@N03/3364812089/
hope it will help for you.
Can you try this patch, please?
Quoted 1 line
From
727c633f7ac374261752b269ee77c007bd55a527Mon Sep 17 00:00:00 2001
From: Pekka Enberg <[email protected]>
Date: Mon, 23 Mar 2009 10:17:36 +0200
Subject: [PATCH] w35und: unregister device from the ieee80211 stack upon ->disconnect()
This patch fixes an oops when the w35und module is removed from the kernel and added back.
--- drivers/staging/winbond/wbusb.c | 9 +++++++-- 1 files changed, 7 insertions(+), 2 deletions(-)
drivers/staging/winbond/wbusb.c +7 -2
@@ -386,7 +386,7 @@ static int wb35_probe(struct usb_interface *intf, const struct usb_device_id *idif (err) goto error_free_hw; -usb_set_intfdata (intf, priv); +usb_set_intfdata (intf, dev);return 0 ;
@@ -415,10 +415,15 @@ static void wb35_hw_halt(struct wbsoft_priv *adapter)static void wb35_disconnect (struct usb_interface *intf) { -struct wbsoft_priv *priv =usb_get_intfdata (intf); +struct ieee80211_hw *hw =usb_get_intfdata (intf); +struct wbsoft_priv *priv = hw->priv;wb35_hw_halt (priv); +ieee80211_stop_queues (hw); +ieee80211_unregister_hw (hw); +ieee80211_free_hw (hw); +usb_set_intfdata (intf,NULL );usb_put_dev (interface_to_usbdev (intf)); }
Signature · 1 line
1.5.4.3