robclark changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
<clover[m]>
its really looking like grub-btrfs is not prepared for our weird kernel names and initrd's, also do we have microcode? i dont think so it seems like just an x86 thing
<steev>
no, no microcode. what do you mean by weird kernel names and initrds? are you naming them something weird? the names i use in kali are identical to what we use on x86_64 (but also, not using grub-btrfs)
<clover[m]>
yeah, so my kernel name is Image and my initrd is named initramfs-linux.img
<clover[m]>
the suffix of my initramfs is not matching my kversion
<harvestz[m]>
anyone using Armbian for the x13s?
<clover[m]>
i think i booted it once
<harvestz[m]>
I'm considering that with the ubuntu concept iso
<harvestz[m]>
s/with/or/
<clover[m]>
I like Armbian. I run it on my little home server box
<clover[m]>
steev: what should I be naming them?
<harvestz[m]>
I think I'll give Armbian a try then
<Stirl[m]>
I'd be interested to know how it goes. I had some trouble with getting the arch iso to work and just haven't had enough time to re investigate
<harvestz[m]>
I had 6.2 on it, compiled the kernel myself but I think I used clover's repo for packages
<harvestz[m]>
ended up going back to windows though (and I haven't really used it much)
<clover[m]>
but i feel like the most likely case is that i am packaging the kernel with the wrong name
<patzek[m]>
<Stirl[m]> "I'd be interested to know how it..." <- I was in the same position, after a bios update i was able to install arch provided by the iso from ironrobin.
<clover[m]>
heads up arch might be changing kernel names. i'll try to add a post hook warning message to update your bootloaders
<steev>
harvestz[m]: i'm not, but they tweeted about it
<steev>
clover[m]: fwiw, debian does whatever-$kver
<steev>
also sorry, was semi afk (thursday night is family dinner night)
sally has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
xypron has quit [Quit: xypron]
xypron has joined #aarch64-laptops
laine has joined #aarch64-laptops
srinik has quit [Killed (NickServ (Too many failed password attempts.))]
srinik has joined #aarch64-laptops
Cyrinux9474 has quit []
Cyrinux9474 has joined #aarch64-laptops
laine has quit [Ping timeout: 480 seconds]
laine has joined #aarch64-laptops
laine_ has joined #aarch64-laptops
laine has quit [Ping timeout: 480 seconds]
laine_ has quit [Remote host closed the connection]
<clover[m]>
doesn't vmlinuz mean compressed? i thought we couldn't boot a compressed kernel
<travmurav[m]>
on aarch64 the bootloader must decompress the kernel
<travmurav[m]>
so anything that your bootloader can eat works
<travmurav[m]>
(as in, compared to self-decompressing kernels that are not allowed afaik)
<ardb>
efi boot on arm64 supports EFI zboot images now, which self decompress in the EFI boot environment
<ardb>
afaik, fedora switched to that for arm64
<clover[m]>
yeah just tested with grub2 and it does work, cool. i'll start shipping just a compressed kernel soon. i think we didn't do it before with arch linux arm because uboot doesnt or at least didnt support kernel decompressing
laine_ has joined #aarch64-laptops
Lucanis0 has joined #aarch64-laptops
Lucanis has quit [Ping timeout: 480 seconds]
laine_ has quit [Remote host closed the connection]
laine_ has joined #aarch64-laptops
laine_ has quit [Remote host closed the connection]
<clover[m]>
OK arch peeps, i pushed linux-x13s-rc with a compressed kernel so be sure to update your bootloader before your next boot and double check it's pointing to the right thing now (vmlinuz-linux)
<clover[m]>
i also commented out this line from /etc/grub/default as it's no longer needed and grub will auto-find your initrd. a nice side effect: