#
#asahi-dev · 2026-06-12 05:01
JamesCalligeros[m]concatenating a kernelcache is also kind of useless since that will just jump to the binary. you can only start the hypervisor properly by using run_guest
#asahi-dev · 2026-06-12 05:00
JamesCalligeros[m]read the user guide again, you need to do some img4 format stuff to get a bootable mach-o binary out of it
#asahi-dev · 2026-06-12 04:55
unifiedgravity[m]I concatenated the dev.kernel.macho.development or whatever it's called to the m1n1.bin and nothing changed
#asahi-dev · 2026-06-12 04:55
unifiedgravity[m]It says Unknown payload at 0x803528000 (magic: cffaedfe) before saying "Running proxy..."
#asahi-dev · 2026-06-12 04:54
unifiedgravity[m]Can't upload the kernelcache from host machine if it hangs at "Running proxy..." and does not respond to the chainloader or run_guest from the host.
#asahi-dev · 2026-06-12 04:48
JamesCalligeros[m]did you read the m1n1 user guide
#asahi-dev · 2026-06-12 04:48
JamesCalligeros[m]youre supposed to upload the kernelcache from a host machine...
#asahi-dev · 2026-06-12 04:38
unifiedgravity[m]Even without proxy cable attached it hangs here at "Running proxy..." and does not boot up MacOS either way
#asahi-dev · 2026-06-12 04:37
unifiedgravity[m]Although it says "Running in EL2". I think this is the same as the Asahi partition
#asahi-dev · 2026-06-12 04:36
unifiedgravity[m]Great, MacOS has m1n1 but it hangs at "Running proxy..." unlike the Asahi partition m1n1 which doesn't hang here. Any ideas?
#asahi-dev · 2026-06-12 04:27
JamesCalligeros[m]the macos kernelcache expects the "booted volume" to match what it expects. if it's different it will panic early
#asahi-dev · 2026-06-12 04:26
JamesCalligeros[m]the correct way to run any version of macos under the m1n1 hv is to install the version youre after into a partition, then replace its kernel with m1n1. you cannot do it any other way.
#asahi-dev · 2026-06-12 04:22
StanfordAppliedCyber[m]like, install macos into some volume, build m1n1, transfer the m1n1 boot object to the volume you want to install m1n1 on, reboot into 1tr and set that that as the default boot volume, reboot into 1TR again, install the image (i think you need to 1TR twice due to the pairing thing)
#asahi-dev · 2026-06-12 04:20
StanfordAppliedCyber[m]just go through 1TR and flash your own m1n1 image
#asahi-dev · 2026-06-12 04:20
StanfordAppliedCyber[m]idk how the installer works but my guess is it's meant for regular users not devs
#asahi-dev · 2026-06-12 04:20
unifiedgravity[m]Thanks. But how to "stick m1n1 on that"? The Asahi installer offers no option of installing m1n1 even in advanced mode.
#asahi-dev · 2026-06-12 04:19
StanfordAppliedCyber[m]disclaimer: i've never done this before, i only have experience on my super weird macbook neo setup
#asahi-dev · 2026-06-12 04:19
StanfordAppliedCyber[m]not the asahi partition, make a new volume and do a vanilla macos install, downgrade the security, stick m1n1 on that, then stream the kernelcache
#asahi-dev · 2026-06-12 04:04
unifiedgravity[m]Anyways super excited, I will be finishing the Linux Presonus 2626 driver and then hopefully finishing USB4 bring-up for Asahi, if Sven hasn't already done the last 5% since we last spoke.
#asahi-dev · 2026-06-12 04:01
unifiedgravity[m]Just to clarify, is m1n1 fully supported in M2? I have t8112, not t8101
#asahi-dev · 2026-06-12 03:58
unifiedgravity[m]Hi all, I have been trying to get MacOS 13.5 running under m1n1. Is it correct that I boot the Asahi partition, connect the proxy, and then upload the development kernel? Because from the logs, it appears to try to mount the Linux partition as root, rather than the MacOS one. But the m1n1 which runs when I select "Macintosh HD" does not wait for proxy, despite having boot-args as -v and csrutil disabled. Cheers :)
#asahi-dev · 2026-06-12 00:06
StanfordAppliedCyber[m]but i'm so close i can taste it
#asahi-dev · 2026-06-12 00:06
StanfordAppliedCyber[m]driverkit is currently dying, apparently some ringbuffer isn't being populated by the firmware?
#asahi-dev · 2026-06-12 00:05
StanfordAppliedCyber[m]but it will soon
#asahi-dev · 2026-06-12 00:05
hardy94does exists also multiple wifi Chips on the neo ?
#asahi-dev · 2026-06-12 00:05
StanfordAppliedCyber[m]macos doesn't boot yet either :)
#asahi-dev · 2026-06-12 00:05
hardy94StanfordAppliedCyber[m]: ioreg gives you the full information too
#asahi-dev · 2026-06-11 23:27
StanfordAppliedCyber[m]ah, i've never booted linux on this so i can't exactly run that command
#asahi-dev · 2026-06-11 23:24
yukalspci I think?
#asahi-dev · 2026-06-11 23:23
StanfordAppliedCyber[m]yeah i have no clue where you got that number from, i can't find it anywhere
#asahi-dev · 2026-06-11 23:18
StanfordAppliedCyber[m]yuka: where did you get 7935 from
#asahi-dev · 2026-06-11 22:33
StanfordAppliedCyber[m]i mean i figured that was implied
#asahi-dev · 2026-06-11 22:33
StanfordAppliedCyber[m]oh ofc
#asahi-dev · 2026-06-11 22:32
chaos_princessnon-zero chance that neo has an apple-flavoured one with a custom firmware load mechanism or something. But may be just a standard one
#asahi-dev · 2026-06-11 22:31
StanfordAppliedCyber[m]no datasheet ofc
#asahi-dev · 2026-06-11 22:31
StanfordAppliedCyber[m]apparently mt7922 is supported upstream already
#asahi-dev · 2026-06-11 22:07
StanfordAppliedCyber[m]158.685962 mt7922SecProtectFWDL: SEC boot semaphore get success
#asahi-dev · 2026-06-11 22:06
yukaI thought it was 7935
#asahi-dev · 2026-06-11 22:06
yukaWhere did you get mt7922?
#asahi-dev · 2026-06-11 22:04
StanfordAppliedCyber[m]AppleSunriseWLAN
#asahi-dev · 2026-06-11 22:04
StanfordAppliedCyber[m]but i'm not trying to just make it to boot with half the functionality missing
#asahi-dev · 2026-06-11 22:04
StanfordAppliedCyber[m]it's a dext actually
#asahi-dev · 2026-06-11 22:03
chaos_princessyank out the kext?
#asahi-dev · 2026-06-11 22:03
StanfordAppliedCyber[m]it is currently very unhappy and this is blocking boot :(
#asahi-dev · 2026-06-11 22:03
StanfordAppliedCyber[m]macbook neo uses the MT7922 wifi chip
#asahi-dev · 2026-06-11 22:02
chaos_princessbut this will allow you to for example run arm windows with hyperv enabled
#asahi-dev · 2026-06-11 22:01
chaos_princessyuka: nah, it is completely irrelevant, you need a full fat macos with running alongside you, as arm64 nv needs a non-insignificant amount of support code
#asahi-dev · 2026-06-11 22:00
chaos_princessopposite, they only exposed nvhe nv on 26 and lower
#asahi-dev · 2026-06-11 22:00
StanfordAppliedCyber[m]like turning vhe off?
#asahi-dev · 2026-06-11 21:59
yukaDoes that make it more realistic to run linux as a 'guest' in sptm and then still support virtualisation?

plus ›