Since I had been using Solus a few years ago on my desktop system and have been using it on a spare laptop for many years, I went with that (Solus Budgie, to be precise).
Things that didn't work right away:
Regarding the Solus 4.8 installation:
When booting from USB, the live session started fine, but as soon as I started the installer, issues arose: On some attempts, the screen started flickering heavily when the installer-window appeared, on other attempts the installer-window seemed to not even load properly, as it stayed frozen in a half-transparent state. When the latter happened, I could still move the mouse, but could not click on anything and the keyboard didn't respond either. Ctrl-Alt-F4 didn't do anything, so I could only keep the power-button of the PC pressed for a few seconds to shut it down.
I managed to fix my issue like this:
Regarding Nvidia drivers: I learned that there are now 3 driver-packages to choose from:
The third one in that list was new to me, but as it turns out, this is now the driver package Nvidia recommends for RTX 20xx (or newer) cards (and for RTX 50xx and newer, it's actually the ONLY driver package that will work). (details here)
In the end, on Solus, these are the Nvidia-packages I am now running:
sudo eopkg list-installed | grep nvidia linux-firmware-nvidia - Firmware required for many devices, Nvidia GSP firmware nvidia-glx-driver-32bit - 32-bit libraries for NVIDIA Binary Driver nvidia-glx-driver-common - Shared assets for the NVIDIA GLX Driver nvidia-glx-driver-modaliases - These files are used by the Software Center for hardware detection nvidia-open-current - NVIDIA open GPU kernel modules (Current Kernel) nvidia-open-modaliases - These files are used by software centers for hardware detection
Regarding the Elgato Wave 3 mic:
My system was behaving VERY strangely after installing Solus. The USB-keyboard would sometimes not work after booting/rebooting (the solution was to wait 1-5 minutes, it would eventually work), sometimes no sound-devices AT ALL very recognized, and the Wave 3 mic itself was NEVER recognized. Oh, and running "dmesg" would show a bunch of errors with a USB-device (the mic). "lsusb" would sometimes show the mic, sometimes not.
Temporary workaround: disconnect the mic
After doing some research, it seems this mic is not behaving too well under Linux. It seems a bunch of people were able to fix their issues by simply using a different USB-port on their motherboard or using a powered USB-hub (the logic being that the mic might turn into a very power-hungry device on Linux). Others fiddled with pavucontrol, PulseAudio and pipewire for a few hours, but even then it doesn't work reliably 100% of the time for everyone.
For now, I've connected the mic to the integrated USB-hub of my monitor (AOC 34") and that seems to work. If, in the coming weeks/months, it doesn't work reliably, I'll probably sell the mic and buy another one (Rode NT Mini, Sennheiser Profile or Shure MV6 seem to be good candidates).
Additional tweaks and additions:
Fan-control for the Nvidia GPU
I wanted something simple, nfancurve does the trick. Some additional tweaks for setting it up and a SystemD-service are mentioned here. Also some useful tips regarding autostarting applications are mentioned here.
libusb-compat
I've had issues in the past with setting up my network printer and installing libusb-compat fixed the issues. So, just to be safe, I installed libusb-compat and libusb-compat-32bit (with "eopkg install"). Yes, as incredible as that sounds, adding libusb-compat fixed an issue with a NETWORK printer.
Speaking of USB, something that could come in handy:
The package "usbutils" includes "usbreset" to reset USB devices.
No comments:
Post a Comment