bazzite installer won't boot up on surface book 2 (Nvidia)
it just gets stuck on this screen
25 Replies
is there 2 GPUs in this?
yes
damn i thought we fixed this ðŸ˜
ok
do you have a second monitor you can plug into it?
yes
this is an issue with nvidia+hybrid graphics on their newest driver
yea
reboot it with the monitor plugged into the nvidia GPU
ok
lmk if that works
doesn't work the monitor doesn't pick up a video signal
did you even get to the "building kargs" section
initramfs
no it just gets stuck at the screen after the boot menu
we used to have surface images
here let me ask some other maintainers about this stuff
you got this ISO from the site right?
yes
alright, so yeah surface images are gone because they were most likely not needed anymore... but you aren't making it to the desktop with our regular
-nvidia builds...ok
if you don't mind i have 2 alternatives but they require you to reflash possibly twice
ok
that's fine
1. select "AMD/Intel" on the site and use our regular
bazzite image to see if it boots. if you make it to the desktop, enter: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-nvidia:stable to rebase to the nvidia images and reboot when that has finished
2. if that doesn't work:
https://github.com/ublue-os/bazzite/releases/tag/v2.2.0
download our old online ISO, but you will have to still rebase to rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-nvidia:stable afterwardsGitHub
Release v2.2.0 - fsync kernel & HDR in Game mode · ublue-os/bazzite
2.2.0 (2024-01-18)
Confused about which image you should use?
Try our new image picker.
It is recommended that you flash this ISO with the Fedora Media Writer. Applications like Ventoy are known to...
Known surface issue w/ the surface kernel, firmware problem
You can install a very old copy of silverblue and then rebase
or wait for the fix to be mainlined
hopefully by F40
@Windows NT is better than 9x ^i would take this advice
ok
i'll just wait a few months
does 3.00 include surface builds that actually work?
100% dependent on surface-kernel & microsoft I'm afraid
we can only support it as well as they do
I guess I'll have to pass on this one, I was gonna make a post about the same issue