08:04 <pitust> ADP stopped working and i'm getting some mildly worrying dmesg logs stopped working: "flip_done timed out" and "[CRTC:33:crtc-0] commit wait timed out" (both from adp 228200000.display-pipe)

08:08 <pitust> the only other message is "adp 228200000.display-pipe: Adding to iommu group 0" and "[drm] Initialized adp 0.1.0 20230412 for 228200000.display-pipe on minor 2"

08:09 <pitust> strongly suspect this is hardware damage; no flickering when suspended unlike before

12:16 <zrhoffman> ayke: This one is not really ALARM's fault, it was a bug in Firefox (for which a fix has already landed, soon to be uplifted for a new release). ALARM provides only the packaging for Firefox, in this case

13:45 <tamar> Hi, I noticed that asahi reports the cache line size to be 64bytes but on OSX the cache line is 128. anyway to get the asahi kernel to also report 128?

13:56 <j`ey> tamar: you could modify the source and rebuild, but I dont think so otherwise

13:58 <tamar> j`ey: of the kernel? sure I'm happy to do so, would you happen to know where? I couldn't find a param

13:58 <j`ey> tamar: Im not sure why you want to do it but check out `cache_line_size_of_cpu`

14:01 <tamar> j`ey:

14:01 <tamar> j`ey: ah trying to track down a performance difference between asahi linux and osx

14:02 <tamar> thanks I'll give it a try!

14:15 <iaguis> I was playing some music on my BT headphones and when one song finished and the next song started the system completely froze and rebooted in 30s (I guess the hardware watchdog got triggered). I don't see anything on journalctl -b -1. Anybody knows how to get some info on what happens in this case? Maybe pstore or something?

15:29 <jeisom> Any one seeing usb issues with linux-asahi-edge-6.5.asahi15-1 ? I am using a 5bay enclosure with 2 4TB drives. I downgraded to linux-asahi-edge-6.5.asahi3-1 and the issue appears to resolve

15:31 <jeisom> I am rsyncing my ALARM to the drive to backup and it was disconnecting and reconnects shortly after start. On ALARM.

15:31 <jeisom> Finished without issue on the older version.

15:34 <j`ey> there doesnt seem to be anything directly usb related in the diffs between -3 and -15

15:37 <jeisom> I'll retest(Both) and get the dmesg(if it reproduces)

15:41 <jeisom> Guess I got lucky. Reproduced on the older. Got "WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state." After that is just "normal" disconnect/reconnect/filesystem erros

15:42 <jeisom> Maybe the enclosure is got an issue.

15:54 <jeisom> I have an m1 mini I am about to switch to Fedora. Would upgrading to macOS 13.6.1 or 14.x be better? macos is on 13.2.x right now.

16:44 <jeisom> While I am still curious about the macOS version, I started with 13.6.1

17:34 <bluetail> jeisom do not upgrade

17:34 <bluetail> sonoma is severely messed up

17:35 <bluetail> I installed it on my working machine and ms teams no longer functions at all

17:35 <bluetail> I heard it even made some machines unbootable

17:37 <bluetail> but don't forget... this was on a mbp 2016... not m1

17:37 <bluetail> coworker has a new m2 and m3 and doesnt report issues yet

17:37 <bluetail> my feeling is that they still messed up something

17:38 <jeisom> Ok. I did update to 13.6.1 from 13.2.x, but I did not do 14.x. I thought 14.x may have some issues to work out for linux, but wasn't sure.

17:46 <bluetail> I think it would be wise to wait it out for now

19:29 <kidplayer666> bluetail: sonoma had several problems regarding ProMotion, discussed a few weeks/days? ago in here. Marcan’s mastondon probably has a good summary

19:46 <nicolas17> kidplayer666: none of the machines mentioned above have ProMotion :P

20:14 <kidplayer666> nicolas17: Oh wait, Jesus Christ

22:43 <Tramtrist> Happy Thanksgiving to you