Page MenuHomeSolus

Cannot load graphical interface of Live USB on a computer with a NVidia RTX graphics card
Open, NormalPublic

Description

Hello,

I'm currently trying to install Solus Budgie 4.0 on my computer.
I created a USB bootable drive with Rufus and booted on it.
On a screen with 2 choices "Solus 4.0 (Budgie)" or "Reboot Into Firmware Interface", i stay on the line for Solus, hit e to add the option nouveau.modeset=0 and then press return.
It loads stuff for a few seconds then i arrive at a black screen with a blinking cursor in the top left corner and then nothing happens.

So i changed tty, log in with root/root and check lightdm status : failed

journalctl -xeu lightdm

i carry on with a startx

and then :

less /var/log/Xorg.0.log


so i can see that nouveau still is not disabled, even with the provided argument at boot time.

My hardware :
AMD Ryzen7 2700X
EVGA GeForce RTX 2070
MSI B450I Gaming plus ac

I've liked Solus so far in a VM, i would very much like to take the experience a step forward, thanks for the hard work! :)

Event Timeline

Rashguir created this task.Apr 12 2019, 2:05 PM
Rashguir renamed this task from Cannot boot on Live USB on a computer with a NVidia RTX graphics card to Cannot load graphical interface of Live USB on a computer with a NVidia RTX graphics card.Apr 12 2019, 2:34 PM
henres added a subscriber: henres.Apr 12 2019, 3:08 PM

Does a regular nomodeset not work?

You will still need to install the nvidia-glx-driver-current package after installing to disk.

@Rashguir is a friend of mine.

For now we have tested so far to boot with`nouveau.modeset=0` or nomodeset.
The exact same think happen.
Blinking white dash on a black screen.

Have you tried blacklisting the nouveau driver?

rd.driver.blacklist=nouveau

Should default to vesa then, giving you a chance to install the proprietary driver.

Hello,

Sorry for the delay, i was away this week-end.
I tried

nomodeset

, then

rd.driver.blacklist=nouveau

, then, in despair,

nomodeset rd.driver.blacklist=nouveau

but i still got the same result... :/

Thanks for the help :)

Hi,

For the record, i managed to install an other distribution (elementary OS) without taking care of nouveau nor altering anything, with the same hardware of course.

I'll be willing to test again if a solution is presented :)

DataDrake triaged this task as Normal priority.Apr 30 2019, 1:28 PM

The workaround for new NVIDIA cards to install nvidia-glx-driver-current after setting nomodeset stopped working recently.
Some essential packages are unfetchable

Downloading 3 / 4
Package nvidia-glx-driver-common found in repository Solus
Program terminated.
Could not fetch destination file "https://mirrors.rit.edu/solus/packages/shannon/n/nvidia-glx-driver-common-418.43-288-1-x86_64.eopkg": [Errno 14] HTTPS Error 404 - Not Found

IMHO it's essential for this to work OOTB on the ISO and now it seems urgent

Best of luck

CReimer added a subscriber: CReimer.Jan 2 2020, 7:40 PM
presianbg added a subscriber: presianbg.EditedJan 5 2020, 9:49 AM

Hi,

Having exact same issues with Acer Aspire 5 - i5 (10th gen) + nvidia mx250 + uefi (no legacy boot available)
With the very same Live USB stick I'm able to boot Solus LIVE and install the system, but on this laptop it hangs on black screen with blinking cursor.
Tried different combinations of kernel parameters like - nouveau.modset=0, nomodeset and nomodeset .. but with no avail.

@Timalex how to pre-install those packages on the LIVE USB ?

EDIT; I'm not able to enter a tty with ctrl+alt+fn 1-6
Appending 3 to the kernel parameters gives me the option to login as root.
EDIT2: is there a way to install the OS without GUI ?

@presianbg The tools to create an adapted Solus ISO was removed since it was abused for evil.

I'm afraid there is no good solution yet.

A convoluted and definitely not recommended approach I tried was to mount the Solus ISO inside a VM on another linux live distro that will boot as expected (Manjaro set with nonfree driver). There the Solus Live environment will see an ancient compatible graphics card, so no problem. If the targeted storage device is passed through as is to the VM it's possible to install on it.
I had to pre-partition the storage device so that it was visible during installation, with manual mounting points mind you. This last part could very well be due to that I had to install on an SD-card as a temporary solution (you don't want to know). It didn't work out great but booted the first time.. (couldn't even use the TTY:s after that) possibly because of a hardware error with the SD-card.
I settled on moving an existing Solus installation drive from my laptop to the desktop as a desperate measure, which sort of worked out after some troubleshooting since that is what I'm typing this on.

TL;DR We're at the mercy of our benevolent leaders and their finite capacity