[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 again |
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: