#asahi-dev · 2026-01-25 00:45
fl0_id__not all of those changes might be necessary, but in earlier attempts cpufreq for example was necessary. not sure if asahi-wip or device tree might mean it works without those changes, will test tomorrow probably#asahi-dev · 2026-01-25 00:44
fl0_id__I compiled the current device tree and other changes I have here: https://gist.github.com/step21/7433ac5471d0eb8f67308fc6deca9202#asahi-dev · 2026-01-25 00:32
fl0_id__up to initramfs shell#asahi-dev · 2026-01-25 00:32
fl0_id__baremetal booting works too, just no serial :/#asahi-dev · 2026-01-25 00:29
fl0_id__(and i had specified init=/init option)#asahi-dev · 2026-01-25 00:27
fl0_id__now ideally I just need glasses or a bigger font lol#asahi-dev · 2026-01-25 00:27
fl0_id__yay i have a shell :) turns out it somehow didn't like the /init, but just specifyig alpine /sbin/init worked#asahi-dev · 2026-01-25 00:24
fl0_id__(and baremetal)#asahi-dev · 2026-01-25 00:24
fl0_id__maybe once serial is working, this can be submitted as a minimal device tree#asahi-dev · 2026-01-25 00:07
fl0_id__smp: Brought up 1 node, 16 CPUs [ 0.044822] SMP: Total of 16 processors activated.#asahi-dev · 2026-01-25 00:05
fl0_id__https://www.pastery.net/kjqmsd/#asahi-dev · 2026-01-25 00:04
fl0_id__well at least smp seems to come up, even if init is not working...#asahi-dev · 2026-01-24 20:11
fl0_id__jannau, thx. still fails but a bit later maybe. does the compression matter? I used gz#asahi-dev · 2026-01-24 19:35
fl0_id__integralpilot - can you maybe share your minimal init script? I packaged the alpine minimal archive + init script, but it panics, "attempted to kill init" I just mounted proc, dev, sysfs and pts and then did exec /bin/sh#asahi-dev · 2026-01-24 12:13
fl0_id__thanks!#asahi-dev · 2026-01-24 12:13
fl0_id__jannau, yeah, i also just remebered how it is supposed to work... #asahi-dev · 2026-01-24 12:11
fl0_id__integralpilot, right. just would be nice to know i can use it if needed#asahi-dev · 2026-01-24 12:10
fl0_id__but then it cut off the 3 with some warning#asahi-dev · 2026-01-24 12:10
fl0_id__yuka, i fixed that#asahi-dev · 2026-01-24 12:09
fl0_id__integralpilot, no, virtual serial works, mostly#asahi-dev · 2026-01-24 12:08
fl0_id__would still be nice to have serial though#asahi-dev · 2026-01-24 12:08
fl0_id__as suspected, without the wrong serial in dt, baremetal also boots to rootfspanic#asahi-dev · 2026-01-24 12:06
fl0_id__yes now with hv i saw it on the screen#asahi-dev · 2026-01-24 12:06
fl0_id__so maybe commenting out the non working serial in device tree would make it boot further#asahi-dev · 2026-01-24 12:05
fl0_id__yuka, well yeah, but when booting it excepted with a serial error. so if it's not unrelaible devices, could also be some serial error I didn't see#asahi-dev · 2026-01-24 12:03
fl0_id__integralpilot, cool thx#asahi-dev · 2026-01-24 12:03
fl0_id__btw this is on hv, yuka said I should try baremetal but sth else is broken there for me (unless it's the same serial thing)#asahi-dev · 2026-01-24 12:02
fl0_id__integralpilot, yeah without serial it boots to rootfspanic#asahi-dev · 2026-01-24 12:00
fl0_id__at the time I had other problems...#asahi-dev · 2026-01-24 12:00
fl0_id__sven, well yeah :)#asahi-dev · 2026-01-24 11:59
fl0_id__integralpilot, right also an option thansk#asahi-dev · 2026-01-24 11:59
fl0_id__sven, make dtbs warned that it cut off the 3 at some point, but at the time I just ignored it...#asahi-dev · 2026-01-24 11:58
fl0_id__sven, yes#asahi-dev · 2026-01-24 11:57
fl0_id__sth about serial driver. I think it's about the device tree. at first when I added the right address it was fine, without errors, but then cut it off or sth#asahi-dev · 2026-01-24 11:55
fl0_id__integralpilot oh i thought i had posted them. here is ctx and backtrace https://www.pastery.net/hytpwv/#asahi-dev · 2026-01-24 02:21
fl0_id__https://www.pastery.net/mhtuha/#asahi-dev · 2026-01-24 02:19
fl0_id__I messed with the chickens again a bit and I got further...#asahi-dev · 2026-01-23 22:45
fl0_id__if I just && it seems to not reconnect or sth. or yeah, tbh it seems like unreliable evice names https://www.pastery.net/vynadt/#asahi-dev · 2026-01-23 22:43
fl0_id__now I think I do.. just if I plugged in CS later, then it was usually ACM2, but when rebooting, it would be ACM0#asahi-dev · 2026-01-23 22:40
fl0_id__is there a trick to chainloading m1n1 before linux.py? it seems that is a problem if I just && it, but I need a newer m1n because I disabled cpufreq there. if I just use linux.py, it fails on cpufreq#asahi-dev · 2026-01-23 22:33
fl0_id__https://www.pastery.net/pjzprs/#asahi-dev · 2026-01-23 22:33
fl0_id__at least I have backtrace symbols back...forgot I messed around in proxyclient/m1n1/hv/__init__.py with symbol offset...#asahi-dev · 2026-01-23 22:28
fl0_id__mmh the cs output seems to be connected now properly. but no m1n1 or linux output there. https://www.pastery.net/bydmnv/#asahi-dev · 2026-01-23 22:08
fl0_id__yes#asahi-dev · 2026-01-23 22:06
fl0_id__or should I then use the CS micro usb for m1n1?#asahi-dev · 2026-01-23 22:06
fl0_id__thx for the feedback. I meant also like when to connect the CS. Like if I just leave it connected when restarting, it seems to sometimes be ACM0, and then m1n1 doesn't work to chainload etc#asahi-dev · 2026-01-23 21:38
fl0_id__I think so... though looking at them again, the control messages are wrong. but it was giving the correct one with the same cable#asahi-dev · 2026-01-23 21:32
fl0_id__yuka, no, the control messages are there#asahi-dev · 2026-01-23 21:29
fl0_id__yuka, I'm prob doing sth wrong with in regards to which serial port goes where...? the CS gets recognized, and should be on ACM2, but there's no output. I now only used /dev/m1n1 (ACM0) to chainload and load kernel, not the ACM1 port#asahi-dev · 2026-01-23 21:21
fl0_id__yes. it got an input/output error "read zero bytes" after, but not sure if that is from resetting myself or not