One interesting observation is that your logs are saying that 60Hz is
the preferred native mode of the monitor:
[ 1165.229] (II) modeset(0): First detailed timing is preferred mode
[ 1165.229] (II) modeset(0): Preferred mode is native pixel format and refresh
rate
...
[ 1165.229] (II) modeset(0): Printing probed modes for output DP-1
[ 1165.229] (II) modeset(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052
2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 1165.229] (II) modeset(0): Modeline "1920x1080"x144.0 356.39 1920 2008
2052 2200 1080 1084 1089 1125 +hsync +vsync (162.0 kHz e)
[ 1165.229] (II) modeset(0): Modeline "1920x1080"x120.0 297.00 1920 1968
2000 2200 1080 1083 1088 1125 +hsync +vsync (135.0 kHz e)
...
Which is also shown in this list:
1920x1080 (0x48) 148.500MHz +HSync +VSync *current +preferred
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.50KHz
v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz
1920x1080 (0x49) 356.390MHz +HSync +VSync
h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 162.00KHz
v: height 1080 start 1084 end 1089 total 1125 clock 144.00Hz
1920x1080 (0x4a) 297.000MHz +HSync +VSync
h: width 1920 start 1968 end 2000 total 2200 skew 0 clock 135.00KHz
v: height 1080 start 1083 end 1088 total 1125 clock 120.00Hz
So it sounds like this might be a hardware limitation. Maybe it's
changing something unusual to go above 60Hz and maybe just the Windows
10 driver is better at handling that, whatever it is.
If this is a software bug then it should probably be assigned to the
Linux kernel or Xorg modeset driver. Because the details of the pixel
layout are only known and controllable there.
** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1852166
Title:
[nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works
Status in linux package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
The primary monitor, Microstep 24", is capable of 144 Hz refresh rate
and I do use that regularly in Windows 10.
When I set the rate to anything higher than 60 Hz (120 or 144) I get a
wrong pixel pattern. See attached photos.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 12 12:06:45 2019
DistUpgraded: 2019-10-23 22:37:24,432 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if
00 [VGA controller])
Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6390]
InstallationDate: Installed on 2010-10-12 (3317 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Supermicro X10SRA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/root
ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-10-23 (19 days ago)
dmi.bios.date: 06/23/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.0a
dmi.board.asset.tag: Default string
dmi.board.name: X10SRA
dmi.board.vendor: Supermicro
dmi.board.version: 1.01
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
dmi.product.family: Default string
dmi.product.name: X10SRA
dmi.product.sku: Default string
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Sun May 13 18:05:25 2018
xserver.configfile: default
xserver.errors:
[drm] Failed to open DRM device for pci:0000:03:00.0: -19
open /dev/dri/card0: No such file or directory
open /dev/dri/card0: No such file or directory
Screen 0 deleted because of no matching config section.
AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.19.6-1ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852166/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
