#
…

2025-01-20

03:14tobhe_ has joined #ubuntu-asahi
03:21tobhe has quit [Ping timeout: 480 seconds]
04:31john-cabaj[m]Sorry, just seeing this. Turned mobile notifications to mentions only for the time being. Saw the email - will have to have a look once logs are attached.
08:47funderscore is now known as f_
10:44tobhe[m]I'm deleting it from the ppa until we figured out what's wrong. Multiple reports now
13:28nukelethuh, curiously only seems to affect m2 devices?
13:28nukeletim on the road right now but ill investigate as soon as i get home
13:28tobhe[m]not even that, because I have an m2 air and that is not affected
13:28tobhe[m]so possibly m2 pro only
13:29nukeletthat new BSOD thing is... less than helpful in this scenario
13:30tobhe[m]I wonder if it can be disabled with a command line arg
13:31nukeletprobably, although on second thought, in this scenario i think we would just get a screen freeze
13:31nukeletthankfully we can grab the logs using m1n1 at least
13:41tobhe[m]> disable all aop device nodes (fixes boot on (some) desktop macs)
13:43nukeletwe rebased on top of asahi-6.12.8-2
13:45nukelethonestly my bet is on the other issue you sent: https://github.com/AsahiLinux/linux/issues/310
13:46tobhe[m]Is that outdated?
13:47nukelethuh, im not sure actually
13:47nukeletno yeah it is outdated
13:49tobhe[m]the changelog at https://launchpad.net/~ubuntu-asahi/+archive/ubuntu/build2/+packages also lists fixup! arm64: dts: apple: Add AOP and subdevices
13:51nukeletactually its worse because the tag in the ubuntu-asahi git repo shouldnt exist at all but thats a problem for later
13:54tobhe[m]I'll ask them to test module_blacklist=sdhci_pci
13:57nukeletyeah please do
13:57nukeletwe can probably add a udev rule to blacklist this automatically if it is indeed the root cause
13:58nukeletvery weird that we weren't bitten by this before, fedora has been getting reports for a long time (and blacklisted the module in udev 6 months ago)
13:59tobhe[m]I think there is a udev fix i planned to backport at some point
13:59tobhe[m]so my fault if it is actually that one 🙂 let's hope it is
14:16tobhe[m]so it panics in dart
14:16tobhe[m]looks like it isn't as easy unfortunately
14:33john-cabaj[m]<nukelet> "actually its worse because the..." <- Which tag?
14:34tobhe[m]the second seems to be what's actually in the ppa
14:42john-cabaj[m]Maybe I grabbed the wrong Ubuntu-asahi-arm-6.12.0-1002.2 tag, somehow..
14:49tobhe[m]the one in the ppa seems to be the correct one though
14:50john-cabaj[m]A bit confused. They mentioned 6.10.0-1001 working, but we'd had 6.12.0-1001 released quite some time
14:50tobhe[m]that is weird yes
14:50tobhe[m]maybe they didn't update for a while
14:52john-cabaj[m]I'd be curious if that state was also broken
14:58john-cabaj[m]That [GitHub issue](https://github.com/AsahiLinux/linux/issues/310) is referenced in a commit that we already carry, and is otherwise "worked around". But I'm not sure what that implies. Maybe the udev rule that nukelet mentioned.
14:58tobhe[m]from all we know right now it looks like something in dart
14:59tobhe[m]yes, but we don't ship that yet. It probably isn't that one though
14:59tobhe[m]latest screenshot shows a panic in dart
14:59tobhe[m]in platform_probe, so very early
15:02tobhe[m]which does make it sound like a dtb issue
15:06john-cabaj[m]I'll try spinning a new updated kernel locally just to have somethign
15:08john-cabaj[m]s/somethign/something/
15:16tobhe[m]do we have anyone with a m2 pro here?
15:19nukeletnope, mine is an m1 sadly
15:22john-cabaj[m]Ok, trying a local build in the meantime. Best I can do for now since I have some errands (carpet cleaning, grocery shopping)
15:23tobhe[m]would have been surprising because otherwise we would have found it during testing
15:23tobhe[m]I will check the dtb and driver for things that changed
15:26nukeletim at home now, looking into this
15:26john-cabaj[m]Perhaps we caught a bad interim tag
15:26tobhe[m]maybe, but I haven't found an obvious cause yet
15:28tobhe[m]new report on a mac mini m2
15:28john-cabaj[m]On an upgrade, too
15:29tobhe[m]fix t602x SEP MMIO addresses ?
15:30tobhe[m]We could build a m1n1 binary with updated dtbs and have them test that
15:32nukeletsure, but from #asahi-dev: "I've tagged asahi-6.12.9-1 not much interesting compared to 6.12.8-2. fix for SError on boot for t602x and a small dcp audio fix for some devices (still not enabled)"
15:33nukeleti think the m1n1 update is still worth it though
15:33nukeletit's just incredibly unfortunate that we caught that bad tag
15:33tobhe[m]yeah that sounds related
15:34tobhe[m]still don't understand why it didn't affect my m2
15:34john-cabaj[m]I'll hopefully have some deb packages to try soon. I'll dump them on my Google Drive with a public link that they could try
15:34nukeletyours is an m2 air, no? the t602x is the m2 pro chipset i think
15:35tobhe[m]that makes sense
15:35nukeletjohn-cabaj[m]: are those debs for a newer asahi tag?
15:35nukeletif not i can prepare one real quick
15:36john-cabaj[m]asahi-6.12.10-2
15:36tobhe[m]I guess we can go straight to 10.2
15:36nukeletok awesome
15:36nukeletim surprised they applied with no issues on top of plucky lol
15:37john-cabaj[m]We had those two upstream correction patches and things have been smooth for a minute
15:40nukeletyeah, i think so
15:41tobhe[m]I'll try to build a m1n1 stage2 for people to test
15:41tobhe[m]because currently they can't even update to a new deb without manual intervention I think
15:41john-cabaj[m]Let's all give it a shot once these local debs come through. If all is good, I'll push to a build PPA, one more test, then binary copy to release later today
15:41tobhe[m]oh ok, I can wait for those
15:42tobhe[m]we will still need to either write a script or provide instructions to copy them into the ESP from macos
15:42john-cabaj[m]Kernel debs?
15:42tobhe[m]+ device trees
15:42tobhe[m] * with updated device trees
15:43tobhe[m]because people can't install updated debs when they can't boot
16:14tobhe[m]sophisticated fixing script
16:15tobhe[m]only need fixed dtbs now
16:29john-cabaj[m]Local kernel posted in private
16:31john-cabaj[m]Fedora is also on this tag, so that's helpful
16:32nukeletseems to be working fine so far
16:33nukeletthe local kernel, i mean
16:34john-cabaj[m]If things go south, we can build elsewhere
16:50tobhe[m]user@m2:~$ uname -a
16:50tobhe[m]Linux m2 6.12.0-1003-asahi-arm #3 SMP PREEMPT_DYNAMIC Mon Jan 20 15:44:16 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux
16:55john-cabaj[m]Lucky day. Launchpad is building it already.
17:24tobhe[m]shared my script and asked for test feedback
17:31nukeletfingers crossed
17:36nukeletwait, john-cabaj[m], did you pull the fixes for that plucky build error that only happened on launchpad?
17:39tobhe[m]works 🙂
17:39nukeletnice, awesome
18:01john-cabaj[m]<nukelet> "wait, john-cabaj, did you pull..." <- Good point, probably not.
18:01john-cabaj[m]Will build a 1004 in parallel in build#2
18:12tobhe[m]updated my script
18:15tobhe[m]happy to hear some test feedback on: https://files.tobhe.de/ubuntu/fix-m1n1
18:15tobhe[m]if it doesn't break your machine I am happy
20:30nukeletoof, the -1004 build failed in build#2 because of yet another toolchain upgrade
20:31nukelettobhe[m]: will it be useful to test it on an m1 machine?
20:43john-cabaj[m]Rust in Ubuntu, the ultimate moving target
20:46nukeletpre-freeze plucky adventures
20:54john-cabaj[m]Buildling back in regular build PPA
21:13john-cabaj[m]Failed again. I’ll need to look at this later today - no time right now.
23:56john-cabaj[m]Ok. Hopefully this build in my PPA gets across the line.
23:57john-cabaj[m]My chroot had versions of Rust that worked a few weeks ago, so it wanted to keep using those.
…