It’s not possible to access more than 60hz with Optimus, latest 525 Nvidia drivers and Fedora 37 on my new machine with the 3070 Ti model.
If I set Nvidia as primary GPU nothing changes.
If I go from Wayland to X, then three replicated 59,9hz options appear besides the 60hz (?).
If I disable Optimus from EFI, then 240hz option appears but battery drains out in slightly more than an hour.
What can be done to access at least 140hz?
With Optimus, the intel igpu is driving the internal screen, meaning it’s an intel issue, the nvidia driver doesn’t have any influence on it.
Please run nvidia-bug-report.sh as root and attach the resulting nvidia-bug-report.log.gz file to your post.
Here it is, I run it with optimus enabled and under Wayland:
nvidia-bug-report.log (555.8 KB)
When executed with optimus disabled the output is larger.
Please create it with Xorg running, Wayland doesn’t provide any useful output.
nvidia-bug-report.log (626.9 KB)
Here it is
So can it be confirmed that it’s an Intel issue? And no workaround for that? A bit sad that for such a machine you can’t use a good refresh rate. Thanks
It’s definitely an intel issue. It reminds me of a known intel bug which should have been fixed recently but I don’t know whether the fix is already committed and it works correctly. Takes some further analysing and research I didn’t find the time for.
Please install drm_info (https://gitlab.freedesktop.org/emersion/drm_info )
and post the output of
drm_info |grep 2560
https://gitlab.freedesktop.org/drm/intel/-/issues/125
Here we have the output:
❯ drm_info | grep 2560
│ │ └───2560x1440@60.00 preferred driver phsync nvsync
│ │ │ ├───Mode: 2560x1440@60.00 preferred driver phsync nvsync
│ │ │ └───2560x1440@60.00 preferred driver phsync nvsync
│ │ │ ├───Size: 2560x1440
│ │ ├───Size: 2560x1440
│ ├───"CRTC_W" (atomic): range [0, INT32_MAX] = 2560
│ ├───"SRC_W" (atomic): range [0, UINT32_MAX] = 2560
Contrary to the issue in the link, when I run xrandr --rate <anything higher than 60> it says Rate 140.00 Hz not available for this size
I see many having this problem, If this doesn’t have anything to do with nvidia then a direction where to investigate is also appreciated.
So it’s obvious the i915 driver now completely ignores the DisplayID 2.0 block of the EDID, it only detects the 60Hz base mode of EDID 1.4
i915 drm driver modes:
└───2560x1440@60.00 preferred driver phsync nvsync
Decoded EDID:
edid-decode (hex):
00 ff ff ff ff ff ff 00 4c 83 79 41 00 00 00 00
00 20 01 04 b5 22 13 78 01 0c f1 ae 52 3c b9 23
0c 50 54 00 00 00 01 01 01 01 01 01 01 01 01 01
01 01 01 01 01 01 63 70 00 90 a1 a0 b4 50 20 08
88 00 58 c2 10 00 00 1b 00 00 00 fd 0c 30 f0 85
85 6c 01 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fe
00 41 54 4e 41 35 36 32 50 30 32 2d 30 20 01 f4
70 20 79 02 00 20 00 0c ba 41 59 79 41 00 00 00
00 00 16 00 21 00 1d 70 0d 94 07 00 0a a0 05 00
e0 0a 52 cc 03 b9 3c c2 0c 00 45 54 40 5e d0 60
d0 1c 22 78 26 00 09 07 07 03 00 00 00 50 00 00
22 00 14 bf 5f 10 84 ff 09 c7 00 27 00 1f 00 9f
05 b3 00 0d 00 05 00 81 00 0b e3 05 80 00 e6 06
05 01 74 60 07 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 9e 90
----------------
Block 0, Base EDID:
EDID Structure Version & Revision: 1.4
Vendor & Product Identification:
Manufacturer: SDC
Model: 16761
Made in: 2022
Basic Display Parameters & Features:
Digital display
Bits per primary color channel: 10
DisplayPort interface
Maximum image size: 34 cm x 19 cm
Gamma: 2.20
Supported color formats: RGB 4:4:4
First detailed timing does not include the native pixel format and preferred refresh rate
Display is continuous frequency
Color Characteristics:
Red : 0.6796, 0.3203
Green: 0.2373, 0.7226
Blue : 0.1396, 0.0498
White: 0.3125, 0.3291
Established Timings I & II: none
Standard Timings: none
Detailed Timing Descriptors:
DTD 1: 2560x1440 59.999583 Hz 16:9 97.199 kHz 287.710000 MHz (344 mm x 194 mm)
Hfront 32 Hsync 8 Hback 360 Hpol P
Vfront 8 Vsync 8 Vback 164 Vpol N
Display Range Limits:
Monitor ranges (Bare Limits): 48-240 Hz V, 388-388 kHz H, max dotclock 1080 MHz
Empty Descriptor
Alphanumeric Data String: 'ATNA562P02-0 '
Extension blocks: 1
Checksum: 0xf4
----------------
Block 1, DisplayID Extension Block:
Version: 2.0
Extension Count: 0
Display Product Primary Use Case: None of the listed primary use cases; generic display
Product Identification Data Block (0x20), OUI BA-41-59:
Product Code: 16761
Year of Manufacture: 2022
Display Parameters Data Block (0x21):
Image size: 344.0 mm x 194.0 mm
Display native pixel format: 2560x1440
Scan Orientation: Left to Right, Top to Bottom
Luminance Information: Minimum guaranteed value
Color Information: CIE 1931
Audio Speaker Information: integrated
Native Color Chromaticity:
Primary #1: (0.679688, 0.320312)
Primary #2: (0.237305, 0.722656)
Primary #3: (0.139648, 0.049805)
White Point: (0.312500, 0.329102)
Native Maximum Luminance (Full Coverage): 400.000000 cd/m^2
Native Maximum Luminance (10% Rectangular Coverage): 616.000000 cd/m^2
Native Minimum Luminance: 0.004700 cd/m^2
Native Color Depth: 10 bpc
Display Device Technology: Organic LED
Native Gamma EOTF: 2.20
Display Interface Features Data Block:
Supported bpc for RGB encoding: 6, 8, 10
Supported bpc for YCbCr 4:4:4 encoding: 6, 8, 10
Supported bpc for YCbCr 4:2:2 encoding: 8, 10
Supported color space and EOTF standard combination 1: DCI-P3, BT.2020/SMPTE ST 2084
Video Timing Modes Type 7 - Detailed Timings Data Block:
DTD: 2560x1440 240.000000 Hz 16:9 388.800 kHz 1073.088000 MHz (aspect 16:9, no 3D stereo, preferred)
Hfront 40 Hsync 32 Hback 128 Hpol N
Vfront 14 Vsync 6 Vback 160 Vpol N
CTA-861 DisplayID Data Block:
Colorimetry Data Block:
BT2020RGB
HDR Static Metadata Data Block:
Electro optical transfer functions:
Traditional gamma - SDR luminance range
SMPTE ST2084
Supported static metadata descriptors:
Static metadata type 1
Desired content max luminance: 116 (616.884 cd/m^2)
Desired content max frame-average luminance: 96 (400.000 cd/m^2)
Desired content min luminance: 7 (0.005 cd/m^2)
Checksum: 0x9e
Checksum: 0x90
So you should open a new bug report with the i915 driver
https://gitlab.freedesktop.org/drm/intel/-/issues
with info from this post and maybe additional debug methods from
https://gitlab.freedesktop.org/drm/intel/-/issues/6223
1 Like
Might be interesting whether this is a new bug or a side effect by the first mentioned bug being “fixed”. You could check by booting an older kernel (e.g. 5.15 using a usb boot system) and there checking the drm_info output.
1 Like
maxim11
January 26, 2023, 5:29pm
11
system
Closed
February 9, 2023, 5:29pm
12
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.