[TRACKER] linux-asahi-edge issues #70
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
Hi, I can not mount my USB2 USB key with both asahi-linux-6.1rc6 and asahi-linux-edge through a USB dongle. Is it a common problem or I'm the first one reporting it? EDIT: last time I've tried AsahiLinux there was 6.1 rc4 and it used to works as expected. EDIT 2: connecting the USB key to the dongle and then the dongle to my MacBook did the trick. EDIT 3: during boot both u-boot and grub see the USB key while the initramfs' shell doesn't. That's a problem for these like me who want to install another OS, like gentoo, over AsahiLinux. |
Restoring brightness after DPMS requires updated brightness to DAC mappings. The current code based on the tables in the ADT results in an increasing brightness for each cycle. |
|
|
The 3.5mm jack is working in linux-asahi but not in linux-asahi-edge. I get no sound and KDE doesn't recognise my headphones. However, I do hear a crackle through the headphones when plugging them in our out. EDIT: Forgot to mention I'm on M2 MBP |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Please only report issues that are specific to the new features of |
|
Update: for those reading this now, this is easily fixed by changing the resolution and logging out/in. You just need to change the resolution once (or twice) to trigger something that fixes the scaling issue. Somehow, the scaling is connected to DCP/no-DCP, and you need to redo this when you switch. (Or use Wayland instead of Xorg I guess). Something is broken in desktop scaling under KDE, but only with linux-asahi-edge. Did not test other desktop environments.
While buttons are mostly correct, other widgets (sliders, scrollbars, icons, etc) are way too small. The window also starts much smaller than with linux-asahi. EDIT: no environment variables related to scaling changed between the two kernels. These are the same whether I use asahi-linux or asahi-linux-edge: |
Is this with an external screen, or otherwise what device? Did you manually change any scaling settings? Scaling on Xorg is... "interesting" to put it mildly. There are several sources of information, and the DCP driver in edge should be capable of reporting the physical screen size where available, which probably affects this. |
|
DCP doesn't report |
Just the laptop screen itself. It's a 2021 Macbook Pro 16" M1 Pro.
The only thing I changed was that I changed "Global scale" in Display Configuration to 250% (from the default of, I think, 200%). I rebooted to linux-asahi-edge with Global scale set to 200% but that doesn't fix the issue (just makes it slightly less noticeable as the difference in scale is smaller).
True that. But it works surprisingly well in KDE, even better than with Wayland IMHO.
I checked some sources of information. Here is diff -u tmp/xrandr-fb.txt tmp/xrandr-dcp.txt
--- tmp/xrandr-fb.txt 2022-11-24 18:47:35.720265529 +0100
+++ tmp/xrandr-dcp.txt 2022-11-24 19:10:34.371000021 +0100
@@ -1,3 +1,3 @@
-Screen 0: minimum 320 x 200, current 3456 x 2160, maximum 4096 x 4096
-None-1 connected primary 3456x2160+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
- 3456x2160 60.00*+
+Screen 0: minimum 320 x 200, current 3456 x 2160, maximum 16384 x 16384
+eDP-1 connected primary 3456x2160+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
+ 3456x2160 60.00*+ 50.00 59.94 48.00 47.95 It's different, but I don't see anything wrong here. I also checked Still, this should not be the issue. KDE/Qt clearly knows at what resolution to render because text looks correct. It's just all the other things that are wrong for some reason. But apparently DCP did affect rendering somehow. EDIT: huh, now this same issue also affects linux-asahi. This is very weird, it has worked fine on linux-asahi all this time. |
|
Ok, I think I figured it out - sort of. Apparently the text scale setting is kept between the framebuffer and DCP, but the scale for other UI elements is not. So if I change the global scale on asahi-linux-edge, global scale only works properly on asahi-linux-edge (but not on asahi-linux), and vice versa. ...with this new information, I don't think there is a linux-asahi-edge bug. Good thing I played with the global scale setting, otherwise I wouldn't have found this. Perhaps KDE/Plasma/X11/whatever stores the display ID with the global scale configuration and only applies it to the same display? (Where DCP is seen as a different display). |
|
Yeah, that sounds about right. As I said, the whole mechanism is... "interesting" to say the least. We're likely to switch to Wayland by default when the GPU stuff lands, which will hopefully make this a bit less crazy. |
|
Hey there! Kudos to everyone for some amazing work. I am typing this from an M1 Max running the edge kernel. I am experiencing some very weird stuff when putting the machine to sleep, I'll try to explain it here. If there are any logs I can provide, I'll be happy to do so. The machine seems to go to sleep ok when using KDE's "sleep" option. When coming back from sleep, however, the keyboard and trackpack (I have no peripherals connected) don't seem to come back. If I power cycle it, same thing, the keyboard will work in GRUB but not when KDE is started. Rebooting to the non edge kernel seems to help somehow. After that I shutdown, boot the edge kernel again and I got the keyboard back. Is this a known issue? Anything I can provide to help? Once again, thanks Asahi team for the work! |
|
I'm running into an interesting issue with DCP with a monitor (LG 32UK550) connected via HDMI to my Mac Studio (M1 Max). My monitor displays indicates that it s in HDR mode, and the display looks rather washed out/dim. There is a setting in my monitor called "HDMI ULTRA HD Deep Color," which I can turn off to get nice bright colors, however it only works at 30 Hz after this change. In macOS, the "High Dynamic Range" setting in settings can toggle the monitor between HDR and non-HDR modes, and when in HDR modes, the "ULTRA HD Deep Color" option is available. Turning it off when in HDR mode makes macOS only drive the display at 30Hz. Which indicates probably some quirk of the display hardware or monitor maybe? It is notable that when plugged into my intel-based laptop on Linux, it sets the display to a non-HDR mode, which seems correct given the state of HDR on Linux. In Windows, I can turn HDR on and it looks quite similar to how it looked in asahi (dim/washed out), but they have a slider to increase the baseline brightness (not really my field, I'm sure there's more precise terminology)...Very strangely, even with HDR on in windows, the "ULTRA HD Deep Color" support is still locked to off, which is disappointing as I could not test if windows could drive it at 60 Hz in this configuration. If there is any info I can provide I'd be happy to. I think the most reasonable fix would be to mimic whatever macOS does when you turn HDR off in settings. I'm pretty technical and happy to collect any information if my setup happens to be useful. |
|
Seen on M2 MBA, adding it here since I didn't find it above: After returning from s2idle, bluetooth devices can no longer be connected. At resume time, dmesg shows: Any manual connection attempts time out, and in dmesg I see: |
This comment was marked as duplicate.
This comment was marked as duplicate.
37 tasks
|
You should change your display scale setting when switching to -edge. Under Xorg, changing that should change the DPI setting in the fonts dialog. It is likely that the display scale got reset to 100% since the display output changed, but not the DPI setting since that is global. This is expected. Display scaling is all kinds of quirky and broken on Xorg. I preconfigured things to work right for new installs, but there's no way to make it work smoothly across changes like this, and approximately nobody is interested in working on Xorg bugs upstream. You should be able to play around with the scale/DPI settings and find something that works. But I don't think there's anything we can do our end here. This has nothing to do with the -edge kernel other than the fact that the new driver shows up as a new display device and therefore doesn't inherit the old scale setting. I've added this to the known issues list; we really can't do anything about it. |
|
Just installed linux-asahi-edge on my M1 Mac Mini which I use as a TV PC. GPU seems to be running great, but the HDMI output brightness seems like it's set too high. Colors are very washed out. It was not this way before installing edge, nor is it this way on MacOS. My TV is an old Apex Digital 1080p from 2013. |
|
@CalcProgrammer1 any chance that this is a hdr tv? Could very well be related to #70 (comment) |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
@tek967 You uninstalled Please don't uninstall our support packages. Things break without them. |
I highly doubt it, it's a pretty low end TV from almost 10 years ago. |
|
It's not about HDR, it's about color formats I believe. So yes, it can affect older TVs. Known issue. |
|
With edge, after boot login with sddm or lightdm freezes keyboard and mouse. TTy terminals are working. |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
@goonmandu That's not a linux-asahi-edge issue. |
|
M2 Air, suspend then resume fails with the X server failing to start. Reproduces intermittently (only on long duration suspends), but tested across more than 5 reboots with the edge kernel. Switching to a tty and restarting sddm fixes the issue. https://gist.github.com/captn3m0/2d8ee1e4b3e7d12d80b49a8edc9809d0 |
|
On a m2 air with edge kernel, sometimes I need to reboot to be able to connect to my headset after I resume from suspend. I got those kernel message when trying to connect, restart bluetooth.service don't help, and I can't unload bluetooth driver. |
|
When trying to run a program doing some ebpf, one module can't be find. |
|
For a few days now (presumably since the last update of -edge kernel and mesa), I'm experiencing occasional freezes of the display/machine (M2 MBA). I'm using Wayland (using sway instead of Plasma). These freezes are quite infrequent (occurring at most every couple of hours), with no direct correlation to what I'm doing on the machine observed yet. When they happen, the display freezes indefinitely (including the mouse pointer), and no reactions to keyboard/mouse input (including hotkeys to e.g. control the backlight) occur. However, audio playback appears to continue, and I can still trigger a shutdown of the machine with a regular (short) power button press. So part of the machine seems to continue operating. asahi-diagnose attached below (note: this is taken after a reboot following one such freeze, not when the machine is in the "frozen" state). I'll try to confirm if I can ssh into the machine next time this happens to see whether dmesg reports anything.. |
|
Above problem happened again (while watching a Youtube video in Firefox, FWIW). No special GPU tricks for Firefox in place, only |
|
The KDE Bluetooth applet in the task bar is slow on the edge kernel with Wayland. Clicking it takes about a second to reveal, which is kind of annoying. It is not slow if:
This could of course be a KDE bug, but it's interesting that it only happens under these specific circumstances. EDIT: this also seems to affect the notifications applet. When there is a notification, it is slow, but after clearing them it is fast. |
|
Screen stays blank after locking it and trying to log in again journalctl output (click to expand)I locked the screen around 17:08, that was the time I had to leave, since I was running to late already anyway. I wanted to log in again starting at 22:55:03. Like said the screen stayed black. Using a Macbook Pro M1 Pro |
|
dcp shuts down:
but doesn't comes up again until the reboot. kwin can't activate the screen:
Probably state issue in the dcp driver but impossible to say from the log. Did you try switch to a different VT with |
|
@jannau It just happened again! I didn't shut down my Macbook before I went to bed and when I wanted to login just 10 minutes ago, the same happened. I was NOT able to switch to a different VT via the Here are the logs againI think I locked the screen around 01:14 / 01:15 and tried to log in again around 07:00 (you can see at 07:00:26 how I trigger the forced shutdown by pressing the power key long time) Is it possible the energy saving settings have something to do with that? Screenshot
Unfortunately I did not have a ssh daemon running on my Macbook, so I couldn't log in from another machine. |
|
I can reproduce the black screen / failure to power it back on when KDE's night color makes display color temperature changes while the screen is off. This is a KDE bug. Fixed by https://invent.kde.org/plasma/kwin/-/merge_requests/3868 |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Physical display size reporting breaks after restarting Sway. This breaks default output scale calculation, which makes Sway reset to 1x scale after a restart. On the first time Sway is started: On the subsequent times Sway is started: Also see: swaywm/sway#7522 |
|
The USB-A ports on my Mac Studio seem to have regressed. Works fine on the non-edge kernel. I'm attempting to use that logitech dongle on the A port and it doesn't work. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
When I change the "HDMI ULTRA HD Deep Color" from "ON" to "OFF" (or from "OFF" to "ON") using my monitor OSD (I have a LG 32UK550) the display goes blank, and appears in the journal. full journal for the entire boot asahi-diagnose-20230727-223724.txt Let me know if there's more useful info I can provide. |
|
Not sure if this is a bug with Asahi or not, but BTRFS filesystems (e.g. USB NVMe) initialized on linux-asahi-edge do not appear to be readable by x86_64 systems due to page size incompatibility: [ 93924.924978] BTRFS: device fsid xxxx-xxxx-xxxx devid 1 transid 13 /dev/sdb1 scanned by (udev-worker) (5742) |
|
This is a btrfs-progs issue, not a kernel problem. They need to switch to 4K block size by default. There was a patch posted but I don't know if it's been applied yet. You can override the block size to 4K manually to work around it.
…On August 23, 2023 10:08:19 AM GMT+09:00, phansel ***@***.***> wrote:
Not sure if this is a bug with Asahi or not, but BTRFS filesystems (e.g. USB NVMe) initialized on linux-asahi-edge do not appear to be readable by x86_64 systems due to page size incompatibility:
[ 93924.924978] BTRFS: device fsid xxxx-xxxx-xxxx devid 1 transid 13 /dev/sdb1 scanned by (udev-worker) (5742)
[ 93935.187193] BTRFS info (device sdb1): using crc32c (crc32c-intel) checksum algorithm
[ 93935.187221] BTRFS error (device sdb1): sectorsize 16384 not yet supported for page size 4096
[ 93935.187240] BTRFS error (device sdb1): superblock contains fatal errors
[ 93935.190036] BTRFS error (device sdb1): open_ctree failed
--
Hector Martin "marcan" ***@***.***)
Public key: https://mrcn.st/pub
|
This comment was marked as off-topic.
This comment was marked as off-topic.
|
@cvrajagopal That has nothing to do with the kernel nor with us, it's a problem with Arch Linux ARM mirrors. We no longer support Arch Linux ARM for this among other reasons; please migrate to Fedora or ask on archlinuxarm.org. |
marcan
pushed a commit
that referenced
this issue
Jan 19, 2024
… when the system is sleeping Some channels may be masked. When the system is suspended, if these masked channels are not filtered out, this will lead to null pointer operations and system crash: Unable to handle kernel NULL pointer dereference at virtual address Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 user pgtable: 4k pages, 48-bit VAs, pgdp=0000000894300000 [00000000000002a0] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Modules linked in: CPU: 1 PID: 989 Comm: sh Tainted: G B 6.6.0-16203-g557fb7a3ec4c-dirty #70 Hardware name: Freescale i.MX8QM MEK (DT) pstate: 400000c5 (nZcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc: fsl_edma_disable_request+0x3c/0x78 lr: fsl_edma_disable_request+0x3c/0x78 sp:ffff800089ae7690 x29: ffff800089ae7690 x28: ffff000807ab5440 x27: ffff000807ab5830 x26: 0000000000000008 x25: 0000000000000278 x24: 0000000000000001 23: ffff000807ab4328 x22: 0000000000000000 x21: 0000000000000009 x20: ffff800082616940 x19: 0000000000000000 x18: 0000000000000000 x17: 3d3d3d3d3d3d3d3d x16: 3d3d3d3d3d3d3d3d x15: 3d3d3d3d3d3d3d3d x14: 3d3d3d3d3d3d3d3d x13: 3d3d3d3d3d3d3d3d x12: 1ffff00010d45724 x11: ffff700010d45724 x10: dfff800000000000 x9: dfff800000000000 x8: 00008fffef2ba8dc x7: 0000000000000001 x6: ffff800086a2b927 x5: ffff800086a2b920 x4: ffff700010d45725 x3: ffff8000800d5bbc x2 : 0000000000000000 x1 : ffff000800c1d880 x0 : 0000000000000001 Call trace: fsl_edma_disable_request+0x3c/0x78 fsl_edma_suspend_late+0x128/0x12c dpm_run_callback+0xd4/0x304 __device_suspend_late+0xd0/0x240 dpm_suspend_late+0x174/0x59c suspend_devices_and_enter+0x194/0xd00 pm_suspend+0x3c4/0x910 Fixes: 72f5801 ("dmaengine: fsl-edma: integrate v3 support") Signed-off-by: Xiaolei Wang <xiaolei.wang@windriver.com> Link: https://lore.kernel.org/r/20231113225713.1892643-2-xiaolei.wang@windriver.com Signed-off-by: Vinod Koul <vkoul@kernel.org>
|
hello! I'm having an issue on my Mac Studio M2 Max which sounds similar to some of the other HDMI suspend issues reported above. I figured I'd add my report and journal logs in case it assisted. great work all around by the way, amazing that it works at all considering the complexity and it's been working much beyond "at all" for me and straight into "pretty decent" note that I'm using NixOS unstable and not the official-like fedora. I adapted asahi-diagnose-20240205-225036.txt sequence of events:
this doesn't appear to happen if I just toggle the monitor input between HDMI and DP, so it seems the longer timing is important to trigger the issue. kernel log snippets:disconnect event:first reconnect:``` 80 2024-02-05T21:29:04.292853-0500 radiance kernel: apple-dcp 289c00000.dcp: DP2HDMI HPD irq, connected:1 79 2024-02-05T21:29:04.293439-0500 radiance kernel: apple-dcp 289c00000.dcp: dcp_dptx_connect(port=0) 78 2024-02-05T21:29:04.293724-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: AppleDCPDPTX.cpp:355: [AFK]powering nub 0x854670 77 2024-02-05T21:29:04.902849-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: DCPDP13Service.cpp:60: [AFK]version: 14 76 2024-02-05T21:29:04.903140-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: DCPDPService.cpp:76: [AFK]version: 14 75 2024-02-05T21:29:04.903406-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: AppleDCPPS190.cpp:78: [AFK]matched PS190: OUI 00.10.FA, DeviceID pHDMIg 74 2024-02-05T21:29:04.979843-0500 radiance kernel: apple-dcp 289c00000.dcp: DPTXPort: acking unhandled call 21 73 2024-02-05T21:29:04.982837-0500 radiance kernel: apple-dcp 289c00000.dcp: DPTXPort: acking unhandled call 15 72 2024-02-05T21:29:04.994849-0500 radiance kernel: apple-dcp 289c00000.dcp: set_drive_settings: 4:0:162:0:0:0:0 71 2024-02-05T21:29:05.012845-0500 radiance kernel: apple-dcp 289c00000.dcp: set_drive_settings: 4:0:164:0:0:0:0 70 2024-02-05T21:29:05.173846-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:135: IOMFB: IOAVVideoInterface published 69 2024-02-05T21:29:05.174144-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:714: IOMFBStatus VideoInterfaceIOAV::plug_gated(IOAVVideoInterface *, bool): display HPD asserted 68 2024-02-05T21:29:05.174381-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:135: IOMFB: IOAVVideoInterface published 67 2024-02-05T21:29:05.178839-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:714: IOMFBStatus VideoInterfaceIOAV::plug_gated(IOAVVideoInterface *, bool): display HPD asserted 66 2024-02-05T21:29:05.179108-0500 radiance kernel: apple-dcp 289c00000.dcp: TimingElements without valid modes! 65 2024-02-05T21:29:05.179838-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: oInterfaceIOAV.cpp:1701: Got peer ID 0 64 2024-02-05T21:29:05.180094-0500 radiance kernel: apple-dcp 289c00000.dcp: cb_hotplug() connected:1, valid_mode:0 63 2024-02-05T21:29:05.180318-0500 radiance kernel: apple-dcp 289c00000.dcp: dcp_hotplug() connected:1 valid_mode:0 nr_modes:0 62 2024-02-05T21:29:05.180836-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: oInterfaceIOAV.cpp:1701: Got peer ID 0 61 2024-02-05T21:29:05.181074-0500 radiance kernel: apple-dcp 289c00000.dcp: cb_hotplug() connected:1, valid_mode:0 60 2024-02-05T21:31:28.858850-0500 radiance kernel: apple-dcp 289c00000.dcp: DP2HDMI HPD irq, connected:0 59 2024-02-05T21:31:28.872845-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:146: IOMFB: IOAVVideoInterface terminated 58 2024-02-05T21:31:28.873258-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: oInterfaceIOAV.cpp:1094: void VideoInterfaceIOAV::unplug_gated(IOAVVideoInterface *): display HPD removed 57 2024-02-05T21:31:28.873550-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:146: IOMFB: IOAVVideoInterface terminated 56 2024-02-05T21:31:28.873784-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: oInterfaceIOAV.cpp:1094: void VideoInterfaceIOAV::unplug_gated(IOAVVideoInterface *): display HPD removed 55 2024-02-05T21:31:28.874835-0500 radiance kernel: apple-dcp 289c00000.dcp: cb_hotplug() connected:0, valid_mode:0 54 2024-02-05T21:31:28.875045-0500 radiance kernel: apple-dcp 289c00000.dcp: cb_hotplug() connected:0, valid_mode:0 53 2024-02-05T21:31:28.876831-0500 radiance kernel: apple-dcp 289c00000.dcp: DPTXPort: acking unhandled call 21 52 2024-02-05T21:31:28.877043-0500 radiance kernel: apple-dcp 289c00000.dcp: DPTXPort: acking unhandled call 20 51 2024-02-05T21:31:28.879832-0500 radiance kernel: apple-dcp 289c00000.dcp: dcp_hotplug() connected:0 valid_mode:0 nr_modes:0 50 2024-02-05T21:31:29.086837-0500 radiance kernel: apple-dcp 289c00000.dcp: DP2HDMI HPD irq, connected:1 49 2024-02-05T21:31:29.087057-0500 radiance kernel: apple-dcp 289c00000.dcp: dcp_dptx_connect(port=0) 48 2024-02-05T21:31:29.255840-0500 radiance kernel: apple-dcp 289c00000.dcp: DPTXPort: acking unhandled call 21 47 2024-02-05T21:31:29.257833-0500 radiance kernel: apple-dcp 289c00000.dcp: DPTXPort: acking unhandled call 15 46 2024-02-05T21:31:29.270833-0500 radiance kernel: apple-dcp 289c00000.dcp: set_drive_settings: 4:0:183:0:0:0:0 45 2024-02-05T21:31:29.287843-0500 radiance kernel: apple-dcp 289c00000.dcp: set_drive_settings: 4:0:185:0:0:0:0 44 2024-02-05T21:31:29.449845-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:135: IOMFB: IOAVVideoInterface published 43 2024-02-05T21:31:29.450073-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:714: IOMFBStatus VideoInterfaceIOAV::plug_gated(IOAVVideoInterface *, bool): display HPD asserted 42 2024-02-05T21:31:29.450271-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:135: IOMFB: IOAVVideoInterface published 41 2024-02-05T21:31:29.454832-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:714: IOMFBStatus VideoInterfaceIOAV::plug_gated(IOAVVideoInterface *, bool): display HPD asserted 40 2024-02-05T21:31:29.455137-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: oInterfaceIOAV.cpp:1701: Got peer ID 0 ```followed by many repeats of later reconnect attempts:``` 45 2024-02-05T21:31:29.605008-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: PPipeDCP_H13P.cpp:18011: Dual pipe disabled offset 0 44 2024-02-05T21:31:29.804841-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: nifiedPipeline.cpp:7700: set_mode: timingID: 40 colorID: 0 43 2024-02-05T21:31:29.805073-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: oInterfaceIOAV.cpp:1268: auto VideoInterfaceIOAV::set_mode(uint32_t, uint32_t, uint32_t *, uint32_t *, IOAVArray *, IOAVArray *)::(anonymous class)::ope 42 2024-02-05T21:31:29.805270-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: nifiedPipeline.cpp:7739: setmode failed 41 2024-02-05T21:31:29.805469-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: nifiedPipeline.cpp:7758: ERROR: Modeset done, but pipe not enabled: fSoftPowerState=1, fDisplayPowerState=0, fHardPowerState=1 40 2024-02-05T21:31:29.805674-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: nifiedPipeline.cpp:7465: set_digital_out_mode returned 80000104 39 2024-02-05T21:31:29.805889-0500 radiance kernel: apple-dcp 289c00000.dcp: set_digital_out_mode finished:8300 38 2024-02-05T21:31:29.806086-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: FramebufferDCP.cpp:1962: IOMFB: swap_submit_dcp: swallowed swap ID 2134056 as fControllerPowerState is 0 for External Display 37 2024-02-05T21:31:29.806284-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: FramebufferDCP.cpp:1967: IOMFB: swap_submit_dcp: swallowed swap ID 2134056 as timinsg are not enabled for External Display 36 2024-02-05T21:31:40.019838-0500 radiance kernel: apple-drm soc:display-subsystem: [drm] *ERROR* [CRTC:33:crtc-0] flip_done timed out 35 2024-02-05T22:21:27.471834-0500 radiance kernel: apple-dcp 289c00000.dcp: DP2HDMI HPD irq, connected:0 34 2024-02-05T22:21:27.485836-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:146: IOMFB: IOAVVideoInterface terminated 33 2024-02-05T22:21:27.485900-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: oInterfaceIOAV.cpp:1094: void VideoInterfaceIOAV::unplug_gated(IOAVVideoInterface *): display HPD removed 32 2024-02-05T22:21:27.485957-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:146: IOMFB: IOAVVideoInterface terminated 31 2024-02-05T22:21:27.486830-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: oInterfaceIOAV.cpp:1094: void VideoInterfaceIOAV::unplug_gated(IOAVVideoInterface *): display HPD removed 30 2024-02-05T22:21:27.486878-0500 radiance kernel: apple-dcp 289c00000.dcp: cb_hotplug() connected:0, valid_mode:1 29 2024-02-05T22:21:27.486922-0500 radiance kernel: apple-dcp 289c00000.dcp: cb_hotplug() connected:0, valid_mode:0 28 2024-02-05T22:21:27.488823-0500 radiance kernel: apple-dcp 289c00000.dcp: DPTXPort: acking unhandled call 21 27 2024-02-05T22:21:27.489822-0500 radiance kernel: apple-dcp 289c00000.dcp: DPTXPort: acking unhandled call 20 26 2024-02-05T22:21:27.491828-0500 radiance kernel: apple-dcp 289c00000.dcp: dcp_hotplug() connected:0 valid_mode:0 nr_modes:37 25 2024-02-05T22:21:27.492825-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: FramebufferDCP.cpp:1962: IOMFB: swap_submit_dcp: swallowed swap ID 2134057 as fControllerPowerState is 0 for External Display 24 2024-02-05T22:21:27.493058-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: FramebufferDCP.cpp:1967: IOMFB: swap_submit_dcp: swallowed swap ID 2134057 as timinsg are not enabled for External Display 23 2024-02-05T22:21:27.493317-0500 radiance kernel: apple-dcp 289c00000.dcp: dcp_poweroff() done 22 2024-02-05T22:21:27.496837-0500 radiance kernel: apple-dcp 289c00000.dcp: dcp_dptx_disconnect(port=0) 21 2024-02-05T22:21:27.497192-0500 radiance kernel: apple-dcp 289c00000.dcp: DPTXPort: acking unhandled call 21 20 2024-02-05T22:21:27.698835-0500 radiance kernel: apple-dcp 289c00000.dcp: DP2HDMI HPD irq, connected:1 19 2024-02-05T22:21:27.699114-0500 radiance kernel: apple-dcp 289c00000.dcp: dcp_dptx_connect(port=0) 18 2024-02-05T22:21:27.699332-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: AppleDCPDPTX.cpp:355: [AFK]powering nub 0x854670 17 2024-02-05T22:21:28.308842-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: DCPDP13Service.cpp:60: [AFK]version: 14 16 2024-02-05T22:21:28.309082-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: DCPDPService.cpp:76: [AFK]version: 14 15 2024-02-05T22:21:28.309293-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: AppleDCPPS190.cpp:78: [AFK]matched PS190: OUI 00.10.FA, DeviceID pHDMIg 14 2024-02-05T22:21:28.384844-0500 radiance kernel: apple-dcp 289c00000.dcp: DPTXPort: acking unhandled call 21 13 2024-02-05T22:21:28.386834-0500 radiance kernel: apple-dcp 289c00000.dcp: DPTXPort: acking unhandled call 15 12 2024-02-05T22:21:28.399839-0500 radiance kernel: apple-dcp 289c00000.dcp: set_drive_settings: 4:0:213:0:0:0:0 11 2024-02-05T22:21:28.416841-0500 radiance kernel: apple-dcp 289c00000.dcp: set_drive_settings: 4:0:215:0:0:0:0 10 2024-02-05T22:21:28.579841-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:135: IOMFB: IOAVVideoInterface published 9 2024-02-05T22:21:28.580053-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:714: IOMFBStatus VideoInterfaceIOAV::plug_gated(IOAVVideoInterface *, bool): display HPD asserted 8 2024-02-05T22:21:28.580264-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:135: IOMFB: IOAVVideoInterface published 7 2024-02-05T22:21:28.583832-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: eoInterfaceIOAV.cpp:714: IOMFBStatus VideoInterfaceIOAV::plug_gated(IOAVVideoInterface *, bool): display HPD asserted 6 2024-02-05T22:21:28.584832-0500 radiance kernel: apple-dcp 289c00000.dcp: TimingElements without valid modes! 5 2024-02-05T22:21:28.585064-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: oInterfaceIOAV.cpp:1701: Got peer ID 0 4 2024-02-05T22:21:28.585274-0500 radiance kernel: apple-dcp 289c00000.dcp: cb_hotplug() connected:1, valid_mode:0 3 2024-02-05T22:21:28.585492-0500 radiance kernel: apple-dcp 289c00000.dcp: dcp_hotplug() connected:1 valid_mode:0 nr_modes:0 2 2024-02-05T22:21:28.586834-0500 radiance kernel: apple-dcp 289c00000.dcp: RTKit: syslog message: oInterfaceIOAV.cpp:1701: Got peer ID 0 1 2024-02-05T22:21:28.587033-0500 radiance kernel: apple-dcp 289c00000.dcp: cb_hotplug() connected:1, valid_mode:0 4 ``` |
|
I am seeing a similar issue to @Dridus and I'm on Fedora Remix. I can try to dump some log as well (if there's any instructions on how that would be appreciated) if it helps to diagnose. |
|
When building asahi-6.8.10-4 with rust 1.77.2, these warnings occur:
|
|
Edge is no longer a thing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
This is a global tracker bug to group reports related to
linux-asahi-edge. Since this is a bleeding-edge kernel, we know some things are broken and we make no promises that we'll get to reports in any amount of time. Please post any issues as comments on this bug, and we'll handle them or break them out into their own bugs as we deem appropriate. Please do not open new bugs forlinux-asahi-edgeissues that are not reproducible with the defaultlinux-asahikernel.Only report issues here if they happen with
linux-asahi-edgeand NOT withlinux-asahi. If you find a problem unrelated to the new features oflinux-asahi-edge, you must test across at least 5 reboots onlinux-asahito make sure it never happens there and is truly a regression related tolinux-asahi-edge.Please make sure you have updated all your packages and have
asahi-metainstalled before reporting anything. Setups withoutasahi-metainstalled are not supported and are expected to randomly break as we make changes to our packages. All Asahi installs since the first official alpha release come withasahi-metapreinstalled (and alsoasahi-desktop-metafor the desktop builds). If you choose to uninstall our infrastructure packages, you are on your own and we cannot provide support.Known issues:
When writing a comment, please run
asahi-diagnoseand attach the resulting logfile.The text was updated successfully, but these errors were encountered: