ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
<Dylanger>
root@05cb9b46fd98:~/initramfs# du -h initrd.img-5.17.0-rc4-cadmium
<Dylanger>
Anyone know how to make initramfs see the LUKs volume?
<Dylanger>
`ln -s /dev/mapper/root /dev/root`?
<hexdump0815>
Dylanger: with a regular initrd it should just work ...
<hexdump0815>
you give your /dev/mapper/encrypted device as root device on the kernel cmdline
<hexdump0815>
then the initrd will see that its defined in /etc/crypttab and set it up/ask for the password
<hexdump0815>
oh - you need to have the cryptsetup-bin and cryptsetup packages installed
<hexdump0815>
i think they then hook into the initrd setup and will result in the cryptsetup stuff to end up in the initrd
<hexdump0815>
small correction: initrd first sees the device mentioned in the /etc/crypttab, does the unlock procedure and afterwards is able to mount it as root as given on the kernel cmdline
<Dylanger>
<hexdump0815> "oh - you need to have the..." <- Ah yeah I had to install that, so I'm trying to generate it on a "live" USB
<Dylanger>
On the device
<Dylanger>
I can't seem to get it to detect /dev/mmc as encrypted
<hexdump0815>
even using a root=LABEL=mycryptfslabel will work then as at the time of root mounting the device is already unlocked
<hexdump0815>
Dylanger: do you have a proper /etc/crypttab?
<Dylanger>
hexdump0815: No, I'll need to make one
<Dylanger>
hexdump0815: Ah even for the live USB?
<hexdump0815>
maybe carefully go through my install-to-emmc-with-luks-full-disk-encryption.txt document and follow the path given there
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
trench has left #aarch64-laptops [#aarch64-laptops]
<amstan>
lol, leming was thinking just a few hours ago that the reason he can't boot the peach chromebooks is because the kernel grew too big
SallyAhaj has quit [Remote host closed the connection]
SallyAhaj has joined #aarch64-laptops
<Dylanger>
`/dev/mmcblk0p3 139264 1187839 1048576 512M Linux filesystem`
<Dylanger>
Can I skip this?
<Dylanger>
There's a 512MB partition that looks to be for legacy BIOS?
<Dylanger>
I think I see, I didn't chroot into the actual LUKs system