I did the installation from scratch so without using any of the Linux images proposed by Tuxedo.
I have been using Debian for more than 15 years (and various Linux distros for a lot longer) but I decided to try Arch Linux on this machine.
The CPU is an AMD Ryzen 7 8845HS with Radeon 780M Graphics
The native screen resolution is 2560x1600 @ 240.000 Hz
I do not expect too much problem since Tuxedo is mosty selling that laptop to Linux users.
- Edit
/etc/default/grub
to addacpi.ec_no_wakeup=1
inGRUB_CMDLINE_LINUX_DEFAULT
- and regenerate
/boot/grub/grub.cfg
withgrub-mkconfig -o /boot/grub/grub.cfg
TODO
This is because of the 2560x1600 resolution.
There are 2 ways to solve that problem:
- list all supported resolutions with videoinfo while in GRUB menu and then customize
GRUB_GFXMODE
in/etc/default/grub
- or use a different PF2 font by setting
GRUB_FONT
in/etc/default/grub
. The toolgrub-mkfont
can be used to generate the required PF2 font file from a standard font format such as TTF.
Reminder: After editing /etc/default/grub
, run grub-mkconfig -o /boot/grub/grub.cfg
See also
The integrated webcam appears as /dev/video0
with several controls and it seems to be working fine with kernel 6.6.59-1-lts
. The resolution is 1920x1080 but the quality is quite poor (especially in low light) but I was not expecting more from it.
The user must of course be in the group video
.
mpv --profile=low-latency --untimed av://v4l2:/dev/video0
v4l2-ctl -d /dev/video0 -l
The second video device /dev/video2
only provides a 640x360 «infrared» video stream without any controls.
It is intended for infrared face recognition.
No major issues. I ordered the US ISO layout.
In XKB configuration, set the layout to us(euro)
since the 5
key has the euro symbol.
Most Fn key combos are working and are properly reported as keyboard events and by sudo libinput debug-events
There are a few exceptions:
Fn+F3
. No idea what this is supposed to do.Fn+F9
will turn the screen off (press any key to restore). This is probably handled by the BIOS.Fn+F11
. This is probably supposed to disable the touchpad. Does nothing so far.Fn+F12
. Should toggle 'plane' mode and so turn off the WiFi. Does nothing so far.
The combo Fn+ESC
toggle Fn by default on the relevant keys (so its a Fn-lock)
Strangely, on that keyboard, the 'shift' characters are below the default characters. This is quite confusing at first.
Here is my preferred configuration for Sway
input "2362:597:UNIW0001:00_093A:0255_Touchpad" {
# disable touchpad while typing
dwt enabled
# allow tap
tap enabled
# two-fingers tap to paste (middle button)
tap_button_map lmr
# or press both physical buttons
middle_emulation enabled
# Scroll by sliding on the right edge
scroll_method edge
}
The touchpad is correct but not as good as my previous laptop.
An annoying issue is that it very close to the side of the laptop. So when I put the laptop on my thighs, the touchpad will something pick the heat of my body and behave strangely.
So far, I am using the following configuration for the HiDPI 2560x1600 screen. This is of course very subjective and some applications may still need to be fine tuned.
output eDP-1 {
mode 2560x1600@60Hz
position 0 0
scale 2
}
Note: A scaling factor of 2 is the «default» for HiDPI displays.
I also found that the following settings can help for some applications (Firefox, GTK, ...)
exec_always {
gsettings set org.gnome.desktop.interface text-scaling-factor 0.75
gsettings set org.gnome.desktop.interface cursor-size 16
}
Applications that use XWayland are pixelated in Sway. I am not sure if this is a Wayland issue, a Sway issue, an XWayland issue or a GTK issue. After reading swaywm/sway#7715 , this is unlikely to change soon.