Black screen when installing Nvidia version

I tried to install the nvidia version onto my desktop and after selecting 'install bazzite' on the text menu, the typical series of lines come up but it then goes blank and I cannot progress any further with the install
27 Replies
HikariKnight
HikariKnight4w ago
try select troubleshoot --> safe graphics from the menu only other workaround i can think of with nvidia
TPepperoni
TPepperoniOP4w ago
Will give it a try later, thanks
TPepperoni
TPepperoniOP4w ago
No description
TPepperoni
TPepperoniOP4w ago
Now getting this error. RAM related? Not sure why it's busy
wolfyreload
wolfyreload4w ago
I'm more concerned with the getfilesystemencoding error in the stack trace. Is this a dual-boot setup with Windows? If so boot into Windows and select restart from Windows rather than shutting down, if you shut it down it semi hibernates the machine rather than shutting down fully. I think this locks the drive fully and the installer cannot read the start of the disk. That's just a hunch though
wolfyreload
wolfyreload4w ago
Looks like my assuption was completely wrong. Found this thread. It looks like if you don't have UTF8 compatible disk partition labels, you might get that error that you are seeing https://discussion.fedoraproject.org/t/all-fedora-versions-fail-to-install/92568/2
Fedora Discussion
All Fedora versions fail to install
You have a device property containing invalid UTF-8, which python infamously doesn’t tolerate well. From the comments on that issue, this may ultimately be caused by a kernel bug. Can you try running this python code, tweaked slightly from the snippet in the issue? #!/usr/bin/python3 import pyudev context = pyudev.Context() try: for dev...
CheckYourFax
CheckYourFax4w ago
Unless you have a device with slow startup time (HDD instead of SSD) might be better to just open cmd (administrator) and type powercfg.exe /h off to prevent this from happening in the future
wolfyreload
wolfyreload4w ago
Managed to reproduce the error you are getting. Notice the accent on the e in the partition name for /dev/sda4 (I called the partition "Héllo") and I can reproduce your error. So the solution is to boot into something like Linux Mint and change any partition labels that have unusual characters in the partition names.
No description
No description
wolfyreload
wolfyreload4w ago
I was completely wrong about Windows Hibernate, but that's a good solution to getting rid of annoying hibernate issues
CheckYourFax
CheckYourFax4w ago
I was about to say that if its a windows hibernation thing it will just give "NTFS partition is in an unsafe state" when you load into grub I think a right click rename in windows changes the label too, so i think that's what the problem is here. Windows doesn't use UTF-8 by default for character encoding, and then UTF-8 gets an error because it expect a UTF format still uses ANSI to this day for anything system related
wolfyreload
wolfyreload4w ago
I couldn't reproduce it by changing the drive label in Windows. Not sure if you can change the partition name from within Windows
CheckYourFax
CheckYourFax4w ago
Drive label automatically changes if you use Windows Explorer->This Computer->Right click disk->Rename but not if he has any hidden drives (partitions)
TPepperoni
TPepperoniOP4w ago
Sorry yes I was playing a game. That's exactly what @Linus Xu ran me through and am greatful. Not sure if there is anything you guys can do to streamline it though. I feel like its more a 'user error' scenario We messed about with gdisk on a live environment and got it going
CheckYourFax
CheckYourFax4w ago
There could be something done to make label read errors non-destructive, not sure, but seems like the whole OS not booting because a label error is a bit much
TPepperoni
TPepperoniOP4w ago
Yeah im guessing it scans all the drives and if 1 isn't compatible, it refuses to load the installer, even if you aren't installing to said drive Bit annoying but good to know I guess. It also flagged errors on normal fedora 40 too
wolfyreload
wolfyreload4w ago
I wouldn't call it a user error, might be worth logging it in https://bugzilla.redhat.com something that should get fixed upstream. Definately something the installer should handle
TPepperoni
TPepperoniOP4w ago
It atleast got to the gui installer but it said an unknown error occured and it would only allow me to debug it or quit, wouldnt progress This was for Fedora 40 Kenoite
wolfyreload
wolfyreload4w ago
Code 1 error message?
TPepperoni
TPepperoniOP4w ago
There wasn't a specific error. I gave me a wall of text and the prompt was along the lines of 'unkown error, here is the logs, see what it is' kind of thing but I honestly didn't know what I was looking at
wolfyreload
wolfyreload4w ago
So not this?
No description
TPepperoni
TPepperoniOP4w ago
Nope not that. There was a drop down box and when I clicked it, a text box appeared with a full log of everything that happened. This was between the gui loading up but occured before I could select a language
wolfyreload
wolfyreload4w ago
Could you record a video with your phone? Will be easier to see the error
TPepperoni
TPepperoniOP4w ago
Ah sorry I can't. The problem is already fixed. You know how you were able to recreate my error? Try doing the same thing but load Fedora 40 Kenoite and installing it? That's how it occured for me Installing bazzite would give me the black screen you got, fedora 40 Kenoite would give me the error in the gui
wolfyreload
wolfyreload4w ago
ohhhh sorry thought you were still having issues. Glad you came right. This error message right?
No description
TPepperoni
TPepperoniOP4w ago
Yep that's the one I had on bazzite correct. Are you able to access locked channels? https://discordapp.com/channels/1072614816579063828/1300653374915608637 if it works, have a look at that if that might be any help? I was just along for the ride hahaha
wolfyreload
wolfyreload4w ago
I've been working on trying to find and reproduce all the weird and wonderful installer issuers. So far this has been one of the weirder ones Very helpful thank you
Linus Xu
Linus Xu4w ago
gdisk should work on windows Took the detour there since I wanted to reproduce the python calls that led to the error and I wasn’t sure where the characters ultimately are
Want results from more Discord servers?
Add your server