Re: Change for the worse in rsu wireless driver
from Adrian Chadd: > Buy a mini-pcie atheros wifi card. How do I know this would work with FreeBSD and/or NetBSD? I could switch the hard drives between the two computers, or put one hard drive in a Sabrent enclosure: IDE and SATA inside, USB 2.0 and eSATA outside interface. I could also buy a USB-to-Ethernet adapter, don't know how these things work under FreeBSD. But I would still have to plug into the 25 ft Ethernet cable that goes across the floor and creates a tripping hazard, though I haven't tripped over it yet in over two years. I already have one wired and two wireless ways of connecting to the Internet, think they might all work with Linux but really need to test them. Again I seem to have lost the Internet connection, despite "ifconfig" showing lo0: flags=8049 metric 0 mtu 16384 options=63 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 inet 127.0.0.1 netmask 0xff00 nd6 options=21 rsu0: flags=8843 metric 0 mtu 2290 options=1 ether 00:13:33:a2:86:f0 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated wlan0: flags=8843 metric 0 mtu 1500 ether 00:13:33:a2:86:f0 inet 192.168.0.101 netmask 0xff00 broadcast 192.168.0.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet OFDM/54Mbps mode 11g status: associated ssid Maclura_pomifera channel 8 (2447 MHz 11g) bssid a0:f3:c1:f9:39:7a country US authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 0 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS roaming MANUAL uname -a shows FreeBSD amelia4 11.0-CURRENT FreeBSD 11.0-CURRENT #8 r267220M: Sun Jun 8 17:16:53 UTC 2014 root@amelia4:/usr/obj/usr/src/sys/SANDY11NC amd64 Tom ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Change for the worse in rsu wireless driver
Hi, Buy a mini-pcie atheros wifi card. -a On 9 June 2014 03:43, Thomas Mueller wrote: > from Adrian Chadd: > >> please bug freebsd-usb@ about flakey usb devices. > >> I have a couple that i need to chase up hans about. they used to be less >> flakey. > > Flaky USB devices in FreeBSD, also NetBSD, are not limited to wireless > adapters. > > I get console messages about keyboard and mouse losing connection, when in > many cases, mouse and keyboard are still working. > > Now I think FreeBSD is topping NetBSD for flaky USB connections. > > NetBSD has no support for Hiro H50191 wireless adapter, device rsu, but > supports Atheros on-motherboard (quasi-)USB AR9271. > > Most of the time, NetBSD fails to load firmware for this Atheros AR9271, > error 35, not allowing enough time, but sometimes the firmware loads. > > Sorry to be late in responding, losing connection slows me down. > > I've been updating FreeBSD-current and stable/10 from source, both amd64 and > i386, whenever I see a change in rsu or re driver. > > On MSI Z77 MPOWER motherboard, of open-source OSes, only Linux and NetBSD > connect with Realtek 8111E/8168 Ethernet. > > DragonFly newest release, 3.8.0, and OpenBSD 5.4, have same bug as does > FreeBSD with this Ethernet. > > I've also been busy installing NetBSD-current amd64 and i386, now on hard > drive on other computer. > > Now I wish I had installed NetBSD-current amd64 and i386 on this computer > with MSI Z77 MPOWER motherboard before FreeBSD to have something to fall back > on when FreeBSD misbehaves with Hiro H50191. > > Remember, I needed to update NetBSD-current amd64 and packages, with > subversion, using wired Ethernet, to checkout and update FreeBSD src, ports > and doc trees; also had to buy a new wireless router when the Netgear router > stopped working. > > Tom > > ___ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org" ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Change for the worse in rsu wireless driver
from Adrian Chadd: > please bug freebsd-usb@ about flakey usb devices. > I have a couple that i need to chase up hans about. they used to be less > flakey. Flaky USB devices in FreeBSD, also NetBSD, are not limited to wireless adapters. I get console messages about keyboard and mouse losing connection, when in many cases, mouse and keyboard are still working. Now I think FreeBSD is topping NetBSD for flaky USB connections. NetBSD has no support for Hiro H50191 wireless adapter, device rsu, but supports Atheros on-motherboard (quasi-)USB AR9271. Most of the time, NetBSD fails to load firmware for this Atheros AR9271, error 35, not allowing enough time, but sometimes the firmware loads. Sorry to be late in responding, losing connection slows me down. I've been updating FreeBSD-current and stable/10 from source, both amd64 and i386, whenever I see a change in rsu or re driver. On MSI Z77 MPOWER motherboard, of open-source OSes, only Linux and NetBSD connect with Realtek 8111E/8168 Ethernet. DragonFly newest release, 3.8.0, and OpenBSD 5.4, have same bug as does FreeBSD with this Ethernet. I've also been busy installing NetBSD-current amd64 and i386, now on hard drive on other computer. Now I wish I had installed NetBSD-current amd64 and i386 on this computer with MSI Z77 MPOWER motherboard before FreeBSD to have something to fall back on when FreeBSD misbehaves with Hiro H50191. Remember, I needed to update NetBSD-current amd64 and packages, with subversion, using wired Ethernet, to checkout and update FreeBSD src, ports and doc trees; also had to buy a new wireless router when the Netgear router stopped working. Tom ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Change for the worse in rsu wireless driver
hi, please bug freebsd-usb@ about flakey usb devices. I have a couple that i need to chase up hans about. they used to be less flakey. -a On 5 June 2014 01:46, Thomas Mueller wrote: > from Idwer Vollering : > >> I'm on 10-STABLE r267049, with a local change to >> sys/dev/usb/wlan/if_rsu.c that reverts EW7622UMN back to RTL8192SU_3. > >> > At least my adapter is working a bit more stable now :-) > >> Mine seems to get stuck in "rsu_calib_task: running calibration task" often. > >> HTH, > >> Idwer > > I browsed svnweb.freebsd.org for rsu and re in stable/10 and head, also for > cups in ports. > > I found an update, 4 hours old, for rsu in head, so that pushed me to update > the head src tree. > > That was after a time when the wireless adapter didn't connect at all, didn't > see the network. > > FreeBSD is flaky at times with USB, not recognizing a good USB stick in a > good USB port. > > After some time web-browsing with Midori 0.5.5 on System Rescue CD, which > itself is fickle and flaky, not as good as Midori 0.5.8 from FreeBSD ports, > Hiro H50191 USB wireless adapter came back and is still working, though I > still intend to do the system build/update for 11-head, both amd64 and i386. > > Tom > > ___ > freebsd-curr...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Change for the worse in rsu wireless driver
2014-06-05 7:59 GMT+02:00 Hans Petter Selasky : > > Hi, > > Is that a patch I need to add to 10-stable? Hi, Not yet, as I can work with if_rsu code from -CURRENT until things are sorted out. > Yeah. Looking at the driver code and comparing to Linux, I see a lot of > things missing :-) Another problem about the calibration task, is that it > runs asynchronous to the other code possibly programming the chip. The adapter works fine from OpenBSD, does not (seem to) get confused during calibration. > Can you turn on: hw.usb.rsu.debug=15 when errors happen? > > Or send what is printed in dmesg? With hw.usb.rsu.debug=6: Yes, the dmesg buffer is full :) $ dmesg rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090298 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090298 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090268 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090268 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090238 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090238 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090208 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090208 rsu_bulk_tx_callback_sub: submitting transfer 0xfe00060907d8 rsu_bulk_tx_callback_sub: transfer done 0xfe00060907d8 rsu_bulk_tx_callback_sub: submitting transfer 0xfe00060907a8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=8 rsu_bulk_tx_callback_sub: transfer done 0xfe00060907a8 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090778 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090778 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090748 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-102 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090748 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090718 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=18 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090718 rsu_bulk_tx_callback_sub: submitting transfer 0xfe00060906e8 rsu_bulk_tx_callback_sub: transfer done 0xfe00060906e8 rsu_bulk_tx_callback_sub: submitting transfer 0xfe00060906b8 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-56 rsu_bulk_tx_callback_sub: transfer done 0xfe00060906b8 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090688 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=9 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090688 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090658 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-81 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090658 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090628 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090628 rsu_bulk_tx_callback_sub: submitting transfer 0xfe00060905f8 rsu_bulk_tx_callback_sub: transfer done 0xfe00060905f8 rsu_bulk_tx_callback_sub: submitting transfer 0xfe00060905c8 rsu_bulk_tx_callback_sub: transfer done 0xfe00060905c8 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090598 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090598 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090568 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-1 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090568 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090538 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-25 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090538 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090508 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=88 rate=11 infosz=32 rssi=-74 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090508 rsu_bulk_tx_callback_sub: submitting transfer 0xfe00060904d8 rsu_bulk_tx_callback_sub: transfer done 0xfe00060904d8 rsu_bulk_tx_callback_sub: submitting transfer 0xfe00060904a8 rsu_bulk_tx_callback_sub: transfer done 0xfe00060904a8 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090478 rsu_rx_multi_frame: Rx 1 frames in one chunk rsu_rx_frame: Rx frame len=136 rate=11 infosz=32 rssi=-86 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090478 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090448 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090448 rsu_bulk_tx_callback_sub: submitting transfer 0xfe0006090418 rsu_bulk_tx_callback_sub: transfer done 0xfe0006090418 rsu_bulk_tx_callback_sub: submitting transfer 0xfe00060903e8 rsu_bulk_tx_callback_sub: transfer done 0xfe00060903e8 rsu_bulk_tx_callback_sub: submitting transfer 0xfe00060903b8 rsu_bulk_tx_callback_sub:
Change for the worse in rsu wireless driver
from Idwer Vollering : > I'm on 10-STABLE r267049, with a local change to > sys/dev/usb/wlan/if_rsu.c that reverts EW7622UMN back to RTL8192SU_3. > > At least my adapter is working a bit more stable now :-) > Mine seems to get stuck in "rsu_calib_task: running calibration task" often. > HTH, > Idwer I browsed svnweb.freebsd.org for rsu and re in stable/10 and head, also for cups in ports. I found an update, 4 hours old, for rsu in head, so that pushed me to update the head src tree. That was after a time when the wireless adapter didn't connect at all, didn't see the network. FreeBSD is flaky at times with USB, not recognizing a good USB stick in a good USB port. After some time web-browsing with Midori 0.5.5 on System Rescue CD, which itself is fickle and flaky, not as good as Midori 0.5.8 from FreeBSD ports, Hiro H50191 USB wireless adapter came back and is still working, though I still intend to do the system build/update for 11-head, both amd64 and i386. Tom ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Change for the worse in rsu wireless driver
> On 06/04/14 08:53, Hans Petter Selasky wrote: > > On 06/04/14 04:13, Thomas Mueller wrote: > >>> Yes, please apply by hand. I'll see if I can do some testing myself. > >>> I happen to have one of these adapters too and the link is very > >>> unstable :-) > >> --HPS > > Hi, > > Please test the following patch, applied to top of 10-stable as of now: > > http://svnweb.freebsd.org/changeset/base/267041 I'm on 10-STABLE r267049, with a local change to sys/dev/usb/wlan/if_rsu.c that reverts EW7622UMN back to RTL8192SU_3. > > At least my adapter is working a bit more stable now :-) Mine seems to get stuck in "rsu_calib_task: running calibration task" often. > > --HPS HTH, Idwer ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Change for the worse in rsu wireless driver
On 06/04/14 08:53, Hans Petter Selasky wrote: On 06/04/14 04:13, Thomas Mueller wrote: Yes, please apply by hand. I'll see if I can do some testing myself. I happen to have one of these adapters too and the link is very unstable :-) --HPS Hi, Please test the following patch, applied to top of 10-stable as of now: http://svnweb.freebsd.org/changeset/base/267041 At least my adapter is working a bit more stable now :-) --HPS ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Change for the worse in rsu wireless driver
On 06/04/14 04:13, Thomas Mueller wrote: Yes, please apply by hand. I'll see if I can do some testing myself. I happen to have one of these adapters too and the link is very unstable :-) --HPS Sometimes Hiro H50191 USB-stick wireless adapter works well in FreeBSD, sometimes, like now and the past few days, it's flaky. It can't seem to download distfile for qt4-xml, on two occasions. I also have Atheros AR9271 quasi-USB wireless adapter on this motherboard as well as Realtek 8111E (?) Ethernet that is recognized by FreeBSD but fails to connect (same as with OpenBSD and DragonFlyBSD, but good with NetBSD and Linux). So I don't want to buy another wireless adapter (USB or PCIE?) until I find if the Hiro H50191 works better with Linux and OpenBSD. Maybe the hardware is perfectly good and the software is soft. All I have for OpenBSD is LiveUSB OpenBSD 5.4 from liveusb-openbsd.sourceforge.net , since OpenBSD can't read my hard drive at all, neither could DragonFlyBSD. Tom Previously there was a bug in the if_rsu driver that prevented the firmware from loading. Is this device on your mainboard? Does the BIOS support it? --HPS ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Change for the worse in rsu wireless driver
> Yes, please apply by hand. I'll see if I can do some testing myself. I happen > to have one of these adapters too and the link is very unstable :-) > --HPS Sometimes Hiro H50191 USB-stick wireless adapter works well in FreeBSD, sometimes, like now and the past few days, it's flaky. It can't seem to download distfile for qt4-xml, on two occasions. I also have Atheros AR9271 quasi-USB wireless adapter on this motherboard as well as Realtek 8111E (?) Ethernet that is recognized by FreeBSD but fails to connect (same as with OpenBSD and DragonFlyBSD, but good with NetBSD and Linux). So I don't want to buy another wireless adapter (USB or PCIE?) until I find if the Hiro H50191 works better with Linux and OpenBSD. Maybe the hardware is perfectly good and the software is soft. All I have for OpenBSD is LiveUSB OpenBSD 5.4 from liveusb-openbsd.sourceforge.net , since OpenBSD can't read my hard drive at all, neither could DragonFlyBSD. Tom ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Change for the worse in rsu wireless driver
On 06/03/14 12:15, Thomas Mueller wrote: from Idwer Vollering : I have a patch for that: Index: head/sys/dev/usb/wlan/if_rsu.c === --- head/sys/dev/usb/wlan/if_rsu.c (revision 266970) +++ head/sys/dev/usb/wlan/if_rsu.c (working copy) @@ -69,11 +69,13 @@ #include +static SYSCTL_NODE(_hw_usb, OID_AUTO, rsu, CTLFLAG_RW, 0, "USB rsu"); + #ifdef USB_DEBUG -static int rsu_debug = 0; -SYSCTL_NODE(_hw_usb, OID_AUTO, rsu, CTLFLAG_RW, 0, "USB rsu"); -SYSCTL_INT(_hw_usb_rsu, OID_AUTO, debug, CTLFLAG_RW, &rsu_debug, 0, +int rsu_debug = 0; +SYSCTL_INT(_hw_usb_rsu, OID_AUTO, debug, CTLFLAG_RW | CTLFLAG_TUN, &rsu_debug, 0, "Debug level"); +TUNABLE_INT("hw.usb.rsu.debug", &rsu_debug); #endif static const STRUCT_USB_HOST_ID rsu_devs[] = { @@ -1284,7 +1286,7 @@ DPRINTF("WPS PBC pushed.\n"); break; case R92S_EVT_FWDBG: - if (ifp->if_flags & IFF_DEBUG) { + if (rsu_debug >= 6) { buf[60] = '\0'; printf("FWDBG: %s\n", (char *)buf); } (end of quote) I do not put "> " in front of these lines for quoting here. Patch failed to apply, something was malformed. I have no directory named head, but even removing that left errors. I suppose I could look through original file and patch, and manually make the changes with vi. Should I try that? I am already long overdue for bed. Anyway, I have other stuff to do on computer, including NetBSD-current amd64 and i386 installations on USB sticks, plan to install on new hard drive as well. I'll be more inclined to come back when cups 1.7.3 becomes available in ports tree. I need to be able to print. Maybe NetBSD will be mainly a way station for cross-compiling Linux? Now FreeBSD 11-current amd64 betrays me again as I lost the wireless connection and have to boot into my FreeBSD 10-stable amd64 or i386 installation or NetBSD-head amd64. Tom Yes, please apply by hand. I'll see if I can do some testing myself. I happen to have one of these adapters too and the link is very unstable :-) --HPS ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Change for the worse in rsu wireless driver
from Idwer Vollering : I have a patch for that: Index: head/sys/dev/usb/wlan/if_rsu.c === --- head/sys/dev/usb/wlan/if_rsu.c (revision 266970) +++ head/sys/dev/usb/wlan/if_rsu.c (working copy) @@ -69,11 +69,13 @@ #include +static SYSCTL_NODE(_hw_usb, OID_AUTO, rsu, CTLFLAG_RW, 0, "USB rsu"); + #ifdef USB_DEBUG -static int rsu_debug = 0; -SYSCTL_NODE(_hw_usb, OID_AUTO, rsu, CTLFLAG_RW, 0, "USB rsu"); -SYSCTL_INT(_hw_usb_rsu, OID_AUTO, debug, CTLFLAG_RW, &rsu_debug, 0, +int rsu_debug = 0; +SYSCTL_INT(_hw_usb_rsu, OID_AUTO, debug, CTLFLAG_RW | CTLFLAG_TUN, &rsu_debug, 0, "Debug level"); +TUNABLE_INT("hw.usb.rsu.debug", &rsu_debug); #endif static const STRUCT_USB_HOST_ID rsu_devs[] = { @@ -1284,7 +1286,7 @@ DPRINTF("WPS PBC pushed.\n"); break; case R92S_EVT_FWDBG: - if (ifp->if_flags & IFF_DEBUG) { + if (rsu_debug >= 6) { buf[60] = '\0'; printf("FWDBG: %s\n", (char *)buf); } (end of quote) I do not put "> " in front of these lines for quoting here. Patch failed to apply, something was malformed. I have no directory named head, but even removing that left errors. I suppose I could look through original file and patch, and manually make the changes with vi. Should I try that? I am already long overdue for bed. Anyway, I have other stuff to do on computer, including NetBSD-current amd64 and i386 installations on USB sticks, plan to install on new hard drive as well. I'll be more inclined to come back when cups 1.7.3 becomes available in ports tree. I need to be able to print. Maybe NetBSD will be mainly a way station for cross-compiling Linux? Now FreeBSD 11-current amd64 betrays me again as I lost the wireless connection and have to boot into my FreeBSD 10-stable amd64 or i386 installation or NetBSD-head amd64. Tom ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Change for the worse in rsu wireless driver
I have a patch for that: Index: head/sys/dev/usb/wlan/if_rsu.c === --- head/sys/dev/usb/wlan/if_rsu.c (revision 266970) +++ head/sys/dev/usb/wlan/if_rsu.c (working copy) @@ -69,11 +69,13 @@ #include +static SYSCTL_NODE(_hw_usb, OID_AUTO, rsu, CTLFLAG_RW, 0, "USB rsu"); + #ifdef USB_DEBUG -static int rsu_debug = 0; -SYSCTL_NODE(_hw_usb, OID_AUTO, rsu, CTLFLAG_RW, 0, "USB rsu"); -SYSCTL_INT(_hw_usb_rsu, OID_AUTO, debug, CTLFLAG_RW, &rsu_debug, 0, +int rsu_debug = 0; +SYSCTL_INT(_hw_usb_rsu, OID_AUTO, debug, CTLFLAG_RW | CTLFLAG_TUN, &rsu_debug, 0, "Debug level"); +TUNABLE_INT("hw.usb.rsu.debug", &rsu_debug); #endif static const STRUCT_USB_HOST_ID rsu_devs[] = { @@ -1284,7 +1286,7 @@ DPRINTF("WPS PBC pushed.\n"); break; case R92S_EVT_FWDBG: - if (ifp->if_flags & IFF_DEBUG) { + if (rsu_debug >= 6) { buf[60] = '\0'; printf("FWDBG: %s\n", (char *)buf); } ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Change for the worse in rsu wireless driver
On 06/02/14 07:30, Thomas Mueller wrote: I sent this message, without this top part, over an hour ago, and notice wlan0 is still up. I intended but forgot to CC to freebsd-current. But I am in newcons, having not started X so far this boot session. Maybe something rotten with Xorg, or interaction between rsu and X, or rsu and Firefox. I am afraid to try again with X, don't want to mess the file system to the extent of losing data. WLAN device is Hiro H50191 USB wireless adapter, chipset RTL8191SU. I just updated FreeBSD-current, both amd64 and i386, now both rsu and Xorg are highly unstable, at least on amd64. FreeBSD amelia4 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r266948: Sun Jun 1 19:12:44 UTC 2014 root@amelia4:/usr/obj/usr/src/sys/SANDY11NC amd64 root@amelia4:~ # ls -l /usr/src/sys/dev/usb/wlan total 1164 -rw-r--r-- 1 root wheel 65759 Jun 1 16:23 if_rsu.c -rw-r--r-- 1 root wheel 19964 Jun 1 16:23 if_rsureg.h (snip) This is a change for the worse. Now I can connect with Hiro H50191; bug in re Ethernet driver persists, so I can't connect that way. I also had several crashes in Xorg, so am typing this with vi in newcons. Tom Hi, Re-compile the rsu module with USB debugging enabled: Add to: sys/modules/usb/rsu/Makefile CFLAGS+= -DUSB_DEBUG Rebuild and install. After that lookup the debug knob using "sysctl hw.usb | grep rsu" and set it to 16. Then collect some debug messages in dmesg, when problems appear. Thank you. --HPS ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Change for the worse in rsu wireless driver
I sent this message, without this top part, over an hour ago, and notice wlan0 is still up. I intended but forgot to CC to freebsd-current. But I am in newcons, having not started X so far this boot session. Maybe something rotten with Xorg, or interaction between rsu and X, or rsu and Firefox. I am afraid to try again with X, don't want to mess the file system to the extent of losing data. WLAN device is Hiro H50191 USB wireless adapter, chipset RTL8191SU. I just updated FreeBSD-current, both amd64 and i386, now both rsu and Xorg are highly unstable, at least on amd64. FreeBSD amelia4 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r266948: Sun Jun 1 19:12:44 UTC 2014 root@amelia4:/usr/obj/usr/src/sys/SANDY11NC amd64 root@amelia4:~ # ls -l /usr/src/sys/dev/usb/wlan total 1164 -rw-r--r-- 1 root wheel 65759 Jun 1 16:23 if_rsu.c -rw-r--r-- 1 root wheel 19964 Jun 1 16:23 if_rsureg.h (snip) This is a change for the worse. Now I can connect with Hiro H50191; bug in re Ethernet driver persists, so I can't connect that way. I also had several crashes in Xorg, so am typing this with vi in newcons. Tom ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Change for the worse in rsu wireless driver
WLAN device is Hiro H50191 USB wireless adapter, chipset RTL8191SU. I just updated FreeBSD-current, both amd64 and i386, now both rsu and Xorg are highly unstable, at least on amd64. FreeBSD amelia4 11.0-CURRENT FreeBSD 11.0-CURRENT #6 r266948: Sun Jun 1 19:12:44 UTC 2014 root@amelia4:/usr/obj/usr/src/sys/SANDY11NC amd64 root@amelia4:~ # ls -l /usr/src/sys/dev/usb/wlan total 1164 -rw-r--r-- 1 root wheel 65759 Jun 1 16:23 if_rsu.c -rw-r--r-- 1 root wheel 19964 Jun 1 16:23 if_rsureg.h (snip) This is a change for the worse. Now I can connect with Hiro H50191; bug in re Ethernet driver persists, so I can't connect that way. I also had several crashes in Xorg, so am typing this with vi in newcons. Tom ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"