Hello:

I'll add my bit.

~$ apt-cache policy hddtemp
hddtemp:
  Installed: 0.3-beta15-54
  Candidate: 0.3-beta15-54
  Version table:
 *** 0.3-beta15-54 100
        100 /var/lib/dpkg/status
~$ 

Just to round it out:

~$ uname -a                
Linux devuan 6.1.0-22-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.94-1 (2024-06-21) x86_64 GNU/Linux
~$ 

~$ apt list | grep installed | grep hddtemp 
--- snip ---
hddtemp/now 0.3-beta15-54 amd64 [installed,local]
~$ 

Yep ...

~$ hddtemp /dev/sdc
/dev/sdc: HITACHI HUS153030VLS300: 36 C
~$ 

Edit:

hddtemp is what provides conky the data for its screen printout in my desktop.
eg:

SATA0: +${execi 60  hddtemp /dev/disk/by-uuid/xxxxxxx-exxb-xcxx-xcxx-xaxcxbafexdx | cut -c 81-86}

Best,

A.

Hello:

Yes, so do I.
I have a number of blacklisted modules, among them the infamous mei and mei_me (a separate one for each just in case) with these stanzas ...
install mei /bin/false
and
install mei_me /bin/false

... to prevent loading if another non-blacklisted module requests it.
ie: blacklists the module and any other that depends on it.

The result is this:

~$ sudo dmesg | grep -i error
--- snip ---
[   24.221918] udevd[427]: Error running install command '/bin/false' for module mei: retcode 1
--- snip ---
~$

I have also blacklisted appletalk, ax25, firewire_ohci, gpio_ich, i8042, lpc_ich, psmouse, tpm, watchdog and intel-microcode.

I'll have to look at your list in detail, thanks for the heads-up.

As usual, I've wandered off track.
Back to the OP modules.

Seeing that blacklisting was not working I went looking for the reason while wondering if they were not baked into the kernel.
And then I found this tidbit:

~$ cat /etc/modules-load.d/cups-filters.conf
# Parallel printer driver modules loading for cups
# LOAD_LP_MODULE was 'yes' in /etc/default/cups
lp
ppdev
parport_pc
~$ 

I remmed all entries and rebooted and as a result, CUPS would show the job as "Processing page 1..." and stay there, with the printer not printing anything, so I undid the editing in the cups-filters.conf, issued a reprint of the same job and things were back to normal again.

My printer is local so no network printing here, at least for now.
But I'll have to poke around and try to find out which of the modules loaded can be eliminated, if any at all.

Will post back when I find out.

Thanks for your input.

Best,

A.

Hello:

@GlennW

It sometimes is.
ie: you can see what is being done because you are doing it.
But I agree, symlinks seems to be reliable enough.

@aluma

Yes, the Beowulf -> Chimaera -> Daedalus was not exactly seamless but everything has been falling in place.
So no complaints, just a few loose ends that turn up as I go along.

~$ sudo symlinks -csrv / | grep dangling
~$ 

No more dangling links.
Thanks to both for your input.

Best,

A.

Hello:

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.

Hello:

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.

Hello:

Quite so.

Like I explained in my OP, that would be the *.ppd file (Samsung_M2020_Series.ppd) extracted from the Linux driver uld_V1.00.39_01.17.tar.gz file which I obtained directly from HP.

As the use of *.ppd files will be deprecated by CUPS in a future release, I need to plan in advance.
I will keep looking to find out what will happen with my M2020W printer when that happens.

Indeed.
It happens that I have an innate distrust for any script coming from HP.
And a *.ppd is a plain text file I can open and look at.
 
Exotic?
Yes, I have to agree.
I think it would be rather difficult to find something more exotic than that. 8^)

Thank you for your input.

Best,

A.

Hello:

Yes.

I still shed a tear when I remember all those LaserJet 4/5 sent to the landfill in early 2000 where I worked.
It was a very different Hewlett Packard back then.

Indeed ...

After having to wrangle (at that time) with this printer's installation in Linux, I resorted to CUPS, which worked from the get-go.

As it did a good job, I want to continue with CUPS instead of using the Samsung/HP ware and its install routine.
Besides, doing so is more akin to the Unix/Linux philosophy.

Thanks for your input.

Best,

A.

Hello:

You're welcome.

Indeed ...
But at least there is a solution to whatever is evidently wrong with that HW.

That said, I cannot imagine why it would be disabled in this manner, but then again ...
Cheaper this way for the OEM?

Please do let the forum know how you fared with this endeavour.
It will surely be useful to others in the same spot.

Best,

A.

Hello:

Interesting ...

Maybe installing/reinstalling what I know I need ie: xserver-xorg-video-nouveau, xserver-xorg-video-vmware and maybe some other one/s (have to figure out which) will keep them in the system (as manually installed) when I get rid of the ones I don't need.

I'll see what gives in a few days' time.

Thank you for your input.

Best,

A.

Hello:

Hmm ...
Me thinks not.

This is what I get in my up-to-date box ...

~$ uname -a
Linux devuan 6.1.0-21-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1 (2024-05-03) x86_64 GNU/Linux
~$ 

... with nvidia-detect:

~$ nvidia-detect
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96CGL [Quadro FX 580] [10de:0659] (rev a1)
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96CGL [Quadro FX 580] [10de:0659] (rev a1)

Checking card:  NVIDIA Corporation G96CGL [Quadro FX 580] (rev a1)
Your card is only supported by the 340 legacy drivers series, which is only available up to buster.

Checking card:  NVIDIA Corporation G96CGL [Quadro FX 580] (rev a1)
Your card is only supported by the 340 legacy drivers series, which is only available up to buster.

Unless I have missed something, the G96CGL/[Quadro FX 580 card (PCI ID:0659) needs the 390.xx driver but it is not available in the Bookworm/Deadalus repository.

~$ sudo lspci -nn | grep -e VGA
[sudo] password for groucho: 
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96CGL [Quadro FX 580] [10de:0659] (rev a1)   # <-
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96CGL [Quadro FX 580] [10de:0659] (rev a1)   # <-
~$

Thanks for your input.

Best,

A.