Видео

Sounds a bit like you removed your EFI partition or your /boot partition accidentally. There is a tool that you can install called boot-repair that can hopefully fix the problem that you are facing help.ubuntu.com/community/Boot-Repair. If you boot a live distro and see your data, I'd recommend that you backup any of your data before attempting to fix anything though

⁠thank you. Data on this device is not really important as it is mostly games. Just hate reinstalling everything again if not recoverable. Does dual booting Bazzite and Windows not advisable in this scenario?

@@CuriousTinkering The Bazzite team recommends using separate physical devices for dual boots. But you can install on one disk if you want, you just need to install Windows first

My guess is that you have legacy boot enabled and are booted into Bazzite with legacy boot? If you disable legacy/CSM in the BIOS and just use UEFI does it work?

@@mikes-tech-tips just tried disabling CSM and it removes bazzite as a bootable drive. With it on though, both options under it are set to UEFI only

Hmmm I'd guess that your machine doesn't have nano installed by default then. You can probably try vi. so 'vi /etc/fstab' but you'll need to do a bit of googling for how to edit, save and exit file editing when using vi

My guess would be that the "reboot" command is missing in the boot-windows script file. I have included the script part in a reddit post. www.reddit.com/r/Bazzite/comments/1fb6gs4/how_to_easily_boot_windows_from_bazzite_gamemode/ if you want to double check the scripts.

It's "fdisk -l" where the l is short for list

@mikes-tech-tips How do I know what the "I" is in my device ?

I've never tried to go the other way around, it probably possible. I'll see if I can figure something out and if it's easy.

@@mikes-tech-tips thanks! I already sub your channel. Awaiting for this content

positively lovely

@Dirufiedziddy I had a look at Windows 11 and it doesn't even detect that there is another operating system installed. So it might be possible with some downloadable software but I haven't found a working scriptable solution yet. Let me know if you figure anything out.

@@mikes-tech-tips noted. Thanks for the update!

Thank you for your very encouraging comment. If I remember correctly, I think it will just run on boot but if not, you'll need to start the distrobox container by entering into it.

What I think is happening is that it's trying to use the GPU for showing the installer. So try the following, when you get to the boot menu try the following: Select "Troubleshooting >> Install bazzite 40 in basic graphics mode" then see if you can get into the installer

@@mikes-tech-tips thanks for the reply. I'll try this out.

I think that you are missing the space between nano and /etc/fstab try `nano /etc/fstab` and see if that works for you.

Thanks

I still can't seem to leave the emergency mode. I still have same result.

​@@MbuaBleck I would look at the steps again and double check that you saved the changes in the /etc/fstab file (it's quite easy to miss pressing CTRL+X, then Y then enter and I have changed a file and not saved the changes numerous time).

It says [Error writing /etc/fstab: read-only file system]

I haven't seen that error before, it looks like most of the threads are about dynamic partition sizes. Do you have some form of disk RAID set up in the BIOS?

Good question. You can leave secure boot enabled, just note that you'll need to add Ventoy's key (provided that you using Ventoy). Also if you don't enter the MOK password incorrectly then you won't be to boot Bazzite at all without re-installing Bazzite or disabling secure boot. Also note that the password is now "universalblue" and no longer "ublue-os"

If you want a desktop experience, you could just rebase to the desktop image, note that it doesn't have gamemode. If that's not an option, you could try the undocumented method `ujust _toggle-autologin` but that can give issues from time to time, which is why it's undocumented

That's a good point. It's usually only /dev/sda if you are running an older SSD drive. Most people are running NVME disks these days. I'll make a note of that in the video comments, thanks.

You are welcome, that's a good point, it might be worth doing a guide on cleaning the EFI boot menu.

Agree on your Anaconda point, I really despise the Fedora default installer. Glad that ChimeraOS is working for you :)

Good idea. The easiest is to get into your BIOS menu and select Windows from there. Alternatively you can open the terminal and type `ujust regenerate-grub` next time you reboot you should see Windows and Bazzite in your list of boot options in the grub menu.

Thanks for the feedback! :)

There is no solution to the scaling and rotation while on Grub. The only nice looking solution is to use rEFInd and use a good theme.

Please disregard, after further research I realized you must pull from a release 90 days ago or sooner and found the recent release dates on the github to input. Thank you for this video, you really saved my new setup and my first dive into linux!

I see that you came right on your own, that's good news! Images are only supposed to be available for 90 days but it looks like the 20240427 edition is still available, typically you wouldn't want to go back to such an old version but you can if you want to. A few weeks back there was an issue with the Universal Blue signing key rotation, so a whole bunch of the originally signed images don't work with the new key. You should be able to use the following commands to rebase to the 20240427 edition because the "ostree-unverified-registry" will ignore the key and let you rebase (NB don't do this unless you really need to): AMD Deck image with KDE: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:40-20240427 AMD Deck image with Gnome: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck-gnome:40-20240427 AMD Desktop image with KDE: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite:40-20240427 AMD Desktop image with Gnome: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-deck:40-20240427 Nvidia Desktop KDE: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-nvidia:40-20240427 Nvidia Desktop Gnome: rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome-nvidia:40-20240427

@@TheNoobPan All the best with your first dive into Linux!

Typically you'll need to launch steam at least once for it to be visible in ProtonFix or ProtonUp-QT as only the steam "launcher" is installed but not steam in it's entirety.

Are you trying to wipe a partition with Bitlocker enabled or any other kind of drive encryption?

You can ignore that part of the installer. You no longer have the option of enabling the root user or not.

Thank for you for feedback :)

womp womp

Thank you for the compliment! I hope that the video was helpful

Thank you so much for the compliment!

Thank you for the update 💚

But why do I, as an end user, even need to do this MOK bs? Why is it not automated in the background? It's crap like this that constantly stops Linux from ever being a genuine alternative to Windows.

Thanks I've added that to the video details but I've made a pinned comment if anyone else misses it.

Which do you want to use (0 to abort)? [0-2]: 2 error: org.kde.gwenview/x86_64/stable is already installed from remote fedora error: Recipe `_install-system-flatpaks` failed with exit code 1

Removed 3 Fedora installed apps with `Discover` app, fixed the install script error.

You might find that your efi partition is structured differently than normal. In that scenario, you'll need to do manual partitioning in the installer and add a second efi partition in the disk. In this person's video they did manually partitioning and it worked great ruclips.net/video/45P3hlvq8jk/видео.htmlsi=eh0AL3uOCEGvswB0&t=865 Hope that you come right

Make sure the correct device is mounted. Look at the device list at the top and adjust the "/dev/sda1" command to match your EFI partition. The note that says to adjust the command can be blocked by the RUclips timebar.

You cannot expand a partition that is currently active. So what you'll typically need to do is boot a live ISO of Ubuntu/Mint/Fedora, fire up Gparted and expand the partition. You should be able to move the partition (in Gparted) too. Just note that it's a good idea to backup your data when adjusting partitions.

@@mikes-tech-tips alr

There is a terminal tool called switcherooctl that ships with Bazzite. You'd run `switcherooctl list` and get the id of both GPUs then you can force a specific GPU with `switcherooctl launch --gpu=gpu-id path/to/your/application` just fill in the gpu-id and the path to your application. More details of the tool here man.archlinux.org/man/switcherooctl.1.en

Sometimes secure boot can be enabled but it's in the mode of enrolling new keys, so it will show has enabled but actually not be enabled. Your best bet would be to google "asus b450 prime cannot enable secure boot", there are a couple of Reddit threads that might help

I'm glad that the guide was helpful for you

You should be able to use the Distrobox approach and the instructions here github.com/ublue-os/bazzite-arch but I'm not sure what the limitations are.

@@mikes-tech-tips Thanks, I will give this a try. There is also a bazzite-arch-gnome image, just wondering what this is....

@@drakemallard6100 I had a quick look at the source code. It looks like bazzite-arch-gnome is the same as bazzite-arch but it has xdg-desktop-portal-gnome so it can access the host system gnome resources from the container. Since you using Silverblue, you would definitely want to try this one rather than bazzite-arch.

@@mikes-tech-tips Ublue is amazing as this channel is 😀

If it's just a desktop app on KDE: * Export the .desktop files with Boxbuddy (under View Applications) * Open KDE Menu >> Settings >> AutoStart * Add your application to autostart If your app starts up with a service, you'll need to create your Distrobox via the terminal and include `--init --additional-packages="systemd" at the end to allow the Distrobox to use systemd. And you might need to run a script that starts the distrobox on startup

@@mikes-tech-tips Thanks for the info! Unfortunately, it seems that I don't have access to the COM ports with the Ubuntu container made with Distrobox. I will probably sleep on that one for tonight and see if i can figure this out tomorrow. 2024-07-02 02:54:20 AM [DEBUG] Auto detected COM port: /dev/ttyACM0 2024-07-02 02:54:20 AM [ERROR] Cannot open COM port /dev/ttyACM0: [Errno 13] could not open port /dev/ttyACM0: [Errno 13] Permission denied: '/dev/ttyACM0'

@@baccusx13 Your current user usually doesn't have access to the com/serial ports by default. Adding your user to the dialout group should fix that. `sudo usermod -a -G dialout $USER`. Although I have no idea if distrobox will have low level access like that. The --root distrobox flag may or may or may not be needed.

@@mikes-tech-tips i tried it and it didn't worked but there is hope because I discovered that Flatpack apps has permission settings so I changed them for Boxbuddy. I think I need to create a new container though... and create more time for my tinkering lol. Thanks for the replies and all. I will keep you informed as soon as I can try this out. :D