Last (debian testing) update with kermel 6.10.6 won't boot #478
Replies: 7 comments 14 replies
-
Hi there, 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.
Was this before or after you tried the |
Beta Was this translation helpful? Give feedback.
-
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: |
Beta Was this translation helpful? Give feedback.
-
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>
|
Beta Was this translation helpful? Give feedback.
-
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>
|
Beta Was this translation helpful? Give feedback.
-
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>
|
Beta Was this translation helpful? Give feedback.
-
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>
|
Beta Was this translation helpful? Give feedback.
-
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>
|
Beta Was this translation helpful? Give feedback.
-
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.
Beta Was this translation helpful? Give feedback.
All reactions