#asahi-dev · 2024-02-14 01:06
nicolas17welp#asahi-dev · 2024-02-14 00:55
nicolas17I must be putting them in the wrong place ._.#asahi-dev · 2024-02-14 00:55
nicolas17the wiki says "for tethered boot we recommend a kernel with modules disabled (all built-in). You can ignore the Arch Linux initramfs, but you should instead provide an initramfs with /lib/firmware/{brcm/apple} to make sure the built-in modules can find their firmware early"#asahi-dev · 2024-02-14 00:54
nicolas17zzywysm: why does putting them in the initramfs not work though?#asahi-dev · 2024-02-14 00:31
nicolas17it seems /lib/dracut/hooks/{pre-udev/10-load-asahi-firmware.sh,cleanup/99-install-asahi-firmware.sh} expect to find a firmware tarball in EFI#asahi-dev · 2024-02-14 00:30
nicolas17it's failing to load *any* firmware though#asahi-dev · 2024-02-13 23:55
nicolas17"You can ignore the Arch Linux initramfs, but you should instead provide an initramfs with /lib/firmware/{brcm/apple} to make sure the built-in modules can find their firmware early"#asahi-dev · 2024-02-13 23:54
nicolas17and no touchbar or wireless... must be firmware then#asahi-dev · 2024-02-13 23:40
nicolas17hm I have keyboard but not trackpad#asahi-dev · 2024-02-13 23:39
nicolas17so everything is built in and the incompatible modules in the initramfs are ignored#asahi-dev · 2024-02-13 23:39
nicolas17except with kernel modules disabled#asahi-dev · 2024-02-13 23:38
nicolas17I built my own kernel with this https://github.com/AsahiLinux/PKGBUILDs/blob/main/linux-asahi/config#asahi-dev · 2024-02-13 23:38
nicolas17ok you know what does work#asahi-dev · 2024-02-13 23:37
nicolas17PE32+ executable (EFI application) Aarch64 (stripped to external PDB), for MS Windows#asahi-dev · 2024-02-13 23:35
nicolas17gzipping it doesn't help#asahi-dev · 2024-02-13 23:35
nicolas17j`ey: I tried copying /boot/vmlinuz-6.6.3-413.asahi.fc39.aarch64+16k from Fedora Asahi to my other computer and booting that with run_guest_kernel.sh, it throws "ERROR: Devicetree found but no kernel."#asahi-dev · 2024-02-13 18:53
nicolas17no, how did you get it to build :D#asahi-dev · 2024-02-13 05:58
nicolas17okay this is too fragile... I need to figure out how to build my own initramfs from my own built modules#asahi-dev · 2024-02-13 05:09
nicolas17I think I got it, Fedora's EXTRAVERSION and my own didn't match so it couldn't load any modules from the initrd#asahi-dev · 2024-02-13 04:52
nicolas17x86 crossbuild just finished, 165 min XD#asahi-dev · 2024-02-13 04:49
nicolas17okay! I have a serial console via run_guest#asahi-dev · 2024-02-13 04:39
nicolas17ah serial console is only with hv#asahi-dev · 2024-02-13 04:28
nicolas17oh also I get no serial console, USB disconnects as soon as the kernel starts#asahi-dev · 2024-02-13 03:33
nicolas17clones repo and meanwhile watches how his original cross-build is *still going*#asahi-dev · 2024-02-13 03:27
nicolas17where can I find that? I don't know how to fedora :<#asahi-dev · 2024-02-13 03:26
nicolas17in hindsight that's probably not going to have matching versions >_<#asahi-dev · 2024-02-13 03:26
nicolas17so I built my own kernel from the asahi-linux repo... and tried booting it with fedora's initramfs#asahi-dev · 2024-02-13 03:26
nicolas17but the kernel is EFI and I need a plain image#asahi-dev · 2024-02-13 03:26
nicolas17I was just going to use fedora's kernel and initramfs from /boot#asahi-dev · 2024-02-13 03:26
nicolas17...yeahhh I probably have a big version mismatch#asahi-dev · 2024-02-13 03:24
nicolas17wonder if this kernel has nvme as a module... but wouldn't it get the module from the initramfs then?#asahi-dev · 2024-02-13 03:23
nicolas17so it's not a btrfs issue, it's not even finding the block dev#asahi-dev · 2024-02-13 03:23
nicolas17I tried "rootwait root=UUID=15636f9a-6784-410d-8635-e6c9f9d7adf5 rootflags=subvol=root" (which is almost what the normal boot has) and it says it can't find /dev/disk/by-uuid/156...#asahi-dev · 2024-02-13 03:22
nicolas17my original kernel build on the i5 is still going btw, at this point I'm just curious how long it will take :D#asahi-dev · 2024-02-13 03:17
nicolas17maybe *fedora's kernel configuration* doesn't work in this scenario and I should use https://github.com/AsahiLinux/PKGBUILDs/blob/main/linux-asahi/config instead#asahi-dev · 2024-02-13 03:16
nicolas17my cheap crappy USB keyboard has a damaged cable (I get "unable to enumerate USB device" on this x86 laptop and this time I couldn't get it to work by wiggling the cable)#asahi-dev · 2024-02-13 03:11
nicolas17it drops me into "press enter for maintenance shell" but the keyboard doesn't work either#asahi-dev · 2024-02-13 03:11
nicolas17I got the kernel to boot but it can't find the root filesystem#asahi-dev · 2024-02-13 03:09
nicolas17hm, in a normal boot, m1n1 starts u-boot which starts grub which starts linux... here m1n1 directly starts linux, how does that work? I thought uboot and grub did extra initialization that was necessary for linux?#asahi-dev · 2024-02-13 02:47
nicolas17it was missing pahole to process debug info or something#asahi-dev · 2024-02-13 02:45
nicolas17oh wait it effing failed#asahi-dev · 2024-02-13 02:44
nicolas17tpw_rules: while waiting for the build to finish I started it on the M2 too, it finished in 18 minutes and the x86 cross-build is still going; see, that's why it was a mistake :P#asahi-dev · 2024-02-13 02:18
nicolas17wish I could know progress%#asahi-dev · 2024-02-13 02:15
nicolas17i5-8250U vs Apple M2#asahi-dev · 2024-02-13 02:15
nicolas17but I bet gcc would go brrrr much faster on the M2#asahi-dev · 2024-02-13 02:15
nicolas17yes, using a cross compiler#asahi-dev · 2024-02-13 02:14
nicolas17I made the mistake of starting to build it on my x86 laptop#asahi-dev · 2024-02-13 02:13
nicolas17then I need to build my own because the stuff I found in fedora's /boot is an EFI image ^^'#asahi-dev · 2024-02-13 02:13
nicolas17but anyway is linux.py or run_guest.py supposed to work with an EFI image?#asahi-dev · 2024-02-13 02:12
nicolas17also it's chainloading a second m1n1 which I may not need