On 05/30/18 17:50, Glen Barber wrote:
Hi,
Could folks please help boot-test the most recent 12.0-CURRENT amd64
memstick images on various hardware? Note, this is not a request to
install 12.0-CURRENT, only a boot-test with various system knobs
tweaked.
The most recent images are available at:
2018-06-03 7:23 GMT+02:00 Albert :
> Hi,
>
>
> I successfully tested the memstick.img on:
> Acer Chromebook 14 (EDGAR) [CB3-431-C5EX]
>
> The Results:
> UEFI (Coreboot) works perfectly, no issues there.
> BIOS (SeaBIOS) does *NOT* work. It puts the machine into a bootloop until
> the install medium
On May 31 22:50, Konstantin Belousov wrote:
On Thu, May 31, 2018 at 08:19:20PM +0200, Dimitry Andric wrote:
On 31 May 2018, at 20:11, Warner Losh wrote:
>
> On Thu, May 31, 2018 at 11:47 AM, Dimitry Andric wrote:
> On 31 May 2018, at 18:04, Benjamin Kaduk wrote:
> > On Thu, May 31, 2018 at 09
cc -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=\"390.59\"
-D__KERNEL__ -DNVRM -Wno-unused-function -Wuninitialized -O2
-fno-strict-aliasing -mno-red-zone -mcmodel=kernel -Wno-sign-co
mpare -Wno-format-extra-args -UDEBUG -U_DEBUG -DNDEBUG -Werror=undef
-Werror -D_KERNEL -DKLD_MODULE -nostdin
On Sun, Jun 03, 2018 at 06:48:01PM +0700, Alex V. Petrov wrote:
>
> --- nvidia_subr.o ---
>
>
> nvidia_subr.c:367:26: error: 'memset' call operates on objects of type
> 'struct nv_ioctl_card_info' while the size is based on a different type
> 'struct nv_ioctl_card_info *' [-Werror,-Wsizeof
>
On Sun, Jun 03, 2018 at 05:08:34AM -0700, David Wolfskill wrote:
> On Sun, Jun 03, 2018 at 06:48:01PM +0700, Alex V. Petrov wrote:
> >
> > --- nvidia_subr.o ---
> >
> >
> > nvidia_subr.c:367:26: error: 'memset' call operates on objects of type
> > 'struct nv_ioctl_card_info' while the size i
‐‐‐ Original Message ‐‐‐
On June 3, 2018 8:21 AM, Konstantin Belousov wrote:
> On Sun, Jun 03, 2018 at 05:08:34AM -0700, David Wolfskill wrote:
>
> > On Sun, Jun 03, 2018 at 06:48:01PM +0700, Alex V. Petrov wrote:
> >
> > >
> > >
> > > --- nvidia_subr.o ---
> > >
> > > nvid
This is caused by r334533 and/or r334534 (memset-related changes).
sysutils/lsof is also affected.
You should revert r334533 and r334534 temporarily until nvidia-driver
support this change.
CC'ing the revision author and maintainers of both ports.
On Sun, 3 Jun 2018 18:48:01 +0700
"Alex V. Petr
Hi,
After upgrading CURRENT to r333992 (from something at least a year
old, quite some changes in mp_machdep.c since), this machine crashes
on boot:
Copyright (c) 1992-2018 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the Uni
On Sun, Jun 3, 2018 at 2:42 PM, Tomoaki AOKI
wrote:
> This is caused by r334533 and/or r334534 (memset-related changes).
> sysutils/lsof is also affected.
>
> You should revert r334533 and r334534 temporarily until nvidia-driver
> support this change.
>
> CC'ing the revision author and maintainer
On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin wrote:
> Hi,
>
> After upgrading CURRENT to r333992 (from something at least a year
> old, quite some changes in mp_machdep.c since), this machine crashes
> on boot:
>
> Copyright (c) 1992-2018 The FreeBSD Project.
> Copyright (c) 1979, 198
sysutils/lsof fixed in r471495.
Thanks, Mateusz!
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106
From: Mateusz Guzik
Date: Sunday, June 3, 2018 at 8:20
SeaBIOS 1.10.2
Upgrading seems to do the trick
> Am 03.06.2018 um 06:25 schrieb Idwer Vollering :
>
> 2018-06-03 7:23 GMT+02:00 Albert :
>> Hi,
>>
>>
>> I successfully tested the memstick.img on:
>> Acer Chromebook 14 (EDGAR) [CB3-431-C5EX]
>>
>> The Results:
>> UEFI (Coreboot) works perfectl
On Sun, 3 Jun 2018 16:21:10 +0300
Konstantin Belousov wrote:
> On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin wrote:
> > Hi,
> >
> > After upgrading CURRENT to r333992 (from something at least a year
> > old, quite some changes in mp_machdep.c since), this machine crashes
> > on boo
On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin wrote:
>
>
> On Sun, 3 Jun 2018 16:21:10 +0300
> Konstantin Belousov wrote:
>
> > On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin wrote:
> > > Hi,
> > >
> > > After upgrading CURRENT to r333992 (from something at least a year
>
On 31 May 2018 at 11:19, Dimitry Andric wrote:
> On 31 May 2018, at 20:11, Warner Losh wrote:
>>
>> On Thu, May 31, 2018 at 11:47 AM, Dimitry Andric wrote:
>> On 31 May 2018, at 18:04, Benjamin Kaduk wrote:
>> > On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote:
>> >> On Thu, 31 Ma
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 s
On Sun, Jun 3, 2018 at 9:53 AM, Dhananjay Balan wrote:
> 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 c
## Dhananjay Balan (m...@dbalan.in):
> 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 s
## Adam (amvandem...@gmail.com):
> > 3. ifconfing wlan0 scan still doesn't show my 5Ghz only APs (at least some
> > I tested)
>
> I don't believe the iwn driver is capable of 5gz. At least mine doesn't
> work on CURRENT.
The iwn driver has code for 5GHz (I've no idea if that's complete).
But lo
In message <20180603174401.rbxa3fcnuopro...@squirrel.exwg.net>,
Christoph Moenc
h-Tegeder writes:
> ## Adam (amvandem...@gmail.com):
>
> > > 3. ifconfing wlan0 scan still doesn't show my 5Ghz only APs (at least som
> e
> > > I tested)
> >
> > I don't believe the iwn driver is capable of 5gz. At
I have a few (3) new files in the projects/pnfs-planb-server subversion tree
that all have the 2 clause FreeBSD copyright.
Do I just add the "SPDX..." line for this license at the top of the copyright
comment
or is there some other exercise needed to be done for this?
Thanks, rick
__
Quoting Alexander Leidinger (from Mon, 28
May 2018 09:02:01 +0200):
Quoting Slawa Olhovchenkov (from Mon, 28 May 2018
01:06:12 +0300):
On Sun, May 27, 2018 at 09:41:59PM +0200, Kirill Ponomarev wrote:
On 05/22, Slawa Olhovchenkov wrote:
> It has been a while since I tried Karl's patch
On Sun, Jun 03, 2018 at 09:14:50PM +0200, Alexander Leidinger wrote:
> Quoting Alexander Leidinger (from Mon, 28
> May 2018 09:02:01 +0200):
>
> > Quoting Slawa Olhovchenkov (from Mon, 28 May 2018
> > 01:06:12 +0300):
> >
> >> On Sun, May 27, 2018 at 09:41:59PM +0200, Kirill Ponomarev wrote
Quoting Alexander Leidinger (from Sun, 27
May 2018 21:12:17 +0200):
Quoting Chris H (from Tue, 22 May 2018
09:59:04 -0700):
Hello, Alexander.
I'm not sure if this landed in -CURRENT. I only know it landed in 11.
But your trouble might be related to pr #224247 :
https://bugs.freebsd.or
I couldn't make the S3 suspend to work at all.
Please see the bug report:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228654
Yuri
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsu
On Sun, 3 Jun 2018 18:04:23 +0300
Konstantin Belousov wrote:
> On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin wrote:
> >
> >
> > On Sun, 3 Jun 2018 16:21:10 +0300
> > Konstantin Belousov wrote:
> >
> > > On Sun, Jun 03, 2018 at 02:48:40PM +0200, Michael Gmelin wrote:
> > > >
I believe the problem of local_unbound segfaulting began after I compiled
the source after the large commit to unbound on Saturday, May 12, 2018
(about 3 weeks ago).
I assumed the problem was probably common if I was experiencing it, but
I've seen no other mentions of it. I'm not sure what info I
On Sun, Jun 03, 2018 at 09:50:20PM +0200, Michael Gmelin wrote:
>
>
> On Sun, 3 Jun 2018 18:04:23 +0300
> Konstantin Belousov wrote:
>
> > On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin wrote:
> > >
> > >
> > > On Sun, 3 Jun 2018 16:21:10 +0300
> > > Konstantin Belousov wrote:
> >
mmacy has sent me a bunch of warnings of the "variable set but not used" kind
generated by gcc8.
When I've looked at the code, these are for RPC arguments I parse but do not
use at this time.
I'd like to leave the code in place, since these arguments may be needed in the
future and it is hard to
On Sun, Jun 3, 2018 at 3:28 PM, Rick Macklem wrote:
> mmacy has sent me a bunch of warnings of the "variable set but not used"
> kind
> generated by gcc8.
>
> When I've looked at the code, these are for RPC arguments I parse but do
> not
> use at this time.
> I'd like to leave the code in place,
On 06/03/18 17:33, Warner Losh wrote:
On Sun, Jun 3, 2018 at 3:28 PM, Rick Macklem wrote:
mmacy has sent me a bunch of warnings of the "variable set but not used"
kind
generated by gcc8.
When I've looked at the code, these are for RPC arguments I parse but do
not
use at this time.
I'd like t
In message
, Warner Losh writes:
> On Sun, Jun 3, 2018 at 3:28 PM, Rick Macklem wrote:
>
> > mmacy has sent me a bunch of warnings of the "variable set but not used"
> > kind
> > generated by gcc8.
> >
> > When I've looked at the code, these are for RPC arguments I parse but do
> > not
> > use at
On Sun, Jun 03, 2018 at 09:28:47PM +, Rick Macklem wrote:
> mmacy has sent me a bunch of warnings of the "variable set but not used" kind
> generated by gcc8.
>
> When I've looked at the code, these are for RPC arguments I parse but do not
> use at this time.
> I'd like to leave the code in p
On Sun, Jun 3, 2018 at 2:40 PM, Theron wrote:
>> 4. Disable the stupid warning in the Makefile / build system. If you don't
>> care, and there's a good reason for what you are doing (sounds like there
>> is), better to just disable the warning as so much useless noise.
>>
>> Warner
>>
On Sun, 3 Jun 2018 23:53:40 +0300
Konstantin Belousov wrote:
> On Sun, Jun 03, 2018 at 09:50:20PM +0200, Michael Gmelin wrote:
> >
> >
> > On Sun, 3 Jun 2018 18:04:23 +0300
> > Konstantin Belousov wrote:
> >
> > > On Sun, Jun 03, 2018 at 04:55:00PM +0200, Michael Gmelin wrote:
> > > >
> I have a few (3) new files in the projects/pnfs-planb-server subversion tree
> that all have the 2 clause FreeBSD copyright.
>
> Do I just add the "SPDX..." line for this license at the top of the copyright
> comment
> or is there some other exercise needed to be done for this?
Just add the SP
Hi all,
I have a ASUS Zenbook UX430U with the same problem. I am heading to
BSDCan (and the FreeBSD Dev Submit as a guest) this week and could spend
some time working on this in the hacker lounge. That said, I am new to
FreeBSD driver code, so I could use some guidance to help me along.
Anyon
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
> rad
39 matches
Mail list logo
