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?

  • somethingsomethingidk@lemmy.worldOPEnglish
    1·
    7 days ago

    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

    • HayadSont@discuss.onlineEnglish
      1·
      7 days ago

      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!

      • somethingsomethingidk@lemmy.worldOPEnglish
        1·
        7 days ago

        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

        • HayadSont@discuss.onlineEnglish
          1·
          7 days ago

          I do think uBlue is downstream

          It’s indeed downstream~ish. But perhaps just different enough to actually make a meaningful change.