Re: urtw0: could not allocate USB transfers
On 03/03/11 02:45 AM, Hans Petter Selasky wrote: I forwarded this thread on -current. Please also find below a stack trace produced with option KDB_UNATTENDED for the rt28700 driver (if_rt28700). On another side note, I have not being able to load the runfw firmware module anymore after having updated the src tree for 8.2-STABLE ? $ sudo kldload /boot/kernel/runfw.ko kldload: can't load /boot/kernel/runfw.ko: Exec format error Here is your real error in dmesg: KLD runfw.ko: depends on firmware - not available or version mismatch linker_load_file: Unsupported file type You need to kldload firmware.ko or make sure 'device firmware' is in your kernel config. Hi, Many thanks. This explains the change of behavior attempting to kldload runfw.ko without the firmware assist module. :) However I find strange that run(4) requires such a firmware to be preloaded when the rt2870 driver doesn't require it! Cheers, Maybe that's due to a missing MODULE_DEPEND() line in the .c file of urtw0. --HPS Hi, Thanks for the input. I realize the urtw(4) and the pseudo rt2870 drivers may be missing a MODULE_DEPEND macro but this issue is not as annoying than the repeated page faults happening when the card is trying to reassociate itself with a router. I also noticed the same (random) page faults with the run(4) driver as well but since I don't use a driver requiring a external firmware to be loaded, I would prefer fixing the errors in the generic wireless code happening unconditionally with run(4), rt2870, and possibly urtw(4). Plus, a external firmware seems not necessary for using at least the TEW-644UB wireless adapter! Cheers, Etienne -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: urtw0: could not allocate USB transfers
On Thursday 03 March 2011 12:26:20 Etienne Robillard wrote: On 03/03/11 02:45 AM, Hans Petter Selasky wrote: I forwarded this thread on -current. Please also find below a stack trace produced with option KDB_UNATTENDED for the rt28700 driver (if_rt28700). On another side note, I have not being able to load the runfw firmware module anymore after having updated the src tree for 8.2-STABLE ? $ sudo kldload /boot/kernel/runfw.ko kldload: can't load /boot/kernel/runfw.ko: Exec format error Here is your real error in dmesg: KLD runfw.ko: depends on firmware - not available or version mismatch linker_load_file: Unsupported file type You need to kldload firmware.ko or make sure 'device firmware' is in your kernel config. Hi, Many thanks. This explains the change of behavior attempting to kldload runfw.ko without the firmware assist module. :) However I find strange that run(4) requires such a firmware to be preloaded when the rt2870 driver doesn't require it! Cheers, Maybe that's due to a missing MODULE_DEPEND() line in the .c file of urtw0. --HPS Hi, Thanks for the input. I realize the urtw(4) and the pseudo rt2870 drivers may be missing a MODULE_DEPEND macro but this issue is not as annoying than the repeated page faults happening when the card is trying to reassociate itself with a router. Hi, Could you re-point me at one of those page faults, like DDB backtrace? You are using 9-current? --HPS I also noticed the same (random) page faults with the run(4) driver as well but since I don't use a driver requiring a external firmware to be loaded, I would prefer fixing the errors in the generic wireless code happening unconditionally with run(4), rt2870, and possibly urtw(4). Plus, a external firmware seems not necessary for using at least the TEW-644UB wireless adapter! Cheers, Etienne ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: urtw0: could not allocate USB transfers
On Thursday, March 03, 2011 12:26:20 Etienne Robillard wrote: On 03/03/11 02:45 AM, Hans Petter Selasky wrote: I forwarded this thread on -current. Please also find below a stack trace produced with option KDB_UNATTENDED for the rt28700 driver (if_rt28700). On another side note, I have not being able to load the runfw firmware module anymore after having updated the src tree for 8.2-STABLE ? $ sudo kldload /boot/kernel/runfw.ko kldload: can't load /boot/kernel/runfw.ko: Exec format error Here is your real error in dmesg: KLD runfw.ko: depends on firmware - not available or version mismatch linker_load_file: Unsupported file type You need to kldload firmware.ko or make sure 'device firmware' is in your kernel config. Hi, Many thanks. This explains the change of behavior attempting to kldload runfw.ko without the firmware assist module. :) However I find strange that run(4) requires such a firmware to be preloaded when the rt2870 driver doesn't require it! Cheers, Maybe that's due to a missing MODULE_DEPEND() line in the .c file of urtw0. --HPS Hi, Thanks for the input. I realize the urtw(4) and the pseudo rt2870 drivers may be missing a MODULE_DEPEND macro but this issue is not as annoying than the repeated page faults happening when the card is trying to reassociate itself with a router. urtw(4) has no firmware, run(4) has the appropriate depend line. The rt2870 driver is not in-tree, contact the maintainter. I also noticed the same (random) page faults with the run(4) driver as well but since I don't use a driver requiring a external firmware to be loaded, I would prefer fixing the errors in the generic wireless code happening unconditionally with run(4), rt2870, and possibly urtw(4). Plus, a external firmware seems not necessary for using at least the TEW-644UB wireless adapter! You should by now have noticed that you can't use a Realtek driver with a Ralink chipset, or the other way around. So please stop calling both broken in one mail. Also, again, the rt2870 driver isn't in-tree, contact the maintainer. -- Bernhard ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: urtw0: could not allocate USB transfers
On 03/03/11 06:42 AM, Hans Petter Selasky wrote: On Thursday 03 March 2011 12:26:20 Etienne Robillard wrote: On 03/03/11 02:45 AM, Hans Petter Selasky wrote: I forwarded this thread on -current. Please also find below a stack trace produced with option KDB_UNATTENDED for the rt28700 driver (if_rt28700). On another side note, I have not being able to load the runfw firmware module anymore after having updated the src tree for 8.2-STABLE ? $ sudo kldload /boot/kernel/runfw.ko kldload: can't load /boot/kernel/runfw.ko: Exec format error Here is your real error in dmesg: KLD runfw.ko: depends on firmware - not available or version mismatch linker_load_file: Unsupported file type You need to kldload firmware.ko or make sure 'device firmware' is in your kernel config. Hi, Many thanks. This explains the change of behavior attempting to kldload runfw.ko without the firmware assist module. :) However I find strange that run(4) requires such a firmware to be preloaded when the rt2870 driver doesn't require it! Cheers, Maybe that's due to a missing MODULE_DEPEND() line in the .c file of urtw0. --HPS Hi, Thanks for the input. I realize the urtw(4) and the pseudo rt2870 drivers may be missing a MODULE_DEPEND macro but this issue is not as annoying than the repeated page faults happening when the card is trying to reassociate itself with a router. Hi, Could you re-point me at one of those page faults, like DDB backtrace? You are using 9-current? --HPS Hi, Thanks for the feedback. It seems to affect unconditionally at least run(4) and rt2870 which isn't in the src tree yet. I copy-paste below a full dmesg output showing the requested backtrace. Also on Linux, its possible to force modules using a external firmware to not being built as a module. Would it be possible to add a similar option to /etc/src.conf to prevent building modules requiring a external firmware such as run(4) when building the kernel ? Waiting on WCTRL with the following non-sleepable locks held: exclusive sleep mutex rt28700_com_loc (rt28700_com_loc) r = 0 (0xff8001466018) locked @ net80211/ieee80211_node.c:653 KDB: stack backtrace: #0 0x804e0da0 at kdb_backtrace+0x60 #1 0x804effec at _witness_debugger+0x2c #2 0x804f1672 at witness_warn+0x322 #3 0x8047a85d at _cv_wait+0x6d #4 0x80400e73 at usbd_do_request_flags+0x4f3 #5 0x8102e0cb at rt2870_io_vendor_req+0x9b #6 0x8102e232 at rt2870_io_mac_write_multi+0x52 #7 0x8102e2ac at rt2870_io_mac_write+0x1c #8 0x81032f2d at rt2870_newassoc+0x12d #9 0x805893d2 at sta_newstate+0x5a2 #10 0x81039a7d at rt2870_vap_newstate+0x4d #11 0x805817a1 at ieee80211_newstate_cb+0x161 #12 0x804eb6b7 at taskqueue_run_locked+0xb7 #13 0x804eb7a0 at taskqueue_thread_loop+0x50 #14 0x804906d5 at fork_exit+0x115 #15 0x8064bc4e at fork_trampoline+0xe Regards, -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: urtw0: could not allocate USB transfers
On Thursday 03 March 2011 14:07:52 Etienne Robillard wrote: ieee80211_newstate_cb Hi, I think the problem is in the ieee80211 layer not draining its taskqueues properly and/or other activities. It crashes in USB because it is accessing freed memory or NULL pointers most likely. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: urtw0: could not allocate USB transfers
On 03/03/11 08:25 AM, Hans Petter Selasky wrote: On Thursday 03 March 2011 14:07:52 Etienne Robillard wrote: ieee80211_newstate_cb Hi, I think the problem is in the ieee80211 layer not draining its taskqueues properly and/or other activities. It crashes in USB because it is accessing freed memory or NULL pointers most likely. --HPS X-UID: 11309 Status: X-Keywords: Content-Length: 0 nice debugging! out of curiosity, what is OFDM and why is it faster than unknown subtype as when using rt2870 ? $ dmesg run0: 1.0 on usbus1 run0: MAC/BBP RT2872 (rev 0x0202), RF RT2720 (MIMO 1T2R), address 00:14:d1:67:a5:de run0: firmware RT2870 loaded run0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps run0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps t_delta 15.fd8648f984182166 too short wlan0: bpf attached wlan0: bpf attached wlan0: Ethernet address: 00:14:d1:67:a5:de wlan0: link state changed to UP $ kldload /boot/kernel/ipfw.ko link_elf_obj: symbol in6_clearscope undefined linker_load_file: Unsupported file type wlan0: link state changed to DOWN wlan0: link state changed to UP $ ifconfig wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:00:00:00:00:00 inet 192.168.0.101 netmask 0xff00 broadcast 192.168.0.255 media: IEEE 802.11 Wireless Ethernet OFDM/12Mbps mode 11g status: associated ssid dlink2 channel 2 (2417 MHz 11g) bssid 00:00:00:00:00:00 country US authmode OPEN privacy OFF txpower 0 bmiss 7 scanvalid 60 protmode CTS wme Cheers! :) -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RE: urtw0: could not allocate USB transfers
On 02/25/2011 07:31, Bernhard Schmidt wrote: On Friday, February 25, 2011 12:47:12 Etienne Robillard wrote: On 25/02/11 06:18 AM, Bernhard Schmidt wrote: On Friday, February 25, 2011 11:03:04 Etienne Robillard wrote: On 25/02/11 04:11 AM, Bernhard Schmidt wrote: On Thursday, February 24, 2011 21:51:23 joseph wrote: Hello, i decided to get my laptop wlan via usb because my internal device isn't supported yet. The usb device is a logilink WL0006 unit its vendorid is 0x0bda and the productid says 0x8187. My search results say that this device depends on a RTL8187 chipset. I tried both, load the kernel module at boot time and compile kernel withe urtw, but i get the same output at dmesg device_attach: urtw0 attach returned 6 urtw0:vendor 0x0bda product 0x8187, class 0/0, rev 2.00/2.00, addr 2 on usbus3 urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE device_attach: urtw0 attach returned 6 im running FreeBSD 8.1-RELEASE-p2 amd64. What might be the reason for this error? Thanks for all hints. Well, I have no clue about USB.. but this smells like one of the endpoints is 'not there'. At least I can't find any reference to it in the Linux driver. Wanna give attached patch a shot? Hi Bernard, For rt287x based cards, you can try using rt28700 chipset instead of urtw0 on FreeBSD 8. The former is not in the stable src tree, but could be retrieved from here: https://gthc.org/distfiles/freebsd/rt2870_fbsd8.tar.gz Any takers to make module rt28700 (if_rt2870) officially part of the FreeBSD src tree? I'm a bit confused now, shouldn't the rt2870 be supported by run(4)? On a site-note, this is Ralink chipset not a Realtek one. I believe this is a different implementation for RT8187 usb network adapters than run(4). However in my view I found urtw0 buggy, but would certainly take a look at run(4) to compare the results with wireless networking agaisnt the other driver (rt28700). Yeah, urtw(4) has a few flaws.. - urtw(4): Realtek RTL8187B/RTL8187L - rum(4): Ralink RT2501/RT2601 - run(4): Ralink RT2700/RT2800/RT3000 So it seems the driver you've posted conflicts with run(4). From a quick glance at it, it seems to support 11n? If so, can I talk you into working on getting those bits merged? Thanks! -- Bernhard X-UID: 10549 Status: X-Keywords: Content-Length: 0 I forwarded this thread on -current. Please also find below a stack trace produced with option KDB_UNATTENDED for the rt28700 driver (if_rt28700). On another side note, I have not being able to load the runfw firmware module anymore after having updated the src tree for 8.2-STABLE ? $ sudo kldload /boot/kernel/runfw.ko kldload: can't load /boot/kernel/runfw.ko: Exec format error $ objdump -x /boot/kernel/runfw.ko /boot/kernel/runfw.ko: file format elf64-x86-64 /boot/kernel/runfw.ko architecture: i386:x86-64, flags 0x0011: HAS_RELOC, HAS_SYMS start address 0x Sections: Idx Name Size VMA LMA File off Algn 0 .text 0056 0040 2**4 CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE 1 .rodata.str1.1 001f 0096 2**0 CONTENTS, ALLOC, LOAD, READONLY, DATA 2 set_modmetadata_set 0020 00b8 2**3 CONTENTS, ALLOC, LOAD, RELOC, READONLY, DATA 3 set_sysinit_set 0008 00d8 2**3 CONTENTS, ALLOC, LOAD, RELOC, READONLY, DATA 4 .data 20d4 00e0 2**4 CONTENTS, ALLOC, LOAD, RELOC, DATA 5 .bss 21b4 2**2 ALLOC 6 .comment 0026 21b4 2**0 CONTENTS, READONLY SYMBOL TABLE: ld .text ld .rodata.str1.1 ld .data l F .text 0056 runfw_fw_modevent l O set_modmetadata_set0008 __set_modmetadata_set_sym__mod_metadata_md_runfw_fw_on_firmware 2000 l O .data 0018 _mod_metadata_md_runfw_fw_on_firmware 0008 l O set_modmetadata_set0008 __set_modmetadata_set_sym__mod_metadata_runfw_fw_version 2020 l O .data 0018 _mod_metadata_runfw_fw_version l O set_sysinit_set0008 __set_sysinit_set_sym_runfw_fwmodule_sys_init 2040 l O .data 0018 runfw_fwmodule_sys_init 0010 l O set_modmetadata_set0008
Re: urtw0: could not allocate USB transfers
On Wednesday, March 02, 2011 11:00:26 am Etienne Robillard wrote: On 02/25/2011 07:31, Bernhard Schmidt wrote: On Friday, February 25, 2011 12:47:12 Etienne Robillard wrote: On 25/02/11 06:18 AM, Bernhard Schmidt wrote: On Friday, February 25, 2011 11:03:04 Etienne Robillard wrote: On 25/02/11 04:11 AM, Bernhard Schmidt wrote: On Thursday, February 24, 2011 21:51:23 joseph wrote: Hello, i decided to get my laptop wlan via usb because my internal device isn't supported yet. The usb device is a logilink WL0006 unit its vendorid is 0x0bda and the productid says 0x8187. My search results say that this device depends on a RTL8187 chipset. I tried both, load the kernel module at boot time and compile kernel withe urtw, but i get the same output at dmesg device_attach: urtw0 attach returned 6 urtw0:vendor 0x0bda product 0x8187, class 0/0, rev 2.00/2.00, addr 2 on usbus3 urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE device_attach: urtw0 attach returned 6 im running FreeBSD 8.1-RELEASE-p2 amd64. What might be the reason for this error? Thanks for all hints. Well, I have no clue about USB.. but this smells like one of the endpoints is 'not there'. At least I can't find any reference to it in the Linux driver. Wanna give attached patch a shot? Hi Bernard, For rt287x based cards, you can try using rt28700 chipset instead of urtw0 on FreeBSD 8. The former is not in the stable src tree, but could be retrieved from here: https://gthc.org/distfiles/freebsd/rt2870_fbsd8.tar.gz Any takers to make module rt28700 (if_rt2870) officially part of the FreeBSD src tree? I'm a bit confused now, shouldn't the rt2870 be supported by run(4)? On a site-note, this is Ralink chipset not a Realtek one. I believe this is a different implementation for RT8187 usb network adapters than run(4). However in my view I found urtw0 buggy, but would certainly take a look at run(4) to compare the results with wireless networking agaisnt the other driver (rt28700). Yeah, urtw(4) has a few flaws.. - urtw(4): Realtek RTL8187B/RTL8187L - rum(4): Ralink RT2501/RT2601 - run(4): Ralink RT2700/RT2800/RT3000 So it seems the driver you've posted conflicts with run(4). From a quick glance at it, it seems to support 11n? If so, can I talk you into working on getting those bits merged? Thanks! -- Bernhard X-UID: 10549 Status: X-Keywords: Content-Length: 0 I forwarded this thread on -current. Please also find below a stack trace produced with option KDB_UNATTENDED for the rt28700 driver (if_rt28700). On another side note, I have not being able to load the runfw firmware module anymore after having updated the src tree for 8.2-STABLE ? $ sudo kldload /boot/kernel/runfw.ko kldload: can't load /boot/kernel/runfw.ko: Exec format error Here is your real error in dmesg: KLD runfw.ko: depends on firmware - not available or version mismatch linker_load_file: Unsupported file type You need to kldload firmware.ko or make sure 'device firmware' is in your kernel config. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: urtw0: could not allocate USB transfers
On 02/03/11 11:47 AM, John Baldwin wrote: On Wednesday, March 02, 2011 11:00:26 am Etienne Robillard wrote: On 02/25/2011 07:31, Bernhard Schmidt wrote: On Friday, February 25, 2011 12:47:12 Etienne Robillard wrote: On 25/02/11 06:18 AM, Bernhard Schmidt wrote: On Friday, February 25, 2011 11:03:04 Etienne Robillard wrote: On 25/02/11 04:11 AM, Bernhard Schmidt wrote: On Thursday, February 24, 2011 21:51:23 joseph wrote: Hello, i decided to get my laptop wlan via usb because my internal device isn't supported yet. The usb device is a logilink WL0006 unit its vendorid is 0x0bda and the productid says 0x8187. My search results say that this device depends on a RTL8187 chipset. I tried both, load the kernel module at boot time and compile kernel withe urtw, but i get the same output at dmesg device_attach: urtw0 attach returned 6 urtw0:vendor 0x0bda product 0x8187, class 0/0, rev 2.00/2.00, addr 2 on usbus3 urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE device_attach: urtw0 attach returned 6 im running FreeBSD 8.1-RELEASE-p2 amd64. What might be the reason for this error? Thanks for all hints. Well, I have no clue about USB.. but this smells like one of the endpoints is 'not there'. At least I can't find any reference to it in the Linux driver. Wanna give attached patch a shot? Hi Bernard, For rt287x based cards, you can try using rt28700 chipset instead of urtw0 on FreeBSD 8. The former is not in the stable src tree, but could be retrieved from here: https://gthc.org/distfiles/freebsd/rt2870_fbsd8.tar.gz Any takers to make module rt28700 (if_rt2870) officially part of the FreeBSD src tree? I'm a bit confused now, shouldn't the rt2870 be supported by run(4)? On a site-note, this is Ralink chipset not a Realtek one. I believe this is a different implementation for RT8187 usb network adapters than run(4). However in my view I found urtw0 buggy, but would certainly take a look at run(4) to compare the results with wireless networking agaisnt the other driver (rt28700). Yeah, urtw(4) has a few flaws.. - urtw(4): Realtek RTL8187B/RTL8187L - rum(4): Ralink RT2501/RT2601 - run(4): Ralink RT2700/RT2800/RT3000 So it seems the driver you've posted conflicts with run(4). From a quick glance at it, it seems to support 11n? If so, can I talk you into working on getting those bits merged? Thanks! -- Bernhard X-UID: 10549 Status: X-Keywords: Content-Length: 0 I forwarded this thread on -current. Please also find below a stack trace produced with option KDB_UNATTENDED for the rt28700 driver (if_rt28700). On another side note, I have not being able to load the runfw firmware module anymore after having updated the src tree for 8.2-STABLE ? $ sudo kldload /boot/kernel/runfw.ko kldload: can't load /boot/kernel/runfw.ko: Exec format error Here is your real error in dmesg: KLD runfw.ko: depends on firmware - not available or version mismatch linker_load_file: Unsupported file type You need to kldload firmware.ko or make sure 'device firmware' is in your kernel config. Hi, Many thanks. This explains the change of behavior attempting to kldload runfw.ko without the firmware assist module. :) However I find strange that run(4) requires such a firmware to be preloaded when the rt2870 driver doesn't require it! Cheers, -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: urtw0: could not allocate USB transfers
On Wednesday 02 March 2011 18:01:19 Etienne Robillard wrote: On 02/03/11 11:47 AM, John Baldwin wrote: On Wednesday, March 02, 2011 11:00:26 am Etienne Robillard wrote: On 02/25/2011 07:31, Bernhard Schmidt wrote: On Friday, February 25, 2011 12:47:12 Etienne Robillard wrote: On 25/02/11 06:18 AM, Bernhard Schmidt wrote: On Friday, February 25, 2011 11:03:04 Etienne Robillard wrote: On 25/02/11 04:11 AM, Bernhard Schmidt wrote: On Thursday, February 24, 2011 21:51:23 joseph wrote: Hello, i decided to get my laptop wlan via usb because my internal device isn't supported yet. The usb device is a logilink WL0006 unit its vendorid is 0x0bda and the productid says 0x8187. My search results say that this device depends on a RTL8187 chipset. I tried both, load the kernel module at boot time and compile kernel withe urtw, but i get the same output at dmesg device_attach: urtw0 attach returned 6 urtw0:vendor 0x0bda product 0x8187, class 0/0, rev 2.00/2.00, addr 2 on usbus3 urtw0: could not allocate USB transfers, err=USB_ERR_NO_PIPE device_attach: urtw0 attach returned 6 im running FreeBSD 8.1-RELEASE-p2 amd64. What might be the reason for this error? Thanks for all hints. Well, I have no clue about USB.. but this smells like one of the endpoints is 'not there'. At least I can't find any reference to it in the Linux driver. Wanna give attached patch a shot? Hi Bernard, For rt287x based cards, you can try using rt28700 chipset instead of urtw0 on FreeBSD 8. The former is not in the stable src tree, but could be retrieved from here: https://gthc.org/distfiles/freebsd/rt2870_fbsd8.tar.gz Any takers to make module rt28700 (if_rt2870) officially part of the FreeBSD src tree? I'm a bit confused now, shouldn't the rt2870 be supported by run(4)? On a site-note, this is Ralink chipset not a Realtek one. I believe this is a different implementation for RT8187 usb network adapters than run(4). However in my view I found urtw0 buggy, but would certainly take a look at run(4) to compare the results with wireless networking agaisnt the other driver (rt28700). Yeah, urtw(4) has a few flaws.. - urtw(4): Realtek RTL8187B/RTL8187L - rum(4): Ralink RT2501/RT2601 - run(4): Ralink RT2700/RT2800/RT3000 So it seems the driver you've posted conflicts with run(4). From a quick glance at it, it seems to support 11n? If so, can I talk you into working on getting those bits merged? Thanks! -- Bernhard X-UID: 10549 Status: X-Keywords: Content-Length: 0 I forwarded this thread on -current. Please also find below a stack trace produced with option KDB_UNATTENDED for the rt28700 driver (if_rt28700). On another side note, I have not being able to load the runfw firmware module anymore after having updated the src tree for 8.2-STABLE ? $ sudo kldload /boot/kernel/runfw.ko kldload: can't load /boot/kernel/runfw.ko: Exec format error Here is your real error in dmesg: KLD runfw.ko: depends on firmware - not available or version mismatch linker_load_file: Unsupported file type You need to kldload firmware.ko or make sure 'device firmware' is in your kernel config. Hi, Many thanks. This explains the change of behavior attempting to kldload runfw.ko without the firmware assist module. :) However I find strange that run(4) requires such a firmware to be preloaded when the rt2870 driver doesn't require it! Cheers, Maybe that's due to a missing MODULE_DEPEND() line in the .c file of urtw0. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
