BPi-M3 (A83T based) under stable/11 -r308135: powerd? (cpufreq?)

https://wiki.freebsd.org/FreeBSD/arm/Allwinner reports "yes" for "cpufreq / DVFS" for A83T (and A64 and H3). But under stable/11 -r308135 powerd on a BPI-M3 (A83T) reports: powerd: no cpufreq(4) support -- aborting: No such file or directory sysctl -a does not seem to have the items for the sub

ath0 associated, wlan0 not associated

Originally posted to freebsd-wireless; no solution yet so I thought I'd try here. After booting up, my ath0 interface says it is associated, but my wlan0 says it is not: FreeBSD 10.3-RELEASE-p11 wpa_supplicant v2.0 Copyright (c) 2003-2012, Jouni Malinen and contributors ath0@pci0:2:0:0:

Re: huge nanosleep variance on 11-stable

On Wed, 2 Nov 2016 10:23:24 -0400 George Mitchell wrote: >On 11/01/16 23:45, Kevin Oberman wrote: >> On Tue, Nov 1, 2016 at 2:36 PM, Jason Harmening >> wrote: >> >>> Sorry, that should be ~*30ms* to get 30fps, though the variance is still >>> up to 500ms for me either way. >>> >>> On 11/01/

Re: ath0 associated, wlan0 not associated

hi, can you please try freebsd-11.0 ? I fixed a whole bunch of bugs in the AR9380 HAL and it may have improved that device. Thanks! -a On 3 November 2016 at 07:09, George Mitchell wrote: > Originally posted to freebsd-wireless; no solution yet so I thought > I'd try here. After booting up,

Re: zfs receive leads to a stuck server

> Am 01.10.2016 um 18:02 schrieb Rainer Duffner : > > Hi, > > I posted this before, but I didn’t really get an answer and I’m still looking > for ways to debug this. > > I have to servers (HP DL 380 Gen8, 192 GB RAM, 6C CPU). > I’ve outfitted them with HP’s H22x cards (really OEMed 9207-8x, th

Re: ath0 associated, wlan0 not associated

Thanks for the suggestion. I won't be able to try it until after a business trip next week. Any patches available that apply to 10.3? -- George On 11/03/16 18:48, Adrian Chadd wrote: > hi, > > can you please try freebsd-11.0 ? I fixed a whole bunch of bugs in the > AR9380 HAL and it may have im

Use of env SRC_ENV_CONF=. . . for buildworld does not override/avoid use of /etc/src.conf : Intentional?

I just had a case of "odd" command text in a buildworld that was based on (in part) env SRC_ENV_CONF=. . . env __MAKE_CONF=. . . does not get the kind of behavior reported below for /etc/src.conf . Overall this means that even with an explicit env SRC_ENV_CONF=. . . one must separately prevent

Re: pax(1) needs to learn POSIX-pax format (by libarchive(3)?)

On Nov 1, 2016, at 13:44, Harry Schmalzbauer wrote: > Has anyone ever thought about? Unfortunately I'm lacking skills and time :-( You’ll want to talk to the folks here: http://libarchive.org That is the upstream project. It actually started on FreeBSD over a decade ago but spun off o