Im running the development version with a odyssey g9 and a 3080 and I do not see 240hz available using my max res 5120x1440. running xrandr does show 239.90hz available at a resolution of 2560x1440. Running Windows I am able to run it this way along with hdr and gsync.
I’ve updated nvidia drivers using dkms command as well.
Any ideas ??
Yeah…Looking at this, looks like X haven’t been made with that extreme refresh rates in mind
Not sure what to advice here, except try wayland (which have a lot of other problems), but perhaps they have already thought about that one…
That is for some reason a “hidden” knowledge, but actual steps should be pretty easy though.
Need someone here who actually use it with KDE for the latest tips, i haven’t used it in a long time myself.
I think it should be:
Which is meta-package, but don’t quote me on that
That should be super-easy, the idea is that you choose with dropdown in login screen which session to launch X or wayland, so if it doesn’t do any good you can switch to X and remove all wayland packages.
This is on a fresh endeavour install using the latest development version so not sure if I misunderstand what to install. Looks like the other user was running a lower resolution than me. The resolution he had shows 240 for me but my max resolution is higher so not sure if a fix needs to be implemented for this res?
Sorry, i didn’t read your first post. I do see there is a lot info online regarding this Monitor and also that Video card. It’s been reported to Nvidia as far as i can see and i notice there are issues with it on Windows also. Eventually hopefully it will get resolved.
There was a firmware update version 1008.1 Nov 19/20 for the Samsung Monitor. Just wondered if you have looked at that? Supposedly to support the 240hz. It say’s all OS. I’m looking at it on the Cdn. site. Not sure if anyone has reported it working on Linux. I guess check what version your monitor has is the first thing.
Yes. I’m guessing this might be an issue with nvidia Linux driver implementation ? Nvidia recently released a beta version that might or might not resolve, but looking at the steps to load it it seems extremely confusing.
That’s the part that confused me. The drivers that came pre-instsalled with endeavour show dkms at the end of the driver name so didn’t know if non dmks was compatible.
I’m able to use non dkms? If so what does dkms actually mean like what’s the difference ?
I don’t know if this AUR version is something you even want to get into. I just saw it in the AUR. I do know there is a hotfix in Windows. Hotfix Driver Version 456.98. Not sure if you have Windows or not but that would be a good place to test the hotfix.