Hi!
The whole situation I'm going to explain is a little bit weird:
I'm running FreeBSD 15-STABLE with custom kernel, I use almost exclusively binary packages, except for graphics/drm-latest-kmod and www/ungoogled-chromium, which I compile from ports (main git brach). Now, I had no surprises with that, until today. Yesterday, I did a pkg-upgrade(8) for binary packages. There were maybe a dozen packages that were updated; I don't remember all of them obviously, but I'm sure there were ffmpeg updated from version 6 to version 8 and Imagick7. Of course, I looked through all the package names and didn't saw anything strange.
Today I rebooted into this system. And a) graphics/drm-latest-kmod was not loaded properly. Now, I know that after compiling your custom kernel or updating a ports tree or updating the world maybe you're almost better off recompiling drm drivers too, because they depend on your kernel interface. But this case is a little bit of a surprise to me: why did drm-latest-kmod refuse to work after updating binary packages (I did not recompile the kernel or something)? Well, I went ahead and recompiled this port (note: without fetching the latest port updates from git, it means there was the very same version of the port that used to be compiled before) and it works now. Yes, I sort of solved the issue, but I want to know what was the actual cause of that?
But that's not all: b) the network things became a little weird too: when I faced problem a) I went to /usr/port and issued
I tried
Well, I recalled that devel/git was among the ports to be upgraded (2.50 -> 2.52), so naturally, I though that there was a conflict with options or network stuff specifically for git. But ping(8) didn't work either, so the problem is not port-specific.
Well, I recently was tinkering with my kernel configuration for networking, so I had another version of kernel that was lingering around since that times. I booted into it and everything works just fine. So I got curious, I dumped sysctl(8)
Looks weird, but ok, I added this options into my current configuration, recompiled the kernel, booted, and it still didn't work. So it seems that 'good kernel' (one that appeared to work) was compiled with different environment options or something... I did tweak /etc/src.conf since then as far as I remember, but I don't believe I was changing something essential or whatnot...
Well, all in all, it seems that I screwed things a little bit compiling all stuff myself, so I've launched a
Thank you!
The whole situation I'm going to explain is a little bit weird:
I'm running FreeBSD 15-STABLE with custom kernel, I use almost exclusively binary packages, except for graphics/drm-latest-kmod and www/ungoogled-chromium, which I compile from ports (main git brach). Now, I had no surprises with that, until today. Yesterday, I did a pkg-upgrade(8) for binary packages. There were maybe a dozen packages that were updated; I don't remember all of them obviously, but I'm sure there were ffmpeg updated from version 6 to version 8 and Imagick7. Of course, I looked through all the package names and didn't saw anything strange.
Today I rebooted into this system. And a) graphics/drm-latest-kmod was not loaded properly. Now, I know that after compiling your custom kernel or updating a ports tree or updating the world maybe you're almost better off recompiling drm drivers too, because they depend on your kernel interface. But this case is a little bit of a surprise to me: why did drm-latest-kmod refuse to work after updating binary packages (I did not recompile the kernel or something)? Well, I went ahead and recompiled this port (note: without fetching the latest port updates from git, it means there was the very same version of the port that used to be compiled before) and it works now. Yes, I sort of solved the issue, but I want to know what was the actual cause of that?
But that's not all: b) the network things became a little weird too: when I faced problem a) I went to /usr/port and issued
git pull origin main in order to download latest changes, but I got an error:
Code:
ssh: Could not resolve hostname git.freebsd.org: Address family for hostname not supported ping google.com and name resolution really didn't work. Well, first I looked into /etc/resolv.conf and I found that my nameserver was set to 192.168.1.4 instead of 192.168.1.1, which I usually had. So I edited the file, then service resolv restart and name resolution was ok, but I still couldn't fetch changes: in the system console I saw the error:
Code:
ntpd[1737]: error resolving pool 0.freebsd.pool.ntp.org: Address family for hostname not supported (1)Well, I recently was tinkering with my kernel configuration for networking, so I had another version of kernel that was lingering around since that times. I booted into it and everything works just fine. So I got curious, I dumped sysctl(8)
kern.conftxt for both kernels into two different files and then run git diff on them and the only difference there was:
Code:
@@ -29,6 +29,10 @@ options PSEUDOFS
options UFS_DIRHASH
options SOFTUPDATES
options FFS
+options IPFIREWALL_VERBOSE_LIMIT=5
+options IPFIREWALL_VERBOSE
+options IPFIREWALL_DEFAULT_TO_ACCEPT
+options IPFIREWALL
options TCP_RFC7413
options TCP_HHOOK
options TCP_BLACKBOXLooks weird, but ok, I added this options into my current configuration, recompiled the kernel, booted, and it still didn't work. So it seems that 'good kernel' (one that appeared to work) was compiled with different environment options or something... I did tweak /etc/src.conf since then as far as I remember, but I don't believe I was changing something essential or whatnot...
Well, all in all, it seems that I screwed things a little bit compiling all stuff myself, so I've launched a
buildworld right now, I will see how it goes. But I want to ask you if you by any chance have an idea what potentially might be the cause for all that mess I've just described?Thank you!
