Can't install Bazzite Gnome Nvidia on HP Envy 13 (ba0553na) Laptop
I've used the the listed options on the Bazzite site to get the Offline ISO. The goal is to have this Dual Booted with an existing install of Windows 11 on the same NVMe SSD. I've already partition the drive, with about half ready for Bazzite. The attached image of the error appears as soon as the installer tries to start. I never actually see the Anaconda installer GUI. I have about 3-5 seconds to click on the
More info link before the cursor disappears and few seconds later the system reboots. As far as I can tell it's not a hard crash since some strings appear once the screen goes to black before the reboot.
Things I've tried:
- Creating the install media with Rufus and Balena Etcher.
- Disabling Secure Boot
None of this appears to have made a difference. Not sure if there are any other ways for me to send you a log of what is happening. Let me know if there is and I will try to do that. Thanks!
P.S. Is using the Nvidia image correct in this use case considering that the laptop has an integrated Intel GPU and a Dedicated Nvidia MX350 GPU?
Solution:
Jump to solution
The culprit was Intel Optane. This laptop comes with a 512gb NVMe SSD and a 32GB Intel Optane on the same stick. This means you can set up the Optane part to speed up / assist the main SDD in the BIOS and that technically means they are operated by a RAID Driver. I had that on and Anaconda apparently doesn't like it.
I figured it out by finding the error in the file:
tmp/anaconda.log.
Then when looking up that issue I've found these two links:
https://discussion.fedoraproject.org/t/error-installing-fedora-with-anaconda-no-device-at-md127/84502...64 Replies
im not sure why there's an error here. i would follow these instructions though: https://discord.com/channels/1072614816579063828/1211875558959484969/1212091558497751070
i would like to also warn you that i dont think that GPU still recieves nvidia's proprietary linux driver support, but let me see if i can double check that
nvidia is known for dropping support on older GPUs on linux
nvm it's supported that's good news
really weird error though. def try rebasing from stock silverblue
this is the 2nd time ive seen issues with
-nvidia ISOs in the last 24 hours but this one is completely differentYeah I saw the other post but considering that I got an error at another point I figured I'd post another just in case there was another solution.
I guess I can follow the instructions for dual booting (partitioning) from Bazzite on the Silverblue install then rebase and it should all be good?
nah dont follow the dual boot guide
what desktop environment are you using
gnome or kde?
oh wait
you're dual booting
Well planning to yes
i wonder if something has changed since the new ISOs
Both my Desktop and Laptop are currently only Win11
dual booting is a pain on fedora atomic in comparison to other distros
I'm trying the Fedora Media Writer as a last shot to see if that does anything. Worst case I'll see if I can get another USB drive just in case.
but that guide used to work
ok.. but im thinking it might be the dual boot part that is a little funky
The laptop isn't mission critical so I can afford for things to mess up.
well if you still have issues with fedora media writer:
https://fedoraproject.org/atomic-desktops/silverblue/ for GNOME
https://fedoraproject.org/atomic-desktops/kinoite/ for KDE
follow the rebase instructions on the website, and yeah try following the dual boot guide
Fedora Silverblue
An atomic variant looks, feels, and behaves just like a regular desktop operating system, but your updates are delivered as full images of a working system. This makes every installation identical to every other, and it will never change while in use. What's more, Silverblue will always keep an older version of the system around for you to boot ...
tbh dual booting on the same drive isn't really supported upstream at all, but i made that guide because it seems others have figured it out
Gotcha. Thank you! Will update on progress. I'm sure it will be fine :clueless:
i mean users have done it before so it does seem to work. good luck!
Ok Fedora Media Writer also didn't fix it. Getting Silverblue now
yeah let me know if that changes anything
Sorry for shaky images. This is on Fedora Silverblue 39. Same error. The only thing different is the warnings on the screen before. Again this is on the same USB drive so I'll try with a different one now.
thats fine thanks for this
is your BIOS UEFI?
Yeah
if this is happening with stock fedora silverblue then it's def something else unrelated to ublue/bazzite
do you have another flash drive or some kind of external device?
it might be the drive you used
but it also may not. it's weird that anaconda is giving you this error
Yeah I'm starting to think it might be. Then again I used it to install Windows on a friends PC a few weeks ago and it was fine. Maybe it's finally had enough. I've got another to try.
lmk if that changes anything because im running out of possible explanations unless fedora's installer hates your laptop lol
Same happens on another drive. Looks like I'm 2 revisions old on the BIOS so I'll give updating that a shot. Honestly it wouldn't surprise me if this laptop is cursed. I've had some issues with it before with Linux where the WIFI card wasn't properly supported and it wouldn't actually connect to anything despite the SSIDs showing. I did try a live image of plain Fedora Workstation 39 when that released and it all seemed to work fine so it gave me some hope then.
I did try a live image of plain Fedora Workstation 39 when that released and it all seemed to work fine so it gave me some hope then.so your laptop def doesnt like fedora atomic lol
I've tried:
- BIOS Update.
- Deleted all Secure Boot Keys which definitely disabled it.
- Disabled TPM.
- Disabled Intel Software Guard Extensions.
- Tried using Silverblue 38 image (Same errors).
None of the above worked...
I've found this article: https://discussion.fedoraproject.org/t/installer-crashes-when-attempting-to-install-on-a-hp-pavilion-g6-amd-from-2011/85387
So I'm getting a Workstation 39 image to see what my EFI boot menu looks like and see if this might do it š¤
good luck, this is a strange issue and i do think your laptop is very cursed š
the dedication is wild
i was going to recommend installing nobara since that's based off "mutable" fedora
at least the installer works for you
So the EFI looks fine at least it doesn't have those symbols anywhere. Also when running the installer in the live environment it threw the same error but then when I ran it again and tried a few times subsequently it just works (?). :clueless: Now to figure out why that happens and try fix it for the direct installer in Bazzite / default Atomic image.
:fedora: š
Solution
The culprit was Intel Optane. This laptop comes with a 512gb NVMe SSD and a 32GB Intel Optane on the same stick. This means you can set up the Optane part to speed up / assist the main SDD in the BIOS and that technically means they are operated by a RAID Driver. I had that on and Anaconda apparently doesn't like it.
I figured it out by finding the error in the file:
tmp/anaconda.log.
Then when looking up that issue I've found these two links:
https://discussion.fedoraproject.org/t/error-installing-fedora-with-anaconda-no-device-at-md127/84502
https://www.reddit.com/r/Fedora/comments/142ve2f/can_i_install_fedora_with_dual_boot_in_a_laptop/
That's when I remembered about the Optaine in this laptop. I've reset all the other options back on so the screenshot above is with Secure Boot, TMP and Intel Software Guard Extensions enabled. Just to note, when you disable the Optane Volume it doesn't give you any progress bar but you won't be able to go up onto the other options so you will know that it's doing things. As it says it will preserve all user data if you select yes so don't worry. Took about 5 mins to do it.
I also got curious so I took the laptop apart so that is the SSD inside.Now to see what mysteries the Dual Boot installation holds for me š
LOL
that's so bad š
how has the dual booting gone
I'm in š„³ There are a few steps I'll suggest to add to the Dual Boot Forum guide and some more info on this specific issue soon.
when you get a chance let me know!
glad it's working
Dual Boot Partitioning Steps
The following steps assume you are Dual Booting Windows on a single drive and have created free space for Bazzite. This can be done with Disk Management in Windows (
Win + R to open Windows Run and type diskmgmt.msc). Right Click your Windows partition and then Shrink Volume in the dropdown. Select how much you want to allocate for Bazzite.
When Installing Bazzite:
In Installation Destination, select Advanced Custom(Blivet-GUI) under Storage Configuration. Configure it like so:
- You will likely have an efi partition already if you are dual booting with Windows, so you don't need to make another one but you have to select it and click the Cog icon, followed by Set Mountpoint in the dropdown. Set it to /boot/efi.
- Create a 1GB /boot partition.
- Create a btrfs volume with the remaining free space.
- Click on the btfs volume and then click on the + to add subvolumes to it. Make /, /var and /var/home subvolumes.
Note that in the screenshots, the nvme0n1p1, nvme0n1p2, nvme0n1p3 and nvme0n1p4 are existing partitions from my Windows install. The space you created in Windows will be tagged as Free Space The new ones I created are nvme0n1p5 for the boot and Bazzite-... for the main btrfs volume. You can see all the subvolumes by clicking on the Btrfs Volumes folder in the sidebar.
Potentially Laptop Specific
- When Install finished and system rebooted, it turned out I still needed to have Secure Boot turned off to be able to boot the system, otherwise I got this issue. Once I turned it off the top option booted the one below gave the kernel error again. I didn't have to regenerate GRUB for Windows to work.
- By default the
OS Boot Manager set Windows Boot Manager to be the first thing to boot which resulted in booting directly into Windows after the install. To have GRUB come up you want to change the order. Doing so is a bit awkward in this BIOS. You open the OS Boot Manager option and use F6 and F5 to shift the selected options up or down. To save them press F10 otherwise if you use ESC it will cancel your changes. No other buttons confirm this... Good one HP. I set Bazzite first, Fedora second and Windows Boot Manager last. So this way you boot your system and get to pick your OS via GRUB. In my case both boot fine without other changes.
- The Wi-Fi chip was detected during install but couldn't see any networks (Not sure if that is intended). Didn't matter since it was an offline ISO with everything there and it works fine once booted into Bazzite.
- Function keys that don't work:
- Brightness (F3 and F4).
- Settings (F12).
- Microphone Mute (F8). It has an LED to indicate Mute is on too.
All other function keys work as intended. Not sure if this is something that can be addressed by Bazzite or if it would need to be done upstream... or if it can be fixed at all but figured I'd mention just in case. If there is an existing way you know of to assign these I'd love to hear about it!
Small Notes
- https://universal-blue.discourse.group/docs?topic=33#wayland-or-x11-14 Mentions that Nvidia images don't use Wayland by default but this Gnome-Nvidia image is using Wayland (I assume it's support became better?). Also, both GPUs appear to be working just fine and appear correctly in Mission Center.
- Wi-Fi wasn't connected on boot since I couldn't select a network during install on boot. Bazzite Portal obviously couldn't download and install the options selected. I only realised something was wrong since it finished the first install step almost instantly. It would be good to have a prompt to connect to the internet first before selecting options if the app can tell there is no internet connection. I know that this should be obvious because you never connected the computer to the internet but still I'm pretty sure it said things installed successfully even though clicking on
Show Console clearly showed things failed.
@tryhardsoccermomswag That's all the notes I took. Sorry not sure what your position is with Bazzite but feel free to use any of this to add to existing docs. Thanks for joining along for the ride! š
oh wow i wasnt expecting all of this š
i talked to kyle, yeah they swapped back to wayland as the default because XWayland got patched
i will fix that
thanks for all of this feedback
Sure. Sorry for the wall of text but I figured there might be some useful info here š
no thats fine, there's useful information that i am going to document later
do you mind if i credit you at the bottom of the dual boot doc?
as a documentation contributor
oh one more thing: that first time bootup application is here as a crutch because of a limitation with fedora's installer. it isn't going to be here forever (or it will change drastically when the time comes)
i documented that it requires a network connection though thanks
also wait your fn keys don't work? that must be exclusive to your hardware then tbh
i have a lenovo ideapad laptop and the microphone mute and brightness work. settings well.. that probably will never work on linux in general due to the desktop environment fragmentation
Yeah the settings and Mic mute ones are whatever. It would be cool to have the brightness keys to work like the rest with the FN key. I know I can custom bind another mod key and the F keys with a command in Gnome so I can resolve this. Just curious if there was a proper way.
i can talk to some of the maintainers, but like it's weird because my laptop's brightness and microphone function keys on my laptop on bazzite
do those functions usually work on other linux operating systems?
if you tested that
Not sure. I haven't used anything else on it recently. I could try a few off a USB live. I'll see if Ubuntu would have them work.
yeah if you don't mind and want to. fedora and upstream universal blue usually has support for hardware like that. your particular laptop might not have the best support for linux lol
Just ran
sudo libinput debug-events --show-keycodes and it shows DEVICE_ADDED HP WMI hotkeys. All the keys but the ones I described print out the right keycodes. The ones that don't work don't print.I think I have the same issue as here https://www.linux.org/threads/hp-laptop-keyboard-codes.40981/
Linux.org
HP Laptop - Keyboard codes
I bought my wife a HP 15-dw0046nr laptop, and installed Linux Mint Debian Edition 5.
* side note: I bought it from local trusted pawn for $150. It smelled like Cheetos.
System info:
~ $ inxi -Fnxx
System: Host: venus Kernel: 5.10.0-15-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 Console...
I ran
journalctl -f and get the same messages. The same identifier for both keys so I could follow the last 2 posts in that thread but only have Brightness Up on both š«
Also for Secure Boot, I missed the part about it in the Initial Setup forum post so I probably could have had it working right away. I dismissed the MOK screen as something that came up from me messing around with the BIOS settings. Anyway I did the post install method and it worked.yeah you're not the only one to miss that it's fine
im happy we have a method post-installation
Yeah it was super easy although I noticed it prints you the
echo"..." string before actually executing it and printing it in the terminalujust is being reworked by hikariknight eventually
so some of these issues will go away
this project isn't even really a year old
so tons of stuff left to do/fix
lolYeah don't mind me being petty. Just noting things down as I see them. This is already fantastic. Besides my BS laptop everything is working perfect so far.
it's fine. better to have issues known and fixe eventually than to say nothing about them
Tried Live environments from:
- Ubuntu 23.10
- Elementary OS 7.1
- EndevourOS Galileo Neo 2024.01.25
- PopOS 22.04
They all only support the same Function keys as Bazzite. Maybe they load some extra stuff when installed but I doubt it.
yeah thats the hardware not being super supported on linux
so you are now missing functionality in your function keys
š
š
Like I said I'll just bind something like Shift and the corresponding F keys to handle brightness. Rest I don't really need so all good. It's not exactly hard to change it manually on Gnome anyway.
hey sorry, have you ever gotten kicked to emergency mode after an install? i can't boot even after following the guide to a T on the steam deck...
No sorry I've not experienced that
i am starting to believe i am cursed šµāš«
Root account is locked? Not sure if I understand that correctly but aren't we supposed to not make a Root account and just have the user account as admin.
yes, i've tried both things :') the only way i've gotten it to boot is my installing it on the sdcard...
i've tried automatic, manual and your guide when it comes to partitioning
i've tried mounting to /home and /var/home as well, no dice :')
i even used the same subvolume names
Considering this is on the Steam Deck I'm guessing there are some other things to keep mind of. My steps were specifically for when a Windows install is already present and you are Dual Booting off the same drive. Assuming you are trying to get Bazzite going alongside SteamOS I bet there will be specific ways to do that setup if you even can.
I decided that Bluefin might be more appropriate for my use case on this laptop so today I ended up fully removing the Bazzite install and reinstalling Bluefin in it's place.
To remove Bazzite it was simply a matter of mounting the EFI partition in Windows with
diskpart (https://superuser.com/a/699353) and deleting the fedora folder in the EFI via Terminal. Rebooted to make sure Windows Boot took over (it did but I still pre-checked in the UEFI). Then I deleted all related partitions to Bazzite but the EFI one with Windows' Disk Management. So this is an effective way to undo the dual boot. Just would have to extend the Windows partition back to fill the drive.
In this case, I installed Bluefin all the same as before and it worked perfectly!
For the Brightness function keys not working I used the following commands to fix it, using Shift instead of FN:
This works perfectly and I get the OSD to indicate the brightness level.