On Sun, Oct 02, 2016 at 10:15:49AM -0700, Adrian Chadd wrote:
> 
> hi,

Hi Adrian,

> can you turn on debugging? Do you see RX frames?

No Rx frames.  The log is pretty much the same one I sent on the list:
https://lists.freebsd.org/pipermail/freebsd-wireless/2016-September/007093.html

> -a

Thanks,
Kevin

> On 1 October 2016 at 08:09, Kevin Lo <ke...@freebsd.org> wrote:
> > Strange, rtwn(4) stops working.  I tried to scan for the available network,
> > but it just returns empty results.
> >
> > On Fri, Sep 23, 2016 at 02:44:13PM +0300, Andriy Voskoboinyk wrote:
> >>
> >> Fri, 23 Sep 2016 10:18:30 +0300 було написано Kevin Lo <ke...@freebsd.org>:
> >>
> >> Few more questions:
> >> 1) does it work with h/w encryption support? (enabled by default)
> >> (if 'yes' - I will remove 'hardware crypto enabled' warning).
> >> 2) is there rate control support? (wlandebug -i wlan0 rate ; then transmit
> >> something - if it works then AMRR will print it's current status
> >> periodically)
> >> 3) can you test some disabled capabilities? (ad-hoc/AP modes, 11n)
> >> (see r92ce_adj_devcaps() in sys/dev/rtwn/rtl8192c/pci/r92ce_attach.c).
> >>
> >> > It works for me, thanks :)
> >> >
> >> >     Kevin
> >> >
> >> > On Fri, Sep 23, 2016 at 09:08:15AM +0300, Andriy Voskoboinyk wrote:
> >> >>
> >> >> Fri, 23 Sep 2016 04:58:40 +0300 було написано Kevin Lo
> >> >> <ke...@freebsd.org>:
> >> >>
> >> >> Thanks for the log file,
> >> >>
> >> >> Tx 'device timeouts' should be fixed in
> >> >> https://github.com/s3erios/rtwn/commit/f78d51b6ed8590e3aeb65fbf616aa767034a89f5
> >> >> (currently I'm reviewing PCI-specific code to see if there are any
> >> >> additional
> >> >> issues - e.g., there are no Rx events in the log file).
> >> >>
> >> >> > On Thu, Sep 22, 2016 at 01:54:21PM +0300, Andriy Voskoboinyk wrote:
> >> >> >>
> >> >> >> Thu, 22 Sep 2016 12:24:42 +0300 було написано Kevin Lo
> >> >> >> <ke...@freebsd.org>:
> >> >> >>
> >> >> >> Hi,
> >> >> >>
> >> >> >> So, the driver was fully tested. Thanks!
> >> >> >> Can you set dev.rtwn.0.debug=0x829f for RTL8188CE to see how big
> >> >> >> the problem is?
> >> >> >
> >> >> > Sure.  Here you go
> >> >> https://people.freebsd.org/~kevlo/rtl8188ce-debug.txt
> >> >> >
> >> >> > Thanks,
> >> >> > Kevin
> >> >> >
> >> >> >> > Hi Andriy,
> >> >> >> >
> >> >> >> > First of all, THANK YOU!  You're doing amazing work!
> >> >> >> > Second, I've done some testing on the following devices,
> >> >> downloading
> >> >> >> > FreeBSD-12.0-CURRENT-amd64-20160809-r303880-disc1.iso from
> >> >> >> > ftp.freebsd.org:
> >> >> >> >
> >> >> >> > - ASUS USB-N10 NANO (RTL8188CUS):
> >> >> >> >   rtwn0: <vendor 0x0b05 product 0x17ba, class 0/0, rev 2.00/2.00,
> >> >> addr
> >> >> >> > 3> on usbus0
> >> >> >> >   rtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R
> >> >> >> >
> >> >> >> > - TP-Link TL-WN725N v2 (RTL8188EU):
> >> >> >> >   rtwn0: <Realtek 802.11n NIC, class 0/0, rev 2.00/0.00, addr 4> on
> >> >> >> > usbus0
> >> >> >> >   rtwn0: MAC/BB RTL8188EU, RF 6052 1T1R
> >> >> >> >
> >> >> >> > - D-Link DWA-131 (RTL8192CU):
> >> >> >> >   rtwn0: <vendor 0x2001 product 0x330d, class 0/0, rev 2.00/2.00,
> >> >> addr
> >> >> >> > 3> on usbus0
> >> >> >> >   rtwn0: MAC/BB RTL8192CU, RF 6052 2T2R
> >> >> >> >
> >> >> >> > - TP-Link Archer T4U (RTL8812AU):
> >> >> >> >   rtwn0: <Realtek 802.11n NIC, class 0/0, rev 2.00/0.00, addr 7> on
> >> >> >> > usbus0
> >> >> >> >   rtwn0: MAC/BB RTL8812AU, RF 6052 2T2R
> >> >> >> >
> >> >> >> > - D-Link DWA-171 rev A1 (RTL8821AU):
> >> >> >> >   rtwn0: <802.11n WLAN Adapter> on usbus0
> >> >> >> >   rtwn0: MAC/BB RTL8821AU, RF 6052 1T1R
> >> >> >> >
> >> >> >> > - RTL8188CE mini pcie:
> >> >> >> >   rtwn0: <Realtek RTL8188CE> port 0xd000-0xd0ff mem
> >> >> >> > 0x90800000-0x90803fff irq 17 at device 0.0 on pci1
> >> >> >> >   rtwn0: r92ce_attach: warning: hardware crypto enabled
> >> >> >> >   rtwn0: MAC/BB RTL8188CE, RF 6052 1T1R
> >> >> >> >
> >> >> >> > All seems to be ok, except RTL8188CE PCIe adapter doesn't work:
> >> >> >> >
> >> >> >> > rtwn0: r92ce_post_init: warning: net80211 ratectl is used
> >> >> >> > rtwn0: device timeout
> >> >> >> >
> >> >> >> >       Kevin
> >> >> >> >
> >> >> >> > On Mon, Sep 19, 2016 at 04:26:38PM +0300, Andriy Voskoboinyk wrote:
> >> >> >> >>
> >> >> >> >> Thu, 01 Sep 2016 19:29:03 +0300 було написано Andriy Voskoboinyk
> >> >> >> >> <a...@freebsd.org>:
> >> >> >> >>
> >> >> >> >> Now it resides on https://github.com/s3erios/freebsd-rtwn
> >> >> (integrated
> >> >> >> >> into src tree, so it can be built with 'make buildkernel' / 'make
> >> >> >> >> buildworld').
> >> >> >> >>
> >> >> >> >> This the last stage; once all reported issues will be resolved,
> >> >> I'm
> >> >> >> >> going to merge it into HEAD.
> >> >> >> >>
> >> >> >> >> > Hi everyone,
> >> >> >> >> >
> >> >> >> >> > rtwn(4), urtwn(4) and urtwm (from previous emails) drivers were
> >> >> >> merged
> >> >> >> >> > into a
> >> >> >> >> > single rtwn driver (plus rtwn_usb / rtwn_pci device glue); the
> >> >> >> code is
> >> >> >> >> > available on https://github.com/s3erios/rtwn repository. Among
> >> >> >> >> bugfixes /
> >> >> >> >> > code deduplication, there some new features too:
> >> >> >> >> >
> >> >> >> >> > 1) multi-vap support (one any wireless interface + one STA
> >> >> >> interface +
> >> >> >> >> > any number of monitor mode interfaces).
> >> >> >> >> > 2) few new sysctls:
> >> >> >> >> >   * dev.rtwn.#.crypto - controls how to use hardware crypto
> >> >> >> >> acceleration
> >> >> >> >> >   * dev.rtwn.#.ratectl_selected
> >> >> >> >> >   * dev.rtwn.#.ratectl - selects current 'rate control'
> >> >> algorithm
> >> >> >> >> > (currently only 'none' and 'net80211' are supported; RTL8192CE
> >> >> >> needs
> >> >> >> >> > testing
> >> >> >> >> > with the last).
> >> >> >> >> > 3) (incomplete) power management support for RTL8188EU (requires
> >> >> >> >> > firmware).
> >> >> >> >> > 4) Short Guard Interval support.
> >> >> >> >> >
> >> >> >> >> > It's known to work with RTL8188CUS, RTL8188EU and RTL8821AU;
> >> >> >> however,
> >> >> >> >> > it was never tested with RTL8192CE or RTL8812AU.
> >> >> >> >> >
> >> >> >> >> > How-to-build:
> >> >> >> >> > 1) download / checkout the repository.
> >> >> >> >> > 2) apply 'patch-usbdevs.diff' against '/usr/src'
> >> >> >> >> > 3) build and install rtwn module:
> >> >> >> >> >     cd $repository/sys/modules/rtwn && make && make install
> >> >> >> >> > 4) build and install rtwn_usb/rtwn_pci:
> >> >> >> >> >     cd ../rtwn_usb && make && make install
> >> >> >> >> >     cd ../rtwn_pci && make && make install
> >> >> >> >> > 5) unload previous && load current drivers:
> >> >> >> >> >     kldunload if_urtwn if_rtwn
> >> >> >> >> >     kldload /boot/modules/if_rtwn.ko
> >> >> /boot/modules/if_rtwn_usb.ko
> >> >> >> >> > /boot/modules/if_rtwn_pci.ko
> >> >> >> >> > 6) Use.
> >> >> >> >> _______________________________________________
> >> >> >> >> freebsd-wireless@freebsd.org mailing list
> >> >> >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> >> >> >> >> To unsubscribe, send any mail to
> >> >> >> >> "freebsd-wireless-unsubscr...@freebsd.org"
> >> >> >> >>
> >> >> >>
> >> >> _______________________________________________
> >> >> freebsd-curr...@freebsd.org mailing list
> >> >> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >> >> To unsubscribe, send any mail to
> >> >> "freebsd-current-unsubscr...@freebsd.org"
> >> >>
> >> >>
> >> > _______________________________________________
> >> > freebsd-wireless@freebsd.org mailing list
> >> > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> >> > To unsubscribe, send any mail to
> >> > "freebsd-wireless-unsubscr...@freebsd.org"
> >>
> >>
> > _______________________________________________
> > freebsd-curr...@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 
> 
_______________________________________________
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Reply via email to