search

geckolinux / geckolinux-project

GeckoLinux bug tracker and documentation
https://geckolinux.github.io
207 stars 17 forks source link

Unbootable after installation with separate boot partition #510

Open ravenclaw900 opened 1 year ago

ravenclaw900 commented 1 year ago

Hi, While installing GeckoLinux Rolling Cinnamon, I configured the partitions as shown below (Fat32 ESP, Ext4 /boot, and encrypted BTRFS /). However, after installation, GRUB can't load the kernel. The problem appears to be that the vmlinuz on the partiton is a broken link to /usr/lib/modules/5.19.1-1-default/vmlinuz. The same thing happens for System.map, sysctl.conf, and config. I'm assuming this is because /boot is expected to be on the root btrfs partiton. Would there be a way to have the kernel actually installed on the separate boot partition?

image

praveens2208 commented 1 year ago

I too experiencing same withthe rolling release of gecko linux any desktop environment fails to load kernel 5.19 after fresh install . However live usb works well unable to load kernel and not booting to desktop.Static release works fine provife help please

BaconCatBug commented 11 months ago

I too am having this issue, which is a little upsetting :(

esteelpaz commented 9 months ago

Over on the main openSUSE forum I and others have hit problems booting from grub AND logging into a GUI with TW and Leap. There were some changes in the kernel that seemed to make things ´different". . . I had to run some commands for śd_mod"which was supposed to get grub going again. Took a long time to get any hints on getting past TW booting to ER/black screen . . . which turned out to be solved by installing ¨sddm-qt6"as the log in manager. Just posted another issue here in this list describing that problem.

As for grub issues . . . the gents on the forum kept saying ÿou have to use LABELS and UUIDs for grub to understand your request". . . my handle on that forum is something like ¨non_space1". . . if that gives any help to bailing you out on it. My ¨solution"to the grub problem was pulling one of the 4 internal drives I had installed in my desktop and then running ¨sudo grub2-mkconfig -o /boot/grub2/grub.cfg". . . . if itś more complicated than that, search the openSUSE forum for ¨michael Hamiltonś or ¨martin wilckś posts to find the ¨sd_mod"moves they prescribed to fix the grub problems of recent days.