Hi,
> > Bilinmek Istemiyor <[email protected]> writes: > > > > > I am newbie to guix and have been trying to install it for the first time > > > with my usual setup with root on luks + lvm + btrfs. For a week, I > > > thought > > > that there was something wrong with my config.scm until being aware of by > > > user ruther in guix channel of libera.chat. > > > > > > Basically in my case grub can open luks, in grup command prompt, I can > > > see > > > the lvm devices by ls command and but load kernel somehow. > > > > > > I am really frustrated that such a important feature is neglected for > > > years. This is truly a show stopper for me. Please do something about > > > this. > > > > My stack is LUKS -> LVM -> BTRFS (seems the same as you) and I can boot > > just fine. I have read through the ticket, and must admit I am bit > > confused what does not work. Could you share what you configuration > > (config.scm) and layout partition layout look like? Maybe also whether > > you are using BIOS or UEFI? > > > > Thanks > > > (define %bootloader > (bootloader-configuration > (bootloader grub-efi-bootloader) > (timeout 7) > (menu-entries > (list > (menu-entry > (label "NixOS") > (device (uuid "3320-6183" 'fat)) > (chain-loader "/EFI/systemd/systemd-bootx64.efi")))) > (targets '("/boot")) > (keyboard-layout %keyboard-layout))) > > I believe that the reason that it works for one of you but not the other is this line > (targets '("/boot")) If you has your efi partition on /boot/efi, then, grub would embed the lvm module automatically to the efi. Presumably because it would detect you have lvm (haven't verified that, maybe it does it always) But when you specify /boot, it doesn't have to embed any modules, because they're on the same partition. So it hands off to the grub.cfg that does NOT load the lvm. So for some LVM on root on Guix will work, while for some it won't. Depending on their config. Rutherther
