marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | "Does XXX work yet?": https://alx.sh/fs | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-alt #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
<matteo>
can I boot a live from an usb drive?
cassepipe has joined #asahi
<cassepipe>
Damn that mastodon thread was epic
<cassepipe>
debugging the debugger is something I wish to be able to do one day. Congrats.
matteo has quit [Remote host closed the connection]
mini0n has quit [Read error: Connection reset by peer]
<bluetail>
as I found fedora to be less problematic on my machines, I slowly start to think I want fedora on my m1 mac too. But iirc GNOME isnt running properly yet, right?
Guest7549 has quit [Quit: G-line: User has been permanently banned from this network.]
vx has joined #asahi
vx is now known as Guest7642
barrett has quit [Ping timeout: 480 seconds]
mxz has quit [Quit: cya]
mxz has joined #asahi
marvin24 has joined #asahi
marvin24_ has quit [Ping timeout: 480 seconds]
blacktop has joined #asahi
blacktop has quit [Quit: leaving]
jamespmo_ has joined #asahi
jamespmorgan has quit [Ping timeout: 480 seconds]
skipwich_ has joined #asahi
skipwich has quit [Read error: Connection reset by peer]
gladiac has joined #asahi
chip_x has quit [Ping timeout: 480 seconds]
possiblemeatball has quit [Quit: Quit]
Guest7642 has quit [Quit: G-line: User has been permanently banned from this network.]
vx has joined #asahi
vx is now known as Guest7650
Zopolis4 has quit []
Guest7650 has quit [Quit: G-line: User has been permanently banned from this network.]
Raito_Bezarius has quit [Read error: Connection reset by peer]
Raito_Bezarius has joined #asahi
<Retr0id>
I'm getting ready to DFU-restore my macbook to start fresh. Is there anything in particular I should bear in mind when setting it up again? (the plan is to keep a small-but-functional macos install hanging around, with the rest of the drive filled with asahi) I have the annoying feeling that I'm forgetting something important...
<waldi>
you need enough space for the macos to upgrade itself. you need to keep the extra recovery partition
<ChaosPrincess>
log out of apple id, and disable find my mac
<Retr0id>
oh damn that could be an issue - the reason I'm DFU-ing in the first place is because the macos install is bricked (it hangs at login, even after a reinstall from recovery)
<Retr0id>
If find-my-mac is already disabled I should be ok having apple id logged in, right? (I'll double check that from my icloud account)
MajorBiscuit has joined #asahi
<ChaosPrincess>
as long as you know the apple id password, it _should_ be fine
nyilas has quit [Remote host closed the connection]
Major_Biscuit has quit [Ping timeout: 480 seconds]
nyilas has joined #asahi
veeyee has joined #asahi
Cromulent has quit [Quit: Connection closed for inactivity]
matteo has joined #asahi
<matteo>
hi all
<j`ey_>
hi
nsklaus has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<matteo>
I still didn't solve my keyboard issues
<matteo>
macbook 16 with m1 pro here
<j`ey_>
matteo: this is the fedora built kernel right? not your own
<matteo>
fedora kernel, right
<matteo>
but the problem also happens in uboot and grub
<matteo>
I can't stop uboot
<matteo>
or boot an older kernel in grub
<matteo>
I guess that I have to recover it somehow via an USB live
<mps>
matteo: ask on #asahi-alt, channel for alternate asashi distros
<matteo>
ok
leif has joined #asahi
Zopolis4 has quit []
guillaume_g has quit [Remote host closed the connection]
guillaume_g has joined #asahi
leif has quit [Quit: Leaving]
<Retr0id>
I survived a DFU restore, and I'm back in asahi. Before I restored, I made a dd backup of my asahi rootfs from within the intramfs environment (using init=/bin/sh). However, I'm not able to restore that backup yet - usb devices no longer enumerate from within the initramfs and I'm not sure why (nothing happens in dmesg when I plug something in).
<Retr0id>
`mkinitcpio -P` warns that there's "possibly missing firmware for module xhci_pci" but I think maybe that's normal? Anyone know what the issue might be? (once booted normally, everything is fully functional including usb-c) (this is all on an M1 Pro 14" mbp)
<Retr0id>
my backup lives on an ext4 drive so it'll be non-trivial to restore from macos although I might be able to bodge something...
<raph_ael>
arch often throws missing firmware at mkinitcpio
<jannau>
firmware handling is special in asahi linux, should be available and is not needed for usb-c
<steffen[m]>
you can mount drives and usb from macos qemu but that's also a bit painful
<Retr0id>
I'm currently doing `nc | dd` under macos, it's working at least (fingers crossed)
<jannau>
Retr0id: my best guess is missing moduels in the initramfs. can you check with lsmod from the initramfs env or lsinitrd?
<jannau>
I can reproduce it and the problem is that xhci-plat-hcd is not loaded, uas is missing as well
<jannau>
after loading both modules manually I have the usb storage is available
<Retr0id>
I have uas added already btw. weirdly I don't remember having to load xhci-plat-hcd the first time around when I made the backup, but maybe something else was auto-loading it somehow. I'll try again in ~10 mins once my nc|dd command finishes
<tpw_rules>
the set of modules needed for usb changed at some point
<tpw_rules>
perhaps your backup or memory was before then
darkapex has joined #asahi
darkapex1 has quit [Ping timeout: 480 seconds]
darkapex1 has joined #asahi
barrett has joined #asahi
<Retr0id>
how does bootaa64.efi get told which UUID to look for, and is there a convenient way to reconfigure that beyond hexediting?
barrett has quit [Remote host closed the connection]
darkapex has quit [Ping timeout: 480 seconds]
<tpw_rules>
that depends entirely on what bootaa64.efi is
leif has joined #asahi
<tpw_rules>
if it's grub, then in grub.cfg on that disk iirc
leif has quit []
leif has joined #asahi
Bey0ndB1nary has joined #asahi
<Retr0id>
seems like I've created a nice chicken and egg problem for myself by not keeping the EFI partition from my previous install lol
leif has quit []
darkapex1 has quit []
leif has joined #asahi
leif has quit []
darkapex has joined #asahi
<steffen[m]>
if you still get into the initramfs you can mount your root somewhere and do chroot + update-grub
<jannau>
bootaa64.efi doesn't care about the efi partition but about the root partition. grub-install/update-grub handles that
<jannau>
I would guess grub fails already
j`ey_ is now known as j`ey
<jannau>
Retr0id: you can boot the kernel/initramfs directly from u-boot