swedebugia writes:
> Joshua Branson skrev: (2 februari 2019 14:50:17 CET)
>>Jack Hill writes:
>>
>>> On Fri, 1 Feb 2019, Joshua Branson wrote:
>>>
Jack Hill writes:
> Ahoy,
>
> I'm using the attached config.scm for a host with an encrypted gpt
> root partition while b
Joshua Branson skrev: (2 februari 2019 14:50:17 CET)
>Jack Hill writes:
>
>> On Fri, 1 Feb 2019, Joshua Branson wrote:
>>
>>> Jack Hill writes:
>>>
Ahoy,
I'm using the attached config.scm for a host with an encrypted gpt
root partition while booking with bios-grub. It produce
Jack Hill writes:
> On Fri, 1 Feb 2019, Joshua Branson wrote:
>
>> Jack Hill writes:
>>
>>> Ahoy,
>>>
>>> I'm using the attached config.scm for a host with an encrypted gpt
>>> root partition while booking with bios-grub. It produces the attached
>>> grub.cfg, which lacks the luks module, thus g
On Fri, 1 Feb 2019, Joshua Branson wrote:
Jack Hill writes:
Ahoy,
I'm using the attached config.scm for a host with an encrypted gpt
root partition while booking with bios-grub. It produces the attached
grub.cfg, which lacks the luks module, thus grub cannot find the
kernel.
If I enter the
Jack Hill writes:
> Ahoy,
>
> I'm using the attached config.scm for a host with an encrypted gpt
> root partition while booking with bios-grub. It produces the attached
> grub.cfg, which lacks the luks module, thus grub cannot find the
> kernel.
>
> If I enter the grub command line and manually i
I have solved my problem, and now have Grub working with an encrypted /.
The config I had before had a gpt partitioned disk, with bios boot. I had
an encrypted / and a separate, unencrypted /boot.
When I changed the configuration to not use a separate /boot filesystem,
and put /boot on the enc
