On Sun, Oct 07, 2018 at 08:21:46AM -0600, Warner Losh wrote:
>
> Oh right. There's a known bug I should have mentioned: If your uname doesn't
> have a '#' in it, the script will reject it. You can add #0+ after the ALPHA8
> and before the r339174 and it will work. I've reported this to the dmesg
On Sat, Oct 06, 2018 at 11:40:36PM -0600, Warner Losh wrote:
> On Sat, Oct 6, 2018 at 12:48 PM Warner Losh wrote:
>
> > Greetings,
> >
> > As you can tell, the project is looking to clear some of the deadwood from
> > its driver lists. One problem is that we have to guess what's in used based
>
est differences will lead to this error.
Starting from a make clean and rsyncing fixed the problems, I can
install and boot my laptop from the build on my server.
Thanks!
Dhananjay Balan
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/m
or env, mktemp etc.
Thanks for all the suggestions I will grok at the installworld a bit
more, and will also give PkgBase a try.
-
Dhananjay Balan
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To
Hi,
I run 12-CURRENT on few machines, some more powerful that other (all
of them x86_64, march varies).
Is there is a way to avoid building CURRENT on all machines? Rather
than building everywhere, can I just build it on the big server that I
have and copy and update my laptop?
-
Dhananjay
On Mon, Aug 06, 2018 at 11:48:47AM -0700, R. Tyler Croy wrote:
> 173.228.82.255
> Aug 5 23:46:18 strawberry dhclient: New Routers (em1): 173.228.82.1
> Aug 5 23:46:19 strawberry syslogd: last message repeated 1 times
> Aug 5 23:49:35 strawberry dhclient[12645]: send_packet: No
On Sun, Aug 05, 2018 at 06:25:57PM +0800, Erich Dollansky wrote:
> when I ran into this problem, I delete the IP address 0.0.0.0, kill
> dhclient and start a new dhclient. As we used fixed IP addresses for
> em0, the problem comes up only on wlan.
I tried that, but now the interface just gives up
the router led never blinks (no
data transfers during DHCPDISCOVER). I am not sure how to debug this.
-
Dhananjay Balan
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
On Wed, Jun 13, 2018 at 08:29:06AM -0700, Adrian Chadd wrote:
> hm. Which country are you in? india?
>
> It seems to think you're in the FCC4 regdomain and DE country, which
> if I read it right won't give you 5G. So somehow it determined you're
> in the "wrong" country?
No it was entirely my
On Sun, Jun 03, 2018 at 07:33:30PM +0200, Christoph Moench-Tegeder wrote:
> Is the regdomain/country setting correct for your area and matches your
> AP? Especially in the 5GHz band there are some "gaps" - not all channels
> may be used in all countries (because of possible interference with
>
On Sat, Jun 02, 2018 at 12:37:12AM +0200, Christoph Moench-Tegeder wrote:
> Did you try adding "mode 11a" to select 5GHz band? (This might be
> out-of-date, as my WiFi stuff is all on 11) (currently I'm also
> using 2.4GHz only, for compatibility with some devices and the fact
> that I have quite
Hi,
(Apologies if this is the wrong list, please point me at the right one if you
know)
I run 12-CURRENT (r334442) on a Thinkpad X230. This machine has an Intel
Centrino Advanced N 6205. But freebsd only uses in in 11g mode. When I
try to scan, it won't even display 5GHz aps.
wlan0:
12 matches
Mail list logo
