Perfect for the job already always in full kowtow mode kissing the a$$ of the murdering scum in Beijing. Totally willing to do or say anything to support his fascist buddies around the world. It is a great match for them.

This is what you see when using Pipewire.

zeus@9600k:~$ pactl info
Server String: /run/user/1000/pulse/native
Library Protocol Version: 35
Server Protocol Version: 35
Is Local: yes
Client Index: 222
Tile Size: 65472
User Name: zeus
Host Name: 9600k
Server Name: PulseAudio (on PipeWire 1.2.7)
Server Version: 15.0.0
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.usb-0d8c_USB_Sound_Device-00.analog-surround-51
Default Source: alsa_input.usb-0d8c_USB_Sound_Device-00.analog-stereo
Cookie: f57b:3733

If still on the PulseAudio that is all that will appear on the Server Name: line.

And I would think you will be until you have all drives in the array available to re-assemble and mount it. Try it doing that I think you will get much farther along on your recovery efforts.

It would be these the type is separate from them, anything after the defaults are options passed to the file system on mount. Oh and BTW defaults already gives you rw option the extras were screwing it up.

,nosuid,nodev,relatime,data=ordered

The arch wiki shows those used with a vfat file system, there is one ,user used in an example for ext4 all the rest have nothing but defaults..

https://wiki.archlinux.org/title/Fstab

Mostly none of them places provide the support for linux drivers, there are exceptions where they will have someone doing it. But for the most part it is some person not associated with the company or product doing the driver support. Sound can be a problem especially the onboard I have found it to be mostly junk. I used a firewire card for a time connected to a FireWave sound device it worked flawlessly. Now I use the below to get my 5.1 sound it works great but I see the scumbags have more than doubled the price in the just over year since I bought it. If searching around for others you want a CM106 based device as that is what it reports as to the system.

https://www.amazon.ca/dp/B09N9LLHSC?ref … asin_title

You are supposed to create it in your ~ directory though like most of these things. I would imagine the option exists to start the program specifying another location for the config file passed as option at startup. The reference file for it lives at the /usr/share/doc/xbindkeys/examples/xbindkeysrc copy that to your ~/.xbindkeysrc then edit for your changes.

alias afl='apt-file list'
root@9600k:~# afl xbindkeys
xbindkeys: /etc/xdg/autostart/xbindkeys.desktop
xbindkeys: /usr/bin/xbindkeys
xbindkeys: /usr/bin/xbindkeys_autostart
xbindkeys: /usr/bin/xbindkeys_show
xbindkeys: /usr/share/doc/xbindkeys/BUGS
xbindkeys: /usr/share/doc/xbindkeys/NEWS.Debian.gz
xbindkeys: /usr/share/doc/xbindkeys/NEWS.gz
xbindkeys: /usr/share/doc/xbindkeys/README.Debian
xbindkeys: /usr/share/doc/xbindkeys/README.gz
xbindkeys: /usr/share/doc/xbindkeys/TODO
xbindkeys: /usr/share/doc/xbindkeys/changelog.Debian.gz
xbindkeys: /usr/share/doc/xbindkeys/changelog.gz
xbindkeys: /usr/share/doc/xbindkeys/copyright
xbindkeys: /usr/share/doc/xbindkeys/examples/xbindkeysrc
xbindkeys: /usr/share/doc/xbindkeys/examples/xbindkeysrc-combo.scm
xbindkeys: /usr/share/doc/xbindkeys/examples/xbindkeysrc.scm
xbindkeys: /usr/share/doc/xbindkeys/examples/xbindkeysrc1
xbindkeys: /usr/share/doc/xbindkeys/examples/xbindkeysrc2
xbindkeys: /usr/share/man/man1/xbindkeys.1.gz
xbindkeys: /usr/share/man/man1/xbindkeys_autostart.1.gz
xbindkeys: /usr/share/man/man1/xbindkeys_show.1.gz
xbindkeys: /usr/share/menu/xbindkeys

Edit: The script I use in the KDE autostart system setting to start it up on login.

zeus@9600k:~$ cat bin/xbindkeys.sh 
#!/bin/bash
# enable it on login if xbindkeys is installed.
if [ -f "/usr/bin/xbindkeys" ]; then
        xbindkeys
fi

Damn missed that way to early in the morning to be replying.

Perfect time to scratch your own itch as the saying goes in Linux. Create a file with these contents.

#!/bin/bash

# A script to halve the brightness of the display
xrandr --output LVDS --brightness 0.5

Make it executable.

chmod +x /path/to/brightness.sh

Put it in your home bin directory if you use one or /usr/local/bin so it will be in the PATH then
brightness.sh used in a shell will execute the command. If using xbindkeys and xdotool you should be able to map it to a key shortcut to just have it done with that shortcut. Or perhaps a .desktop file can be made to run the command via a click on its icon. Just a couple of ways of doing it and as I say scratching your own itch. I have dozens of little scripts I run all the time from my cloning/backup one that will clone or backup my running system to media conversion, file copying to other machines, the list is endless.

The output of the lsmod would be different with your machine as it actually has the hardware needed/used by the module. The output for the rc?.d leftovers is because the --purge option was not used when removing the package so left behind the configuration files. The package left in the archives folder is normal until the apt clean or apt autoclean commands are run to clear the cache one clears the entire cache the second leaves packages that are still available in the archives in the cache. You want to do the sudo apt autoremove to get rid of the packages not needed anymore to clean the excess junk off the system. I really have no idea if you want to try it again from the start and see if the package will actually install without error with the module loaded before starting the install. If you do at least you now know how to remove the thing if it fails once more.

Couple of points you are not patching the kernel, you are passing it a boot option through grub. If you patch a kernel, a re-compile then installation of new version is necessary where you boot with the patched to see the changes. For the grub there is no need to make a new file the update-grub command run as root or normal user using sudo at the front of it will have the option used in the grub.cfg upon the next boot. And now I look at that part again you do not mention you need to reboot for that change to take place setting the option and having the  grub file updated does nothing to have it used, only booting the kernel with the updated/new file has it take effect. Other than those items a reasonable effort at it.

The one you used to install but either should work. You say the graphical tool says it is marked for removal you could let it do it as well. Now there is one for me to ask about where is the link to the . deb you use? I see nothing like that on the page I just linked too.

Forget the stupid graphics tools they are useless junk for solving problems they only work when there are no problems. Open a terminal and sudo dpkg --configure -a to see if it is going to allow you to configure the broken package.

Edit did some reading on the package I downloaded here.

https://sourceforge.net/projects/fnfx/

The last update of 2015 is not a good sign but it appears it could be possible to get the required support file.

root@9600k:~# file /home/zeus/Downloads/usr/bin/fnfx
/home/zeus/Downloads/usr/bin/fnfx: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.0.0, stripped
root@9600k:~# file /home/zeus/Downloads/usr/sbin/fnfxd
/home/zeus/Downloads/usr/sbin/fnfxd: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.0.0, stripped

The /lib/ld-linux.so.2 by installing the having the i386 libc6 installed. I am rapidly running out of ideas on this one.

https://packages.debian.org/search?sear … e&arch=any

Debian and their BS breaking things changes strikes again.

root@9600k:~# apt-file search modprobe | grep bin
discover: /usr/sbin/discover-modprobe
kmod: /usr/sbin/modprobe

From my /root/.bashrc so I do not run into that BS.

# set PATH so it includes /sbin if running distro without it in the PATH like Debian Buster.
needpath=$(which fdisk)

if [ -z $needpath ] ; then
    PATH="/sbin:$PATH"
fi

Use the full path sudo /usr/sbin/modprobe toshiba_acpi.

Edit: Now I noticed you may want to run apt autoremove to get rid of that extra kernel and stop ignoring apt when it tells you to do this every time there is a package(s) to remove that is not needed anymore.