14.0-CURRENT panic in early boot

2021-11-17 Thread Dustin Marquess
I just updated a machine from a build that was ~2 weeks old. The latest commit when I built it was 2e946f87055. The system boots using UEFI, if that matters. The system is panicking pretty early in the boot, however: real memory = 137438953472 (131072 MB) avail memory = 133651496960 (127460 MB)

Re: Incompatible change in LLD13 causing link errors?

2021-11-17 Thread Stefan Esser
Am 17.11.21 um 21:20 schrieb Dimitry Andric: > On 17 Nov 2021, at 21:07, Stefan Esser wrote: >> >> I have just received pkg-fallout for a port that has not been touched >> for several months, specifically lang/silq. >> >> ld.lld: error: undefined hidden symbol: __start___minfo > referenced by

Re: Incompatible change in LLD13 causing link errors?

2021-11-17 Thread Dimitry Andric
On 17 Nov 2021, at 21:07, Stefan Esser wrote: > > I have just received pkg-fallout for a port that has not been touched > for several months, specifically lang/silq. > > ld.lld: error: undefined hidden symbol: __start___minfo referenced by terminal.d silq.o:(ldc.register_d

"Khelp module "ertt" can't unload until its refcount drops from 1 to 0." after "All buffers synced."?

2021-11-17 Thread Mark Millard via freebsd-current
I've not noticed the ertt message before in: . . . Waiting (max 60 seconds) for system thread `bufspacedaemon-1' to stop... done All buffers synced. Uptime: 1d9h57m18s Khelp module "ertt" can't unload until its refcount drops from 1 to 0. === Mark Millard marklmi at yahoo.com ( dsl-only.net wen

Incompatible change in LLD13 causing link errors?

2021-11-17 Thread Stefan Esser
I have just received pkg-fallout for a port that has not been touched for several months, specifically lang/silq. ld.lld: error: undefined hidden symbol: __start___minfo >>> referenced by terminal.d >>> silq.o:(ldc.register_dso) ld.lld: error: undefined hidden symbol: __stop___minfo

Re: aarch64(?) poudiere-devel based builds seem to get fairly-rare corrupted files after recent system update(s?)

2021-11-17 Thread Mark Millard via freebsd-current
On 2021-Nov-15, at 15:43, Mark Millard wrote: > On 2021-Nov-15, at 13:13, Mark Millard wrote: > >> On 2021-Nov-15, at 12:51, Mark Millard wrote: >> >>> On 2021-Nov-15, at 11:31, Mark Millard wrote: >>> I updated from (shown a system that I've not updated yet): # uname -apKU

Re: FreeBSD 14.0-CURRENT snapshots in Google Compute Engine

2021-11-17 Thread Ed Maste
On Tue, 16 Nov 2021 at 23:22, Li-Wen Hsu wrote: > > You can use this command to list all the images built by re: > > gcloud compute images list --no-standard-images > --project=freebsd-org-cloud-dev Aside, it looks like we have many EOL images that are not marked as deprecated in the gcloud l

Re: sound on FreeBSD 14.0-CURRENT

2021-11-17 Thread Ludovit Koren
> Hans Petter Selasky writes: > On 11/17/21 13:36, Ludovit Koren wrote: >> firefox plays via speakers > In firefox go to "about:config", then add this string: > media.cubeb.backend oss > Then restart firefox. yes, it plays via headphones thanks, lk

Re: sound on FreeBSD 14.0-CURRENT

2021-11-17 Thread Ludovit Koren
> Jakob Alvermark writes: > On 11/17/21 11:03, Ludovit Koren wrote: >>> Hans Petter Selasky writes: >> > Hi, >> >> Still the same result... >> >> >> >> > Please show all commands you try! >> >> > Can you explain, which if these devices you want to re

Re: sound on FreeBSD 14.0-CURRENT

2021-11-17 Thread Hans Petter Selasky
On 11/17/21 13:36, Ludovit Koren wrote: firefox plays via speakers In firefox go to "about:config", then add this string: media.cubeb.backend oss Then restart firefox. --HPS

Re: sound on FreeBSD 14.0-CURRENT

2021-11-17 Thread Jakob Alvermark
On 11/17/21 11:03, Ludovit Koren wrote: Hans Petter Selasky writes: > Hi, >> Still the same result... >> > Please show all commands you try! > Can you explain, which if these devices you want to receive audio > from, and which you want to transmit audio to:

Re: sound on FreeBSD 14.0-CURRENT

2021-11-17 Thread Ludovit Koren
> Hans Petter Selasky writes: > Hi Ludovit, >> It does not work automatically on the new notebook. I suppose pcm1, >> is >> the output for the jack headphones. >> I just tried without virtual_oss, with virtual_oss, starting with -f >> /dev/dsp0; /dev/dsp1; /dev/dsp2; /

Re: sound on FreeBSD 14.0-CURRENT

2021-11-17 Thread Vladimir Kondratyev
On 17.11.2021 13:03, Ludovit Koren wrote: Hans Petter Selasky writes: > Hi, >> Still the same result... >> > Please show all commands you try! > Can you explain, which if these devices you want to receive audio > from, and which you want to transmit audio to:

Re: sound on FreeBSD 14.0-CURRENT

2021-11-17 Thread Hans Petter Selasky
Hi Ludovit, It does not work automatically on the new notebook. I suppose pcm1, is the output for the jack headphones. I just tried without virtual_oss, with virtual_oss, starting with -f /dev/dsp0; /dev/dsp1; /dev/dsp2; /dev/dsp1.0; /dev/dsp2.0; then using virtual_oss_cmd using different devi

Re: sound on FreeBSD 14.0-CURRENT

2021-11-17 Thread Ludovit Koren
> Hans Petter Selasky writes: > Hi, >> Still the same result... >> > Please show all commands you try! > Can you explain, which if these devices you want to receive audio > from, and which you want to transmit audio to: > pcm0: (play/rec) default > pcm1:

Re: sound on FreeBSD 14.0-CURRENT

2021-11-17 Thread Hans Petter Selasky
Hi, Still the same result... Please show all commands you try! Can you explain, which if these devices you want to receive audio from, and which you want to transmit audio to: pcm0: (play/rec) default pcm1: (play) pcm2: (play) It might also be the mixer has the volume or recording