Last (debian testing) update with kermel 6.10.6 won't boot

[Spaceboy60]

Just get a black screen, have to use old kernel to boot. Plus snapshots gone from grub menu. Also, now when i try run snapper rollback i get error:

Cannot detect ambit since default subvolume is unknown. This can happen if the system was not setup for rollback. The ambit can be specified using the --ambit option.

[geckolinux]

Hi there, snapper rollback is not to be used in SpiralLinux. Please follow these instructions:
https://github.com/SpiralLinux/SpiralLinux-project/wiki#working-with-btrfs-snapshots-and-rollbacks

Also, if the problem is just with a kernel update then it's best to simply select a different working kernel in GRUB and optionally uninstall the buggy kernel, no need to rollback the system.

snapshots gone from grub menu

Was this before or after you tried the snapper rollback command?

[Spaceboy60]

Was this before or after you tried the snapper rollback command?

Before.

Also according to the above instructions i should use: sudo snapper-rollback X where X is the number of the snapshot to rollback to. However when i run the command i get the error: root argument can only be used together with no-dbus

In terms of kernel, i've removed the current kernel, so that's not an issue.

[geckolinux]

Sorry it didn't work. I imagine that the snapper rollback command broke something. I just tried an upgrade to Testing and then a rollback and it worked:

[Spaceboy60]

Sorry it didn't work. I imagine that the snapper rollback command broke something. I just tried an upgrade to Testing and then a rollback and it worked:

And you did a full upgrade?

Has it got anything to do with having a separate home partition? Any other ideas why these two issues may have occurred?

I used apt update & & apt upgrade.

[Spaceboy60]

I imagine that the snapper rollback command broke something

I doubt it, It was broken before that as no snapper option in grub menu and unable to boot after upgrade

[geckolinux]

And you did a full upgrade?

Yep, I used this method:
https://github.com/SpiralLinux/SpiralLinux-project/wiki#switching-from-debian-stable-to-the-testing-or-unstable-branch

Has it got anything to do with having a separate home partition? Any other ideas why these two issues may have occurred?

Not sure what might have happened, sorry I can't be more helpful. The separate /home partition won't make any difference, because even on a single / partition installation /home is on a separate Btrfs subvolume.

At this point the easiest way to recover the rollback functionality for your system would be to reinstall. Especially since you have a separate /home partition it should be quite painless (but still backup your data first). Just keep in mind that breakage in Debian Testing and Sid is to be expected.
https://github.com/SpiralLinux/SpiralLinux-project/wiki#switching-from-debian-stable-to-the-testing-or-unstable-branch

Important: Debian's Testing and Unstable branches may work very well for some users' needs, but they do not claim to be stable releases and should only be used with extra care by experienced users.

[Spaceboy60]

I've reinstalled the budgie version, done the update again via synaptic, once again black screen upon reboot. Last time i selected not replace lightdm and lightdm config, this time i selected to replace them both, same result: black screen with new kernel. And once again: sudo snapper-rollback X where X is the number of the snapshot to rollback to brings root argument can only be used together with no-dbus error.

[geckolinux]

Sorry I just saw your latest update. There are two separate issues here:

1. Debian "Testing" as the name says is not meant to be a stable release. It's very common for different kernels in Testing to fix or break something depending on your specific hardware. When this happens, instead of doing a rollback it's best to select a different kernel in GRUB and/or uninstall the broken kernel.
2. I'm not sure why snapper-rollback isn't working for you, I'll look into this later.

[geckolinux]

Is your installation on a legacy BIOS or UEFI system?

[geckolinux]

I just did a fresh installation from SpiralLinux_Budgie_12.231120_x86-64.iso on a UEFI system with a separate /home partition, and upgraded it to Testing as described earlier.

At this point in time it looks like Budgie is broken in Testing, because it removes some core budgie-* packages and others are not installable. Upon reboot into the upgraded Testing system there was just an X session graphical terminal with no Budgie session available in LightDM.

So I rebooted into snapshot #1 and performed a successful rollback:

So if you could, please give a detailed list of the steps that you're taking when you reinstall (including the partition layout) as well as screenshots of the rollback attempts. Or if you prefer I would recommend you reinstall and stay on Debian 12 Stable for now, as Budgie is broken in Testing.

[Spaceboy60]

Is your installation on a legacy BIOS or UEFI system?

Legscy

[Spaceboy60]

Ok, will do when I get back from hospital. Would the fact the /home partition is ext4 make a difference? / is btrfs. And what may be causing the latest kernel to not book (black screen)? Also if I select a snapshot in grub menu how do I make the rollback permanent since you say you can't just do snapper rollback followed by a reboot?

…

On Fri, 6 Sept 2024, 16:03 GeckoLinux, ***@***.***> wrote: I just did a fresh installation from SpiralLinux_Budgie_12.231120_x86-64.iso on a UEFI system with a separate /home partition, and upgraded it to Testing as described earlier. At this point in time it looks like Budgie is broken in Testing, because it removes some core budgie-* packages and others are not installable. Upon reboot into the upgraded Testing system there was just an X session graphical terminal with no Budgie session available in LightDM. So I rebooted into snapshot #1 and performed a successful rollback: Screenshot.from.2024-09-06.09-54-59.png (view on web) <https://github.com/user-attachments/assets/514d31b7-9876-45db-afd7-b2c5f42d2ccb> Screenshot.from.2024-09-06.09-56-42.png (view on web) <https://github.com/user-attachments/assets/5cc9ca90-ab1a-4401-8515-60955139d042> So if you could, please give a detailed list of the steps that you're taking when you reinstall (including the partition layout) as well as screenshots of the rollback attempts. Or if you prefer I would recommend you reinstall and stay on Debian 12 Stable for now, as Budgie is broken in Testing. — Reply to this email directly, view it on GitHub <#478 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2NC4WPJKBMDCTJI2IZ27I3ZVG725AVCNFSM6AAAAABNXQHCR2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANJXGA2DKOA> . You are receiving this because you authored the thread.Message ID: <SpiralLinux/SpiralLinux-project/repo-discussions/478/comments/10570458@ github.com>

[geckolinux]

Hi there,

Would the fact the /home partition is ext4 make a difference?

No, snapper-rollback only handles the Btrfs root partition.

And what may be causing the latest kernel to not book (black screen)?

There's a million changes in every new kernel version, and in Debian Testing they're not guaranteed to work and frequently don't work.

Also if I select a snapshot in grub menu how do I make the rollback permanent since you say you can't just do snapper rollback followed by a reboot?

Notice that snapper [space] rollback is not the same as snapper-rollback . They are completely different utilities. The instructions given for snapper-rollback do perform a permanent rollback after you reboot.

[Spaceboy60]

Just wanted to check/clarify couple of things : sudo snapper-rollback x 1.There are no spaces after snapper, i.e snapper-rollback and not snapper - rollback. 2. To get the rollback number I use sudo snapper list?? 3. If I've booted from a read only snapshot I still need to specify a snapshot number, i.e I can't just use sudo snapper-rollback

…

On Fri, 6 Sept 2024, 02:36 GeckoLinux, ***@***.***> wrote: Hi there, snapper rollback is not to be used in SpiralLinux. Please follow these instructions: https://github.com/SpiralLinux/SpiralLinux-project/wiki#working-with-btrfs-snapshots-and-rollbacks snapshots gone from grub menu Was this before or after you tried the snapper rollback command? — Reply to this email directly, view it on GitHub <#478 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2NC4WJMFHQ7YLPHAXO2VLDZVEBJPAVCNFSM6AAAAABNXQHCR2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANJWGM2TKMY> . You are receiving this because you authored the thread.Message ID: <SpiralLinux/SpiralLinux-project/repo-discussions/478/comments/10563553@ github.com>

[geckolinux]

Hi there,

1. sudo snapper-rollback X
2. The number is visible when you select the snapshot to be booted in GRUB, and/or you can use Snapper GUI (Instructions)
3. Correct.

[Spaceboy60]

Thanks, not sure why but just did a sudo apt update & & sudo apt upgrade and I'm presented with a black screen upon reboot.

…

On Sun, 29 Sept 2024, 20:41 GeckoLinux, ***@***.***> wrote: Hi there, 1. sudo snapper-rollback X 2. The number is visible when you select the snapshot to be booted in GRUB, and/or you can use *Snapper GUI* (Instructions) <https://github.com/SpiralLinux/SpiralLinux-project/wiki#working-with-btrfs-snapshots-and-rollbacks> 3. Correct. — Reply to this email directly, view it on GitHub <#478 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2NC4WN5S3K4AV5C3XRB4GDZZBJVXAVCNFSM6AAAAABNXQHCR2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZZGEYDMNQ> . You are receiving this because you authored the thread.Message ID: <SpiralLinux/SpiralLinux-project/repo-discussions/478/comments/10791066@ github.com>

[geckolinux]

Hi there, are you on Debian Testing or Stable?

[Spaceboy60]

Stable branch, boots on old kernel still

…

On Tue, 1 Oct 2024, 02:08 GeckoLinux, ***@***.***> wrote: Hi there, are you on Debian Testing or Stable? — Reply to this email directly, view it on GitHub <#478 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2NC4WJ7IZDWMNKEPYOOMV3ZZHY2LAVCNFSM6AAAAABNXQHCR2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOBQGM3DCMY> . You are receiving this because you authored the thread.Message ID: <SpiralLinux/SpiralLinux-project/repo-discussions/478/comments/10803613@ github.com>

[marwenius]

Perhaps problems with the graphics card drivers as discussed here:
https://github.com/orgs/SpiralLinux/discussions/448#discussioncomment-10467356

[geckolinux]

The easiest solution would probably be to just uninstall the broken kernel. If the Debian Stable 6.1.0 kernel works you could even remove the Backports kernel APT preference that SpiralLinux uses by default.

[Spaceboy60]

Yes that's what I ended up doing I'm using grub customizer to point to the old kernel. I'll pay more attention to the kernel update version when I'm updating next time. Or maybe freeze the kernel packages before updating.

…

On Tue, 1 Oct 2024, 16:49 marwenius, ***@***.***> wrote: Perhaps problems with the graphics card drivers as discussed here: #448 (comment) — Reply to this email directly, view it on GitHub <#478 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2NC4WL4FBPHJYY6PGRAVULZZLAALAVCNFSM6AAAAABNXQHCR2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOBRGA4DGMI> . You are receiving this because you authored the thread.Message ID: <SpiralLinux/SpiralLinux-project/repo-discussions/478/comments/10810831@ github.com>