When I last updated Kinoite (1-2 days ago), the only packages that were updated were kernel related things. Going from 6.14.4-200 to 6.14.5-300.
When I try to boot into the new deployment, the system just hangs on the plymouth boot screen and I have to do a hard reset on the computer. No logs are generated, so I’m either not getting out of grub or I’m stuck in the iniramfs stage (but that usually prints some errors and drops you into a rescue shell). It’s so weird. It just sits there.
My old deployment works fine though. Anybody else experienced something similar? Or know of a way I can get some more info out of the system?
No Nvidia, just intel integrated graphics. Its a dell ispiron 7500.
My system isn’t pristine but it’s not that bad, and I don’t see how any of the packages would cause this problem. I can upgrade fine, there’s no conflicts. I could see it messing up if I tried to layer a different bootloader but it’s nothing like that. Here’s my layered packages anyway
LayeredPackages: alacritty bat btop distrobox fish flatpak-builder kpeoplevcard light lsd mako neovim parallel python3-neovim shellcheck swaybg swayfx swayidle swaylock syncthing tailscale tmux virt-manager waybar wlogout wlsunset wofijournalctlshows nothing. That’s what I meant by no logs, I should have been clearer. It’s not even getting that far. It’s like it’s stuck in grub, but only when I try the new kernel.The only deviation from the vanilla kargs have been for troubleshooting this and I did it in the grub editor so they aren’t persistent. I tried removing
rhgbchangedquiettoverboseanddebugandloglevel=7just to see if anything would happen. It still just hangsYeah, that shouldn’t cause any pecularities.
Hmm…, nothing too outrageous, I think; still, consider
rpm-ostree resetto at least rule out the possibility that any of the layered packages are to be blamed. If you’re afraid of losing your working deployment, ensure to evoke thesudo ostree admin pin 1command to pin it. (ASSUMING THAT THERE ARE ONLY TWO DEPLOYMENTS WHEN YOU DO THIS). After you’ve done the pinning, ensure that you pinned the correct one by checking this withrpm-ostree status; the deployment you wish to pin should state the fact that it’s pinned.Perhaps I had to be more clear and explicit, boot twice:
journalctl -b -1command. This should, unless something is wrong with how systemd is setup on your system, show you the logs of the previous boot. You could even compare it with your current boot (which can be accessed withjournal -b) and see where it diverges, though looking at the logs of the corrupt boot sequence should suffice.Aight. Thank you for putting in the work so we can rule that out!
date > time.txt && rebootjournalctl -b -1and the last entry was 2 seconds after thedateoutput in step one.It is not even getting to systemd.
I tried uninstalling the packages, and rebasing to silverblue. Nothing changed. I think I’m going to just put a pin in it and hope that the next update fixes something haha
speaking of pins
This is so important and the first thing I did. I got screwed a few years ago when I first tried silverblue. Everyone talks about how you can just rollback, no one ever mentions that you can lose your last working deployment hahah thanks though
I’m pretty clueless at that point. Never seen something like it. Apologies for not actually being able to help out. Hopefully it will be resolved soon, though.
This is probably not the advice you’d like to hear, but I wonder if rebasing to uBlue’s Kinoite would make any difference. Regardless, wish you the best!
Right? It’s super strange. On a normal system I would try reinstalling GRUB and maybe manually generating the initramfs, maybe compile a new kernel, but idk if I can do that here.
That’s actually really interesting, maybe getting away from the fedora ecosystem would help. I do think uBlue is downstream. But it wouldn’t hurt
It’s indeed downstream~ish. But perhaps just different enough to actually make a meaningful change.