#
#asahi-dev · 2026-05-05 07:15
jannauFelix[m]1: generally yes, M3 Pro/Max/Ultra support is behind but I'm planning on bringing it to the same lavel in thext few days
#asahi-dev · 2026-05-05 07:14
jannauthe fedora44 images from the installer are not bootable because m1n1 and u-boot miss m3 support
#asahi-dev · 2026-05-05 07:13
Felix[m]1I guess when people talk about the M3 here, they’re referring only to the base model, which does not include M3 Max?
#asahi-dev · 2026-05-05 07:08
jannauhopefully that will make the wifi firmware hacks obsolete
#asahi-dev · 2026-05-05 07:08
jannauthat is waiting on the final m1n1 1.6.0 release and it needs to switch to 14.8.3 update
#asahi-dev · 2026-05-05 07:06
jannauunifiedgravity[m]: see https://github.com/jannau/asahi-installer/tree/wip-m3-ipsw-14.6.1 for the patched installer
#asahi-dev · 2026-05-05 06:44
unifiedgravity[m]I can patch the installer I guess, cheers
#asahi-dev · 2026-05-05 06:44
unifiedgravity[m]By the way, search Ebay for "Macbook b-grade" you can find Macs with some scratches which don't affect anything but knock the price down a lot, occasionally. I got my Macbook Air 15 M2 16GB/1TB for equivalent of about $786 USD.
#asahi-dev · 2026-05-05 06:43
chaos_princessif you want an install on m3, go manual route or patch the installer
#asahi-dev · 2026-05-05 06:42
chaos_princessno
#asahi-dev · 2026-05-05 06:42
unifiedgravity[m]So if I buy a M3, will the Asahi installer work?
#asahi-dev · 2026-05-05 06:42
unifiedgravity[m]I don't expect it to be pleasant; my understanding of this project is to get the kernel changes mainlined and that Asahi is for development, and then any repo can then support the platform in stable releases.
#asahi-dev · 2026-05-05 06:40
JamesCalligeros[m]I’d describe M3 as “bootable”. Storage, kb, trackpad, usb and display via firmware framebuffer work but it’s not a pleasant daily driving experience
#asahi-dev · 2026-05-05 06:39
unifiedgravity[m]To clarify, the post which was made a few months ago about M3 running. I saw it about a week ago.
#asahi-dev · 2026-05-05 06:37
unifiedgravity[m]I saw something a few months ago about M3 running but the progress pages hadn't been updated to reflect so I guess it's still alpha/WIP but that will be awesome too. I got an M2 Air 15 as a sacrifice target. Will be excited to help with platform drivers for M3-M5 once bring-up is completed. I don't think I am capable of helping for the initial platform bring-up work.
#asahi-dev · 2026-05-05 06:34
unifiedgravity[m]Anyways brew doesn't like my host config so it's compiling llvm from source so I'll have to wait for that so I can build m1n1 and then I will let you know what happens. Cheers
#asahi-dev · 2026-05-05 06:33
unifiedgravity[m]Yeah
#asahi-dev · 2026-05-05 06:33
svenand then lspci is just going to work on linux
#asahi-dev · 2026-05-05 06:33
unifiedgravity[m]Cool, I will see what I can do with it
#asahi-dev · 2026-05-05 06:33
sventhen the pcie driver needs some adjustments to bring up that side of the tunnel
#asahi-dev · 2026-05-05 06:33
unifiedgravity[m]No, it won't, but it will be interesting
#asahi-dev · 2026-05-05 06:33
svenfirst NHI needs to see the connection and bring up the tbt tunnels
#asahi-dev · 2026-05-05 06:33
svenuh, i don't see how visualising will help
#asahi-dev · 2026-05-05 06:32
unifiedgravity[m]Do you have any idea of the feasibility of porting lspci to MacOS? It will be interesting to finally see the whole PCIe layout when Linux can bring up the domains for USB4 PCIe. I have no way of visualising it easily in MacOS. ioreg seems like a blunt mallet
#asahi-dev · 2026-05-05 06:30
NSA_RECON_BOTOh damn, that's impressive, I had no idea there was that branch
#asahi-dev · 2026-05-05 06:29
svenprobably some wrong sequence in atcphy
#asahi-dev · 2026-05-05 06:29
svenhttps://github.com/AsahiLinux/linux/commits/sven/tbt-wip/ that's 95% of tbt bringup, there's "just" some bug in there that prevents the NHI to see the connection
#asahi-dev · 2026-05-05 06:26
unifiedgravity[m]Anyways my practice will be to finish the Linux Presonus 2626 driver first (it is structurally there, but seems to be missing something in the init sequence) but then I will be doing the USB4 host bringup for Asahi.
#asahi-dev · 2026-05-05 06:22
unifiedgravity[m]Ah thanks so I take it that it writes the bin file somewhere it can find it later
#asahi-dev · 2026-05-05 06:22
JamesCalligeros[m]Serve the build from your host and copy it to 1tr with curl or whatever
#asahi-dev · 2026-05-05 06:21
unifiedgravity[m]And besides even if I mounted it, when it booted using that filepath, it wouldn't necessarily be the same path when in the bootloader
#asahi-dev · 2026-05-05 06:20
unifiedgravity[m]kmutil configure-boot \... (full message at <https://matrix.org/oftc/media/v1/media/download/AZxBc9EIxDqJ2uvj_agTrDKVJ14PrpRxWe9Mfx2acdnH3Lmx3VjJkm8A6bY7mz9qaohORwyv8HmjT8zn2UAqk9BCeePuSjQwAG1hdHJpeC5vcmcvWEFGTmVpUU5pVnByUmxNekpmTmVYenh0>)
#asahi-dev · 2026-05-05 06:15
unifiedgravity[m]These things would make it easier.
#asahi-dev · 2026-05-05 06:15
unifiedgravity[m]Yeah, I will propose amendments to the docs, whilst they may be technically sufficient, a heap of notes for instance to note that the "recovery" option in boot options goes to the recovery image of the currently selected default boot disk, that there is a 1tr for every boot option and they are not the same. And to disable Filevault etc etc. A note that the kernel must be uploaded, it cannot boot the one from the partition, etc.
#asahi-dev · 2026-05-05 06:11
unifiedgravity[m]Okay thanks, jumping into the MacOS partition's 1tr, will see
#asahi-dev · 2026-05-05 06:10
JamesCalligeros[m]Do what the documentation says. Replace whatever your container’s boot object currently is with m1n1 and only m1n1. If there is nothing concatenated on the end of m1n1, it will start the proxy and wait for instructions from the host.
#asahi-dev · 2026-05-05 06:10
unifiedgravity[m]I have a couple of iPhone 60W cables somewhere but I can't find them for the life of me.
#asahi-dev · 2026-05-05 06:08
unifiedgravity[m]Waiting for UART device file '/dev/cu.usbmodemP_03' to appear (Ctrl+C to abort)...
#asahi-dev · 2026-05-05 06:08
unifiedgravity[m]$ ./tools/picocom-sec.sh
#asahi-dev · 2026-05-05 06:08
unifiedgravity[m]Hm, I just booted MacOS and it did m1n1 but flew past, never paused for proxy, and this never changed
#asahi-dev · 2026-05-05 06:08
JamesCalligeros[m]Active Thunderbolt/USB4 cables may not work. The stock apple charging cable does though
#asahi-dev · 2026-05-05 06:04
unifiedgravity[m]Does it matter if I use a C-C 2.0 cable, USB4 cable or a USB-C to USB-A to USB-C with target as peripheral/downstream
#asahi-dev · 2026-05-05 05:59
unifiedgravity[m]But I just can't get the USB serial device to appear on the host machine from the target machine
#asahi-dev · 2026-05-05 05:58
unifiedgravity[m]Okay I'll try to understand it. If I sort it out then I will amend the documentation to make it clearer in ways that would have helped me and you can consider updating the docs if my edits make sense.
#asahi-dev · 2026-05-05 05:58
JamesCalligeros[m]The host machine uploads the kernel and tells the DUT to jump to it
#asahi-dev · 2026-05-05 05:57
JamesCalligeros[m]You cannot just magically have the DUT chainload a kernel and automatically connect to the host machine
#asahi-dev · 2026-05-05 05:57
JamesCalligeros[m]Yes. You need to do it the way the documentation says. There is literally no other way to do it
#asahi-dev · 2026-05-05 05:57
unifiedgravity[m]No, I am not interested in uploading kernels. I just want m1n1 to enter proxy, boot the kernel that came with the MacOS installation. Am I trying to do something that does not make sense here?
#asahi-dev · 2026-05-05 05:55
JamesCalligeros[m]Did you extract the kernelcache to upload to the DUT using the proxyclientv
#asahi-dev · 2026-05-05 05:54
JamesCalligeros[m]Did you replace the macos kernel of the container youre trying to virtualise with m1n1?

plus ›