What you want is an OEM install. Ubuntu and mint have them. Note sure what others do.

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.

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.

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!

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

Perhaps I had to be more clear and explicit, boot twice So yeah it’s not showing anything from the “first” broken deployment. Just to be empirical,

• I ran date > time.txt && reboot
• Tried to boot the new deployment, waited about 10 min
• reset and booted into working deployment
• ran journalctl -b -1 and the last entry was 2 seconds after the date output 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

If you’re afraid of losing your working deployment, ensure to evoke the sudo ostree admin pin 1 command to pin it.

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

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 wofi

journalctl shows 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 rhgb changed quiet to verbose and debug and loglevel=7 just to see if anything would happen. It still just hangs

I left it for an hour and it did nothing :(

I added earlyprintk verbose loglevel=7 to the kernel params in grub and all it says is: Booting a command list

Still hangs

Nope, escape does nothing. Tried different tty, does nothing. It’s not even showing the fedora symbol under the Dell icon. I am about to try and just let it sit for 15-30 minutes and see if it does anything.

Damn I had no idea, you made my day

Yes

https://github.com/Pranshul-Thakur/DOOM-in-excel

Today I learned I’m a masochist