11:16latenite: Hi folks, is there a way to make the nouveau driver drive my dispplay with its native 5120x2160? At the moment the highest available is 3840x2160
11:16latenite: I am on Fedora 37
11:16latenite: The card is a Quadro P620
11:17latenite: The monitor a LG 34WK95U
12:08DodoGTA: latenite: What display connector do you use?
12:23latenite: DodoGTA, DP
12:23latenite: at both ends
12:28karolherbst_: I don't think pascal can do this.. mhh
12:28latenite: DodoGTA, https://paste.ee/p/HD8xz
12:28latenite: why does it not support my 5k?
12:29DodoGTA: latenite: Maybe it might be a EDID parsing issue? (try forcing your monitor's native resolution and refresh rate and see if dmesg explodes)
12:29karolherbst_: seems like it does DP 1.4
12:29DodoGTA: Or actually start from 30 Hz just in case
12:31karolherbst_: soo.. for this to work out it needs HBR3
12:31karolherbst_: at least on 60 hz
12:32karolherbst_: I might know what bug this _could_ be.. let me check how we can get the kernel to list rejected modes
12:33DodoGTA: karolherbst_: I just looked at the DP Wikipedia page and noticed that
12:34karolherbst: latenite: boot with drm.debug=0x115 and share your dmesg
12:34latenite: karolherbst, how did you figure out it only does/has DP 1.4 ?
12:34karolherbst: because it's a pascal one only having DP 1.4
12:35latenite: karolherbst, what is a "pascal one"?
12:35karolherbst: the architecture of the gpu
12:35latenite: ah :)
12:36karolherbst: anyway, HBR support is kinda new, so I wouldn't be surprised if there are a few bugs
12:36latenite: karolherbst, how do you know this pascal one gpu only has dp1.4
12:36latenite: HBR?
12:36karolherbst: some DP tech for higher bandwidth
12:37karolherbst: anyway, I think we might calculate the required bandwidth incorrectly or something
12:37karolherbst: what's your kernel version?
12:39latenite: https://en.wikipedia.org/wiki/DisplayPort#Resolution_and_refresh_frequency_limits
12:39karolherbst: we landed initial support for HBR3 in 5.18
12:39latenite: uname -a
12:39latenite: Linux desktop 6.2.8-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Mar 22 19:11:02 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
12:39karolherbst: okay, so that should be good at least...
12:40latenite: I still try to find data/specs on: IF my card can do 5k with at least 60hz
12:40karolherbst: should work if it's not HDR
12:41karolherbst: but it's quite tight and I think there is a bug in nouveau in regards to checking if hte bandwidth is available... but then it should still list the 30 hz stuff.. or well.. maybe it doesn't because it's not advertised by the display
12:41karolherbst: hard to tell without kernel logs
12:41latenite: using the wikipedia table ^^ I need: HBR3 or UHBR 10
12:41karolherbst: anyway, I'd need the output of dmesg when booting with drm.debug=0x115
12:42latenite: karolherbst, I ll do that: drm.debug=0x115
12:42karolherbst: is it a HDR display by any chance?
12:43karolherbst: because those are funky and I still need to fix something for those...
12:43karolherbst: sadly, I don't have a 5k display, so I can only fix a bug I've seen with 4k... :(
12:44latenite: https://paste.ee/p/8sD9K
12:45latenite: karolherbst, what -exactly- IS an HDR display?
12:45karolherbst: uhm.. mind pluging the display out and in again and give me a new log?
12:46karolherbst: an HDR display? that' what they are called if they support HDR
12:46latenite: ...doing it
12:46karolherbst: mhh.. maybe it was a different number.. those ioctl things are kinda spammy
12:46latenite: karolherbst, https://www.lg.com/de/monitore/lg-34WK95U-W
12:47karolherbst: yeah.. that has HDR
12:47karolherbst: you might get it to work by disabling HDR somewhere in the display menu
12:47karolherbst: but yeah, then I might know what bug is it
12:47karolherbst: *it is
12:48karolherbst: some of those displays advertise insanely high bit rates (e.g. 12 or 16 even) and we only use the maximun to do the calculation
12:48karolherbst: and in non HDR mode you only have 8
12:48karolherbst: so we might just think we can't deliver the bandwidth required
12:49latenite: karolherbst, plug in/out https://paste.ee/p/cIgGK
12:49karolherbst: ahh yeah.. wrong number, but what was the right one...
12:50latenite: karolherbst, So I use the on-screen-display menu to search for HDR settings?
12:50karolherbst: yeah
12:50latenite: wrong number?
12:50karolherbst: for drm.debug
12:53latenite: I can boot again if you like
12:53karolherbst: yeah.. try with drm.debug=0xe instead
12:54latenite: I could not find HDR (on/off or alike) BUT I found DP settings beeing set to 1.1
12:54latenite: so I changed them to be 1.4
12:54latenite: rebooted
12:58latenite: LOL setting it (the display) to DP 1.4 makes it: not show anything
12:58latenite: not even the boot screen
12:58latenite: nothing, not even the DELL info at start
12:59karolherbst: strange
13:00karolherbst: to what was it set before? DP 2.0?
13:02karolherbst: anyway, might have to replug so the change get noticed by the GPU
13:02karolherbst: but there should be a dedicated HDR option somehwere
13:02karolherbst: might also call it something funky
13:03latenite: karolherbst, It was set to DP1.1
13:03karolherbst: oops
13:04latenite: I changed it to DP1.4 and after reboot it went and stayed black
13:04latenite: So I tried DP1.2 and it booted
13:04karolherbst: strange
13:04latenite: it even presented 5k @ 30hz
13:04latenite: which I activated
13:04latenite: almost there
13:04karolherbst: yeah..
13:04karolherbst: I am even surprised you got 4k with DP 1.1
13:04latenite: here is the log with unplugging the display: https://paste.ee/p/r7xiB
13:05karolherbst: ahh yeah, that's better
13:05karolherbst: "[ 116.973376] [drm:drm_mode_prune_invalid] Not using 5120x2160 mode: CLOCK_HIGH"
13:05latenite: the display only hat 1.1 1.2 and 1.4 to chose from. no 2.0 at all
13:05karolherbst: let's see if HBR2 could do it even...
13:06latenite: do these displays have firmware updates?
13:06karolherbst: mhh.. yes, but nothing you can install easily afaik
13:06karolherbst: maybe try to disconnect power after switching to DP1.4
13:06karolherbst: but yeah.. with 1.2 30 hz should be the max you'll get
13:07latenite: karolherbst, how do I know what the display CAN do?
13:08karolherbst: reading the edid
13:08karolherbst: but it does advertise 5120x2160@60
13:08karolherbst: it's just that we don't have the bandwidth for it
13:08latenite: on the website is sais:
13:08latenite: Thunderbolt™ 3: Intel 5120 x 2160@60Hz / DisplayPort/MiniDP: AMD und Nvidia: 5120 x 2160@60Hz / HDMI 3840 x 2160 @60Hz
13:08karolherbst: yeah
13:08latenite: so there is more to get
13:08karolherbst: but that will require DP 1.4
13:09latenite: now what is a fault when setting it to DP1.4 and all goes black?
13:09karolherbst: hard to judge
13:10latenite: karolherbst, you say "we" don't have the bandwith? Who is we? The driver, the cable, the display setting (DP 1.2)
13:10karolherbst: the driver, because it can't use HBR3
13:10latenite: karolherbst, how can/does/should it use HBR3?
13:11karolherbst: with DP 1.4
13:12latenite: karolherbst, so when I set the display to DP1.4 we should have the bandwidth for/in the driver?
13:13latenite: karolherbst, would you have an explanation to: why it does not show the UEFI stuff at start when set to DP1.4?
13:13karolherbst: no idea
13:14karolherbst: this involves the motherboards uefi firmware and the onboard GPU firmware
13:14karolherbst: _but_ once nouveau loads it should be able to initialize the GPU so it starts printing stuff
13:14karolherbst: unless you run into HBR3 bugs
13:15karolherbst: mhh that reminds me, I have a 4K@120 screen, but last time I checked it worked
13:18karolherbst: maybe I should check it with my pascal gpu and see what happens
13:19karolherbst: but that also means moving my desktop around :D
13:19latenite: karolherbst, I rebooted with the display being set to DP1.2. After login I set it to DP1.4 and unplugged the power, plugged it back in and all is black...
13:20latenite: ..but the is the log: https://paste.ee/p/9Veyo
13:20latenite: karolherbst, :D thank you tons for trying to make this work :)
13:20karolherbst: ahh
13:21karolherbst: yeah..
13:21karolherbst: that looks like a nouveau bug
13:21karolherbst: weird tho
13:22karolherbst: yeah.. let me check with my 4K@120 display and one of my pascal gpus and see if I figure something out
13:22karolherbst: it's hdmi sadly, so not sure if it works with my DP adapter..
13:23karolherbst: well.. my pascal doesn't have DP :)
13:23latenite: I'll stay here until you tell me to do something.
13:23karolherbst: let's see with a newer GPU then and hope it triggers the same bug
13:23latenite: Any more logs you need?
13:23latenite: Also, what is that bug you just mentioned?
13:23karolherbst: nah, it's more about triggering the same issue and figuring out what's wrong
13:23karolherbst: next steps will involve building a custom kernel and stuff
13:24latenite: karolherbst, I did that before (long time like 6 years) but sure we can build a kernel
13:28latenite: karolherbst, I misinformed you. Set to DP1.4 it DOES show DELL UEFI and GRUB. It was just so fast (I set the timeout to 0) done with the POST...
13:28latenite: Then the display needs some seconds to start (it is never instant ON)
13:29latenite: After that I never saw the boot happening
13:29karolherbst: funky...
13:29latenite: So yes my hardware seems fine
13:29karolherbst: even nvidia only sees 60 hz on it.. :'(
13:29latenite: it really IS the driver having problems
13:30karolherbst: yeah.. figures
13:31karolherbst: anyway.. not sure if your 5k@30 is any better than 4K@60 :)
13:31karolherbst: or weren't you getting 4K@60 with DP 1.1?
13:31karolherbst: wouldn't be surprised if that was limited to 30 hz
13:32latenite: karolherbst, I was getting 3800x???? at 60hz with DP1.1
13:32karolherbst: ahh
13:33karolherbst: ehh.. getting that other "disp: error 00000001" bug with the adapter...mhh
13:33karolherbst: I should look into this
13:34latenite: ok
13:39karolherbst: mhh.. this adapter is silly
13:54karolherbst: latenite: btw, did you find a way to disable HDR? This could make it work potentially
13:55karolherbst: even on DP 1.2
13:56karolherbst: _maybe_
13:56karolherbst: it's very close to the 4K@75 thing, a little higher in the bandwidth required, but maybe it would pan out
13:57latenite: karolherbst, I did not. It might just not have that option to disable
13:57karolherbst: should still be within HBR2 limits
13:57karolherbst: mhh
13:57latenite: I can chose from color profiles...many... one is called HDR
13:57karolherbst: then a kernel patch might help...
13:57latenite: I want to sRGB
13:57karolherbst: mhh
13:57karolherbst: yeah, maybe
13:57karolherbst: this might actually be it
13:59karolherbst: latenite: yeah.. the internet suggest it's the color profile setting in deed
13:59karolherbst: *indeed
14:00karolherbst: but might also be something else.. those menus are always a pain
14:00latenite: So with sRGB I am fine?
14:01karolherbst: mhh
14:01karolherbst: maybe it's that 'ultra HD deep color' option
14:01karolherbst: ehh wait, that's HDMI stuff
14:03latenite: What is DFC? in the monitor settings?
14:04karolherbst: uhm... no idea what DFC is
14:06latenite: Digital Fine Contrast ... some LG whoodooo for contrast
14:07karolherbst: figures
14:07karolherbst: I mean.. I have a patch I'm trying out now which should make this not needed, but it also requires a patched kernel :)
14:07karolherbst: though I could potentially build rpms for fc37
14:10latenite: :)
14:10karolherbst: nice, my patch works
14:10karolherbst: 24Hz -> 60 Hz at 4k
14:16latenite: I have to leave for like 7h
14:17latenite: I will leave this chat open but will not be able to answer.
14:17latenite: I ll write once I am back
14:17latenite: okay?
14:18karolherbst: k
21:43latenite: karolherbst, I am back
22:09karolherbst: let me check if the build is done by now
22:09karolherbst: yes
22:09karolherbst: latenite: you could enable this copr and it should give you my kernel buikd: https://copr.fedorainfracloud.org/coprs/karolherbst/Nouveau_Testing/
22:10latenite: :)
22:12latenite: karolherbst, I know copr is some repo thingy. But I have not used it before...
22:12latenite: How should I get at it?
22:17latenite: karolherbst, did it: https://paste.ee/p/poz66
22:18latenite: karolherbst, so now I reboot and see what happens?
22:18karolherbst: yeah
22:23latenite: karolherbst, it worked perfekt
22:23karolherbst: okay
22:23karolherbst: so it works with DP 1.2 now?
22:24karolherbst: what about DP 1.4?
22:24latenite: I can use 5120x2160@60hz
22:24karolherbst: though I suspect DP 1.4 is still broken
22:24karolherbst: or maybe not...
22:24latenite: yes we are in DP1.2 for now
22:24karolherbst: yeah...
22:24latenite: lets see and test 1.4 ...
22:24karolherbst: maybe I also fix that issue.. dunno
22:24karolherbst: maybe capping to 10 bpc fixes things, no clue
22:28latenite: So I set it to 1.4 while up and running. nothing happened. then I unpluges the display power and plugged back in
22:28latenite: it was all black
22:28latenite: so I rebooted
22:28karolherbst: ah yeah...
22:28latenite: still after UEFI and POST (which was visible) all I could see was initrramfs....then it went black
22:29latenite: here is the log: https://paste.ee/p/WgA4U
22:29karolherbst: no idea what's the issue. The "crash" is odd
22:30karolherbst: but it looks less fatal than before
22:30latenite: weird is: when I reset it to 1.2 and unpower / repower it. The black remains. I would have expected it to come back to life.
22:31karolherbst: probably have to reboot
22:31latenite: I will I you tell me to.
22:31latenite: Whats next?
22:31karolherbst: no idea.. probably asking skeggsb about that log
22:31latenite: I would be happy to see your changes in the next real Fedora updates... :)
22:31karolherbst: maybe Lyude has any ideas
22:31karolherbst: yeah.. I'll get it reviewed and merged asap
22:32latenite: karolherbst, great work. I mean you just did it!!! :)
22:32latenite: 5k at 60hz, all I wanted.
22:32karolherbst: I mean.. I wrote the initial patch like 2 years ago and never cleaned it up, so it's kinda on me 🙃
22:33latenite: Is there anything I can do to help? I mean I could test more if you like me to...
22:33latenite: later on...
22:34karolherbst: yeah.. not sure yet. I'll wait until Lyude or skeggsb have any chance to look at this. The current issue is a bit beyond on what I'm familiar on in that area of the driver
22:36latenite: So how will you get a hold of me then?
22:37latenite: Shall I just drop by once a week and say hello?
22:37latenite: I love the display now :) It looks so much sharper now.
22:37karolherbst: could leave your email
22:37karolherbst: but yeah..
22:38karolherbst: I mean at some point it's going to be
22:38karolherbst: fixed
22:38karolherbst: maybe
22:38karolherbst: :D
22:38karolherbst: but yeah, once we have an idea what's going on I could send a patch to try out to you
22:38latenite: may I ask another video related question?
22:38karolherbst: uhm.. or a build
22:38karolherbst: sure
22:38latenite: sure, just drop me an email
22:39latenite: so: when I am on youtube and watch a "original" music video... any. None in particular.
22:40latenite: It feels like it buffers while still playing. As if someone would slow it down for like 0.5s and the it resumes to regular speed
22:40karolherbst: mhhh
22:40latenite: have you experienced that before?
22:41karolherbst: so the main problem we have atm is, that we kinda have to stay on default clocks which makes the GPU be very slowly... not sure if it's simply a performance problem or something else going on
22:42latenite: karolherbst, this for example. https://www.youtube.com/watch?v=UdM9hLGZ1-M
22:42latenite: see how they move infront of the trees?
22:43latenite: the trees here, shake, stop, move, tear apart
22:43latenite: not in a way one could not watch it, but very noticeable
22:43karolherbst: mhhh
22:43karolherbst: are you on wayland or X?
22:44latenite: karolherbst, wayland (maybe)
22:44latenite: unsure
22:44karolherbst: though I guess if you are on fedora and just have the default thing, it should be gnome on wayland
22:44latenite: I think wayland is the fedora default these days
22:44karolherbst: yeah
22:44karolherbst: what web browser?
22:44latenite: firefox
22:44karolherbst: mhh
22:44latenite: KDE on wayland (maybe)
22:44latenite: how do I test for wayland?
22:44karolherbst: but yeah.. shouldn't matter.. I guess the GPU might just be overloaded
22:45karolherbst: try FHD or something even smaller and see if it's better?
22:46latenite: karolherbst, setting the resolution to 320p in youtube. No change though.
22:46karolherbst: I didn't mean the video res
22:46karolherbst: but like the entire desktop
22:46latenite: karolherbst, or did you mean to set FHD on the card?
22:46latenite: oh ok...
22:46latenite: lets see
22:47karolherbst: 4k is already kinda a lot on one of the more high end GPUs, because reasons...
22:47karolherbst: I'd really wished we could ramp up the clocks on more GPUs
22:48latenite: karolherbst, I played with resolution on both ends (desktop and video)
22:49latenite: and yes I is fluent at 1200x800 and video at 800p
22:49karolherbst: mhhh
22:49karolherbst: annoying
22:49karolherbst: :)
22:49latenite: going higher makes it "shake"
22:50latenite: annoying indeed :) especially when it is such a nice display LOL
22:50karolherbst: I wouldn't be surprised running firefox as a wayland app might improve things
22:50latenite: anyhow I am happy for what you accomplished today
22:50karolherbst: but then again.. with a low end GPU on lowest clocks.. mhhh
22:50latenite: maybe in a few months someone has figured out a way...
22:50karolherbst: doubtful
22:51karolherbst: we'll get firmware from nvidia for the next generation after yours to ramp up clocks
22:51latenite: can you explain the clock thing in lay mens terms?
22:51karolherbst: soo...
22:51karolherbst: uhm.. gpu clocks, like the CPU clock
22:51karolherbst: we are just stuck at low clocks
22:51karolherbst: so everything is slow
22:51latenite: who/what sets the clock speed?
22:52karolherbst: like.. your GPU can max out at around 1.3GHz, but it's probably stuck at 300MHz or something low
22:52karolherbst: the driver, normally
22:52karolherbst: or firmware running on the GPU
22:52latenite: CPUs is set in UEFI. Right?
22:52karolherbst: no
22:52karolherbst: also the kernel or the CPU itself
22:52karolherbst: these days it's all on the CPU
22:52latenite: So the kernel should also set the GPU clock speed but does not?
22:52latenite: If so. Why?
22:52karolherbst: yeah, because shit is complicated
22:53karolherbst: also
22:53latenite: haha nice
22:53karolherbst: we can't :)
22:53karolherbst: so with pascal some of the voltage regulation stuff is only allowed by nvidia signed firmware
22:53karolherbst: on the previous gens the fans got locked down
22:53karolherbst: sooo...
22:53karolherbst: and we can't redistribute the firmware
22:53karolherbst: it's a real annoying situation no matter what
22:53latenite: Can not or may not?
22:54karolherbst: difficult question
22:54karolherbst: the license doesn't allow it at least
22:54karolherbst: _but_ with the new GSP firmware nvidia uses on Turing and newer (20 series) we can do all of that
22:54karolherbst: it's just bad luck for users having older gpus
22:55latenite: So what you are saying is: IF I would get a newer GPU I'd have a display I can watch videos with?
22:55latenite: I'd be in! :)
22:55karolherbst: well.. not yet
22:55karolherbst: but it's work in progress
22:56karolherbst: but yeah.. until the using anything above FHD is a pain
22:56karolherbst: *then
22:57karolherbst: we could do that stuff on a few older gpus even, but I didn't really bothered with figuring out what we'd need to do on Pascal, because if you can't change the fans and can't change the voltage there isn't much you can do
22:57latenite: karolherbst, would you (although being here on nouveau) recommend to use the nvidia driver for my use case?
22:57karolherbst: yeah, that's probably the saner option
22:57karolherbst: just then you should use X11 for now and not wayland
22:58latenite: why x11?
22:59karolherbst: because I tried wayland today on nvidia and it's still a laggy mess :')
22:59karolherbst: and some apps didn't even work
22:59karolherbst: e.g. discord just didn't display anything
22:59karolherbst: which I think is a xwayland problem
23:00latenite: okay, I ll give nvidia a chance on sunday
23:00latenite: for now I ll some sleep
23:00karolherbst: good night :)
23:00latenite: karolherbst, thank you tons for helping :)
23:08DodoGTA: karolherbst: So Maxwell 2.0 and Pascal GPUs will never have reclocking support?