Re: Wake from sleep with nvidia-modeset

[David Wolfskill]

On Thu, Jul 29, 2021 at 06:15:19PM +0100, Graham Perrin wrote:
> nvidia-driver-460.84 from ports, nvidia-modeset, NVIDIA Quadro K1100M 
> (GK107GLM), HP ZBook 17 G2, KDE Plasma.
> 
> 
> 
> An initial wake from sleep was almost entirely successful, one exception:
> 
> * title bars of windows lacked colour.
> 
> Since then: all sleeps succeed, however I can never wake the computer. 
> There's an (immediate) dimly lit screen but nothing visible, and no 
> response to keyboard or trackpad input. It's necessary to force off the 
> computer.
> 
> I experimented with nvidia-driver-390-390.144, no better.
> 
> Any other suggestions?
> 
> I'd _love_ it to work, and the one near-success makes me believe that 
> it's possible.

I presume (since this is to current@) that you are workiing with head
(FreeBSD 14).

My older laptop is also using nvidia-modest from nvidia-driver-460.84;
hardware is NVIDIA GPU Quadro K2100M (GK106GL) (on a Dell PRecision
M4800).

Suspend/resume almost always works while running stable/12, tested most
recently running:

FreeBSD 12.2-STABLE #1099 stable/12-n233460-ac56cd3ba62: Tue Jul 27 03:32:24 
PDT 2021 
r...@g1-55.catwhisker.org:/common/S1/obj/usr/src/amd64.amd64/sys/CANARY  amd64 
1202508 1202508

but last I checked, resume fails for stable/13 and head (I track
each of the 3 daily).

One possibly-salient difference is that I had been running with

kern.vty="sc"

(and still do, for stable/12), but since the VBE changes earlier
this year, I let kern.vty take the default value (which I am not
recalling at the moment) for stable/13 and head.

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Life is not intended to be a zero-sum game.

See https://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: Building multiple kernels with "make release"

[Emmanuel Vadot]

On Thu, 29 Jul 2021 00:13:54 +
Glen Barber  wrote:

> On Wed, Jul 28, 2021 at 06:00:28PM -0600, Alan Somers wrote:
> > On Wed, Jul 28, 2021 at 5:52 PM Miroslav Lachman <000.f...@quip.cz> wrote:
> > 
> > > On 28/07/2021 20:46, Juraj Lutter wrote:
> > > >
> > > >
> > > >> On 28 Jul 2021, at 20:37, Glen Barber  wrote:
> > > >>
> > > >> On Wed, Jul 28, 2021 at 12:05:25PM -0600, Alan Somers wrote:
> > > >>> On Wed, Jul 28, 2021 at 11:57 AM Glen Barber  wrote:
> > >  Just on a hunch, could you try with adding INSTALLKERNEL="${KERNEL}"
> > > to
> > >  your release.conf?
> > > 
> > >  I now seem to recall some weirdness with this, but the exact details
> > >  elude me at the moment.
> > > 
> > > >>>
> > > >>> Setting INSTALLKERNEL="GENERIC-NODEBUG"  during "make installkernel"
> > > >>> overrides whatever KERNCONF was set to.  But it still only installs 
> > > >>> one
> > > >>> kernel.  Trying to set that variable to a list doesn't work.
> > > >>
> > > >> Ok.  Give me a day or so to try to figure out what is (or isn't)
> > > >> happening here.  I do not recall any recent-ish changes that would have
> > > >> caused this, and I am 95% certain it has worked in the past.
> > > >
> > > > According to Makefile.inc1:
> > > >
> > > > make installkernel KERNCONF=?KERN1 KERN2?
> > > >
> > > > should install KERN1 and KERN2. Similar goes for buildkernel.
> > > >
> > > > Or is there something I am missing?
> > >
> > > Does 'make installkernel KERNCONF=?KERN1 KERN2?' really install both
> > > kernels? Under which names?
> > > I have 3 kernels defined in KERNCONF in /etc/make.conf for years. 3
> > > kernels are built by "make buildkernel" but only one installed by "make
> > > installkernel".
> > >
> > > To install other kernels I use:
> > >
> > > make installkernel KERNCONF=KERN2 KODIR=/boot/kernel.KERN2
> > >
> > > make installkernel KERNCONF=KERN3 KODIR=/boot/kernel.KERN3
> > >
> > 
> > Miroslav is right.  Despite the comment that Juraj found, "make
> > installkernel" only installs the first kernel listed in KERNCONF.
> 
> Good find.  I honestly thought this worked as expected versus as
> written.  In fact, I *thought* secondary, tertiary, etc. kernels were
> installed as /boot/kernel.KERN2, /boot/kernel.KERN3 (using the example
> above).

 You need to set NO_INSTALLEXTRAKERNELS=no for that to happens (yes the
variable name and double no sucks if anyone have a patch for that that
would be awesome).

> Although, I may be misremembering, and 'kernel.KERN2.txz' may be created
> instead, although not installed/extracted.  Though, we are going back at
> least seven years, and I do not even remember what I had eaten for
> dinner last night, so there's that...
> 
> Glen
> 


-- 
Emmanuel Vadot  

Re: awk behaviour?

[Stefan Esser]

Am 29.07.21 um 18:42 schrieb Michael Butler via freebsd-current:
> On 7/29/21 6:09 AM, Michael Gmelin wrote:
>>
>>
>> On Wed, 28 Jul 2021 16:02:30 -0400
>> Ed Maste  wrote:
>>
>>> On Wed, 28 Jul 2021 at 15:15, Michael Butler via freebsd-current
>>>  wrote:

 What prompted the question was my (obviously poor) attempt to debug
 and resolve this failure when attempting to build a release for
 i386 on an amd64 ..
>>>
>>> This will be due to my 4e224e4be7c3. I'm not sure exactly what's
>>> happening yet, but I can provoke this behaviour if `${PKG_CMD}
>>> --version` outputs something other than a single line with the version
>>> number.
>>>
>>
>> Could it be, that the pkg binary isn't installed in $LOCALBASE/sbin/pkg,
>> (whatever LOCALBASE is at that point)? This would make pkg --version
>> shows its bootstrap message:
>>
>>    The package management tool is not yet installed on your system.
>>    Do you want to fetch and install it now? [y/N]:
>>
>> which could explain the behavior.
>>
>> Just speculating...
> 
> This is consistent with the behaviour I'm now seeing after the most recent 
> patch.
> 
> In the chroot environment used by a cross-compilation, there is no installed
> pkg port. When pkg is invoked in the target environment, it now waits on the
> yes/no response,

Passing "ASSUME_ALWAYS_YES=yes" in the environment should cause the
installation to proceed without a wait for user input.

Regards, STefan



OpenPGP_signature
Description: OpenPGP digital signature

Wake from sleep with nvidia-modeset

[Graham Perrin]

nvidia-driver-460.84 from ports, nvidia-modeset, NVIDIA Quadro K1100M 
(GK107GLM), HP ZBook 17 G2, KDE Plasma.




An initial wake from sleep was almost entirely successful, one exception:

* title bars of windows lacked colour.

Since then: all sleeps succeed, however I can never wake the computer. 
There's an (immediate) dimly lit screen but nothing visible, and no 
response to keyboard or trackpad input. It's necessary to force off the 
computer.


I experimented with nvidia-driver-390-390.144, no better.

Any other suggestions?

I'd _love_ it to work, and the one near-success makes me believe that 
it's possible.

Re: Building multiple kernels with "make release"

[Chris]

On 2021-07-28 10:11, Alan Somers wrote:

Is it possible to build multiple different kernels and include them all in
a release image?  release.conf says so.  But from experiment, what I see is
that:

* release.sh does pass both kernels in the KERNCONF variable to "make
buildkernel"
* "make buildkernel" dutifully builds both
* BUT, "make installkernel" only installs the first kernel and ignores the
rest
* Only the first kernel ends up in the final image
* It's not really clear where an alternate kernel should go, anyway.

FWIW
For me, the way I've always accomplished this was via the DESTDIR keyword
for kernels. Probably not the most elegant, or maybe even the "correct"
way. But It's something figured out a good while ago and since it worked. I
continue to use it. Maybe it'll work for you.

HTH

--Chris

Probably someplace like /boot/kernel.debug , but release.conf doesn't
provide a way to specify that.

So is the "multiple kernels in release.conf" feature unfinished?  If so,
does anybody have a good idea about the best way to finish it?

https://github.com/freebsd/freebsd-src/blob/7045b1603bdf054145dd958a4acc17b410fb62a0/release/release.conf.sample#L32

-Alan


0xBDE49540.asc
Description: application/pgp-keys

Re: awk behaviour?

[Michael Butler via freebsd-current]

On 7/29/21 6:09 AM, Michael Gmelin wrote:



On Wed, 28 Jul 2021 16:02:30 -0400
Ed Maste  wrote:


On Wed, 28 Jul 2021 at 15:15, Michael Butler via freebsd-current
 wrote:


What prompted the question was my (obviously poor) attempt to debug
and resolve this failure when attempting to build a release for
i386 on an amd64 ..


This will be due to my 4e224e4be7c3. I'm not sure exactly what's
happening yet, but I can provoke this behaviour if `${PKG_CMD}
--version` outputs something other than a single line with the version
number.



Could it be, that the pkg binary isn't installed in $LOCALBASE/sbin/pkg,
(whatever LOCALBASE is at that point)? This would make pkg --version
shows its bootstrap message:

   The package management tool is not yet installed on your system.
   Do you want to fetch and install it now? [y/N]:

which could explain the behavior.

Just speculating...


This is consistent with the behaviour I'm now seeing after the most 
recent patch.


In the chroot environment used by a cross-compilation, there is no 
installed pkg port. When pkg is invoked in the target environment, it 
now waits on the yes/no response,


imb

Re: Fwd: Information for freebsd-current@FreeBSD.org

[Baptiste Daroussin]

On Thu, Jul 29, 2021 at 05:39:04PM +0200, Matthias Apitz wrote:
> 
> Is this a phishing attack or did I missed some change in the FBSD
> mailing lists?
> 

This is not phishing attack this is the result of someone requesting help using
freebsd-current@f.o in the from and somehow not catched by our antispam.

Anyway those kind of request are now blocked.

As for the change in FBSD mailing list, it happened for most of the a couple of
month ago. Some are still in migration (the moderated one)

Best regards,
Bapt

Re: Fwd: Information for freebsd-current@FreeBSD.org

[Steve Kargl]

The mailing lists are migrating from mailman to Mlmmj.  I
suspect, but haven't verified, that this is the new norm
for the monthly notice about mailing list subscriptions.

I would suggesting reading the mailing list archives,
but needs to guess where the relevent discussion might
be found.  If you got here:

https://www.freebsd.org/community/mailinglists/

You'll find

   You can *search* or *browse* the mailing list archives.
   At the current time, archives prior to May 2021 are *in
   a separate archive.*

where *search*, *browse* and *in a separate archive.* are
hyperlinks.  This is quite misleading as at least

dev-commits-doc-all/-   2021-Jul-02 03:27
dev-commits-ports-all/  -   2021-Jul-01 03:27
dev-commits-ports-branches/ -   2021-Jul-04 03:27
dev-commits-ports-main/ -   2021-Jul-01 03:27
dev-commits-src-all/-   2021-Jul-02 03:27
dev-commits-src-branches/   -   2021-Jul-03 03:27
dev-commits-src-main-   2021-Jul-03 03:27

are under *in a separate archive*, which clearly shows
messages newer than the May 2021 date are not archived
under *browse*.  There are a few other archives that 
violate the statement on the FreeBSD.org.


-- 
steve

On Thu, Jul 29, 2021 at 05:39:04PM +0200, Matthias Apitz wrote:
> 
> Is this a phishing attack or did I missed some change in the FBSD
> mailing lists?
> 
>   matthias
> 
> - Forwarded message from freebsd-current+ow...@freebsd.org -
> 
> Date: Thu, 29 Jul 2021 15:00:41 +
> From: freebsd-current+ow...@freebsd.org
> To: freebsd-current@FreeBSD.org
> Subject: Information for freebsd-current@FreeBSD.org
> 
> Hi, this is the Mlmmj program managing the 
> mailing list.
> 
> Here is some information about the list.
> 
> You can subscribe to the following versions:
> 
> - The normal version: Every time a post is sent to the list, subscribers
>   receive a copy of it. Subscribe by emailing
>   .
> 
> - The digest version: Subscribers receive multiple posts in a single mail
>   message, at regular intervals, or when a lot of posts have accumulated.
>   Subscribe by emailing .
> 
> - The no-mail version: Subscribers do not receive any posts to the list.
>   This means, though, they are able to post to a list which only
>   subscribers may post to, while they follow the list using a web archive
>   or another subscribed email address. Subscribe by emailing
>   .
> 
> Unsubscribe by emailing .
> 
> Posts are made by emailing .
> 
> However, only subscribers may post to the list.
> 
> The list also has access rules which may affect who can post and which
> posts are moderated.
> 
> Subscribers can retrieve message number N from the list's archive by
> sending a message to  (change the N to
> the number of the desired message).
> 
> You can retrieve the frequently asked questions document for the list by
> sending a message to .
> 
> To contact the list owner, send a message to
> .
> 
> 
> 
> - End forwarded message -
> 
> -- 
> Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
> Public GnuPG key: http://www.unixarea.de/key.pub
> Tear it down! Defund the Humboldt Forum!
> https://www.jungewelt.de/artikel/406715.humboldt-forum-feudaler-themenpark.html
> 

-- 
Steve

Fwd: Information for freebsd-current@FreeBSD.org

[Matthias Apitz]

Is this a phishing attack or did I missed some change in the FBSD
mailing lists?

matthias

- Forwarded message from freebsd-current+ow...@freebsd.org -

Date: Thu, 29 Jul 2021 15:00:41 +
From: freebsd-current+ow...@freebsd.org
To: freebsd-current@FreeBSD.org
Subject: Information for freebsd-current@FreeBSD.org

Hi, this is the Mlmmj program managing the 
mailing list.

Here is some information about the list.

You can subscribe to the following versions:

- The normal version: Every time a post is sent to the list, subscribers
  receive a copy of it. Subscribe by emailing
  .

- The digest version: Subscribers receive multiple posts in a single mail
  message, at regular intervals, or when a lot of posts have accumulated.
  Subscribe by emailing .

- The no-mail version: Subscribers do not receive any posts to the list.
  This means, though, they are able to post to a list which only
  subscribers may post to, while they follow the list using a web archive
  or another subscribed email address. Subscribe by emailing
  .

Unsubscribe by emailing .

Posts are made by emailing .

However, only subscribers may post to the list.

The list also has access rules which may affect who can post and which
posts are moderated.

Subscribers can retrieve message number N from the list's archive by
sending a message to  (change the N to
the number of the desired message).

You can retrieve the frequently asked questions document for the list by
sending a message to .

To contact the list owner, send a message to
.



- End forwarded message -

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
Tear it down! Defund the Humboldt Forum!
https://www.jungewelt.de/artikel/406715.humboldt-forum-feudaler-themenpark.html

Information for freebsd-current@FreeBSD.org

[freebsd-current+owner]

Hi, this is the Mlmmj program managing the 
mailing list.

Here is some information about the list.

You can subscribe to the following versions:

- The normal version: Every time a post is sent to the list, subscribers
  receive a copy of it. Subscribe by emailing
  .

- The digest version: Subscribers receive multiple posts in a single mail
  message, at regular intervals, or when a lot of posts have accumulated.
  Subscribe by emailing .

- The no-mail version: Subscribers do not receive any posts to the list.
  This means, though, they are able to post to a list which only
  subscribers may post to, while they follow the list using a web archive
  or another subscribed email address. Subscribe by emailing
  .

Unsubscribe by emailing .

Posts are made by emailing .

However, only subscribers may post to the list.

The list also has access rules which may affect who can post and which
posts are moderated.

Subscribers can retrieve message number N from the list's archive by
sending a message to  (change the N to
the number of the desired message).

You can retrieve the frequently asked questions document for the list by
sending a message to .

To contact the list owner, send a message to
.

Re: awk behaviour?

[Michael Gmelin]

On Wed, 28 Jul 2021 16:02:30 -0400
Ed Maste  wrote:

> On Wed, 28 Jul 2021 at 15:15, Michael Butler via freebsd-current
>  wrote:
> >
> > What prompted the question was my (obviously poor) attempt to debug
> > and resolve this failure when attempting to build a release for
> > i386 on an amd64 ..  
> 
> This will be due to my 4e224e4be7c3. I'm not sure exactly what's
> happening yet, but I can provoke this behaviour if `${PKG_CMD}
> --version` outputs something other than a single line with the version
> number.
> 

Could it be, that the pkg binary isn't installed in $LOCALBASE/sbin/pkg,
(whatever LOCALBASE is at that point)? This would make pkg --version
shows its bootstrap message: 

  The package management tool is not yet installed on your system.
  Do you want to fetch and install it now? [y/N]: 

which could explain the behavior.

Just speculating...

-m

-- 
Michael Gmelin

Error in buildkernel

[Filippo Moretti via current]

Good morning,    I have the following error in build 
kernel:ror=unused-function -Wno-error=pointer-sign 
-Wno-error=shift-negative-value -Wno-address-of-packed-member 
-Wno-format-zero-length   -mno-aes -mno-avx  -std=iso9899:1999 -Werror vers.c
ctfconvert -L VERSION -g vers.o
linking kernel.full
ld: error: undefined symbol: xen_clock_init
>>> referenced by pv.c
>>>   pv.o:(xen_pvh_init_ops)

ld: error: undefined symbol: xen_delay
>>> referenced by pv.c
>>>   pv.o:(xen_pvh_init_ops)
*** Error code 1

Stop.
make[2]: stopped in /usr/obj/usr/src/amd64.amd64/sys/STING
*** Error code 1

Stop.
make[1]: stopped in /usr/src

[root@sting /usr/src]# uname -a
FreeBSD sting 14.0-CURRENT FreeBSD 14.0-CURRENT #43 main-n248147-8539518055d: 
Thu Jul 22 11:36:29 CEST 2021 
root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING  amd64

sincerelyFilippo