#
✕ nick:flokli
#asahi-dev · 2026-06-30 22:45
flokli`msr((3, 5, 15, 1, 3), mrs((3, 5, 15, 1, 3)))` still broken on t6040 with 26.6b3 / 25G5052e, freshly DFU-restored :/
#asahi-dev · 2026-06-25 21:07
flokliunfortunately it's buried in months of matrix history that's unsearchable.
#asahi-dev · 2026-06-25 21:07
flokliyes, there were various error messages in macvdmtool / tuxvdmtool.
#asahi-dev · 2026-06-25 21:00
flokliI never got it to work with another mac and non-debugusb, only with the CS.
#asahi-dev · 2026-06-25 19:12
flokliyuka and I usually use the build deps from nixpkgs (which follows the releases) as a basis for a development shell to tinker with the python scripts. But we didn't package the scripts themselves in there, as chances are you already have an m1n1 checkout somewhere if you use the scripts.
#asahi-dev · 2026-06-25 18:55
floklijannau: can we get https://github.com/AsahiLinux/m1n1/pull/601 landed before that?
#asahi-dev · 2026-06-24 23:56
flokliYup
#asahi-dev · 2026-06-24 23:54
flokliAnd without maxcpus=1 it crashes for you as well?
#asahi-dev · 2026-06-24 23:52
flokliAnd does it bring all cores online?
#asahi-dev · 2026-06-24 23:51
floklienverbalalic: what kernel config are you using?
#asahi-dev · 2026-06-24 15:58
flokliTy!
#asahi-dev · 2026-06-24 15:55
flokli27.0 beta 2, m1n1 reports mBoot-20457.0.13.0.11
#asahi-dev · 2026-06-24 15:54
floklijust tested `msr((3, 5, 15, 1, 3), mrs((3, 5, 15, 1, 3)))` on t6040 with latest beta, still broken :-/
#asahi-dev · 2026-06-24 14:19
floklienverbalalic: i was about to :)
#asahi-dev · 2026-06-24 14:18
flokliI didn't check if it also got fixed for my t6040 with 27.0 beta 2.
#asahi-dev · 2026-06-24 14:17
flokliyou might not need HEAD~2 if you're running 26.6 beta2
#asahi-dev · 2026-06-24 14:11
floklienverbalalic: https://github.com/flokli/linux/tree/j773s
#asahi-dev · 2026-06-24 12:38
flokliConsidering there's also t602x-common.dtsi, that's how it might end up getting upstreamed anyways
#asahi-dev · 2026-06-24 12:37
flokliI can probably post my t6040 one, most of it might be applicable to t6041 as well
#asahi-dev · 2026-06-24 11:42
flokliBut this machine has 12 cores, so fairly high chance it reproduces whatever race there is easily without restricting.
#asahi-dev · 2026-06-24 11:41
flokliso booting with maxcpus=6 also worked after a few attempts
#asahi-dev · 2026-06-24 11:37
flokliLarstiQ: i'd need to probably do a lot more reboots to give you a somewhat confident answer to that ;-)
#asahi-dev · 2026-06-24 11:34
flokliyeah, so the higher I set maxcpus=, the less likely the chance for the bootup to succeed. maxcpus=4 is a bit hit and miss, any more cores than that I wasn't able to boot up the kernel without oopsing
#asahi-dev · 2026-06-24 11:31
flokliso it correlates with the number of cores that are running. i wasn't able to successfully boot at all with all 12 cores. but i was able to boot up with maxcpus=2 just now
#asahi-dev · 2026-06-24 11:28
floklisorry, was missing the 'unable to handle kernel write' line. more logs of another boot: https://paste.linuxlounge.net/PMTU4BIEOV4UPN55VPS2V6OSBY
#asahi-dev · 2026-06-24 11:23
floklihttps://paste.linuxlounge.net/AG72ORIPUUH6KEAN2FXWDVOADI
#asahi-dev · 2026-06-24 11:21
flokliyuka: so the less minimal kernel config still crashes somewhat reliably without maxcpus=1. Maybe there's some other place using wfi, which we didn't catch with this patch?
#asahi-dev · 2026-06-24 11:12
floklii'm just chainloading kernels, yuka is doing all the work, lol
#asahi-dev · 2026-06-24 11:08
floklii'll try a slightly bigger kernel now
#asahi-dev · 2026-06-24 11:07
flokliI successfully booted it into this quite minimal kernel which previously did crash pretty reliably
#asahi-dev · 2026-06-20 21:42
flokliagree.
#asahi-dev · 2026-06-19 17:58
floklidfu restored to 26.6 beta 2.
#asahi-dev · 2026-06-19 17:58
flokliJ773s, t6040
#asahi-dev · 2026-06-19 17:57
floklitried to boot in the hv on m4, but I'm hitting the for me still-disallowed SYS_IMP_APL_VM_TMR_FIQ_ENA_EL2 reg write
#asahi-dev · 2026-06-17 19:39
flokliI installed 26.6 beta 2 (mBoot-18000.160.14.501.1) and msr((3, 5, 15, 1, 3), mrs((3, 5, 15, 1, 3))) does throw an exception. t6040
#asahi-dev · 2026-06-14 12:43
flokliAlso sent a PR for t6040 m1n1 bits. With maxcpus=1 it's booting linux with a minimal device tree (which I also intend to send), no need to only have this sitting on my machine.
#asahi-dev · 2026-06-12 13:26
floklioh, very cool
#asahi-dev · 2026-06-09 21:30
flokli:+1:
#asahi-dev · 2026-06-09 21:23
flokli26.5.1
#asahi-dev · 2026-06-09 21:21
flokliStanfordAppliedCyber[m]: this is a boot which oopses on a secondary cpu as it's loosing state presumably: https://paste.linuxlounge.net/OE
#asahi-dev · 2026-06-09 09:04
flokliJ773s, with a minimal device tree I get all the way into a a linux initrd, with some m1n1 changes I get the cores initialized, but when not passing cpus=1 i get two 'Unable to handle kernel write to read-only memory at virtual address ffff8000039f8000', and then oops.
#asahi-dev · 2026-06-09 08:59
floklim4pro here
#asahi-dev · 2026-06-09 08:48
floklino point in continuing further if it's known to be buggy
#asahi-dev · 2026-06-09 08:48
flokliStanfordAppliedCyber[m]: ok, I am on still on 26.4. Guess I'll spend some time upgrading and re-installing m1n1 into that.
#asahi-dev · 2026-06-09 08:21
flokliStanfordAppliedCyber[m]: "debugging smp on 26.4.1"... How's the error behavior for you with that?
#asahi-dev · 2026-05-19 19:36
flokliit was quite annoying to desolder everything again, but I'm glad it didn't blow anything up
#asahi-dev · 2026-05-19 19:35
flokliLarstiQ: the friend who soldered it soldered the rpi the wrong way round, and I didn't properly verify again before trying it 😂
#asahi-dev · 2026-05-19 15:53
flokliyes, I now saw some m1n1 logs fly by as well. very cool, I take it!
#asahi-dev · 2026-05-19 15:48
floklihttps://paste.linuxlounge.net/ZU
#asahi-dev · 2026-05-19 15:35
floklimaz: with the soldering issue fixed, It now does print stuff on the terminal: https://imgur.com/a/nxr3IpZ

plus ›