Huh? It's the parent directory

Nope. The location is right. This variable is not an absolute path (note that it hasn't a forward slash at the beginning), but a relative path (relative to /usr/src/snd_hda_codec_cs8409-1.0/ where the tarball has been uncompressed). And it's the path to the Makefile, which is located in the parent directory.

In some cases, for example, you can find the Makefile in

/usr/src/<name>-<version>/src/Makefile

Hence, the variable would be BUILT_MODULE_LOCATION=./src

If I'm not mistaken

Yes, if you are referring to the icon.

Disclaimer: don't use hyphens ( - ) in the name, use underscores ( _ ) instead.

It's not so trivial. I recommend you to install the driver using the Dynamic Kernel Module Support (DKMS).

You need to install dkms together with the linux-headers (replace the version of the headers to match your kernel version):

# apt-get install dkms linux-headers-5.16.0-1-amd64

Download the tarball:

$ wget https://github.com/egorenar/snd-hda-codec-cs8409/archive/refs/heads/master.zip

and extract the content (you'll need to install unzip first):

$ unzip master.zip

Enter the directory:

$ cd snd-hda-codec-cs8409-master

Create the dkms.conf file inside of the extracted source code directory. For example:

PACKAGE_NAME=snd_hda_codec_cs8409
BUILT_MODULE_NAME=snd_hda_codec_cs8409
PACKAGE_VERSION=1.0
BUILT_MODULE_LOCATION=./
DEST_MODULE_LOCATION=/kernel/driver/updates
AUTOINSTALL=yes

This example identifies a kernel module named snd_hda_codec_cs8409 with version 1.0.

As root, copy the kernel module source code into the /usr/src/ directory:

# mkdir /usr/src/snd_hda_codec_cs8409-1.0
# cp -Rv . /usr/src/snd_hda_codec_cs8409-1.0

In the above commands, the name of the folder must be:  <PACKAGE_NAME> - <PACKAGE_VERSION>

Add the kernel module to the dkms tree so that it is tracked by if:

# dkms add -m snd_hda_codec_cs8409

Build the kernel module using dkms:

# dkms build -m snd_hda_codec_cs8409 -v 1.0

Install the kernel module using dkms:

# dkms install -m snd_hda_codec_cs8409 -v 1.0

The modprobe command can be used to load it:

# modprobe snd_hda_codec_cs8409

Validate the kernel module is loaded:

$ lsmod | grep snd_hda_codec_cs8409

Good luck!

Don't forget Janis Joplin

Thanks

The part concerning to dm-verity in /usr/share/initramfs-tools/hooks/live should be as follows:

# dm-verity support
if [ "${DISABLE_DM_VERITY:-}" != "true" ] && [ "${DISABLE_DM_VERITY:-}" != "yes" ]
then
	[ "${QUIET}" ] || echo -n " dm-verity"
	manual_add_modules dm-verity
	# The BusyBox mount does not support dm-verity so we use the util-linux version.
	copy_exec /bin/mount
fi

The problem arises trying to copy the mount binary, which is located at /bin instead of /usr/bin. So, the line:

copy_exec /usr/bin/mount /bin

must be replaced with:

copy_exec /bin/mount

in live-boot-initramfs-tools

Quoting Ralph Ronnquist, there is an initial collection of trial installer ISOs that need to be tested in a range of settings at:

https://ido.rrq.id.au/download/

Thanks for your work, Ralph

Yes. Although I used setnet in devuan jessie, I didn't mention it because I can't remember whether it depended on ifupdown. On the other hand, I can't find the packages in chimaera.

Thanks

Yes, I've fixed some issues related to Hopman.

On the other hand, I'm also looking at the following plugin for SpaceFM, the file manager included in the openbox version:

https://github.com/jpfleury/corbeille-spacefm

because it doesn't send files to the trash bin when you hit delete in the right click popup menu.

If you decide to install another file manager, you must indicate it in the files below:

• ~/.xmenurx

• ~/.hopmanrc

If they don't exist, you can create them and copy the content of the respective files located in /etc/default, modifying them for matching your installed programs.