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> 8.1M initrd.img-5.17.0-rc4-cadmium
<Dylanger> Not bad at all
<Dylanger> I should be able to get away with not including the modules
<Dylanger> All of the CRYPT stuff is compiled into the kernel
Lucanis has joined #aarch64-laptops
<Dylanger> > <@dylanger:diagnostix.io> ```... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/lEDApcmrMHxRqDSZSHZESUBR)
<Dylanger> Then you wanna shove it in with the kernel
<Dylanger> So both kernel + initramfs are 1
<Dylanger> Dead Space "Make us whole" vibes
shawnguo has quit [Quit: The Lounge - https://thelounge.chat]
srinik has quit []
vkoul has quit [Quit: ZNC 1.7.2 - https://znc.in]
vkoul has joined #aarch64-laptops
srinik has joined #aarch64-laptops
<Dylanger> Calling hook cryptroot
<Dylanger> cryptsetup: ERROR: Couldn't resolve device /dev/root
<Dylanger> cryptsetup: WARNING: Couldn't determine root device
<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
SallyAhaj_ has joined #aarch64-laptops
SallyAhaj has quit [Ping timeout: 480 seconds]
<Dylanger> Down to 11MB
<Dylanger> Nice
<Dylanger> With xz
<amstan> Dylanger: one of them adds like 1 second to the boot time, despite being smaller
<amstan> so i avoided it
<Dylanger> `mkimage: verify_header failed for FIT Image support with exit code 1`
<Dylanger> Hm
<Dylanger> I just added `-i`
<Dylanger> To Cadmium
<Dylanger> I think I need to define the new initramfs in the .its?
<Dylanger> 23Mvmlinux.uimg
<Dylanger> That's better
<Dylanger> You have to add the ramdisk into the its definition
<Dylanger> If I was using UUIDs, what should I put in the `root=` cmdline arg?
<Dylanger> Does this look okay?
<Dylanger> It does not like that
<Dylanger> Won't even attempt to boot
<Dylanger> `compression = "xz";`
<Dylanger> I this might need to be lzma
<Dylanger> So I think compression needs to be 'none'
<Dylanger> Hm, I can't seem to get this working
<Dylanger> Is the best I can come up with, it doesn't hang depthcharge
<macc24> Dylanger: um
<macc24> lzma
<macc24> also FYI if you use default cadmium kernel config, initramfs support is completely disabled
<Dylanger> Aaaa
<Dylanger> lol that's prob it then
<Dylanger> Just switched it to lzma
<macc24> in my initrd experiments with depthcharge machines i bundled initramfs with kernel using kernel's mechanisms
<macc24> and didn't tell anything about initrd to depthcharge
<Dylanger> Hm, if I set lzma or xz in compression, it hangs at depthcharge
<Dylanger> I just enabled initramfs support in the kernel
<macc24> Dylanger: do you have suzyqable to read what's going on?
<macc24> or other means of having serial logs?
<Dylanger> Yeah, not getting any output from the AP tho
<Dylanger> I think compression has to be "none" for some reason
<macc24> you don't have suzyqable or you have suzyqable and get log from ap?
<macc24> can't get log*
<macc24> if you make depthcharge decompress initrd, the kernel has to support uncompressed initrd
<macc24> kernel /does/ have support for decompressing initrd by itself and you might want to make kernel decompress it
<macc24> this says literally nothing to me
<Dylanger> Ah, well I just enabled that in the kernel, so maybe if compression = none in the FIT, might make the kernel decompress it instead
<Dylanger> Ayyyy
<macc24> if your init in initrd isn't in default kernel search path you have to point kernel through its cmdline to init too
<Dylanger> That worked I think
<Dylanger> I don't know 100% - but I think I'm in the initramfs now
<Dylanger> Getting close now 👌
<macc24> that doesn't look like kernel logs
<macc24> also it's `PARTLABEL=Root` iirc
<Dylanger> 👍️
<Dylanger> Okay I just need to fiddle with the update-initramfs inside the chroot
<Dylanger> Ooooh boy we're close now
<Dylanger> BAAHAHHA
<Dylanger> YES!
<Dylanger> I'm in GNOME ❤️
<Dylanger> Thanks everyone
SallyAhaj_ has quit [Remote host closed the connection]
SallyAhaj has joined #aarch64-laptops
SallyAhaj has quit []
derzahl has quit [Ping timeout: 480 seconds]
derzahl has joined #aarch64-laptops
SallyAhaj has joined #aarch64-laptops
SallyAhaj has quit [Read error: Connection reset by peer]
derzahl has quit [Ping timeout: 480 seconds]
derzahl has joined #aarch64-laptops