#
✕ nick:devdrago
#asahi-dev · 2026-10-02 23:45
devdragoanyone know where i might be able to find more info on debugusb? Is it supposed to be a non-serial alternative to serial mode in macvdmtool? I seem to be able to create a connection to m1n1 via debugusb but not via serial
#asahi-dev · 2026-10-01 20:59
devdragoupgraded target volume to 26 as sven suggested, bootloop is gone! still no connection via picocom-sec.sh on my host device, so i'll probably have to wait until i can do dcuart with another mac to confirm, but thank you all so much!
#asahi-dev · 2026-09-30 23:51
devdrago(so unfortunately not yet)
#asahi-dev · 2026-09-30 23:51
devdragoI'm currently looking for someone else with an M-series mac who's willing to run macvdmtool for a dcuart
#asahi-dev · 2026-09-30 23:50
devdragoMacbook Pro Mac16,7 J616s, SoC T6040, board ID 0x6, target volume is based on Sequoia ("OS Version 24.7.830) but my system firmware is Golden Gate-era (wasn't sure what was & wasn't needed so sorry for unnecessary info)
#asahi-dev · 2026-09-30 22:47
devdragoi also tried setting early_proxy_timeout to 8 seconds just out of curiosity, still bootloops in less than 4 so no change... im not seeing anything at all on dmesg -w on the host device so i assume m1n1 isnt even getting as far as initializing usb
#asahi-dev · 2026-09-30 22:45
devdragojust tried again from the most recent commit with the new mBoot versions, still nothing
#asahi-dev · 2026-09-30 07:57
devdragoi also just had a duh-doy moment bc i just remembered i recently upgraded my main macOS install to 27.0... it was doing the boot loop before when i was on 26.x, but i assume my system firmware being on 27.x-era firmware will probably be bad for debugging regardless, is that correct
#asahi-dev · 2026-09-30 07:55
devdragojust tried again with NO_DISPLAY and BRINGUP enabled (neither of which i had before), still bootlooping, probably <4 seconds between the apple icon displaying and the screen going black again
#asahi-dev · 2026-09-30 07:03
devdragoatm? Or is this a known / previously encountered error?
#asahi-dev · 2026-09-30 07:03
devdragoHello, on my M4 Pro MBP (T6040, J616sAP) I'm having trouble booting into m1n1 in proxy mode. I installed manually using `kmutil configure-boot` which I assume is the only way right now, m1n1 was built from the most recent commit, and I've double checked that I'm installing from 1TR on the correct volume; however it just bootloops. Is there an alternative boot flow for T604x SOCs
#asahi-dev · 2026-09-03 20:24
devdragoHi, I have an M4 Pro Macbook, and I saw that the latest commit of m1n1 now includes support for the T6040 series SoCs; I had three questions: