#asahi-dev · 2026-10-08 23:26
Hel3ziOnce m1n1 boots and shows 'Proxy running' on screen, it initializes its own USB stack (t8110 DART) and enumerates on Linux as a standard CDC-ACM device #asahi-dev · 2026-10-08 23:24
Hel3zijdrago: Just a regular USB-C cable. Connected it to the rear-left port (closest to MagSafe/screen). #asahi-dev · 2026-10-08 19:37
Hel3ziThank you so much, you're amazing! Pulling the branch to test on mine now <3#asahi-dev · 2026-10-08 19:31
Hel3ziCan you share the branch / commit link for the rebased old driver?#asahi-dev · 2026-10-08 19:30
Hel3ziNice!#asahi-dev · 2026-10-08 18:01
Hel3ziNice! What’s on the plan for today? Let me know if you need anything tested on mine in parallel#asahi-dev · 2026-10-08 17:21
Hel3ziyuka: Hey yuka, did you get the M4 Pro MacBook?#asahi-dev · 2026-10-07 13:27
Hel3ziyuka: Ah damn, got it, that sucks :( Thanks for explaining though!#asahi-dev · 2026-10-07 13:19
Hel3ziAh lol, that explains it! Is the USB setup on M4 Pro much different from base M4, or could the nodes be ported over?#asahi-dev · 2026-10-07 13:14
Hel3ziyuka: hit that same dead USB port on my M4 Pro. What was the typo in DT? Can test the fix right away.#asahi-dev · 2026-10-06 15:43
Hel3zireally?! It feels like a scam#asahi-dev · 2026-10-06 15:27
Hel3ziWow, they're already running it on the M5...#asahi-dev · 2026-10-06 15:12
Hel3ziGot it! I'll be around and ready to test then. Thanks and see you on Thursday!#asahi-dev · 2026-10-06 15:10
Hel3ziThen we'll have to get a lot done :) Do you know roughly around what time (and timezone) that'll be?#asahi-dev · 2026-10-06 15:08
Hel3ziyuka: Oh nice, will it be an M4 Pro MacBook? For how long will you have it?#asahi-dev · 2026-10-06 15:02
Hel3ziThat'd be great :) I'll need to test it afterwards, right?#asahi-dev · 2026-10-06 14:29
Hel3ziUnfortunately, I haven't managed to get the keyboard working yet :(#asahi-dev · 2026-10-06 12:09
Hel3ziyuka: hey! Getting the internal keyboard to work on M4 Pro takes quite a bit of sweat, doesn't it? I got dockchannel-hid initialized on t6040, but STM/AFE looks like it's held in reset via SMC. Did you manage to bring up topcase on M4 yet?#asahi-dev · 2026-10-05 17:35
Hel3ziupd: cat /proc/cpuinfo | grep processor processor : 0 processor : 1 processor : 2 processor : 3 processor : 4 ~ ##asahi-dev · 2026-10-05 17:15
Hel3zicat /proc/cpuinfo | grep processor processor : 0 processor : 1 processor : 2 processor : 3#asahi-dev · 2026-10-05 17:14
Hel3ziyuka: Further confirmation on M4 Pro: -C 4,5,6,7 brings up all 4 P-cores cleanly!#asahi-dev · 2026-10-05 17:03
Hel3ziUptime 12+ min#asahi-dev · 2026-10-05 16:52
Hel3ziyuka: NVMe is fully working on M4 Pro! Rebuilt with built-in RTKIT/NVME_APPLE/SART, partitions are visible and benchmark passed cleanly: code Text ~ # fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 1954210120 sectors, 2785M Number Start (sector) End (sector) Size Name 1 6 128005 500M iBootSystemContainer 2 128006 242965550 926G Container 3 242965551 244276259 5119M RecoveryOSContainer #asahi-dev · 2026-10-05 12:24
Hel3ziNothing from the actual NVMe driver in dmesg, only PMGR power state lines: [ 11.502775] apple-pmgr-pwrstate ... sync_state() pending due to 44dcc0000.nvme [ 11.504760] apple-pmgr-pwrstate ... sync_state() pending due to 40dc50000.sart So Yuka is likely right - CONFIG_NVME_APPLE is probably =m in defconfig, and no modules are loaded in this bare initramfs.#asahi-dev · 2026-10-05 12:15
Hel3ziUpd: uptime 00:18:48 up 18 min, 0 users, load average: 0.00, 0.00, 0.00 ~ ##asahi-dev · 2026-10-05 12:15
Hel3ziyuka: No /dev/nvme* (No such file or directory), but uptime is beyond 10 minutes without any crash: 00:10:24 up 10 min, load average: 0.00, 0.00, 0.00 (Keep in mind pcie_init is stubbed out in m1n1).#asahi-dev · 2026-10-05 12:14
Hel3ziHaha, oh no, what have I gotten myself into :D There's no turning back now! Thanks a lot for guiding me through all of this, it was an awesome experience!#asahi-dev · 2026-10-05 12:03
Hel3ziyuka:Keyboard backlight is physically ON! echo 255 > /sys/class/leds/kbd_backlight/brightnesssuccessfully lit up the keyboard on the 14" M4 Pro! The internal display (simpledrm) is also working perfectly with the framebuffer console. Both test requests are complete! (Caps Lock indicator isn't working yet as expected without dockchannel-hid).#asahi-dev · 2026-10-05 11:54
Hel3zi@sven @yuka: Makes sense! With -C 1 I was able to get all the way to an interactive Alpine rootfs shell (/bin/sh). Just recompiled the kernel with DRM_SIMPLEDRM=y and PWM_APPLE=y built-in, testing if the framebuffer console and keyboard backlight come up now.#asahi-dev · 2026-10-05 11:31
Hel3zi26.6.2 #asahi-dev · 2026-10-05 11:28
Hel3ziyuka: To get it booting, the key changes were: 1. Stubbed out dapf and pcie_init in m1n1. 2. Used run_guest.py -C 1 (without -C 1, secondary CPU bringup crashes the hypervisor). 3. Fixed KeyError: 4 in hv/__init__.py for self.sysreg (boot CPU is cpu4). With that, the kernel boots cleanly all the way to VFS panic! code Text [ 0.670571] leds_pwm led-controller: CLIDR_EL1.LoC == 0, treating as coherent [ 0.674128] apple-pmgr-pwrstate ... PS dispext2_sys#asahi-dev · 2026-10-05 11:07
Hel3ziyuka: Using run_guest.py -C 1, the kernel successfully boots on the M4 Pro! Log via ttyACM1: code Text [ 0.000000] Booting Linux on physical CPU 0x0000010100 [0x611f0551] [ 0.000000] Machine model: Apple MacBook Pro (14-inch, M4 Pro, 2024) [ 0.000000] earlycon: s5l0 MMIO32:0x0000000429200000 (options '') [ 0.012056] smp: Brought up 1 node, 1 CPU [ 0.013396] CPU: All CPU(s) started at EL1 [ 0.040109] Memory: 22762848K/2304#asahi-dev · 2026-10-05 10:35
Hel3ziYes, m4 pro#asahi-dev · 2026-10-05 10:35
Hel3ziHangs on the Asahi logo (from m1n1, not Apple logo). Using linux.py (with -b "earlycon console=tty0 loglevel=7"). Regarding pcie_init: before I stubbed it out, m1n1 hung right at pcie: No common tunab... and stopped responding there.#asahi-dev · 2026-10-05 10:31
Hel3ziyuka: stubbed out dapf and pcie_init in m1n1. Now m1n1 cleanly reaches Preparing to boot kernel at 0x1... and jumps. After that, USB proxy disconnects as expected and the kernel hangs on the logo#asahi-dev · 2026-10-05 09:56
Hel3ziyuka: Quick update: I flashed the patched m1n1 directly to the SSD via kmutil configure-boot in 1TR to bypass chainload. Disabling DAPF worked - no more SError, and the Mac doesn't reboot anymore! It now progresses further and hangs at pcie: Initializing t6040 PCIe controller (right around No common tunables).#asahi-dev · 2026-10-05 00:03
Hel3ziyuka: Thanks a lot! No second Mac unfortunately, but the build setup is all set up. Let me know whenever you need more tests on the M4 Pro :)#asahi-dev · 2026-10-04 23:13
Hel3ziI guess there's not much else I can help with for now? Did I even help at all though, feels like I just took up your time haha#asahi-dev · 2026-10-04 23:07
Hel3ziJust a regular USB-C cable between the Mac and the PC (I get /dev/ttyACM0 and /dev/ttyACM1 when m1n1 is booted). No dedicated hardware serial cable.#asahi-dev · 2026-10-04 23:03
Hel3ziI tried chainload.py -r build/m1n1.bin. It connects after the stub, but then immediately reboots with UartTimeout. I'm currently on AsahiLinux/m1n1 main branch. Which repo and branch should I use?#asahi-dev · 2026-10-04 22:55
Hel3ziI'm chainloading build/m1n1.macho, not Linux. But in chainload.py I had to skip setting secondary CPU RVBARs because writing to cpu5 [0x211150000] caused an SError. With that skipped, it loads into the stub, says "Connected", but then immediately times out on iface.nop() and the Mac reboots.#asahi-dev · 2026-10-04 22:51
Hel3ziyuka: applied your dapf.c patch and built m1n1. When using chainload.py, it reconnects (Connected), but then Mac immediately reboots (UartTimeout on iface.nop). Does chainload work on t6040, or should I update m1n1 on disk / use hypervisor?#asahi-dev · 2026-10-04 22:29
Hel3zitry it#asahi-dev · 2026-10-04 22:22
Hel3ziyuka: tested your kernel on t6040 (j614s). It didn't reach Linux, got SError in m1n1 at EL2 right after dapf: Initialized /arm-io/dart-mtp. TTY> Exception: SError TTY> Exception taken from EL2h TTY> MPIDR: 0x80010100#asahi-dev · 2026-10-04 21:37
Hel3ziPage size (16KB)?#asahi-dev · 2026-10-04 21:32
Hel3ziokey#asahi-dev · 2026-10-04 21:00
Hel3zim1n1 booted on m4 pro! internal display framebuffer works and the asahi logo showed up, currently sitting at "Running proxy..”#asahi-dev · 2026-10-04 18:17
Hel3zifetching the 26.6.2 installer right now, will have the test volume ready shortly#asahi-dev · 2026-10-04 17:37
Hel3ziabsolutely, i'd be glad to contribute even in a small way! going to read through everything now and get m1n1 up and running. thanks yuka!#asahi-dev · 2026-10-04 17:31
Hel3zimacbook