If I understand correctly, you are not able to adjust your refresh rate, both in Displays & Nvidia X Server Settings...
If this is the case, please try the following bellow please...
(Install Compiz)
Launch Compiz & click on "Composite."
Uncheck "Detect Refresh Rate," now, attempt to set your refresh rate in the "Refresh Rate" box right...
The fact that the night light no longer works could be due to the Nvidia drivers.
You could also check the following:
If you are using the automatic night light function, where the night light should be set from sunset to sunrise:
Is the time zone set correctly? Have you activated the location services under Settings>Privacy?
If this does not work, you could create a manual schedule.
Or try to install beacondb to use other location services if they are the problem.
So you are using a video card that is just a month older than my nvidia quadro k620 and I'm using nvidia driver 570. I actually just installed nvidia driver 575 a few hours ago. I don't see why you can't use 570 or 470.
There was a time when you can specify a refresh rate for your monitor using xorg.conf. If you're using X11 and not Wayland, maybe you can still. Not totally sure though. Haven't done it in a good while.
hi can i have a link to download this program? i have searched for it and im lost on which version or trust able website
how do i check? it hasant let me at all
i have no idea, at some point ill upgrade graphics card but this issue idk if it will be solved
You have to ask the team at Zorin if it's still possible. This link will help: xorg.conf
It can be added to the xorg.conf file this way, IF and that's a BIG IF, you can still use it:
Section "Monitor"
Identifier "DP-3"
Option "Primary" "true"
ModeLine "1440@165" 635.54 2560 2568 2600 2640 1440 1443 1453 1459 +hsync +vsync
Option "PreferredMode" "1440@165"
EndSection
looks like theres alot of underlying issues im having with my gpu without fix, is there a way to rest my computer or something and it can get fixed? it was fine until i started tinkering and wanting a new mouse them and thats why this all happened
This might be what you need. This guy was able to install nvidia 340 on Debian 12 Bookworm. Good luck to you buddy.
How to install nvidia-legacy-340xx-driver on Debian 12 Bookworm · GitHub
Or you can downgrade kernel that will support 390
You can install kernel 5.15 with this commands:
"sudo apt install linux-headers-5.15.0-141-generic linux-image-5.15.0-141-generic linux-modules-5.15.0-141-generic linux-modules-extra-5.15.0-141-generic"
Then reboot and set this kernel as default.
With this kernel you can use nvidia 390 drivers without problems and you need no kelebek ppa.
Because of your nightlight problems you could take a look at this thread to see if any helps you:
ok i put the command how to i check
also with the nightlight i tried the commands but it didnt work
Which command do ypu mean? You have installed kernel 5.15? Okay.
Is usually your grub menu shown at boot or not? If not, change the /etc/default/grub file with this link so that grub menu is shown when you boot:
Then reboot and in grub menu choose "Advanced options for Zorin" then select kernel 5.15 there. So you can see if kernel 5.15 is installed. Then it boots with this kernel.
After login follow the steps in the link "How to set an older kernel as default". Edit etc/default/grub with sudo rights.
Delete all old nvidia packages with:
sudo apt remove --purge '^nvidia-.*'
Then install the nvidia 390 drivers with:
sudo apt install nvidia-driver-390 nvidia-dkms-390
Now reboot.
Regarding the issue with the night light:
Does the night light not work at all or only not on the automatic schedule from sunset to sunrise?
You could create a manual schedule or set your location manually to test if that helps.
If you have disabled geolocation services you could also test if enabling them helps.
Here is a thread of reddit where the solution is to add geolocation datas to geoclue.
https://www.reddit.com/r/Ubuntu/comments/1h5ck8j/automatic_night_light_not_working_in_24041/
Been trying to understand this whole downgrading stuff to support old drivers and this helped shed some light. Or a lot actually. Thought I'd share
The difference between the kernel's Application Binary Interface (ABI) and the user-space dependencies of a display server like X.Org
Linux Kernel Downgrades
The Linux kernel team follows a strict "don't break user space" policy. This means that
they strive to maintain a stable user-space ABI. The ABI is the interface that user-space
programs (like the graphical desktop, applications, and system utilities) use to
communicate with the kernel.
When you downgrade a kernel, you're replacing the kernel binary with an older one.
The ABI of this older kernel is what matters, and since the kernel's user-space ABI is
stable, your user-space programs and most drivers (especially those included in
the kernel) can still function correctly with the older kernel. The dependencies for the
kernel itself, like modules (.ko files), are often self-contained within the kernel
package, or are built for that specific kernel version, which is why a downgrade often
works smoothly.
Display Driver and X.Org Dependencies
Proprietary graphics drivers, such as those from NVIDIA or AMD, are a different story.
These drivers consist of two main parts:
A kernel module that talks to the kernel.
A user-space component that provides libraries and drivers for the display server
(like X.Org or Wayland).
This user-space component has its own set of dependencies. X.Org is a modular system with
a versioned ABI. When an old driver is built for an old X.Org version, its user-space
components are compiled to be compatible with that specific X.Org ABI.
Modern operating systems, however, ship with a newer version of X.Org, which has a newer
ABI. The old driver's user-space libraries are not built to work with this newer ABI.
This creates an incompatibility, resulting in the "unmet dependencies" or "broken package"
errors you're describing.
Even if you downgrade the kernel, the user-space part of your OS is still new. The old
driver's user-space components need specific library versions from the older OS to work
with X.Org, and those libraries are no longer present in your newer OS. This is a
fundamental conflict between the user-space libraries and the display server, independent
of the kernel version.
In short, the kernel's ABI is designed to be backwards compatible, but the user-space
ABI of a graphics stack like X.Org is not always forward compatible with older drivers.
ok so guys i got a 3060 ti as a gift. super exicted to try. is there a way to still fix this issue by plugging this one in? im down to reset my pc. i have nothing important on it
Yes, you can insert the new 3060, then boot. You will likely boot to fallback mode, but from there, you can install the Preferred Nvidia driver of your choosing and reboot again.
after reset or i dont have to?