Hi,
Yesterday, I tried to install Solus 4.1 Budgie in UEFI mode.
I ran into a couple of issues, which I bypassed eventually but it did not work afterwards.
Hardware
MSI RTX 2080
Ryzen 7 3700X
16GB of Corsair DDR4 3.600Mhz RAM
512GB Intel NVMe (Windows)
256GB Kingston SSD (To be used to install Solus on)
16GB USB (Solus Installation)
Windows installed in UEFI
Secure boot off
CSM off, only UEFI enabled
Nvidia Drivers, nomodeset & LightDM
The first issue I came across was that I everything was buggy, due to not having the right drivers.
Obviously, the first thing I did was using the flag nomodeset
. This was working and it booted into the installation.
However, it did not load into Budgie and I was looking at a blackscreen with a blinking cursor, and nothing happened eventually. I took some action to solve this.
Actions
- Starting TTY
- Updating all package and check for broken packages (https://getsol.us/articles/troubleshooting/general-troubleshooting/en/)
- Installing
nvidia-glx-driver-current
sudo journalctl -b 1
- Found out that LightDM had an error and did not start.
- Restarted LightDM and successfully loaded Budgie DE.
Okay, great. I'm in Budgie. Let's start the installation. I'm erasing my second drive and I would like to encrypt it.
Successfully installed Solus, time for a reboot!
But... I ran into another issue. There were no nvidia drivers installed, so immediately after unlocking my encrypted drive, all I saw were blurry, buggy colors across my screen.
I tried to solve this by taking the following steps:
- Reading through https://getsol.us/articles/troubleshooting/boot-rescue/en/
- Unlocking and mounting my encrypted root partition
- Mounting my boot partition
- Binding
proc
dev
sys
chroot
into SolusSystem-Root
on /target
sudo eopkg up
sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall
sudo eopkg install nvidia-glx-driver-current
sudo usysconf run -f
- This should work, right? Exit chroot and reboot..
Booting into the system.. Unlocking disk.. (fingerscrossed)
Hm, nothing is happening? How long does it take to unlock?
Strange, let me use TTY again and see if it's unlocked.
lsblk
, yes it seems like it has been unlocked.
LightDM Status: Running
and everything else seems to be working fine, nothing special in journalctl
either.
It already took me a couple of hours to get to this point, so I was a bit disappointed and I see a lot of issues about Dual Booting and UEFI..
This was my first experience with Solus, ever. I hope someone has a solution for this, or maybe there's something that needs to get patched.
Thanks!