#asahi-dev · 2026-09-12 08:09
myrialol#asahi-dev · 2026-09-12 07:39
chadmedmyria: sorry ignore me i cant read today lol #asahi-dev · 2026-09-11 12:25
myriaThanks!#asahi-dev · 2026-09-11 11:51
jannautagged asahi-7.1.13-2 with the m3 pro jack hpd irq fix#asahi-dev · 2026-09-11 11:50
sofusdoes wifi make it worse?#asahi-dev · 2026-09-11 11:49
chadmedyeah i get gpu coil whine on my j314#asahi-dev · 2026-09-11 11:48
sofuswas there ever an report of squealing on a pro/max device?#asahi-dev · 2026-09-11 10:20
chaos_princesssame#asahi-dev · 2026-09-11 10:19
jannauwhich matches disp_reserved_regions_t602x#asahi-dev · 2026-09-11 10:18
jannauI have following segments (numbers are region id): 49, 50, os_log, 57, 94, 95, 14/vram, 157#asahi-dev · 2026-09-11 10:06
jannaumy segment-ranges has for some reason one additional segment#asahi-dev · 2026-09-11 10:04
jannauthat's not mapped either#asahi-dev · 2026-09-11 10:03
chaos_princesseverything else is in carveouts, including vram, which is region 14#asahi-dev · 2026-09-11 10:03
chaos_princessyes#asahi-dev · 2026-09-11 10:03
jannauthat is the third segment / __OS_LOG?#asahi-dev · 2026-09-11 09:54
chaos_princess`struct.unpack('QQQI4xQQQI4xQQQI4xQQQI4xQQQI4xQQQI4xQQQI4x', u.adt['/arm-io/dcp/iop-dcp-nub'].segment_ranges)`#asahi-dev · 2026-09-11 09:53
jannauchaos_princess: where do you see 0x100045c4000? I only see phys ram from the top of memory#asahi-dev · 2026-09-11 09:34
sofusthe regs should be fixed now#asahi-dev · 2026-09-11 09:29
chaos_princessthat one is not present in carveouts at all#asahi-dev · 2026-09-11 09:28
chaos_princessif we go by segment-ranges, they do match, except for '0x100045c4000', '0x901000', '0x100045c4000', '0x1f000'#asahi-dev · 2026-09-11 09:20
sofuschaos_princess: sorry i forgot you also need https://github.com/AsahiLinux/linux/pull/607/changes/62bd293cb0a47f6807e5019f3a905a529a0f94d8#asahi-dev · 2026-09-11 09:12
sofusyeah, thats also wrong#asahi-dev · 2026-09-11 09:10
chaos_princessyou are on a t6030, no?#asahi-dev · 2026-09-11 09:10
sofushow did it even work on my device...#asahi-dev · 2026-09-11 09:09
sofusi did them all completly wrong#asahi-dev · 2026-09-11 09:09
chaos_princessyes#asahi-dev · 2026-09-11 09:09
sofusim confusing myself, sorry. the first reg is dcp_reg[0], the rest are disp0 right?#asahi-dev · 2026-09-11 09:03
jannauprobably unavoidable for disp0 although one of the regions is vram#asahi-dev · 2026-09-11 09:03
chaos_princessyes, they don't seem to#asahi-dev · 2026-09-11 09:01
jannauthey don't match. I'd recommend using segment-ranges dart-dcp* and use region-id tables only if unavoidable#asahi-dev · 2026-09-11 08:57
chaos_princesswell, mbox must be correct since rtkit works at all#asahi-dev · 2026-09-11 08:57
chaos_princessmbox is correct, no?#asahi-dev · 2026-09-11 08:57
sofuschaos_princess: you did also fix the regs right? Both dcp and mbox are wrong if im not mistaken#asahi-dev · 2026-09-11 08:52
jannaumatch the phys ram from the dart against the addresses in the ADT#asahi-dev · 2026-09-11 08:52
chaos_princessjust check if the reserved regions are mapped in those darts?#asahi-dev · 2026-09-11 08:51
chaos_princesshow do i do that. As in, how do i verify that they are correct.#asahi-dev · 2026-09-11 08:51
jannauin m1n1?#asahi-dev · 2026-09-11 08:51
jannauchaos_princess: have you verified that the region ids are still correct by dumping disp0 and dcp0 dart?#asahi-dev · 2026-09-11 08:50
jannauit doesn't on the m3 pro/max devices. if it doesn't on the m3 mba it's likely related to the spmi type-c controller and whatever other changes apple did to the usb-c ports#asahi-dev · 2026-09-11 08:49
chaos_princessdo y'all do any other m1n1 changes than adding t6030 to the t602x branches to get dcp working? Trying it on t6031, it runs through the rtkit boot, even logs various things to syslog, but leaves the kernel on read once it tries to start endpoint 0x20, and fails to load#asahi-dev · 2026-09-11 08:47
chadmedsofus: it will either be RFI amplified and output by the speaker codecs (aiui should not really be possible when the codecs are in software shutdown) or coil whine#asahi-dev · 2026-09-11 08:46
jannauon the m3 14-inch macbook pro. replugging the usb device and then running `usb reset` mostly works#asahi-dev · 2026-09-11 08:46
sofuschadmed: i honestly have no idea what even _can_ make sounds, i dont think its the speakers. Its definitely coming from somewhere around the upper right middle of the laptop#asahi-dev · 2026-09-11 08:44
jannauplease do not write emails to individual persons to report bugs. those will most likely be ignored#asahi-dev · 2026-09-11 08:43
jannauI meant after the ':' but if it no longer prints "Port not available." then it's ok#asahi-dev · 2026-09-11 08:40
jobe[m]looks fine as on M1/M2 (one month ago I had Bus usb@7022800000: Port not available. and wrote an e-mail to sven)#asahi-dev · 2026-09-11 08:39
jobe[m]Bus usb@7022800000 and Bus usb@b022800000#asahi-dev · 2026-09-11 08:38
jannauwhat does u-boot log after "Bus usb@..."?#asahi-dev · 2026-09-11 08:28
jobe[m]yes, several times#asahi-dev · 2026-09-11 08:26
jannaudid you try after replugging the usb device while in u-boot?