Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing

[Andriy Voskoboinyk]

Mon, 03 Oct 2016 03:55:23 +0300 було написано Kevin Lo :

Hi!

Can you refresh the tree and retest it (dev.rtwn.0.debug=0x829f) ?

P.S. If Rx is still broken (status is always 0) try to execute
'ifconfig wlan0 promisc'


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  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  
:

>>
>> 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
>> >> :
>> >>
>> >> 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
>> >> >> :
>> >> >>
>> >> >> 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: 2.00/2.00,

>> >> addr
>> >> >> > 3> on usbus0
>> >> >> >   rtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R
>> >> >> >
>> >> >> > - TP-Link TL-WN725N v2 (RTL8188EU):
>> >> >> >   rtwn0: addr 4> on

>> >> >> > usbus0
>> >> >> >   rtwn0: MAC/BB RTL8188EU, RF 6052 1T1R
>> >> >> >
>> >> >> > - D-Link DWA-131 (RTL8192CU):
>> >> >> >   rtwn0: 2.00/2.00,

>> >> addr
>> >> >> > 3> on usbus0
>> >> >> >   rtwn0: MAC/BB RTL8192CU, RF 6052 2T2R
>> >> >> >
>> >> >> > - TP-Link Archer T4U (RTL8812AU):
>> >> >> >   rtwn0: 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:  port 0xd000-0xd0ff mem
>> >> >> > 0x9080-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

>> >> >> >> :
>> >> >> >>
>> >> >> >> 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 

Re: 11.0-RELEASE Status Update

[Glen Barber]

On Fri, Oct 07, 2016 at 08:57:26AM -0700, jungle Boogie wrote:
> On 6 October 2016 at 13:18, Glen Barber  wrote:
> > the final release announcement is planned for Monday, October 10.
> 
> suggestion:
> update the schedule
> https://www.freebsd.org/releases/11.0R/schedule.html
> 

I thought I did, but it looks like a local network hiccup caused the
commit to fail.

Fixing.  Thanks.

Glen



signature.asc
Description: PGP signature

Re: 11.0-RELEASE Status Update

[jungle Boogie]

On 6 October 2016 at 13:18, Glen Barber  wrote:
> the final release announcement is planned for Monday, October 10.

suggestion:
update the schedule
https://www.freebsd.org/releases/11.0R/schedule.html



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: CURRENT: "service netif restart" looses default route

[Trond Endrestøl]

On Wed, 5 Oct 2016 19:50+0200, Trond Endrestøl wrote:

> Oct  4 13:23:24  [WITHHELD] kernel: add net default: gateway 
> 2001:x:y:z::1 fib 0: Network is unreachable

This problem was due to a typo, sorry for the noise.

> Also, why do the startup scripts attempt to add additional routes for 
> 127.0.0.1 and ::1? I see that behaviour on both head and stable/11.

It might be worth investigating this issue further, since this 
behaviour is absent on stable/10.

-- 
+---++
| Vennlig hilsen,   | Best regards,  |
| Trond Endrestøl,  | Trond Endrestøl,   |
| IT-ansvarlig, | System administrator,  |
| Fagskolen Innlandet,  | Gjøvik Technical College, Norway,  |
| tlf. mob.   952 62 567,   | Cellular...: +47 952 62 567,   |
| sentralbord 61 14 54 00.  | Switchboard: +47 61 14 54 00.  |
+---++
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"