#
✕ nick:siirko[m]
#asahi-dev · 2026-05-08 14:02
siirko[m](Around February, I wanted to link the message that I’ve sent on this discussion group but didn’t worked)
#asahi-dev · 2026-05-08 14:01
siirko[m]At this time I get this problem but nice to know, I will retry it when I will have free time !
#asahi-dev · 2026-05-08 12:49
siirko[m]Hello, I’ve seen that the device tree was sent to the kernel mailing list and long time ago I’ve looked up to boot on u-boot on my M3 but I’d gotten stucked because of power domains missing setup and I was wondering if there is any info about this ?
#asahi-dev · 2026-02-25 14:27
siirko[m]<siirko[m]> "Hi ! I'm coming back from my..." <- For this, In my case the problem is related that while doing uart setup at early stage of u-boot, it tries to select according power domain informationfor uart0 but fails. I don't know if the problem is from me or it was already there.
#asahi-dev · 2026-02-24 19:51
siirko[m]Hi ! I'm coming back from my problem to boot u-boot on M3, I digged through and I want to ask if someone can confirm that me that on M1/M2 it goes on this condition https://github.com/AsahiLinux/u-boot/blob/asahi/drivers/serial/serial-uclass.c#L88, I'm trying to understand why it doesn't actually found serial console
#asahi-dev · 2026-02-22 09:54
siirko[m]fl0_id: here also a pastebin of the logs that I get https://pastebin.com/Uwkciv2f
#asahi-dev · 2026-02-22 09:32
siirko[m]jannau: oh yes, that worked !
#asahi-dev · 2026-02-22 08:53
siirko[m]fl0_id: https://filebin.net/v8wm3qqn6a0i61yo here my m1n1-stage1.bin, m1n1-stage2.bin/macho
#asahi-dev · 2026-02-22 08:52
siirko[m]My m1n1 is from main, I applied also https://github.com/AsahiLinux/m1n1/pull/538 diff
#asahi-dev · 2026-02-22 08:52
siirko[m]fl0_id: from m1n1 build, while running as run_guest.py it doesn't want to load a bin file because there is a mismatch between what he expect to read and what he has in reality. And seeing the top of python stack trace it definitly waits a Macho file, I'm running this with : sudo python3 proxyclient/tools/chainload.py -r build/m1n1.bin && sudo python3 proxyclient/tools/run_guest.py ../m1n1-stage2.macho
#asahi-dev · 2026-02-21 23:52
siirko[m]fl0_id: I basically chainload m1n1 stage 1, then run_guest.py by m1n1+uboot+dtc macho file, I have logs about cpu cores but then nothing else and I have access to hypervisor shell
#asahi-dev · 2026-02-21 23:18
siirko[m]yeah nevermind it seems that I managed to access to hypervisor shell but couldn't achieve to get logs from ACM1
#asahi-dev · 2026-02-21 22:48
siirko[m]It may stupid but, does the m1n1-stage1.bin has to be built from the os kernel that we are using for m1n1/hypervisor ?
#asahi-dev · 2026-02-21 21:56
siirko[m]jannau: yup, I'm on the way ! That's nice because with that I will able to use gdb according to doc :D
#asahi-dev · 2026-02-21 21:50
siirko[m]To sad that I don't own another mac m series haha thing would've been simple ...
#asahi-dev · 2026-02-21 21:50
siirko[m]jannau: Didn't know what wa the central scrutinizer until I found https://asahilinux.org/docs/hw/soc/serial-debug/#inflexible-usb-pd-debug-interface-aka-central-scrutinizer
#asahi-dev · 2026-02-21 21:39
siirko[m]From my understand ACM1 is just here for enabling proxy and then ACM0 to send payloads (https://asahilinux.org/docs/sw/m1n1-user-guide/#backdoor-proxy-mode-in-stage-1-release-builds mentionned at the end of documentation) I tried to picocom on ACM0 and send payloads on ACM1 but it wont work
#asahi-dev · 2026-02-21 21:32
siirko[m]fl0_id: wait, for on which port do I have to listen with that script ?
#asahi-dev · 2026-02-21 21:26
siirko[m]fl0_id: Yes I have the right port, I’m sending the payload through the proxy from my main workstation through a usb cable
#asahi-dev · 2026-02-21 21:06
siirko[m]Apparently you can have uart output for u-boot debugging https://docs.u-boot.org/en/latest/board/apple/m1.html#debug-uart, I retrieved correct uart base addr for M3 (0x2a1200000) but still nothing shows up. If anyone have some more experiences with u-boot I would be happy to talk
#asahi-dev · 2026-02-21 14:58
siirko[m]jannau: oh, really sorry didn't know about that
#asahi-dev · 2026-02-21 14:58
siirko[m]s///
#asahi-dev · 2026-02-21 14:58
siirko[m]* jannau Hi, I've dumped my ADT, there is a lot of info but I found some infomration about pcie addr/size, but I'm not sure of other information ... For example in actual layout it is mapped like... (full message at <https://matrix.org/oftc/media/v1/media/download/AfzThpj74tiwzv0eXkpdHAkbqJf0xtA6-wUrqpiNGGEDPIs-vZGnxNKIwlutLSOyTKYrqYsRzVFxEWr3b1WDZS9CecyM5ijgAG1hdHJpeC5vcmcveHRNQm9sa1NFeWxmd3FpS2NxQWJodVht>)
#asahi-dev · 2026-02-21 14:58
siirko[m]* jannau Hi, I've dumped my ADT, there is a lot of info but I found some infomration about pcie addr/size, but I'm not sure of other information ... For example in actual layout it is mapped like... (full message at <https://matrix.org/oftc/media/v1/media/download/AWMa5WStWfqYloN29OoatvKumcZRSuTuLLxOUUNEghGMRmuMjsTHYRlqcLjyvdo_ACjL8CHruXlBrHsuXFEt7whCecyM4thgAG1hdHJpeC5vcmcvVVd2dGVIY0diV1BtQ2t3dU9WcU56Vm1W>)
#asahi-dev · 2026-02-21 14:57
siirko[m]* jannau Hi, I've dumped my ADT, there is a lot of info but I found some infomration about pcie addr/size, but I'm not sure of other information ... For example in actual layout it is mapped like... (full message at <https://matrix.org/oftc/media/v1/media/download/ASkFqE_uvqRcCcBh4F3dL9N5QpRhXQqV8A5aHnGXz-RTlL81vyYd9NxsZ3vxBetl4GTaiysXkey2_wV7fXnuLkNCecyM39pgAG1hdHJpeC5vcmcveEJZUkRVRm1SbU94alFJbndPcmF4Skxu>)
#asahi-dev · 2026-02-21 14:57
siirko[m]jannau Hi, I've dumped my ADT, there is a lot of info but I found some infomration about pcie addr/size, but I'm not sure of other information ... For example in actual layout it is mapped like... (full message at <https://matrix.org/oftc/media/v1/media/download/AYj-CEJLKXcxW2evs2YdmMcFjYBaxsECdz1VBNpbEh8co9N2lK8QteOgrrrDWo9kFH7YxACncfbkArsK4By4CDtCecyM3TCgAG1hdHJpeC5vcmcvT2J2VHNjdE1VYkJLeUZWaWNRb1dMR2V1>)
#asahi-dev · 2026-02-20 22:13
siirko[m]* doing things with the device tree.
#asahi-dev · 2026-02-20 22:13
siirko[m]fl0_id: I will try to do that, but I have the impression that it hangs before doing things device tree. I’m trying to reads more about u-boot for understanding how can i toy with it for debugging
#asahi-dev · 2026-02-20 22:05
siirko[m]* demanding work to do ?
#asahi-dev · 2026-02-20 22:04
siirko[m]jannau: Alright, do you think it is a demanding work ?
#asahi-dev · 2026-02-20 14:53
siirko[m]Seeing this might explain why it get stucked, there just no implementation yet for m3
#asahi-dev · 2026-02-20 14:53
siirko[m]https://github.com/AsahiLinux/u-boot/blob/asahi/arch/arm/mach-apple/board.c#L713
#asahi-dev · 2026-02-20 14:53
siirko[m]* https://github.com/AsahiLinux/u-boot/blob/asahi/arch/arm/mach-apple/board.c#L21
#asahi-dev · 2026-02-20 14:26
siirko[m]https://github.com/AsahiLinux/u-boot/blob/asahi/arch/arm/mach-apple/board.c#L21 Seeing this might explain why it get stucked, there just no implementation yet for m3
#asahi-dev · 2026-02-20 13:56
siirko[m]fl0_id: yup, just hangs on asahi logo
#asahi-dev · 2026-02-20 13:53
siirko[m]edit : I've looked at m1n1 code and I think this is closely related to u-boot or something else that I've not done correctly on u-boot code
#asahi-dev · 2026-02-20 13:53
siirko[m]* I compiled it from source like explained here https://asahilinux.org/docs/sw/u-boot/#prerequisites I put the right dtb from https://github.com/AsahiLinux/linux/pull/445 and applied https://github.com/AsahiLinux/m1n1/pull/538
#asahi-dev · 2026-02-20 13:38
siirko[m]fl0_id: I compiled it from source like explained here https://asahilinux.org/docs/sw/u-boot/#prerequisites I put the right dtb from https://github.com/AsahiLinux/linux/pull/445 and applied https://github.com/AsahiLinux/m1n1/pull/538
#asahi-dev · 2026-02-20 13:32
siirko[m]fl0_id: nevermind about that it was bad english , I meaned that while I tried to boot a kernel directly through m1n1 stage 1 I tried with m1n1 -> uboot
#asahi-dev · 2026-02-20 13:16
siirko[m]I tried to go the other way around and do the m1n1 -> u-boot, but it seems that I'm stuck on asahi logo. This happens juste before it prepare to load kernel. Is anyone have a clue of what I might did wrong ? I see within the log that it loads correct device tree blob and pcie initialisation goes alright
#asahi-dev · 2026-02-20 09:53
siirko[m]I choose the path of booting a linux kernel directly like explained in https://asahilinux.org/docs/sw/m1n1-user-guide/#configuring-to-boot-linux-directly
#asahi-dev · 2026-02-20 09:53
siirko[m]jannau
#asahi-dev · 2026-02-20 09:53
siirko[m]chaos_princess: Thank you !
#asahi-dev · 2026-02-20 09:46
siirko[m]Hi !, I've managed to boot up partially linux kernel on my m3, but it is blocked with "waiting for root device /dev/nvme....", I put this string into the boot bin 'chosen.bootargs=earlycon debug root=/dev/nvme0n1p6 rootwait rw' with other information. The only thing that came to my mind is that it might be because I didn't gave it a initramfs and at this stage it can't load nvme
#asahi-dev · 2026-02-18 17:30
siirko[m]fl0_id: yes of course, for which m3 I have is T8122 if i'm not mistaken (I have a M3 2024 13 inch), seeing current and old pr's it should be 👍️
#asahi-dev · 2026-02-18 17:17
siirko[m]fl0_id: perfect, thank you !
#asahi-dev · 2026-02-18 17:12
siirko[m]chaos_princess: "on top", what do you mean by that ? https://gist.github.com/IntegralPilot/85c355124fe54e670e6d5586c7a07826 it is mentionned, I guess I have use both the wiki and that gist as a reference ?
#asahi-dev · 2026-02-18 17:02
siirko[m]chaos_princess: Okay and with that I can follow without a problem https://asahilinux.org/docs/sw/m1n1-user-guide/ ?
#asahi-dev · 2026-02-18 16:35
siirko[m]Hi, I wanted to contribute to the progress of M3 port but I know there is only patches to make it work. Is there a place to gather all of these patches so I can tinker things my to make things work ?