Hi all. Everything has been working relatively smoothly on gnome 45.5 except gnome’s nightlight feature. I am wondering if any of you are experiencing the same issue? My kernel is the latest linux 6.8.7.
2 Likes
Update: Gnome 46 fixes the issue with adjusting night light if color profiles were configured for the two monitors. However, it is impossible to import icc files in Settings in Gnome 46. Additionally, touch screen configuration is still broken in Gnome 46. It is impossible to use the stylus on the second screen, as all inputs still map to the first screen even on the second screen.
2 Likes
The reason is that there is no Wayland protocol for display management that everyone implements. The only one as far as I know is wlr-output-management-unstable-v1 which is used by wlroots-based compositors, but neither GNOME nor KDE implement it. I use GNOME, so I had to use GNOME-specific tool for this. It should be reasonably easy to add similar functionality for KDE or wlroots-based compositors, just add equivalent commands for KDE to those scripts and submit a pull-request.
After recent nixpkgs-unstable pull we got the kernel 6.9 and the bottom display is completely black with it (everything behaves as if it’s attached and working, but it’s just black whatever you try to do, including modifying brightness for it). For now I just replaced boot.kernelPackages = pkgs.linuxPackages_latest; in my config with boot.kernelPackages = pkgs.linuxPackages_6_8; but it would be good if someone can figure out what’s wrong and make 6.9 work.
1 Like
I can replicate this as well. I should be able to look into it in a week or so if no-one else has by then.
I bumped up to 6.9 briefly as well, but encountered a different problem – the laptop wouldn’t sleep when the lid closed. I haven’t had time to dig into that as well, and I seem to have lost the relevant logs, but it’s another issue to be aware of.
Version 306 of the UEFI firmware is available through the MyASUS app. There’s no changelog yet, but I’ve noticed two immediate improvements: UEFI GOP performance is much better (so boot menus appear faster), and the lag shortly after booting that many were experiencing seems to be gone.
I’m using Arch instead but also notice the kernel 6.9 and 6.10 (mainline) doesn’t seem to work. dmesg have a lot of assert errors in i915 driver and the entire system is very slow to respond. Wondering if ya’ll using nix have the same issue with newer kernel as well.
Many thanks for sharing. I was able to to implement all of these on Ubuntu 24.04 which solved most of my driver issue.
There is a large annoyance that remains and I can’t figure out how to solve it. When the keyboard is attached (single-monitor mode), the OS successfully ignores input to touchpad while typing (to prevent accidental inputs). But in detached mode (dual screen), the touchpad continues to provide input while typing. Given the substantial size of the touchpad, it becomes almost impossible to continue a paragraph without hitting other things.
Anyone else experiencing this?
2 Likes
Hello, took me at surprise that you are saying that you have mostly everything working on Ubuntu 24.04, i still have problems with
- Toggling monitors ( err: Failed to set configuration … Logical monitors not adjacent)
- Sync of brightness ( was low on priority list )
- Still bluetooth keyboard won’t connect but i expect this is due to my not familiarity with linux
- And on some upgrade the sound is disappearing due to some driver updates, which supposedly happened automatically at some point
Could you tell if there are some guides you used beside this one and alesya-h’s script guide?
Hello, for the bluetooth keyboard just press f10 for 5 seconds, you will see some lighting and that will set the pair mode on.
Thanks i did not know that, after pressing the button i first time noticed it named in my bluetoothctl and it is paired, have to turn it on manually after taking it off, and sound also appeared again out of nowhere.
1 Like
nixpkgs 24.05 - Kernel 6.8 - Plasma6.
Other then keyboard attach / de-attach being mapped to rfkill command (basically toggles wifi on / off on plasma), everything works out of the box:
- Screen brightness Sync - Works
- Screen Position must be configured, but once that’s done, turning the secondary screen on or off is just a matter of ‘kscreen-doctor output.eDP-2.enable’ or disable. Plasma memorizes the position.
I think there’s a problem with SDDM though. But I’m using GDM. Doesn’t really matter, I use luks and have a password prompted for the FS encryption, so I just use GDM in auto login mode.
1 Like
You have to tune the shell script according to your screen resolution. I think the author machine has the lower res screen with 1030 pixels height. You need to change the offset inside the script to your appropriate value (probably 1800).
What happens is that the script try to setup the screens virtually one above the other, so you can jump between them naturally with your cursor. But since the height don’t match if you don’t adjust the script, there will be no adjacency (or a shared border) between the screens.
1 Like
Has anyone found a way to change the backlight?
For toggling monitors are you referring to automatic toggle upon keyboard detach? The original repo here covers it all. You mentioned you’re new to linux, if so my own git may help as I’ve already compiled the monitor config for Ubuntu 24.04. Please read and follow through the first section of this repo
Yes it works, thank you! Now disabled automatic light because it was flickering and trying to find the right method to launch initial set-displays command.
Sorry I realized I pasted the wrong link. Please read my comment above again (second link replaced). The step #9 of the first section addresses your issue.
As for the flickering, are you using the 3k version of this laptop (185h CPU) or the 1080p (155h) version?
Your step 9 works, thank you. By the way i am using set-displays on startup and toggle on the keyboard wlan key, and it seems to work flawlessly. I have 185h, could probably go through the auto bright ess setup in your writeup.
Yeah keep me posted on that flickering issue. I’m actually considering swapping my 155h version with 185h. Not super happy with CPU performance and the display somehow hurts my eyes. Hopefully the 3K version is better.