ChanServ changed the topic of #asahi-alt to: Asahi Linux: porting Linux to Apple Silicon macs | User-contributed/unofficial distribution ports | Logs: https://alx.sh/l/asahi-alt
zzUzz has joined #asahi-alt
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #asahi-alt
opticron has quit [Remote host closed the connection]
chrisl has quit [Ping timeout: 480 seconds]
opticron has joined #asahi-alt
ipatch has joined #asahi-alt
vimproved has quit [Remote host closed the connection]
vimproved has joined #asahi-alt
chrisl has joined #asahi-alt
zerdox has joined #asahi-alt
chrisl has quit [Ping timeout: 480 seconds]
<zzUzz>
Hey yall --- I'm trying to install void on my m1 air. I think my question pertains to installing any os through the UEFI environment only though. Im stuck on https://docs.voidlinux.org/installation/guides/chroot.html#create-a-new-root-and-mount-filesystems ...How do I mount the boot partition before I chroot in? Do I need to update GRUB? I've heard GRUB cannot boot BTRFS systems... how does asahi fedora do it?
chrisl has joined #asahi-alt
HitokiriKincho has joined #asahi-alt
chrisl has quit [Ping timeout: 480 seconds]
<Calandracas>
you're probably going to need to mount ESP to /boot
<Calandracas>
mkdir /mnt/boot
<Calandracas>
mount /dev/nvme0nWhateverPartitionESPisOn /mnt/boot
<Calandracas>
but there's nothing asahi specific about any of that
<Calandracas>
m1n1 will execute whatever is at $ESP/EFI/BOOT/BOOTAA64.EFI
<Calandracas>
erm well uboot will execute that, not m1n1
<Calandracas>
which can be any EFI executable; grub, UKI, etc.
<Calandracas>
I use systemd-boot, and it works well for me
<zzUzz>
Not AFK, just working through it again. I think that (mount /dev/whatever on /mnt/boot) is one of the things that I did my first go around which was a f*stercl*ck. I'll isolate it though now
<zzUzz>
systemd-boot?? for void??
<Calandracas>
systemd-boot is an EFI executable, and really has nothing to do with the rest of systemd
<Calandracas>
that being said, alot of us (void users) have no problems with systemd beyond upstream refusing to support musl
<Calandracas>
i actually ran a hacked up void asahi musl systemd system until it was time to test void's RC images
<abby>
systemd-boot is just gummiboot but maintained
tobhe has joined #asahi-alt
<zzUzz>
I knew that about gummiboot bc I used it before it was renamed
<zzUzz>
I had heard of void before I heard of musl xD
<Calandracas>
if you do choose to mount ESP to /boot, you do need to change in /etc/default/m1n1-kernel-hook : M1N1_T=/boot/m1n1
* Calandracas
wonders if the systemd-boot 16k page size bug has been fixed yet
tobhe_ has quit [Ping timeout: 480 seconds]
sudtho has quit [Ping timeout: 480 seconds]
nightbreak has joined #asahi-alt
sudtho has joined #asahi-alt
<zzUzz>
I'm at the grub-install section now. Started off with `mount /dev/nvme0n1p4 (or whatever) /mnt/boot/efi/` ....now /boot/efi/ contains asahi, m1n1, and vendorfw.... /etc/default/m1n1-kernel-hook has PAYLOAD=uboot, and M1N1_T=/boot/efi/m1n1.......
<zzUzz>
I'm tempted to run ```grub-install --target=arm64-efi --efi-directory=/boot/efi --removable --bootloader-id="void"```
sudtho has quit [Ping timeout: 480 seconds]
<abby>
can't hurt
chrisl has joined #asahi-alt
n3ph_ has quit [Remote host closed the connection]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #asahi-alt
zerdox has quit [Remote host closed the connection]
sudtho has joined #asahi-alt
zerdox has joined #asahi-alt
chrisl has quit [Ping timeout: 480 seconds]
HitokiriKincho has quit [Remote host closed the connection]