Re: FreeBSD 14.x localhost source address

Van: Craig Leres Datum: dinsdag, 2 juli 2024 01:04 Aan: Michael Proto CC: freebsd-sta...@freebsd.org Onderwerp: Re: FreeBSD 14.x localhost source address On 7/1/24 15:53, Michael Proto wrote: > What netmask are you using for 127.0.0.2? I'd treat it as I would an > IP alias (only on localhost

Re: BIND 9.19.24 not listening to rndc port (953)

>> Other info: >> >> - BIND 9.18.24 on the same host works perfectly, with no rndc issues. >> - BIND 9.19.24 on the same host also works *if I change it to run as >> root* (by default it runs as user bind). The syslog messages are gone, >> and rndc works as expected. > > That sounds like they try

Re: FreeBSD Day 2024 - Colin Percival

Steven Friedrich: > Linux routes sound from the audio driver to the video > driver causing sound to come out of the HDMI cable. > FreeBSD can't. This affects ALL i3, i5, i7, i9 systems. > FreeBSD can't even support x11 on my GMKtec K8 with Radeon > 780M graphics. Linux Mint does. Sounds a tad r

Re: freebsd hdmi audi

On Tue, 2 Jul 2024, at 03:56, Steven Friedrich wrote: > Linux routes sound from the audio driver to the video driver causing > sound to come out of the HDMI cable. FreeBSD can't. This affects ALL i3, > i5, i7, i9 systems. > FreeBSD can't even support x11 on my GMKtec K8 with Radeon 780M > graphi

Re: freebsd hdmi audi

Thank you for a response, it's the first in a decade for this issue. I have two HP's, a Slimline with an i7, and an Envy with an i7. Both are small towers (desktops). I too use drm-kmod and x11. dmesg: hdacc0: at cad 0 on hdac0 hdaa0: at nid 1 on hdacc0 pcm0: at nid 20 and 27 on hdaa0 pcm

Re: new error messages after upgrade 14.0-p5 to 14.1-p1 amd64

On Sat, Jun 29, 2024 at 3:18 AM void wrote: > > On Fri, Jun 28, 2024 at 01:23:29PM +0100, void wrote: > > (snip) > > Just to add to this, the reported error does *not* occur on > 15.0-CURRENT #5 n270917-5dbf886104b4 arm64 > > and that system has *only* nfs_client_enable="YES" > > and it's a slower

Re: BIND 9.19.24 not listening to rndc port (953)

On Tue, 2 Jul 2024, sth...@nethelp.no wrote: Other info: - BIND 9.18.24 on the same host works perfectly, with no rndc issues. - BIND 9.19.24 on the same host also works *if I change it to run as root* (by default it runs as user bind). The syslog messages are gone, and rndc works as expected.

Re: BIND 9.19.24 not listening to rndc port (953)

On Mon, 1 Jul 2024, Craig Leres wrote: On 7/1/24 10:17, Bakul Shah wrote: On Jul 1, 2024, at 9:18 AM, Craig Leres wrote: On 6/30/24 04:46, sth...@nethelp.no wrote: Short description: Fresh install of bind9-devel-9.19.24_1 doesn't listen to localhost port 953, with the result that rndc doesn

Re: BIND 9.19.24 not listening to rndc port (953)

>> So we set uid 53 (bind) at 0.083518302, and then try to bind to port >> 953 at 0.093282161. > > Are you going to poe a bug with the bind people? Already did: https://gitlab.isc.org/isc-projects/bind9/-/issues/4793 Steinar Haug, AS2116

Re: FreeBSD 14.x localhost source address

On 7/2/24 01:40, Ronald Klop wrote: Could it be that this mail thread also applies to your situation? https://lists.freebsd.org/archives/freebsd-current/2024-June/006047.html It has a follow-up about a fix in https://l

x11/nvidia-driver fails on 14-STABLE/amd64

Hi, I updated my STABLE-14/amd64 to 1a0314d6e30554fc2b07caa5121b00956f416cc4 (ctladm: Fix a race), and it appears that the latest kernel update breaks x11/nvidia-driver. The system panics when X starts up. Just to be sure I have rebuild and resinstalled x11/nvidia-driver with the updated /u

Re: x11/nvidia-driver fails on 14-STABLE/amd64

On Tue, 02 Jul 2024 22:11:45 + j...@chen.org.nz wrote: > Hi, > > I updated my STABLE-14/amd64 to 1a0314d6e30554fc2b07caa5121b00956f416cc4 > (ctladm: Fix a race), and it appears that the latest kernel update breaks > x11/nvidia-driver. The system panics when X starts up. Just to be sure