Solus Linux Installation Issue

Solus Linux Installation Issue

Whenever I first install Solus Linux, the installer never adds Solus to the UEFI Boot Menu. Here are the steps to fix that issue:

Boot from your live CD/USB. Connect to the internet, and do the following:

Install efibootmgr: sudo eopkg it efibootmgr

(This paragraph probably isn’t necessary, but I am including it to remember how to clean up the UEFI Boot Menu 🙂 )Run efibootmgr with no arguments. You should see an entry for Linux Boot Manager, which for some reason doesn’t show up in your actual boot menu but does here. There’s a number listed for that entry. Delete it with sudo efibootmgr -b [num] -B

Now you can recreate it. If your EFI partition is /dev/sda1 then do this: sudo efibootmgr -c -d /dev/sda -p 1 -l "\EFI\systemd\systemd-bootx64.efi" -L "Linux Boot Manager"

KDE Font Fix on NVIDIA Driver

KDE Font Fix on NVIDIA Driver

For KDE font/gui size issues after switching to NVIDIA driver, I found the following post:

It’s a nvidia thing lol I had the same issue and never even noticed it until one day I gave the free noveau drivers a try and everything looked way better and smaller. For some reason nvidia sets/forces my DPI to I believe 120, anyways it’s really easy to solve.

Open the nvidia.conf file in your text editor
sudoedit /etc/X11/mhwd.d/nvidia.conf

Then edit or add the option DPI under the screen display sub section and disable UseEdidDpi.

To make things easier here is what I have under my “Screen” section which now forces the use of 96 for dpi scaling.

Section “Screen”
    Identifier “Screen0”
    Device “Device0”
    Monitor “Monitor0”
    DefaultDepth 24
    SubSection “Display”
        Depth 24
        Option “UseEdidDpi” “False”
        Option “DPI” “96×96”
    EndSubSection
EndSection

I hope this helps you as it did for me.

Fix For Kernel Panic on Shutdown

Fix For Kernel Panic on Shutdown

My desktop computer, an Alienware Aurora R7, likes to fail to shutdown in Linux with a kernel panic. Here’s the solution to fix it.

If using Grub:
Add initcall_blacklist=dw_i2c_init_driver to the kernel command line.

Run in the terminal: sudo nano -w /etc/default/grub
Append blacklist string to the GRUB_CMDLINE_LINUX_DEFAULT=”… initcall_blacklist=dw_i2c_init_driver”
Save the file.
For Debian:  sudo update-grub
For Fedora:  grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
For Arch: grub-mkconfig -o /boot/grub/grub.cfg

Reboot and test!

If using goofiboot (Solus):
sudo nano -w /etc/kernel/cmdline
Insert the following line: initcall_blacklist=dw_i2c_init_driver
Save the file.
sudo clr-boot-manager update

Reboot and test!

If using systemd-boot (Pop_OS):
sudo nano -w /etc/kernelstub/configuration
Insert the following line: “initcall_blacklist=dw_i2c_init_driver”, (Don’t miss the trailing coma!)
Save the file.
sudo kernelstub

Reboot and test!