#asahi-dev · 2026-02-05 21:01
getzok testing that thx#asahi-dev · 2026-02-05 21:01
chaos_princessif they can - the cable is probably ok#asahi-dev · 2026-02-05 21:01
jannau5th random cable or 5th usb3+dp-altmode / thunderbolt cable?#asahi-dev · 2026-02-05 21:00
chaos_princessboot macos on both machines and check if they can talk over thunderbolt#asahi-dev · 2026-02-05 21:00
getzalthough macvdmtool prints: Putting target into serial mode... OK Putting local end into serial mode... OK Exiting DBMa mode... OK#asahi-dev · 2026-02-05 20:59
getzim on my 5th cable now but could be bad luck#asahi-dev · 2026-02-05 20:59
jannauother potential issue is the cable, needs a fully connected cable (specifically connected SBU pins)#asahi-dev · 2026-02-05 20:59
getzneither works, i tried setting M1N1DEVICE=/dev/cu.debug-console#asahi-dev · 2026-02-05 20:58
jannaumacvmdtool readme says to use /dev/cu.debug_console and not /dev/tty.debug-console#asahi-dev · 2026-02-05 20:50
getzyep dfu on both, m1 pro usb-c nearest magsafe and usb-c nearest power on m1 mini#asahi-dev · 2026-02-05 20:37
jannauare you using the correct usb-c port on both devices? rebooting works on any port but the serial is just on the dfu port#asahi-dev · 2026-02-05 20:37
getztime to reboot to new macos kernel without the shim#asahi-dev · 2026-02-05 20:36
getzi got -v and crsutil disable to enable the proxy and that works fine, just no life on the serial port#asahi-dev · 2026-02-05 20:35
jannausee https://asahilinux.org/docs/sw/tethered-boot/#enabling-the-backdoor-proxy-mode#asahi-dev · 2026-02-05 20:35
jannauat least I think so. my devices probably all have "-v" in boot-args and SIP disabled#asahi-dev · 2026-02-05 20:33
getzthe python tools are super fun#asahi-dev · 2026-02-05 20:33
getzalso tried proxyclient with uboot and my own efi payload but got nothing#asahi-dev · 2026-02-05 20:33
getzyep its m1n1 then i tried an openbsd installer but there was nothing on the serial out#asahi-dev · 2026-02-05 20:32
jannaugetz: what are you booting on the target device? if it's m1n1 there should be output at 115200 baud#asahi-dev · 2026-02-05 20:31
jannauthanks. I was remembering that someone said that#asahi-dev · 2026-02-05 20:30
Shizfwiw :p#asahi-dev · 2026-02-05 20:30
ShizI never had to nuke AppleSerialShim on my macOS 26 install#asahi-dev · 2026-02-05 20:28
getznice!#asahi-dev · 2026-02-05 20:28
jannauAppleSerialShim prevents accesing the serial port on the hsot device#asahi-dev · 2026-02-05 20:27
jannauthere might be an easier solution soon#asahi-dev · 2026-02-05 20:26
getzOh Im not supposed to run that on the device under test?#asahi-dev · 2026-02-05 20:26
jannauit applies to the system running macvdmtool and accessing /dev/tty.debug-console on regardlessly of the os the target device is booting#asahi-dev · 2026-02-05 20:24
getzyes but does that apply when booting non macos systems?#asahi-dev · 2026-02-05 20:24
jannaugetz: did you see https://github.com/AsahiLinux/macvdmtool?tab=readme-ov-file#note-about-macos-12#asahi-dev · 2026-02-05 19:58
getzshould i set any boot-args to open the serial port when booting something with m1n1? I'm able to run macvdmtool reboot serial but connecting to /dev/tty.debug-console shows nothing#asahi-dev · 2026-02-05 15:53
jannaukloenk: feel free to send any changes by email to me instead of a githup pr for the downstream kernel. I saw that you already did it for this change#asahi-dev · 2026-02-05 15:48
kloenkwrote with yukain the meantime and found the ml :)#asahi-dev · 2026-02-05 15:47
kloenkjannaunot sure I parse correclty. the first sentence is superseeded by you seeing my mail? :)#asahi-dev · 2026-02-05 15:34
jannaukloenk: feel free to b4 send me changes. I saw the mail#asahi-dev · 2026-02-05 15:05
fl0_idkloenk sure :)#asahi-dev · 2026-02-05 14:24
kloenkno, but thanks. have my b4 setup and all that, favor that over github web ui shit :)#asahi-dev · 2026-02-05 14:23
fl0_idkloenk you might be able to klick edit in github, and then it forks for you automatically. but not sure if that's better for you...#asahi-dev · 2026-02-05 14:20
kloenkjust wish I could do it without forking and then fighting with github :)#asahi-dev · 2026-02-05 14:13
kloenkwill do a gh pr in a bit#asahi-dev · 2026-02-05 14:13
kloenkit's not in upstream. otherwise would just have send it to miguel :)#asahi-dev · 2026-02-05 14:12
fl0_idkloenk for the asahi / asahi-wip tree you can use github, there is no ML. For the upstream tree, it goes throuhg the relevant MLs like normal. You can also first wait for feedback here or on a WIP PR on gh#asahi-dev · 2026-02-05 14:10
kloenkjust discovered that linux asahi-6.18.7-2 does not build without "RUST_FW_LOADER_ABSTRACTIONS". Looks like a copy past error. but also actually using kconfig more complex and I actually did include a shortcut to catch this. what is the prefered way to contibute to the linux tree? gh pr or mail as with other linux trees?#asahi-dev · 2026-02-05 12:09
nickchanin that i just checked the parent's (smc) compatible#asahi-dev · 2026-02-05 12:09
nickchananother similar issue is t8012 having the touchid button event without a corresponding smc key#asahi-dev · 2026-02-05 12:07
nickchanso if i just try to use a new compatible then the macsmc-reboot would either get probed with no node (when not hardcoded in smc mfd) or probed multiple times (when hardcode another compatible alongside the existing one)#asahi-dev · 2026-02-05 12:06
nickchan2. mfd core probes driver even without a matching node#asahi-dev · 2026-02-05 12:05
nickchan1. compatible is hardcoded in mfd core#asahi-dev · 2026-02-05 12:05
nickchannormally for incompatibilites like this it should just be a compatible but:#asahi-dev · 2026-02-05 12:05
nickchanso t8015 uses 'off0' in MBSE to shutdown and doesn't support 'phra'#asahi-dev · 2026-02-04 13:11
mazfor those interested, I've just pushed a CS SW update, moving to a newer SDK, which fixes a break handling issue.