upgrade success but reboot failed about bazzite HOT 20 CLOSED

Yeah and as soon as you’re system is up with the working version you may enter in Terminal: rpm-ostree rollback to keep that version as your main os and to boot directly to that. Afaik there‘s a bug with the current 20240415 release with some devices (I‘m using Loki Max). You have to rollback to an earlier version (I‘m currently on 20240406, which works well so far).

I only have the 20240415 option on grub ... i will install a previous iso from scratch. Is there a way to install a previous image version build or should install the 2.4.0 20240314 and manage from there ?

Yeah you should install 2.4.0. afterwards you may manually update to a more recent version if you wish. But you have to do it through Terminal commands to get the correct update. When you update through Steam Gaming Mode it will always install the most recent stable one.

from bazzite.

Sure, here it is :

You can click esc once immediately, when you power on the computer. As this, you can see the boot menu. Select the ostree:1 to boot into previous version. But if you update to the newest version, problem is still here.

from bazzite.

Yeah and as soon as you’re system is up with the working version you may enter in Terminal: rpm-ostree rollback to keep that version as your main os and to boot directly to that. Afaik there‘s a bug with the current 20240415 release with some devices (I‘m using Loki Max). You have to rollback to an earlier version (I‘m currently on 20240406, which works well so far).

from bazzite.

Did v3.0.0 fixed this bug?

yeap! At least for me the desktop bazzite stable 3.0.0 works fine, upgraded and boots correctly. 👍 tx!

from bazzite.

Might be related to #972

from bazzite.

Might be related to #972

Thanks! But, Does it means that, i have to reinstall the system, and can't retain my data? Because i can't boot into the system now. 🥲

from bazzite.

Today, I reinstall the system, it’s still like this.

from bazzite.

Might be related to #972

Thanks! But, Does it means that, i have to reinstall the system, and can't retain my data? Because i can't boot into the system now. 🥲

previous update should be in the boot menu
marked ostree:1 at the end

if your grub menu is hidden you press esc at boot to show the menu.

from bazzite.

Might be related to #972

Thanks! But, Does it means that, i have to reinstall the system, and can't retain my data? Because i can't boot into the system now. 🥲

previous update should be in the boot menu marked ostree:1 at the end

if your grub menu is hidden you press esc at boot to show the menu.

I entered grub command line, but which command can boot into “ostree:1”? I’m unfamiliar with grub.

from bazzite.

Might be related to #972

Thanks! But, Does it means that, i have to reinstall the system, and can't retain my data? Because i can't boot into the system now. 🥲

previous update should be in the boot menu marked ostree:1 at the end
if your grub menu is hidden you press esc at boot to show the menu.

I entered grub command line, but which command can boot into “ostree:1”? I’m unfamiliar with grub.

https://universal-blue.discourse.group/docs?topic=36#rollbacks-13

from bazzite.

Make sure to only hit esc once (timing is critical) otherwise it will just leave the ostree and go in grub command line. The easiest way for me was to go into bios first and boot bazzite directly from bios. After you hit enter to boot bazzite partition you have to press esc immediately one time.

from bazzite.

Might be related to #972

Thanks! But, Does it means that, i have to reinstall the system, and can't retain my data? Because i can't boot into the system now. 🥲

previous update should be in the boot menu marked ostree:1 at the end
if your grub menu is hidden you press esc at boot to show the menu.

I entered grub command line, but which command can boot into “ostree:1”? I’m unfamiliar with grub.

https://universal-blue.discourse.group/docs?topic=36#rollbacks-13

Thanks. But it’s not useful. I can boot into the previous update, but when I get system update, still failed to boot into system.

from bazzite.

Same here on my Legion GO, after upgrading and also in a new install ...

from bazzite.

Same here on my Legion GO, after upgrading and also in a new install ...

Can you show me the informations? Is the same problem as this?

from bazzite.

Sure, here it is :

from bazzite.

Yeah and as soon as you’re system is up with the working version you may enter in Terminal: rpm-ostree rollback to keep that version as your main os and to boot directly to that. Afaik there‘s a bug with the current 20240415 release with some devices (I‘m using Loki Max). You have to rollback to an earlier version (I‘m currently on 20240406, which works well so far).

I only have the 20240415 option on grub ... i will install a previous iso from scratch.
Is there a way to install a previous image version build or should install the 2.4.0 20240314 and manage from there ?

from bazzite.

Yeah and as soon as you’re system is up with the working version you may enter in Terminal: rpm-ostree rollback to keep that version as your main os and to boot directly to that. Afaik there‘s a bug with the current 20240415 release with some devices (I‘m using Loki Max). You have to rollback to an earlier version (I‘m currently on 20240406, which works well so far).

I only have the 20240415 option on grub ... i will install a previous iso from scratch. Is there a way to install a previous image version build or should install the 2.4.0 20240314 and manage from there ?

Yeah you should install 2.4.0. afterwards you may manually update to a more recent version if you wish. But you have to do it through Terminal commands to get the correct update. When you update through Steam Gaming Mode it will always install the most recent stable one.

Here can i download the 2.4.0 iso ? tried to build myself , also tried to rebase on fedora atomic , but i can't or i dont know how to fetch the 2.4.0 tag. The only tags i can use is stable or testing which are both broken on my desktop and LLGO ...

Really want to use bazzite but its hard to have a working system...

from bazzite.

Managed to generate isos from bazzite tags by docker run --rm --privileged --volume ./iso:/build-container-installer/build ghcr.io/jasonn3/build-container-installer:latest VERSION=39 IMAGE_NAME=bazzite IMAGE_TAG=39-20240314 VARIANT=Kinoite IMAGE_REPO=ghcr.io/ublue-os

from bazzite.

Did v3.0.0 fixed this bug?

from bazzite.

OK, the bug seems to have been solved.

from bazzite.