#asahi-dev · 2026-05-15 06:27
nickchanmidr should be printed by normal m1n1 logs#asahi-dev · 2026-05-15 05:49
nickchaniboot or dfu anyways#asahi-dev · 2026-05-15 05:49
nickchanand iboot's usb serial number#asahi-dev · 2026-05-15 05:47
nickchananother place with the chip-revision is the MIDR_EL1 register#asahi-dev · 2026-05-15 05:47
StanfordAppliedCyber[m]if yours is also 0x11 then i need to investigate the hell out of this, because that may be the difference#asahi-dev · 2026-05-15 05:47
StanfordAppliedCyber[m]yuka: can you check what chip revision you have? `ioreg -p IODeviceTree -d 1 -k "chip-revision"`#asahi-dev · 2026-05-15 05:46
StanfordAppliedCyber[m]that's actually very reassuring because it indicates I might not be crazy#asahi-dev · 2026-05-15 05:46
StanfordAppliedCyber[m]one difference, her chip revision is 0x11, mine is 0x10#asahi-dev · 2026-05-15 05:46
StanfordAppliedCyber[m]we're talking right now#asahi-dev · 2026-05-15 05:46
StanfordAppliedCyber[m]firmware version is identical, boot policy settings are identical#asahi-dev · 2026-05-15 05:44
nickchanStanfordAppliedCyber[m]: maybe check firmware version and boot policy settings like ctrr#asahi-dev · 2026-05-15 05:05
StanfordAppliedCyber[m]something is very strange with specifically my machine#asahi-dev · 2026-05-15 05:05
StanfordAppliedCyber[m]chewyeclaire sent me her m1n1 binary and it doesn't successfully start the cores on my machine either-- the exact same image works for her#asahi-dev · 2026-05-14 23:42
StanfordAppliedCyber[m]unfortunate-- does anyone here have a working m1n1 1tr image that gets smp working on the macbook neo? i need to rule out me doing something royally stupid with a known good branch#asahi-dev · 2026-05-14 23:40
fl0_idStanfordAppliedCyber[m] they are probably on their way home / bed#asahi-dev · 2026-05-14 23:34
StanfordAppliedCyber[m]yuka: are you online right now? i could really use your help if so#asahi-dev · 2026-05-14 23:33
StanfordAppliedCyber[m]@ nick i did pass cpus=1, pmgr panics due to cpu topology issues#asahi-dev · 2026-05-14 19:43
fl0_id__when using https://gist.github.com/IntegralPilot/85c355124fe54e670e6d5586c7a07826 I get https://www.pastery.net/ayyaxd/#asahi-dev · 2026-05-14 19:26
fl0_id__mmmh. those noops for m3 unfortunately are not enough for m3 max... :/#asahi-dev · 2026-05-14 19:22
sventhat one#asahi-dev · 2026-05-14 19:22
svenapcieC#asahi-dev · 2026-05-14 19:22
svenbah#asahi-dev · 2026-05-14 19:22
sven*acpcieC#asahi-dev · 2026-05-14 19:22
sventhe tbt controller is usually acpieC fwiw#asahi-dev · 2026-05-14 19:08
yukaso -gp being some new variant is unlikely#asahi-dev · 2026-05-14 19:08
yukafwiw M5 Max has apciege-axi2af-tunables & apcie-axi2af-tunables#asahi-dev · 2026-05-14 19:06
yukaso -ge is the pcie controller that connects over tb?#asahi-dev · 2026-05-14 18:55
chaos_princess*pcie controller that connects over tb#asahi-dev · 2026-05-14 18:55
chaos_princessi guess they included both and gp is the new name of the thunderbolt controller?#asahi-dev · 2026-05-14 18:50
yukabut no apcie-axi2af-tunables#asahi-dev · 2026-05-14 18:50
yukaapcie-gp-axi2af-tunables and apcie-ge-axi2af-tunables are both present in an M3 Max macbook adt#asahi-dev · 2026-05-14 18:49
chaos_princessmac pro has a slightly different pcie controller as it has real pcie ports#asahi-dev · 2026-05-14 18:48
yukadoes anyone know what apcie-gp and apcie-ge mean?#asahi-dev · 2026-05-14 14:47
fl0_id__gonna try later to figure it out with yuka#asahi-dev · 2026-05-14 14:46
fl0_id__also tried macos under hv. it continues to iboot <version> with integralpilots binary patches but then hangs somewhere with iokit#asahi-dev · 2026-05-14 14:46
fl0_id__yay, finally had some time to fix my local setup + have linux booting + basic shell again.#asahi-dev · 2026-05-14 12:41
jannauthe larger mess is "a17 pro == t8130" vs. "a18 pro == t8140" vs. "m4 == T8132"#asahi-dev · 2026-05-14 12:37
jannaudifference between Pro and Max is the GPU die#asahi-dev · 2026-05-14 12:37
jannauI think there is only a single M5 Pro/Max/Ultra CPU die type #asahi-dev · 2026-05-14 12:36
nickchan(even more of a mess!)#asahi-dev · 2026-05-14 12:35
nickchanBut M5 Pro/Max both claims to be T6050#asahi-dev · 2026-05-14 12:35
svencpu_m{0,1,2} is just confusing imho#asahi-dev · 2026-05-14 12:35
nickchanultra is assumed since M5 ultra is not released#asahi-dev · 2026-05-14 12:35
nickchanchadmed: not that fast to run out of islands at least since pro max ultra is _S _C _D now and uses one CPID#asahi-dev · 2026-05-14 12:35
jannauwhile everest / sawtooth, ... are CPU core code names#asahi-dev · 2026-05-14 12:35
svenm1n1 current uses donan ({e,p}-core) code and i'd just add -s core there#asahi-dev · 2026-05-14 12:35
chadmedoh theyre the same as the soc codenames that makes more sense now#asahi-dev · 2026-05-14 12:34
jannauapple uses islands as code names for the SoC since a while: https://asahilinux.org/docs/hw/soc/soc-codenames/#socs#asahi-dev · 2026-05-14 12:34
chadmedsomething like $codename-{e,s,p} would be my preference#asahi-dev · 2026-05-14 12:34
readyee[m]Then cpu_s1 cpu_s2