Thread: [Ndiswrapper-general] Dlink DWL-120+ ndiswrapper issues
Status: Beta
Brought to you by:
pgiri
From: Sven <le...@gm...> - 2007-04-07 03:11:37
|
Hi, I've been having a few issues with getting a DWL-120+ (acx100 chipset/USB interface) working properly under ndiswrapper 1.41, under ubuntu edgy. The drivers contain the following files, tiacxusb.sys, tiacxusb.inf and ACX100.bin Upon running ndiswrapper -i on the .inf file, the tiacxusb.sys and tiacxusb.inf file are copied to /etc/ndiswrapper but not the ACX100.bin file, which raises suspicions at least in my mind. I've copied the ACX100.bin file manually to the /etc/ndiswrapper/tiacxusb directory but I doubt it's actually being touched. Anyway - on modprobe ndiswrapper, I get the following kernel output Apr 7 18:51:25 persephone kernel: [17183131.220000] ndiswrapper version 1.41 loaded (smp=no) Apr 7 18:51:25 persephone kernel: [17183131.352000] usb 1-2: reset full speed USB device using uhci_hcd and address 3 Apr 7 18:51:25 persephone kernel: [17183131.516000] ndiswrapper: driver tiacxusb (D-link,08/08/2003,3.0.32.1) loaded Apr 7 18:51:26 persephone kernel: [17183132.368000] wlan0: ethernet device 00:40:05:31:79:95 using NDIS driver: tiacxusb, version: 0x30000, NDIS version: 0x500, vendor: 'D-Link WLAN USB Adapter', 2001:3B00.F.conf Apr 7 18:51:26 persephone kernel: [17183132.368000] wlan0: encryption modes supported: none Apr 7 18:51:26 persephone kernel: [17183132.368000] ndiswrapper (set_scan:1178): scanning failed (003D0BF0) Apr 7 18:51:26 persephone kernel: [17183132.368000] usbcore: registered new driver ndiswrapper iwconfig shows wlan0 present, root@persephone:/etc# iwconfig wlan0 wlan0 IEEE 802.11b ESSID:off/any Mode:Ad-Hoc Frequency:2.437 GHz Cell: Not-Associated Bit Rate:22 Mb/s Tx-Power:0 dBm Sensitivity=0/3 RTS thr:2347 B Fragment thr:2346 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 iwlist fails miserably root@persephone:/etc# iwlist wlan0 scan wlan0 Interface doesn't support scanning : Operation not supported and changes to any iwconfig parameters also fails. root@persephone:/etc# iwconfig wlan0 key open Error for wireless request "Set Encode" (8B2A) : SET failed on device wlan0 ; Invalid argument. root@persephone:/etc# iwconfig wlan0 mode managed root@persephone:/etc# iwconfig wlan0 wlan0 IEEE 802.11b ESSID:off/any Mode:Ad-Hoc Frequency:2.437 GHz Cell: Not-Associated Bit Rate:22 Mb/s Tx-Power:0 dBm Sensitivity=0/3 RTS thr:2347 B Fragment thr:2346 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 root@persephone:/etc# iwconfig wlan0 essid homenet root@persephone:/etc# iwconfig wlan0 wlan0 IEEE 802.11b ESSID:off/any Mode:Ad-Hoc Frequency:2.437 GHz Cell: Not-Associated Bit Rate:22 Mb/s Tx-Power:0 dBm Sensitivity=0/3 RTS thr:2347 B Fragment thr:2346 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 I'm kind of stumped - from a driver level, everything implies that it should be working, except for that it isn't. Does anyone have any suggestions for further places for me to look? Ta Sven |
From: Jonas P. <jon...@xm...> - 2007-04-07 08:26:13
|
Hi Sven, Sven wrote: > I've been having a few issues with getting a DWL-120+ (acx100 chipset/USB > interface) working properly under ndiswrapper 1.41, under ubuntu edgy. > [...] I don't have the same card as you (I'm on a MacBookPro Core2Duo) so this may be utterly irrelevant, but I upgraded to 1.41 yesterday and it stopped working. Backing down to 1.38 worked perfectly again and so did everything since 1.34. (1.30 didn't.) So, from my point of view there seems to be some kind of issue with 1.41. Don't get me wrong here, I think ndiswrapper is an excellent fallback when there is no other option, but I'm really hoping for madwifi to get native support properly working for my hardware. At the moment ndiswrapper will often stop responding about once a day - a reload helps though. On my old system (Asus l5800c) ndiswrapper worked perfectly for many years (including suspend2 for hundreds of cycles)- but obviously with different hardware and a different windows driver. YMMV / Jonas -- Jonas Petersson | XMS Penvision | mailto:Jon...@xm... Box 3294, Västgötegatan 13, S-600 03 Norrköping | http://www.xms.se/ Tel: +46 11 400 13 00 | Dir: +46 11 400 13 05 | Fax: +46 11 10 30 50 |
From: Giridhar P. <pg...@ya...> - 2007-04-07 19:19:10
|
--- Sven <le...@gm...> wrote: > The drivers contain the following files, tiacxusb.sys, tiacxusb.inf and > ACX100.bin Upon running ndiswrapper -i on the .inf file, the tiacxusb.sys > and > tiacxusb.inf file are copied to /etc/ndiswrapper but not the ACX100.bin > file, > which raises suspicions at least in my mind. I've copied the ACX100.bin > file > manually to the /etc/ndiswrapper/tiacxusb directory but I doubt it's > actually > being touched. More details would've helped (e.g., did you have to muck with device ID for it to be initialized). The driver from dlink.com seems to indicate that you need to install both tiacxubt (which installs acx100.bin) and tiacxusb - similar to some atheros usb cards. Install both and at the least attach output file created by ndiswrapper-buginfo Giri ____________________________________________________________________________________ Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html |
From: Giridhar P. <pg...@ya...> - 2007-04-07 19:19:23
|
--- Sven <le...@gm...> wrote: > The drivers contain the following files, tiacxusb.sys, tiacxusb.inf and > ACX100.bin Upon running ndiswrapper -i on the .inf file, the tiacxusb.sys > and > tiacxusb.inf file are copied to /etc/ndiswrapper but not the ACX100.bin > file, > which raises suspicions at least in my mind. I've copied the ACX100.bin > file > manually to the /etc/ndiswrapper/tiacxusb directory but I doubt it's > actually > being touched. More details would've helped (e.g., did you have to muck with device ID for it to be initialized). The driver from dlink.com seems to indicate that you need to install both tiacxubt (which installs acx100.bin) and tiacxusb - similar to some atheros usb cards. Install both and at the least attach output file created by ndiswrapper-buginfo Giri ____________________________________________________________________________________ Be a PS3 game guru. Get your game face on with the latest PS3 news and previews at Yahoo! Games. http://videogames.yahoo.com/platform?platform=120121 |
From: Giridhar P. <pg...@ya...> - 2007-04-07 19:20:34
|
--- Sven <le...@gm...> wrote: > The drivers contain the following files, tiacxusb.sys, tiacxusb.inf and > ACX100.bin Upon running ndiswrapper -i on the .inf file, the tiacxusb.sys > and > tiacxusb.inf file are copied to /etc/ndiswrapper but not the ACX100.bin > file, > which raises suspicions at least in my mind. I've copied the ACX100.bin > file > manually to the /etc/ndiswrapper/tiacxusb directory but I doubt it's > actually > being touched. More details would've helped (e.g., did you have to muck with device ID for it to be initialized). The driver from dlink.com seems to indicate that you need to install both tiacxubt (which installs acx100.bin) and tiacxusb - similar to some atheros usb cards. Install both and at the least attach output file created by ndiswrapper-buginfo Giri ____________________________________________________________________________________ Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. http://answers.yahoo.com/dir/?link=list&sid=396545367 |