A bit late to the party but finally found the key to this.

It seems that the nouveau driver looks for a /lib/firmware/nvidia directory containing 28 directories with firmware for supported Nvidia cards neeeding non-free firmware files to work properly. ie: gaxxx, gkxxx, gmxxx, gpxxx, tegraxxx and tuxxx.

Not finding the directory, it prints out the warning.
Makes sense but should this not be part of the installation/ upgrade process?

If your Nvidia hardware is not on that list, you obviously do not need those firmware files in your system (~4.5MiB on disk).
So you either learn to live with the warning (shows up with every kernel and initramfs upgrade) or install the firmware-misc-nonfree package.

No idea why the nouveau driver looks for firmware it clearly does not need.
Is it not aware of the installed hardware to check against the supported cards that need firmware?

eg:

:~$ lspci                                 
--- snip ---
01:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] (rev a1)
02:00.0 VGA compatible controller: NVIDIA Corporation G96CGL [Quadro FX 580] (rev a1)
--- snip ---
:~$

Best,

A.

Fortunately, it is relatively easy to extract and install the nvidia firmware yourself. The whole issue is explained here, in the Firmware section: https://nouveau.freedesktop.org/VideoAcceleration.html

I updated more of them and I see that they still work,  but I will have to give you more details probably.

EDIT:

Refer to this link:

https://dev1galaxy.org/viewtopic.php?id=6700

Same topic I am mentioning, but yeah.

Weird stuff.

Could be ...

~$ sudo symlinks -csrv / | grep dangling
dangling: /usr/bin/hsdb -> /etc/alternatives/hsdb
dangling: /usr/bin/clhsdb -> /etc/alternatives/clhsdb
dangling: /usr/lib/x86_64-linux-gnu/qt-default/qtchooser/default.conf -> ../../../../share/qtchooser/qt5-x86_64-linux-gnu.conf
dangling: /usr/share/texmf/ls-R -> /var/lib/texmf/ls-R-TEXMFMAIN
dangling: /etc/systemd/system/reboot.target.wants/hwclock-save.service -> /lib/systemd/system/hwclock-save.service
dangling: /etc/systemd/system/getty.target.wants/getty@tty1.service -> /lib/systemd/system/getty@.service
dangling: /etc/systemd/system/multi-user.target.wants/smartd.service -> /lib/systemd/system/smartd.service
dangling: /etc/systemd/system/multi-user.target.wants/remote-fs.target -> /lib/systemd/system/remote-fs.target
dangling: /etc/systemd/system/timers.target.wants/apt-daily.timer -> /lib/systemd/system/apt-daily.timer
dangling: /etc/systemd/system/timers.target.wants/apt-daily-upgrade.timer -> /lib/systemd/system/apt-daily-upgrade.timer
dangling: /etc/systemd/system/poweroff.target.wants/hwclock-save.service -> /lib/systemd/system/hwclock-save.service
dangling: /etc/systemd/system/halt.target.wants/hwclock-save.service -> /lib/systemd/system/hwclock-save.service
dangling: /etc/alternatives/hsdb -> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/hsdb
dangling: /etc/alternatives/clhsdb -> /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/clhsdb
/tmp/.mount_LibreWI1bucL: Permission denied
dangling: /root/.config/pulse/26a708d3d7dc6778fc6ff9f55921b024-runtime -> /tmp/pulse-PKdhtXMmr18n
~$ 

... but none of them look like they are nouveau related.
I will have a closer look next week and decide what to nuke.

With respect to the missing firmware, it seems to be some (unattended) Debian bug or regression.

In any case, none of those files is related to my Nvidia Quadro FX580 (G96) cards which used the legacy 340.108 driver, so everything works.
The missing firmware is probably for newer hardware.

Still, although a Warning and not an Error, it should not be happening.
Fixed upstream? Not clear.

BTW: my wireless Logitech Ergo M575 works as before the upgrade.

Thanks for your input.

Best,

A.

Its kind of annoying, because I don't know how to downgrade the packages needed to fix my problem.

https://upload.disroot.org/r/54sJQDA0#J … IkqA1GsIs=

This is the packages I updated.  Once I do this, I poweroff computer and reboot and wireless mouse no longer works.

2 programs I have used are, ldconfig and symlinks.

The warning may be just noise, but cleaning up old links may remove them.

check out ...

symlinks --help (is a stand-alone package)
ldconfig --help (is installed with libc-bin package)

I use these quite often, but have a look first to be sure, to be sure.

symlinks -csrv /

ldconfig -Cfpv

I hope this helps get rid of the noise so you can see other messages clearer.

Indeed ...

But if I do:

~$ sudo update-initramfs -u

I get the same warnings I made reference to in my OP:

--- snip ---
update-initramfs: Generating /boot/initrd.img-6.1.0-22-amd64
W: Possible missing firmware /lib/firmware/nvidia/gp100/acr/ucode_load.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp100/acr/bl.bin for module nouveau
--- snip ---

The printout makes reference to a total of 297 *.bin files (Nvidia firmware files) which the system says are posibly missing.
And they are: there is no /lib/firmware/nvidia directory in my system.

~$ ls /lib/firmware/nvidia
ls: cannot access '/lib/firmware/nvidia': No such file or directory
~$ 

And then...
Why should there be?
I use the nouveau driver.

This is most probably (?) something left over from when the system was running Beowulf and did use Nvidia drivers/firmware.
Something which did not get cleaned up as I upgraded first to Chimaera and then to Daedalus.   

-----------------
Edit:
Maybe not ...

The printout does say ... for module nouveau.
Which would mean that it is the nouveau driver that is asking for them.
-----------------

Maybe there is a package missing / not installed?

How to fix this?
*What* is looking for Nvidia firmware?

Thanks in advance,

Best,

A.

At least once a week.
But everything seems to be working properly now.

The slim and ALSA lines in /var/log/boot are gone with the fixes previously posted.

The last one I just found is this one:

--- snip ---
09:54:58 2024: /sbin/dhclient-script: 88: cannot create /etc/resolv.conf: Directory nonexistent
--- snip ---

But ...

~$ cat /etc/resolv.conf
# Generated by Connection Manager
search Home 
nameserver 192.168.1.11
~$ 

... is correct.
192.168.1.11 is the address of a Chimaera VM hosted in my box and running a Pi-hole+unbound recursive DNS.

Using MC to check the file I see it is @resolv.conf with this content:

# Generated by Connection Manager
search Home
nameserver 192.168.1.11

So I guess that everything is as it should be.
ie: no apparent issues.

Thanks for your input.

Best,

A.

CCommit Log for Sun Jun 30 07:40:01 2024

Upgraded the following packages:
bash (5.2.15-2+b2) to 5.2.15-2+b7
curl (7.88.1-10+deb12u5) to 7.88.1-10+deb12u6
gir1.2-gdkpixbuf-2.0 (2.42.10+dfsg-1+b1) to 2.42.10+dfsg-1+deb12u1
intel-microcode (3.20231114.1~deb12u1) to 3.20240514.1~deb12u1
libbluetooth3 (5.66-1+deb12u1) to 5.66-1+deb12u2
libcjson1 (1.7.15-1) to 1.7.15-1+deb12u1
libcpupower1 (6.1.90-1) to 6.1.94-1
libcurl3-gnutls (7.88.1-10+deb12u5) to 7.88.1-10+deb12u6
libcurl4 (7.88.1-10+deb12u5) to 7.88.1-10+deb12u6
libfreetype6 (2.12.1+dfsg-5) to 2.12.1+dfsg-5+deb12u3
libgdk-pixbuf-2.0-0 (2.42.10+dfsg-1+b1) to 2.42.10+dfsg-1+deb12u1
libgdk-pixbuf2.0-bin (2.42.10+dfsg-1+b1) to 2.42.10+dfsg-1+deb12u1
libgdk-pixbuf2.0-common (2.42.10+dfsg-1) to 2.42.10+dfsg-1+deb12u1
libglib2.0-0 (2.74.6-2+deb12u2) to 2.74.6-2+deb12u3
libglib2.0-bin (2.74.6-2+deb12u2) to 2.74.6-2+deb12u3
libglib2.0-data (2.74.6-2+deb12u2) to 2.74.6-2+deb12u3
libgnutls30 (3.7.9-2+deb12u2) to 3.7.9-2+deb12u3
libltdl7 (2.4.7-5) to 2.4.7-7~deb12u1
libpython3.11 (3.11.2-6) to 3.11.2-6+deb12u2
libpython3.11-minimal (3.11.2-6) to 3.11.2-6+deb12u2
libpython3.11-stdlib (3.11.2-6) to 3.11.2-6+deb12u2
libqt5concurrent5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5core5a (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5dbus5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5gui5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5network5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5printsupport5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5sql5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5sql5-sqlite (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5widgets5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libqt5xml5 (5.15.8+dfsg-11) to 5.15.8+dfsg-11+deb12u2
libseccomp2 (2.5.4-1+b3) to 2.5.4-1+deb12u1
libssl3 (3.0.11-1~deb12u2) to 3.0.13-1~deb12u1
libtool (2.4.7-5) to 2.4.7-7~deb12u1
linux-compiler-gcc-12-x86 (6.1.90-1) to 6.1.94-1
linux-headers-amd64 (6.1.90-1) to 6.1.94-1
linux-image-amd64 (6.1.90-1) to 6.1.94-1
linux-kbuild-6.1 (6.1.90-1) to 6.1.94-1
linux-libc-dev (6.1.90-1) to 6.1.94-1
nano (7.2-1) to 7.2-1+deb12u1
openssl (3.0.11-1~deb12u2) to 3.0.13-1~deb12u1
python3-idna (3.3-1) to 3.3-1+deb12u1
python3.11 (3.11.2-6) to 3.11.2-6+deb12u2
python3.11-minimal (3.11.2-6) to 3.11.2-6+deb12u2
wpasupplicant (2:2.10-12) to 2:2.10-12+deb12u1

Installed the following packages:
linux-headers-6.1.0-22-amd64 (6.1.94-1)
linux-headers-6.1.0-22-common (6.1.94-1)
linux-image-6.1.0-22-amd64 (6.1.94-1)

Twor things stand out in /var/log/boot.

This:

08:47:20 2024: Starting slim: slimUnknown option name: input_fgcolor

The solution for Unknown option name: input_fgcolor is here*.
* still have to try it out and check.

and this:

--- snip ---
08:47:19 2024: Setting up ALSA...warning: 'alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore' failed with error message 'alsa-lib parser.c:2783:(load_toplevel_config) Unable to find the top-level configuration file '/usr/share/alsa/ucm2/ucm.conf'.
08:47:19 2024: alsa-lib main.c:1541:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2'...done.
--- snip ---
08:47:19 2024: Setting up ALSA...warning: 'alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore' failed with error message 'alsa-lib parser.c:2783:(load_toplevel_config) Unable to find the top-level configuration file '/usr/share/alsa/ucm2/ucm.conf'.
08:47:19 2024: alsa-lib main.c:1541:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2'...done.
--- snip ---

The printout seems to be accurate:

~$ ls /usr/share/alsa
alsa.conf  alsa.conf.d  cards  ctl  init  pcm  utils.sh
~$ 

ie: no ucm2 directory.

But I found a package for that, for whatever reason it was not installed when I upgraded from Beowulf via Chimaera to Daedalus:

~$ apt list | grep -i alsa-ucm
alsa-ucm-conf/stable,stable 1.2.8-1 all
~$

I will install the package and report later / tomorrow.
Hopefully that will be it.

Best,

A.

Asked apt to update early today:

~$ sudo apt update
Hit:1 http://deb.devuan.org/merged daedalus InRelease
Hit:2 http://deb.devuan.org/merged daedalus-updates InRelease
Hit:3 http://deb.devuan.org/merged daedalus-security InRelease
Reading package lists... Done                     
Building dependency tree... Done
Reading state information... Done
89 packages can be upgraded. Run 'apt list --upgradable' to see them.
~$ 

89 packages seemed rather a large number so I checked my /etc/apt/sources.list and asked again, with the same result.

--- snip ---
89 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 236 MB of archives.
After this operation, 470 MB of additional disk space will be used.
Do you want to continue? [Y/n] 

The three new packages are linux-headers-6.1.0-22-amd64, linux-headers-6.1.0-22-common and linux-image-6.1.0-22-amd64.

Watching the printout as it rolled on, I noticed multiple lines which started with a W:

--- snip ---
update-initramfs: Generating /boot/initrd.img-6.1.0-22-amd64
W: Possible missing firmware /lib/firmware/nvidia/gp100/acr/ucode_load.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/gp100/acr/bl.bin for module nouveau
--- snip ---
W: Possible missing firmware /lib/firmware/nvidia/tu102/sec2/image.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/tu102/sec2/desc.bin for module nouveau
--- snip ---

It was a very long list of Possible missing firmware entries which I have shortened for clarity.
Everything else went on as expected and sudo apt install -f had nothing to say.

Anyone else see this?
Have not rebooted yet so I cannot say if there are any ill effects.
I will check the logs report later.

Thanks in advance.

Best,

A.