#
#asahi-dev · 2024-02-13 16:30
zzywysmthe next step for my personal Apple Silicon machines is getting the Asahi firmware into CONFIG_EXTRA_FIRMWARE so i can go module-less
#asahi-dev · 2024-02-13 16:28
j`eymakes sense
#asahi-dev · 2024-02-13 16:27
mazj`ey: a better option is to keep building it, but to reclaim the section at boot time. I had patches for that, but it was something like a couple of pages, which wasn't worth the complexity.
#asahi-dev · 2024-02-13 16:27
j`eyzzywysm: I agree if you have some fixed hw for whatever reason, but of course general purpose distros cant do that
#asahi-dev · 2024-02-13 16:25
j`eymaz: yes I was just trying to split it for fun, but it was a case of never-ending errors, so I gave up
#asahi-dev · 2024-02-13 16:23
mazzzywysm: size doesn't matter in that case. I can compile a kernel in a couple of minutes. testing takes hours, multiplied by the number of architectural variants this needs to run on.
#asahi-dev · 2024-02-13 16:23
zzywysmcode that isn't built can't hurt you
#asahi-dev · 2024-02-13 16:22
zzywysmmaz: but by drastically reducing the size of the kernel configuration, you also drastically reduce the size of the exponential tree of testing you need to be doing
#asahi-dev · 2024-02-13 16:21
mazthat's what maintenance means.
#asahi-dev · 2024-02-13 16:21
mazno: the maintenance cost is that an every *patch* you apply, you test *all* the possible combinations.
#asahi-dev · 2024-02-13 16:21
zzywysmmaz: the maintenance cost is basically "every time a new kernel release gets cut, you do a make oldconfig and answer a couple questions"
#asahi-dev · 2024-02-13 16:20
mazzzywysm: sure. but the maintenance cost is way too high, and completely impractical.
#asahi-dev · 2024-02-13 16:19
zzywysmi'm of the philosophy that every kernel configuration option you can turn off is a return-oriented-programming gadget that no longer exists
#asahi-dev · 2024-02-13 16:19
mazI really don't want to have to ever split the two. specially when people use nVHE on 9.x HW.
#asahi-dev · 2024-02-13 16:17
j`eynvhe = arm 8.0 virtualisation, vhe = 8.1+ virtualisation
#asahi-dev · 2024-02-13 16:16
j`ey(a particular mode of KVM, it supports the other mode)
#asahi-dev · 2024-02-13 16:16
zzywysmi'm afraid to disable containers because i suspect NixOS would crap a brick
#asahi-dev · 2024-02-13 16:16
j`eyzzywysm: M1 doesn't support the nvhe mode
#asahi-dev · 2024-02-13 16:16
zzywysmi like KVM, and use a M1 most of the time
#asahi-dev · 2024-02-13 16:16
j`eyI tried to compile a kernel without nvhe KVM.. but that stuff is tangled quite firmly
#asahi-dev · 2024-02-13 16:15
j`eyzzywysm: stuff like enabling the LSE instructions at compile time, removing a bunch of the perf tables that werent for M1
#asahi-dev · 2024-02-13 16:15
j`eyccmp x18, #0, #0xd, pl, does nothing, but encodes to MZ!
#asahi-dev · 2024-02-13 16:14
zzywysmj`ey: what were the nature of the source changes?
#asahi-dev · 2024-02-13 16:14
mazj`ey: by luck!
#asahi-dev · 2024-02-13 16:14
j`eyzzywysm: no sorry just did it locally, I can maybe look at sending you some bits (I dont think it's worth actually doing, was just for fun)
#asahi-dev · 2024-02-13 16:13
j`eythe EFI header is also executable arm64 assembly!
#asahi-dev · 2024-02-13 16:13
j`eynicolas17: also if by EFI image you mean the kernel file.. that should be fine to boot
#asahi-dev · 2024-02-13 16:13
zzywysmj`ey: if you've got a link to those source changes, i'd love to peek
#asahi-dev · 2024-02-13 16:12
j`eyI probably went further than you since I also did source changes!
#asahi-dev · 2024-02-13 16:12
zzywysmin the future, consider trying this instead: https://github.com/AsahiLinux/docs/wiki/Reference-Asahi-kernel-config
#asahi-dev · 2024-02-13 16:12
j`eyzzywysm: not at all, I also spent a long time working on a slim build :P
#asahi-dev · 2024-02-13 16:09
zzywysmnicolas17: everyone looks at me weird when i try to slim down kernel configurations for Apple Silicon, but i suppose a 165 minute build must be thrilling for some
#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:31
tpw_rules(never used dnf either i don't think)
#asahi-dev · 2024-02-13 03:31
tpw_rulesso i'm 95% sure it's the source and what users are actually installing. would be nice to figure out how to query dnf and check
#asahi-dev · 2024-02-13 03:29
tpw_rulesbut copr i think is what builds the .rpms and the latest ver there matches the latest tag in that repo
#asahi-dev · 2024-02-13 03:28
tpw_rulesidk if you can build it like a normal linux tree, i never tried
#asahi-dev · 2024-02-13 03:28
tpw_ruleshttps://copr.fedorainfracloud.org/coprs/g/asahi/kernel/packages/
#asahi-dev · 2024-02-13 03:28
tpw_ruleshttps://gitlab.com/fedora-asahi/kernel-asahi/-/tree/fedora-asahi-6.6
#asahi-dev · 2024-02-13 03:27
tpw_ruleshold on i figured all that out and wrote it down for myself
#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
tpw_ruleswhy not just get the same kernel source
#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

plus ›