You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use the lastest NomadBSD and after the major update (2023/01/08) Xorg use more CPU and NomadBSD is slow
I reinstalled NomadBSD from the beginning, after reboot "picom" is present twice in the autostart settings.
I removed "picom" from the autostart settings, only one remains and I don't have these slowness anymore.
The package has been updated
picom: 9.1_1 → 10.2
For information, sometimes NomadBSD works normally, no slowness.
I tested on several PCs that have the graphics card (UHD Graphics 630).
Xorg uses too much CPU and is slow
nomad@NomadBSD$ fgrep LoadModule /var/log/Xorg.0.log
[ 39.050] (II) LoadModule: “glx”
[ 39.051] (II) LoadModule: “modesetting”
[ 39.073] (II) LoadModule: “glamoregl”
[ 39.181] (II) LoadModule: “fb”
[ 39.443] (II) LoadModule: “libinput”
Hi,
I use the lastest NomadBSD and after the major update (2023/01/08) Xorg use more CPU and NomadBSD is slow
I reinstalled NomadBSD from the beginning, after reboot "picom" is present twice in the autostart settings.
I removed "picom" from the autostart settings, only one remains and I don't have these slowness anymore.
The package has been updated
picom: 9.1_1 → 10.2
For information, sometimes NomadBSD works normally, no slowness.
I tested on several PCs that have the graphics card (UHD Graphics 630).
Xorg uses too much CPU and is slow
nomad@NomadBSD$ fgrep LoadModule /var/log/Xorg.0.log
[ 39.050] (II) LoadModule: “glx”
[ 39.051] (II) LoadModule: “modesetting”
[ 39.073] (II) LoadModule: “glamoregl”
[ 39.181] (II) LoadModule: “fb”
[ 39.443] (II) LoadModule: “libinput”
nomad@NomadBSD$ pciconf -lv
vgapci0@pci0:0:2:0: class=0x030000 rev=0x00 hdr=0x00 vendor=0x8086 device=0x3e91 subvendor=0x17aa subdevice=0x312d
vendor = ‘Intel Corporation’
device = ‘CoffeeLake-S GT2 [UHD Graphics 630]’
class = display
subclass = VGA
Bye
The text was updated successfully, but these errors were encountered: