xorg issueshttps://gitlab.freedesktop.org/groups/xorg/-/issues2022-02-08T10:04:53Zhttps://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/131the Greek phi symbol does not print when CapsLock is on2022-02-08T10:04:53ZRay Vinethe Greek phi symbol does not print when CapsLock is onOn the Greek keyboard, the 3rd level character on the <AC04> key, unicode point U03D5, doesn't print when Caps Lock is on.
This is the Greek phi *symbol* which is mapped in KeyBind.c, Greek_upper_mapping[&zwj;&ThinSpace;&zwj;], to 0...On the Greek keyboard, the 3rd level character on the <AC04> key, unicode point U03D5, doesn't print when Caps Lock is on.
This is the Greek phi *symbol* which is mapped in KeyBind.c, Greek_upper_mapping[‍ ‍], to 0x03A6, the Greek capital letter PHI.
For the key sequences AltGr+‍<AC04> Caps+AltGr+‍<AC04>, the print out is ϕ , which should be ϕ Φ.
The problem seems to be related to the 1st & 2nd level characters on that key also being phi - Greek_phi & Greek_PHI, φ & Φ, unicode points U+03C6 & U+03A6.
Assign code point U03D5 to another key, say <AC06> which is the Greek_eta & Greek_ETA key, and the print out for AltGr+‍<AC06> Caps+AltGr+‍<AC06> is correct, ie ϕ Φ - ***and*** then it also starts working from the <AC04> key!https://gitlab.freedesktop.org/xorg/xserver/-/issues/604Have to type on internal keyboard to get proper layout2022-02-06T14:39:04ZBugzilla Migration UserHave to type on internal keyboard to get proper layout## Submitted by Samuel Thibault `@sthibaul`
Assigned to **Xorg Project Team**
**[Link to original bug (#26402)](https://bugs.freedesktop.org/show_bug.cgi?id=26402)**
## Description
Created attachment 33017
xev log
Hello,
I've re...## Submitted by Samuel Thibault `@sthibaul`
Assigned to **Xorg Project Team**
**[Link to original bug (#26402)](https://bugs.freedesktop.org/show_bug.cgi?id=26402)**
## Description
Created attachment 33017
xev log
Hello,
I've recently upgraded my laptop to Xorg 7.5, and since then by default
the layout of my external USB keyboard is qwerty, and as soon as I type
something on the internal keyboard, the layout switches to the expected
azerty layout. I'm attaching an xev log: I've typed the external 'a'
key, then the internal 'a' key, then the external 'a' key again.
Samuel
**Attachment 33017**, "xev log":
[xev](/uploads/38d182509984a8abcf5851445de91acf/xev)
Version: githttps://gitlab.freedesktop.org/xorg/xserver/-/issues/1295xorg-server-21.1.3 does not display fonts correctly as compared to 1.20.112022-02-05T09:53:33ZJohn Frankishxorg-server-21.1.3 does not display fonts correctly as compared to 1.20.11I'm trying to update from xorg-server-1.20.11 to xorg-server-21.1.3, but the fonts do not display correctly.
At first xorg-server-21.1.3 will not start:
```
[ 264.459] (WW) `fonts.dir' not found (or not valid) in "/usr/local/lib/X11/...I'm trying to update from xorg-server-1.20.11 to xorg-server-21.1.3, but the fonts do not display correctly.
At first xorg-server-21.1.3 will not start:
```
[ 264.459] (WW) `fonts.dir' not found (or not valid) in "/usr/local/lib/X11/fonts").
[ 264.459] Entry deleted from font path.
[ 264.459] (Run 'mkfontdir' on "/usr/local/lib/X11/fonts").
[ 264.459] (==) FontPath set to:
```
Note that the fonts are a loop mounted squashfs package symlinked to the root fs and the fonts.dir files are one level down in 75dpi, TTF, Type1, misc, etc, which xorg-server-1.20.11 has no problem with.
Anyway, after "sudo mkfontdir /usr/local/lib/X11/fonts", which creates fonts.dir containing "0", xorg-server-21.1.3 starts with:
```
$ sudo mkfontdir /usr/local/lib/X11/fonts
[ 4113.857] (==) FontPath set to:
/usr/local/lib/X11/fonts
```
..but fonts do not display correctly - is it possible that xorg-server-21.1.3 does not follow symlinks?
Note that with xorg-server-1.20.11:
```
[ 94.062] (==) FontPath set to:
/usr/local/lib/X11/fonts/misc/,
/usr/local/lib/X11/fonts/TTF/,
/usr/local/lib/X11/fonts/Type1/,
/usr/local/lib/X11/fonts/75dpi/
```https://gitlab.freedesktop.org/xorg/xserver/-/issues/1281graphical server crash while using BitwigStudio-4.1.2, maybe related to vsync...2022-02-04T07:35:08ZAlexandre Biquegraphical server crash while using BitwigStudio-4.1.2, maybe related to vsync/present extensionHi,
I've got an up to date Archlinux installation.
xorg-server-21.1.3-1
nvidia-dkms-495.46-1
openbox-3.6.1-8
Steps:
1. flatpak install com.bitwig.BitwigStudio
2. flatpak run com.bitwig.BitwigStudio
```
[root@knot abique]# coredumpctl...Hi,
I've got an up to date Archlinux installation.
xorg-server-21.1.3-1
nvidia-dkms-495.46-1
openbox-3.6.1-8
Steps:
1. flatpak install com.bitwig.BitwigStudio
2. flatpak run com.bitwig.BitwigStudio
```
[root@knot abique]# coredumpctl gdb
PID: 1017 (Xorg)
UID: 1000 (abique)
GID: 1000 (abique)
Signal: 6 (ABRT)
Timestamp: Tue 2022-01-04 15:30:10 CET (3min 32s ago)
Command Line: /usr/lib/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3
Executable: /usr/lib/Xorg
Control Group: /user.slice/user-1000.slice/session-3.scope
Unit: session-3.scope
Slice: user-1000.slice
Session: 3
Owner UID: 1000 (abique)
Boot ID: 9e1961d92135478d8e876611c93a4677
Machine ID: 0ea2984942fd4ea1bc4b2ae62006bec7
Hostname: knot
Storage: /var/lib/systemd/coredump/core.Xorg.1000.9e1961d92135478d8e876611c93a4677.1017.1641306610000000.zst (present)
Disk Size: 25.7M
Message: Process 1017 (Xorg) of user 1000 dumped core.
Module linux-vdso.so.1 with build-id 58148cd38d5f960415b6503de0114713cc1c971a
Module libnss_files.so.2 with build-id 1a36dfc01d3a1010b2ee79766a24a8090a3266d5
Module libffi.so.8 with build-id f90d8b734f6de9b25faedb8cbfab7054dafc0a42
Module libgobject-2.0.so.0 with build-id 3e451709a0a5772b9550d3a4c28dcb37a87028fa
Module libgudev-1.0.so.0 with build-id a9f734ea9206d637d5aacfbd86298c91cdc1a33a
Module libwacom.so.2 with build-id 1d9b89a6d39be5568d5f44888b8a74f46a30c152
Module libevdev.so.2 with build-id b62ae69f839f1b6b06ef2c1df19f25ff09b0d824
Module libmtdev.so.1 with build-id 0cea2a842ae9a0ef02a08477076caab0e5ac5e42
Module libinput.so.10 with build-id e03db31785b31a4e48fde375cf7e13e3a6ad604a
Module libinput_drv.so with build-id d9f69f11259485316bd206e67e34dd23bbede5cc
Module libnvidia-glcore.so.495.46 with build-id 8113b84202e276df12ecc4fc58788506fd5ba386
Module libnvidia-tls.so.495.46 with build-id 59f61b3d522665be01a2429d278e7892f4e56e41
Module libglxserver_nvidia.so with build-id b448f7b6982718772d814f0b5fd3a01a9c226578
Module libwfb.so with build-id e7f4027f76d37b1d8a37119132fa7e68fbe757ed
Module libstdc++.so.6 with build-id 9b5eeeb149bf3c4efe787fb398b44f00507aec87
Module nvidia_drv.so with build-id c0f43c87bd9d909d127cd02f169aace2269ffe5d
Module libxcb.so.1 with build-id 0d1ef11740a5daad2ee331e812a51aa6574af222
Module libX11.so.6 with build-id 5ba5798d193c0065014b8c6252a0678671c8d478
Module libGLX.so.0 with build-id 2a08836c6e6126ce9ff4496b6aacaf29ae9b4e7b
Module libGLdispatch.so.0 with build-id 501765b3a78d668860fa54229b18107473aeda4c
Module libGL.so.1 with build-id 912ac4f37a9fa2d5abcf7a9088c9983cfe46f12a
Module libglx.so with build-id 6b205eec3a3ff50b171967e2bd104793f92ea0b3
Module libpcre.so.1 with build-id 845483dd0acba86de9f0313102bebbaf3ce52767
Module libbrotlicommon.so.1 with build-id a4ba3f4b4571c8272343b621da812a6e24a202a7
Module libglib-2.0.so.0 with build-id 8214b56e554b7cbead4034b6ba32c90bc8c674da
Module libgraphite2.so.3 with build-id 47761dc11e553f519cde97ed9ee985be12ccdae2
Module libresolv.so.2 with build-id c915c72668282861a813f7ea3c0780f37b681dc0
Module libkeyutils.so.1 with build-id ac405ddd17be10ce538da3211415ee50c8f8df79
Module libkrb5support.so.0 with build-id adf65240a4d2aba772d7a0772b4d015469934113
Module libcom_err.so.2 with build-id be99503e12b86d78d6ede2f0d1ffb66408a37576
Module libk5crypto.so.3 with build-id eb8220b8f36675aac769450be4cb6bb7f97ec38a
Module libkrb5.so.3 with build-id 72d26767c5cb1097db75a5f5bff88860233c902b
Module libgpg-error.so.0 with build-id 3801187d42c4955bd93c605451430cdf1b164e63
Module libbrotlidec.so.1 with build-id 45defc036e918e0140a72f1fbce6e7692d38241d
Module libharfbuzz.so.0 with build-id 1d9dee49dd99162c3f83eb3259c3c88c6b4cd7fe
Module libpng16.so.16 with build-id 2dc0bce07f199bf983c07a05fb95a6f4af83a9b3
Module libbz2.so.1.0 with build-id 919597c477c9b2cb9cdbb7745ed6494ac0e6da60
Module libgssapi_krb5.so.2 with build-id e6e098ad51ce7bdd3dbe902d7b0f69a90f8a9e08
Module libgcc_s.so.1 with build-id 7f8508bb914546ada778809b64b99d234337d835
Module libgcrypt.so.20 with build-id db45f5d5e0f7af1e77324fea1885f974619ad268
Module libcap.so.2 with build-id f56c6cd6ad4d35053340d7ff2f8f954498796739
Module liblz4.so.1 with build-id e63600ab23b2f6997f42fac2fa56e1f02ce159a1
Module libzstd.so.1 with build-id 6214183688018e3fba6d66db10c2c8d0b45e0578
Module liblzma.so.5 with build-id 8b615460aa230708c5183f16bede67aa0437d95e
Module librt.so.1 with build-id 75484da2d6f1515189eefa076e0a40328834cd16
Module libfreetype.so.6 with build-id 26c5f833068ff72660d1975cbc2074c3eb47fad8
Module libfontenc.so.1 with build-id 5a11f1fb8c3f2714be9eb6697318f20e301e1d2f
Module libz.so.1 with build-id 0c1459c56513efd5d53eb3868290e9afee6a6a26
Module ld-linux-x86-64.so.2 with build-id 040cc3dd10461562f177df39e3be2f3704258c3c
Module libc.so.6 with build-id 4b406737057708c0e4c642345a703c47a61c73dc
Module libxcvt.so.0 with build-id 30bad674c8227152bb709556a3657d0258554309
Module libpthread.so.0 with build-id 07c8f95b4f3251d08550217ad8a1f31066229996
Module libtirpc.so.3 with build-id 5bef2adfdee3df283f593b3e2d37b6dac405256a
Module libdrm.so.2 with build-id 457a1a1bd25f1d5541a10d3f16c5dc1440d77c7d
Module libudev.so.1 with build-id 10f0c06a98ef914275a2a3067cb7ccbfab69d558
Module libdbus-1.so.3 with build-id 74f2ab9c60512f3a93c932c3f627564d42e0b11e
Module libsystemd.so.0 with build-id 5e0c342d74b444cce6793925b41760cf298c417c
Module libxshmfence.so.1 with build-id 8876d9ccf620858795724ca24b9e567585a77cec
Module libXfont2.so.2 with build-id 154202dd7ddb86f6ae4d3bc762dfd8570b86882a
Module libXdmcp.so.6 with build-id 8ca0792d23c8b8b4c0864297512349292bea5955
Module libXau.so.6 with build-id 1c67764663e07bec24d8951e5fd93f4d165979ff
Module libnettle.so.8 with build-id 9a878e513c02007598fcf1e2e286c2203f13536e
Module libpciaccess.so.0 with build-id 9dd24e76ebc38465541313b36446ffb4af842c12
Module libdl.so.2 with build-id 5abc547e7b0949f89f3c0e21ab0c8331a7440a8a
Module libm.so.6 with build-id 2b8fd1f869ecab4e0b55e92f2f151897f6818acf
Module libpixman-1.so.0 with build-id 341f793dcada3a48a306a793d265a517e3f2e7d6
Module Xorg with build-id 54f45e59d2fb69e7a45684977b9a172ae1dd2730
Stack trace of thread 1017:
#0 0x00007fcb12622d22 raise (libc.so.6 + 0x3cd22)
#1 0x00007fcb1260c862 abort (libc.so.6 + 0x26862)
#2 0x00005641d85699b0 OsAbort (Xorg + 0x1539b0)
#3 0x00005641d856b4f5 FatalError (Xorg + 0x1554f5)
#4 0x00005641d8570eca n/a (Xorg + 0x15aeca)
#5 0x00007fcb127ca870 n/a (libpthread.so.0 + 0x13870)
Stack trace of thread 1032:
#0 0x00007fcb127c9600 __lll_lock_wait (libpthread.so.0 + 0x12600)
#1 0x00007fcb127c2580 __pthread_mutex_lock (libpthread.so.0 + 0xb580)
#2 0x00005641d855ee05 n/a (Xorg + 0x148e05)
#3 0x00005641d85695e1 n/a (Xorg + 0x1535e1)
#4 0x00005641d8565629 n/a (Xorg + 0x14f629)
#5 0x00007fcb127c0259 start_thread (libpthread.so.0 + 0x9259)
#6 0x00007fcb126e45e3 __clone (libc.so.6 + 0xfe5e3)
ELF object binary architecture: AMD x86-64
GNU gdb (GDB) 11.1
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/Xorg...
(No debugging symbols found in /usr/lib/Xorg)
warning: Can't open file /SYSV00000000 (deleted) during file-backed mapping note processing
warning: Can't open file /memfd:/.nvidia_drv.XXXXXX (deleted) during file-backed mapping note processing
[New LWP 1017]
[New LWP 1032]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/lib/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -nolisten tc'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007fcb12622d22 in raise () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7fcb11d63940 (LWP 1017))]
(gdb) bt
#0 0x00007fcb12622d22 in raise () at /usr/lib/libc.so.6
#1 0x00007fcb1260c862 in abort () at /usr/lib/libc.so.6
#2 0x00005641d85699b0 in System ()
#3 0x00005641d856b4f5 in FatalError ()
#4 0x00005641d8570eca in ()
#5 0x00007fcb127ca870 in <signal handler called> () at /usr/lib/libpthread.so.0
#6 0x0000000000000000 in ()
#7 0x00005641d84f49be in ()
#8 0x00005641d84f7b12 in ()
#9 0x00005641d84f6af6 in ()
#10 0x00005641d845330a in ()
#11 0x00007fcb1260db25 in __libc_start_main () at /usr/lib/libc.so.6
#12 0x00005641d845375e in _start ()
(gdb)
```
[Xorg.0.log](/uploads/d63966f76985dc236eab6c47278dac5e/Xorg.0.log)https://gitlab.freedesktop.org/xorg/xserver/-/issues/1285server-21.1.3: periodic mouse and keyboard freezes2022-02-03T15:24:04ZJose Marinoserver-21.1.3: periodic mouse and keyboard freezesAfter upgrade from xorg-server-21.1.2 to xorg-server-21.1.3 I started noticing periodic (very frequent) freezes in mouse pointer movement. Very annoying 1s or so long hiccups. This also affected the keyboard: some key presses would be sp...After upgrade from xorg-server-21.1.2 to xorg-server-21.1.3 I started noticing periodic (very frequent) freezes in mouse pointer movement. Very annoying 1s or so long hiccups. This also affected the keyboard: some key presses would be sporadically ignored. Mouse (both touchpad and wireless mouse) and keyboard (both wireless and laptop) were affected by the periodic freezes.
I see these errors in /var/log/Xorg.0.log:
```
[ 32484.997] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 32506.259] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 32506.858] (EE) event20 - Logitech K750: client bug: event processing lagging behind by 27ms, your system is too slow
[ 32527.525] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 32571.730] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 32606.586] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 32720.827] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 32744.832] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 32777.608] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 32810.145] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 32837.381] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 32866.189] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 32897.850] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 32933.146] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 32957.402] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 33001.786] (II) event12 - Logitech M325: SYN_DROPPED event - some input events have been lost.
[ 33027.554] (II) event6 - ASUE1209:00 04F3:319F Touchpad: SYN_DROPPED event - some input events have been lost.
[ 33027.554] (EE) client bug: timer event6 tap: scheduled expiry is in the past (-408ms), your system is too slow
[ 33027.554] (EE) client bug: timer event6 hold: scheduled expiry is in the past (-548ms), your system is too slow
[ 33052.071] (II) event6 - ASUE1209:00 04F3:319F Touchpad: SYN_DROPPED event - some input events have been lost.
[ 33074.423] (II) event6 - ASUE1209:00 04F3:319F Touchpad: SYN_DROPPED event - some input events have been lost.
[ 33074.423] (EE) client bug: timer event6 tap: scheduled expiry is in the past (-241ms), your system is too slow
[ 33074.423] (EE) client bug: timer event6 hold: scheduled expiry is in the past (-381ms), your system is too slow
[ 33096.410] (II) event6 - ASUE1209:00 04F3:319F Touchpad: SYN_DROPPED event - some input events have been lost.
[ 33096.410] (EE) client bug: timer event6 tap: scheduled expiry is in the past (-397ms), your system is too slow
[ 33096.410] (EE) client bug: timer event6 hold: scheduled expiry is in the past (-537ms), your system is too slow
[ 33118.818] (II) event6 - ASUE1209:00 04F3:319F Touchpad: SYN_DROPPED event - some input events have been lost.
[ 33169.539] (II) event6 - ASUE1209:00 04F3:319F Touchpad: SYN_DROPPED event - some input events have been lost.
[ 33169.539] (EE) client bug: timer event6 tap: scheduled expiry is in the past (-339ms), your system is too slow
[ 33169.539] (EE) client bug: timer event6 hold: scheduled expiry is in the past (-479ms), your system is too slow
[ 33175.708] (EE) event20 - Logitech K750: client bug: event processing lagging behind by 23ms, your system is too slow
```
ASUE1209:00 is the laptop's touchpad. Logitech M325 is the wireless mouse. Logitech K750 is the wireless keyboard.
I have downgraded to xorg-server-21.1.2 and the freezes go away.
Laptop is ASUS ROG Zephyrus G15 GA503QR with AMD Ryzen 9 5900HS processor.
I run ArchLinux:<br/>
linux-5.15.12.arch1-1<br/>
libinput-1.19.3-1<br/>
xf86-input-libinput-1.2.0-2<br/>https://gitlab.freedesktop.org/xorg/xserver/-/issues/707Xwayland refresh rate reported by xrandr is incorrect2022-02-03T08:50:19ZBugzilla Migration UserXwayland refresh rate reported by xrandr is incorrect## Submitted by Daniel van Vugt `@vanvugt`
Assigned to **Wayland bug list**
**[Link to original bug (#102721)](https://bugs.freedesktop.org/show_bug.cgi?id=102721)**
## Description
Xwayland refresh rate reported by 'xrandr' is inc...## Submitted by Daniel van Vugt `@vanvugt`
Assigned to **Wayland bug list**
**[Link to original bug (#102721)](https://bugs.freedesktop.org/show_bug.cgi?id=102721)**
## Description
Xwayland refresh rate reported by 'xrandr' is incorrect:
1920x1200 59.88*+
Actually my display runs at 59.95Hz, as confirmed by 'weston-info'.
If Xwayland is reporting the wrong frequency to apps via Xrandr then apps and toolkits implementing frame clocks (i.e. not synchronously tied to swap buffers) may animate at the wrong frequency, causing some stuttering and skipped frames.
### See also
* https://launchpad.net/bugs/1717155https://gitlab.freedesktop.org/xorg/xserver/-/issues/1172Xserver/modesetting/glamor/intel: double/triple buffering issue results in fl...2022-01-31T22:09:59ZYuriXserver/modesetting/glamor/intel: double/triple buffering issue results in flicker and outdated screen contentOn Xorg 1.20.11 (debian unstable) with an intel i7-10610U CML GT2, modesetting driver + glamor, the screen frequently swaps between what looks like the front and a backbuffer.
This is made apparent when using X11 _without_ a compositor....On Xorg 1.20.11 (debian unstable) with an intel i7-10610U CML GT2, modesetting driver + glamor, the screen frequently swaps between what looks like the front and a backbuffer.
This is made apparent when using X11 _without_ a compositor. Typing or scrolling into a window shows cyclically the image of ~0.25 seconds ago and the actual image.
Also worsens further (becoming basically unusable) when the laptop in on battery, probably due to some power-saving feature reducing frame updates.
This is on a Dell 7410 with an intel i7-10610U, CML GT2, modesetting driver, glamor enabled: this is the default config from debian unstable. Kernel tested between 5.10.24-5.10.28, Xorg 1.20.10-1.20.11.https://gitlab.freedesktop.org/xorg/driver/xf86-video-omap/-/issues/1xf86-video-omap access request2022-01-30T23:46:32ZBugzilla Migration Userxf86-video-omap access request## Submitted by Robert Nelson
Assigned to **fd.o Admin Massive**
**[Link to original bug (#87115)](https://bugs.freedesktop.org/show_bug.cgi?id=87115)**
## Description
Created attachment 110583
gpg public key
Access request for g...## Submitted by Robert Nelson
Assigned to **fd.o Admin Massive**
**[Link to original bug (#87115)](https://bugs.freedesktop.org/show_bug.cgi?id=87115)**
## Description
Created attachment 110583
gpg public key
Access request for git access to xf86-video-omap for beagleboard.org
**Attachment 110583**, "gpg public key":
[rcn-ee-gpg.pub](/uploads/38893943397a1aa4bb091553af2f7fc2/rcn-ee-gpg.pub)
Version: githttps://gitlab.freedesktop.org/xorg/driver/xf86-video-tseng/-/issues/2Broken struct2022-01-30T20:12:53ZRobert BrownBroken struct@see this commit - https://gitlab.freedesktop.org/xorg/xserver/-/commit/5a945f54e738f6e9c5a489febdd8b87cd8a41210
It remmoved maxHValue and maxVValue from struct _ScrnInfoRec in the xf86str.h include file. The primary driver file in this...@see this commit - https://gitlab.freedesktop.org/xorg/xserver/-/commit/5a945f54e738f6e9c5a489febdd8b87cd8a41210
It remmoved maxHValue and maxVValue from struct _ScrnInfoRec in the xf86str.h include file. The primary driver file in this repo, tseng_drivers.c, still references those values and fails to compile.
I created a simple patch to remove those values and instead use the already-set versions of them. That allows it to build.
[tseng.patch](/uploads/b62b698e2ab0d18af7b181f8f384feb8/tseng.patch)
I'm relatively clueless as to how this bit of code works or the implications but I'll test and report back. I intentionally did not submit a merge, a code review here would be needed given my rusty dev skills.https://gitlab.freedesktop.org/xorg/lib/libxres/-/issues/3Bugs regarding the allocation of XResClientIdValue::value in ReadClientValues...2022-01-30T17:01:36ZDaniel AbrechtBugs regarding the allocation of XResClientIdValue::value in ReadClientValues, which is used in XResQueryClientIdsThis is about these two lines of code: https://gitlab.freedesktop.org/xorg/lib/libxres/-/blob/97d312e5fd9b4b97e3f50c899a40325768f246a5/src/XRes.c#L258-259
I think there isn't enough memory allocated for the `_XRead32`. If I understand t...This is about these two lines of code: https://gitlab.freedesktop.org/xorg/lib/libxres/-/blob/97d312e5fd9b4b97e3f50c899a40325768f246a5/src/XRes.c#L258-259
I think there isn't enough memory allocated for the `_XRead32`. If I understand that function correctly, while it reads the number of bytes specified, it returns/writes one long for every 32bit of data. On a 64bit system, a long is usually 8 bytes big. The memory allocated is only the number of bytes read, not the number of space the long values would need. This causes twice as much memory to be overwritten as was allocated on 64bit system.
Another thing which seams odd to me about this is that the memory is allocated there, and not in `XResQueryClientIds` as part of the memory allocated for the `client_ids`. Is the caller of `XResQueryClientIds` really supposed to free all these values by himself?
And the last thing I wonder about, why is `XResClientIdValue::value` of type `void*`, shouldn't it be of type `long*`?
According to the spec here: https://www.x.org/releases/X11R7.7/doc/resourceproto/resproto.txt
It says `client_ids: LISTofCLIENTIDVALUE` and
```
CLIENTIDVALUE [ spec: CLIENTIDSPEC
length: CARD32
value: LISTofCARD32 ]
```
And I think `CARD32` seams to usually be translated to a long in the libraries other data structures?
(Closed previous identical issue 2 which I marked as confidential because noone responded to it in over a month and I can't unmark it anymore.)https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/41GPU artifcats since xf86-video-amdgpu-21.0.0 (bisected)2022-01-29T17:41:38ZDor AskayoGPU artifcats since xf86-video-amdgpu-21.0.0 (bisected)Since `xf86-video-amdgpu-21.0.0`, a corruption is seen in some fullscreen games. It's also seen when logging out of the desktop session or switching focus between fullscreen games.
It reproduces consistently in Brutal Legend (Steam), in...Since `xf86-video-amdgpu-21.0.0`, a corruption is seen in some fullscreen games. It's also seen when logging out of the desktop session or switching focus between fullscreen games.
It reproduces consistently in Brutal Legend (Steam), in what appears like every frame:
![IMG_20210821_002152](/uploads/3ded3c8ce1459d01ba2e0c758e0b4209/IMG_20210821_002152.jpg)
I bisected it to the following commit:
```
git bisect start
# bad: [0d68a91dce88eeacd15bf1159ddc6200a01b1f2e] Bump version for the 21.0.0 release
git bisect bad 0d68a91dce88eeacd15bf1159ddc6200a01b1f2e
# good: [b467d2569a003da05ad222b0dc095bee5eec450a] Bump version for the 19.1.0 release
git bisect good b467d2569a003da05ad222b0dc095bee5eec450a
# good: [e2cd67abb4aa8b5c942b46dd66dac091b9fad7ad] Bail from amdgpu_pixmap_get_handle with ShadowFB
git bisect good e2cd67abb4aa8b5c942b46dd66dac091b9fad7ad
# bad: [442efe73dd579dc36445a3b232937abbed9d2fbb] Make drmmode_crtc_scanout_create/destroy static
git bisect bad 442efe73dd579dc36445a3b232937abbed9d2fbb
# bad: [e923642bae6077f71a8f251fe885342757737224] gitlab CI: update to use the latest CI templates
git bisect bad e923642bae6077f71a8f251fe885342757737224
# bad: [0732f81a2c67354ddfa7a495bee6b0997c6ef244] glamor: Make pixmap scanout compatible if its dimensions are
git bisect bad 0732f81a2c67354ddfa7a495bee6b0997c6ef244
# good: [cb27a5b1120266e4baaa3eb784ff041977ded43f] Handle NULL fb_ptr in pixmap_get_fb
git bisect good cb27a5b1120266e4baaa3eb784ff041977ded43f
# first bad commit: [0732f81a2c67354ddfa7a495bee6b0997c6ef244] glamor: Make pixmap scanout compatible if its dimensions are
```
```
commit 0732f81a2c67354ddfa7a495bee6b0997c6ef244 (HEAD, refs/bisect/bad)
Author: Michel Dänzer <mdaenzer@redhat.com>
Date: Tue Apr 21 10:54:47 2020 +0200
glamor: Make pixmap scanout compatible if its dimensions are
Namely, if its dimensions match those of the screen pixmap (enough that
it could stand in for it). When that's the case, the pixmap may end up
being scanned out directly due to page flipping via the Present
extension, e.g. with xfwm4 --vblank=xpresent .
v2:
* Use AMDGPU_CREATE_PIXMAP_SCANOUT instead of second-guessing in
amdgpu_alloc_pixmap_bo, fixes corruption when resizing from smaller
to larger virtual size via RandR.
Closes: https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/10
```
OS: Fedora 34 (GNOME 40, Xorg session)
GPU: RX 580
Mesa: 21.1.4 (Running on Flatpak)
Kernel: 5.13.10-200.fc34
Log from 0732f81a2c67354ddfa7a495bee6b0997c6ef244: [Xorg.0.log](/uploads/cd65ce7ec6f50d391650a55a37e8eab2/Xorg.0.log)
CC: @daenzer, @agd5fhttps://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/132the case conversions for Greek symbols are incomplete2022-01-27T22:10:41ZRay Vinethe case conversions for Greek symbols are incompleteRe: KeyBind.c#293 /* Case conversion for UCS, as in Unicode Data version 4.0.0 */
There is currently no entry for the Greek dotted lunate sigma symbols, ͼ & Ͼ, U037C & U03FE.
03FE first appeared in UnicodeData-4.1.0.txt and 037C in Un...Re: KeyBind.c#293 /* Case conversion for UCS, as in Unicode Data version 4.0.0 */
There is currently no entry for the Greek dotted lunate sigma symbols, ͼ & Ͼ, U037C & U03FE.
03FE first appeared in UnicodeData-4.1.0.txt and 037C in UnicodeData-5.0.0.txt
This results in the printout for these characters on key <AC07> of the Greek basic keyboard for the key sequence
```
AltGr Caps+AltGr AltGr+Shift Caps+AltGr+Shift
```
being
```
ͼ ͼ Ͼ Ͼ
```
I.e. no case toggle for Caps Lock
I don't know how the mapping tables are generated, so haven't tested with a newer version of Unicode, but patching Greek_upper_mapping[‍ ‍] and Greek_lower_mapping[‍ ‍], the print output then toggles with Caps Lock
```
ͼ Ͼ Ͼ ͼ
```
```diff
--- src/KeyBind.c
+++ src/KeyBind.c
@@ -340 +340 @@
- 0x0000, 0x0000, 0x037A, 0x0000, 0x0000, 0x0000, 0x037E, 0x0000,
+ 0x0000, 0x0000, 0x037A, 0x0000, 0x03FE, 0x0000, 0x037E, 0x0000,
@@ -356 +356 @@
- 0x03F7, 0x03F9, 0x03FA, 0x03FA, 0x0000, 0x0000, 0x0000, 0x0000
+ 0x03F7, 0x03F9, 0x03FA, 0x03FA, 0x0000, 0x0000, 0x03FE, 0x0000
@@ -361 +361 @@
- 0x0000, 0x0000, 0x037A, 0x0000, 0x0000, 0x0000, 0x037E, 0x0000,
+ 0x0000, 0x0000, 0x037A, 0x0000, 0x037C, 0x0000, 0x037E, 0x0000,
@@ -377 +377 @@
- 0x03F8, 0x03F2, 0x03FB, 0x03FB, 0x0000, 0x0000, 0x0000, 0x0000
+ 0x03F8, 0x03F2, 0x03FB, 0x03FB, 0x0000, 0x0000, 0x037C, 0x0000
```
For Caps Lock to toggle case for all level 3 & 4 characters on the basic keyboard as defined in xkb/symbols/gr, there are a number of other characters in the group `/* Greek and Coptic, U+0370 to U+03FF */` which also need adding.
I've included them in the attached patch which I use in my own build of libX11. Hopefully, it'll be of some use.
[KeyBind.c.patch](/uploads/30e6eb44b2fa4a7f93e8e106e9635633/KeyBind.c.patch)https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/48(libX11-1.6.3) Logically Dead Code in XKBCvt.c2022-01-26T20:55:39ZBugzilla Migration User(libX11-1.6.3) Logically Dead Code in XKBCvt.c## Submitted by Bhavi Dhingra
Assigned to **Xorg Project Team**
**[Link to original bug (#92162)](https://bugs.freedesktop.org/show_bug.cgi?id=92162)**
## Description
Created attachment 118484
Removing Dead Code
In libX11-1.5.0.t...## Submitted by Bhavi Dhingra
Assigned to **Xorg Project Team**
**[Link to original bug (#92162)](https://bugs.freedesktop.org/show_bug.cgi?id=92162)**
## Description
Created attachment 118484
Removing Dead Code
In libX11-1.5.0.tv.17/src/xkb/XKBCvt.c, Line #77,
At condition keysym == 173UL, the value of keysym must be in one of the following intervals: {[65288,65291], [65293,65293], [65307,65307], [65417,65417], [65421,65421], [65450,65465], [65469,65469], [65535,65535]}.
The condition keysym == 173UL cannot be true.
Execution cannot reach the below else block,
else if (keysym == XK_hyphen)
buffer[0] = (char) (XK_minus & 0xFF);
Hence, removing the dead-code.
**Attachment 118484**, "Removing Dead Code":
[XKBCvt.patch](/uploads/d5c548e361e4dd135e44947281d993a2/XKBCvt.patch)https://gitlab.freedesktop.org/xorg/xserver/-/issues/1292xorg-server-21.1.3 error: redefinition of 'xf86AutoConfigOutputDevices'2022-01-25T12:56:46ZJohn Frankishxorg-server-21.1.3 error: redefinition of 'xf86AutoConfigOutputDevices'Using gcc-11.2, xorg-server-21.1.3 build fails with meson and autotools with the following error:
```
FAILED: hw/xfree86/common/libxorg_common.a.p/xf86Init.c.o
gcc -mtune=generic -Os -pipe -Ihw/xfree86/common/libxorg_common.a.p -Ihw/xf...Using gcc-11.2, xorg-server-21.1.3 build fails with meson and autotools with the following error:
```
FAILED: hw/xfree86/common/libxorg_common.a.p/xf86Init.c.o
gcc -mtune=generic -Os -pipe -Ihw/xfree86/common/libxorg_common.a.p -Ihw/xfree86/common -I../hw/xfree86/common -IXext -I../Xext -IXi -I../Xi -Icomposite -I../composite -Idamageext -I../damageext -Iexa -I../exa -Ifb -I../fb -Iglamor -I../glamor -Imi -I../mi -Imiext/damage -I../miext/damage -Imiext/shadow -I../miext/shadow -Imiext/sync -I../miext/sync -Idbe -I../dbe -Idri3 -I../dri3 -Iinclude -I../include -Ipresent -I../present -Irandr -I../randr -Irender -I../render -Ixfixes -I../xfixes -Ihw/xfree86/ddc -I../hw/xfree86/ddc -Ihw/xfree86/dri2 -I../hw/xfree86/dri2 -Ihw/xfree86/i2c -I../hw/xfree86/i2c -Ihw/xfree86/int10 -I../hw/xfree86/int10 -Ihw/xfree86/loader -I../hw/xfree86/loader -Ihw/xfree86/modes -I../hw/xfree86/modes -Ihw/xfree86/os-support -I../hw/xfree86/os-support -I../hw/xfree86/os-support/bus -Ihw/xfree86/parser -I../hw/xfree86/parser -Ihw/xfree86/ramdac -I../hw/xfree86/ramdac -Ihw/xfree86/vgahw -I../hw/xfree86/vgahw -I. -I.. -I/usr/local/include -I/usr/local/include/X11/dri -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -I/usr/local/include/libpng16 -I/usr/local/include/harfbuzz -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/libdrm -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -DHAVE_DIX_CONFIG_H -fno-strict-aliasing -fvisibility=hidden -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast -Wold-style-definition -Wunused -Wuninitialized -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main -Werror=missing-braces -Werror=sequence-point -Werror=return-type -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fPIC -D_DEFAULT_SOURCE -D_BSD_SOURCE -DHAS_FCHOWN -DHAS_STICKY_DIR_BIT -DHAVE_XORG_CONFIG_H -DXORG_NO_SDKSYMS '-DFALLBACK_INPUT_DRIVER="libinput"' -MD -MQ hw/xfree86/common/libxorg_common.a.p/xf86Init.c.o -MF hw/xfree86/common/libxorg_common.a.p/xf86Init.c.o.d -o hw/xfree86/common/libxorg_common.a.p/xf86Init.c.o -c ../hw/xfree86/common/xf86Init.c
../hw/xfree86/common/xf86Init.c:272:1: error: redefinition of 'xf86AutoConfigOutputDevices'
272 | xf86AutoConfigOutputDevices(void)
```https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/57X does not support locale es_CU.UTF-82022-01-23T23:30:58ZBugzilla Migration UserX does not support locale es_CU.UTF-8## Submitted by Dominique Michel
Assigned to **Xorg Project Team**
**[Link to original bug (#63493)](https://bugs.freedesktop.org/show_bug.cgi?id=63493)**
## Description
When installing gentoo ~amd64 on a laptop, I followed the gu...## Submitted by Dominique Michel
Assigned to **Xorg Project Team**
**[Link to original bug (#63493)](https://bugs.freedesktop.org/show_bug.cgi?id=63493)**
## Description
When installing gentoo ~amd64 on a laptop, I followed the guide as usual. I made glic to support several locales:
```
# locale -a
C
en_US.utf8
es_CU
es_CU.utf8
fr_CH.utf8
POSIX
sv_SE.utf8
```
Root have a en_US.utf8 locale, and at the beginning, I used fr_CH.utf8 for my user account. X was working just fine. Recently, I shifted the user locale to es_CU.utf8, and from that moment, I get a lot of warnings like:
[FvwmButtons][FlocaleSetlocaleForX]: WARNING -- X does not support locale es_CU.UTF-8
According to this message, this is not an issue with fvwm but with X.
For gentoo, this is libX11-1.5.0-r1https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/533NVAC fails to resume from suspend to RAM (GeForce 9400M; MacBookPro 5,5)2022-01-23T00:54:39ZPhilip StewartNVAC fails to resume from suspend to RAM (GeForce 9400M; MacBookPro 5,5)When I close the lid, system appears to enter sleep, but fails to resume upon opening lid, tapping buttons or pressing the power button. There is no sign of activity once the lid is opened. I have to perform a hard reset to start the sys...When I close the lid, system appears to enter sleep, but fails to resume upon opening lid, tapping buttons or pressing the power button. There is no sign of activity once the lid is opened. I have to perform a hard reset to start the system.
Looking at dmesg, I noticed the following which appears related to both the power management and the GPU:
```
[ 2.009996] ACPI Warning: \_SB.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20190816/nsarguments-59)
[ 2.010028] ACPI: \_SB_.PCI0.IXVE.IGPU: failed to evaluate _DSM
```
and further down:
`[ 23.511249] nouveau 0000:02:00.0: fb: trapped read at 01004ad000 on channel -1 [0fedf000 unknown] engine 06 [BAR] client 08 [PFIFO_READ] subclient 01 [IN] reason 00000002 [PAGE_NOT_PRESENT]`
I have tested with the proprietary drivers (340.108) and the suspend/resume works as expected.
I'm not sure how to diagnose this further but happy to try given suggestions.
Many thanks,
Phil
* edited to include full dmesg as attachment [dmesg.txt](/uploads/6c600daf38e3dd0137da6c5058adf9a7/dmesg.txt)https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/545Stale texture data and flicker in small SDL2 program2022-01-23T00:50:22ZKevin CahalanStale texture data and flicker in small SDL2 programVideo of bug: https://youtu.be/O0__VNN9G_o
At 0:11 in the video you see old web browser data showing up in my program.
At 0:19 when I close a window in my program the texture for my piano key letters
flicker. By luck the texture for my...Video of bug: https://youtu.be/O0__VNN9G_o
At 0:11 in the video you see old web browser data showing up in my program.
At 0:19 when I close a window in my program the texture for my piano key letters
flicker. By luck the texture for my keys sometimes flickers to stuff previously
displayed on my desktop. This flickering is linked to my mouse movement/placement.
When I run my program with the proprietary 440 NVIDIA driver things work fine. It also works fine with the opensource Intel video driver on a different computer.
I am on Ubuntu budgie 20.04 using XFCE on X.org X11.
The SDL2 program source:
https://github.com/kevinacahalan/piano_waterfall
git hash 553bb6c8ca18b23494a6c92f4551baa1649f0374
[kernel_log.txt](/uploads/9b4057f74becbef5b17b6611ba36f62a/kernel_log.txt)https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/5423d frame-packing mode not supported in X112022-01-23T00:48:31Zmax maier3d frame-packing mode not supported in X11Sorry, if its a foolish question - i'm not a Linux-pro...
I would like to give out a video stream in frame-packing mode to a 3d capable projector. But it seems impossible, because X11 can not handle this mode.
Thats at least what Kodi de...Sorry, if its a foolish question - i'm not a Linux-pro...
I would like to give out a video stream in frame-packing mode to a 3d capable projector. But it seems impossible, because X11 can not handle this mode.
Thats at least what Kodi devs told me, is the reason for the lack of 3d-possibilities in Linux.
So is there a reason for excluding this common 3d-protocol or was it somehow forgotten?
The frame-packing mode was introduced in the HDMI protocol more than 10 years ago.
And is there maybe a way to access the frame-packing mode which is hard to find?https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/558Crash using Sway, in Arch Linux, while dragging windows2022-01-23T00:44:02ZgreenCrash using Sway, in Arch Linux, while dragging windowsI was sent here from [GitHub Sway Repo](https://github.com/swaywm/sway/).
They claimed it was a nouveau bug, so I'll post it here. Read the issue below for details.
https://github.com/swaywm/sway/issues/6669I was sent here from [GitHub Sway Repo](https://github.com/swaywm/sway/).
They claimed it was a nouveau bug, so I'll post it here. Read the issue below for details.
https://github.com/swaywm/sway/issues/6669https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/535[NVC0] GF119 failed to load nouveau/nvd9_fuc409c (-2)2022-01-23T00:42:17Zplatofff[NVC0] GF119 failed to load nouveau/nvd9_fuc409c (-2)Hello. I am using Debian Sid with 5.6 Linux kernel and Nvidia GT 520 GPU and it is always on 270Mhz because nouveau driver can't load firmware.
```
[ 2.214364] nouveau 0000:03:00.0: firmware: failed to load nouveau/nvd9_fuc409c (-2)
[...Hello. I am using Debian Sid with 5.6 Linux kernel and Nvidia GT 520 GPU and it is always on 270Mhz because nouveau driver can't load firmware.
```
[ 2.214364] nouveau 0000:03:00.0: firmware: failed to load nouveau/nvd9_fuc409c (-2)
[ 2.214387] nouveau 0000:03:00.0: Direct firmware load for nouveau/nvd9_fuc409c failed with error -2
[ 2.214401] nouveau 0000:03:00.0: firmware: failed to load nouveau/fuc409c (-2)
[ 2.214404] nouveau 0000:03:00.0: Direct firmware load for nouveau/fuc409c failed with error -2
```
But I installed firmware and did `update-initramfs -u`:
```
root@worksation1:~# file /lib/firmware/nouveau/nvd9_fuc409c
/lib/firmware/nouveau/nvd9_fuc409c: data
root@worksation1:~# du -sh /lib/firmware/nouveau/nvd9_fuc409c
16K /lib/firmware/nouveau/nvd9_fuc409c
root@worksation1:~# ls /lib/firmware/nouveau/
nv106_fuc084 nv84_vp nv98_vp nva8_fuc086 nvc0_fuc085 nvc1_fuc409d nvc4_fuc086 nvce_fuc084 nvcf_fuc41ac nvd9_fuc409c nve4_fuc41ad nve7_fuc409d nvf1_fuc086 vuc-vp3-h264-0
nv106_fuc085 nv84_vp-h264-1 nva3_bsp nvaa_fuc084 nvc0_fuc086 nvc1_fuc41ac nvc4_fuc409c nvce_fuc085 nvcf_fuc41ad nvd9_fuc409d nve6_fuc084 nve7_fuc41ac nvf1_fuc409c vuc-vp3-mpeg12-0
nv106_fuc086 nv84_vp-h264-2 nva3_fuc084 nvaa_fuc085 nvc0_fuc409c nvc1_fuc41ad nvc4_fuc409d nvce_fuc086 nvd7_fuc084 nvd9_fuc41ac nve6_fuc085 nve7_fuc41ad nvf1_fuc409d vuc-vp3-vc1-0
nv108_fuc084 nv84_vp-mpeg12 nva3_fuc085 nvaa_fuc086 nvc0_fuc409d nvc3_fuc084 nvc4_fuc41ac nvce_fuc409c nvd7_fuc085 nvd9_fuc41ad nve6_fuc086 nvf0_fuc084 nvf1_fuc41ac vuc-vp3-vc1-1
nv108_fuc085 nv84_vp-vc1-1 nva3_fuc086 nvac_fuc084 nvc0_fuc41ac nvc3_fuc085 nvc4_fuc41ad nvce_fuc409d nvd7_fuc086 nve0_bsp nve6_fuc409c nvf0_fuc085 nvf1_fuc41ad vuc-vp3-vc1-2
nv108_fuc086 nv84_vp-vc1-2 nva3_ppp nvac_fuc085 nvc0_fuc41ad nvc3_fuc086 nvc8_fuc084 nvce_fuc41ac nvd7_fuc409c nve0_vp nve6_fuc409d nvf0_fuc086 vuc-h264-0 vuc-vp4-h264-0
nv108_fuc409c nv84_vp-vc1-3 nva3_vp nvac_fuc086 nvc0_ppp nvc3_fuc409c nvc8_fuc085 nvce_fuc41ad nvd7_fuc409d nve4_fuc084 nve6_fuc41ac nvf0_fuc409c vuc-mpeg12-0 vuc-vp4-mpeg12-0
nv108_fuc409d nv98_bsp nva5_fuc084 nvaf_fuc084 nvc0_vp nvc3_fuc409d nvc8_fuc086 nvcf_fuc084 nvd7_fuc41ac nve4_fuc085 nve6_fuc41ad nvf0_fuc409d vuc-mpeg4-0 vuc-vp4-mpeg4-0
nv108_fuc41ac nv98_fuc084 nva5_fuc085 nvaf_fuc085 nvc1_fuc084 nvc3_fuc41ac nvc8_fuc409c nvcf_fuc085 nvd7_fuc41ad nve4_fuc086 nve7_fuc084 nvf0_fuc41ac vuc-mpeg4-1 vuc-vp4-mpeg4-1
nv108_fuc41ad nv98_fuc085 nva5_fuc086 nvaf_fuc086 nvc1_fuc085 nvc3_fuc41ad nvc8_fuc409d nvcf_fuc086 nvd9_fuc084 nve4_fuc409c nve7_fuc085 nvf0_fuc41ad vuc-vc1-0 vuc-vp4-vc1-0
nv84_bsp nv98_fuc086 nva8_fuc084 nvc0_bsp nvc1_fuc086 nvc4_fuc084 nvc8_fuc41ac nvcf_fuc409c nvd9_fuc085 nve4_fuc409d nve7_fuc086 nvf1_fuc084 vuc-vc1-1 vuc-vp4-vc1-1
nv84_bsp-h264 nv98_ppp nva8_fuc085 nvc0_fuc084 nvc1_fuc409c nvc4_fuc085 nvc8_fuc41ad nvcf_fuc409d nvd9_fuc086 nve4_fuc41ac nve7_fuc409c nvf1_fuc085 vuc-vc1-2 vuc-vp4-vc1-2
```
I can't switch pstate for my GPU and video memory without firmware:
```
root@worksation1:~# cat /sys/kernel/debug/dri/0/pstate
07: core 810 MHz memory 897 MHz
0f: core 810 MHz memory 897 MHz
AC: core 270 MHz memory 405 MHz
root@worksation1:~# LC_ALL=C echo 7 > /sys/kernel/debug/dri/0/pstate
-bash: echo: write error: Function not implemented
```
Temperature and voltage in `sensors` while playing OpenGL game are 40C and 0.9V. While using proprietary driver they were 65C and 1.01V.
My kernel boot options:
`nouveau.config="NvBoost=2,NvGrUseFW=1,NvClkMode=7"`
The full dmesg output: [dmesg1.log](/uploads/79d661b8fee81dd63a58f617a764eb7e/dmesg1.log)
On my GPU 3D Mesa nvc0 driver is really good comparing to proprietary driver on 270 Mhz. I really want to use free driver with normal P15 clocks because of good performance and coming EoL of proprietary one :)
Thanks for help.