On 31/10/2022 14:53, stan via users wrote:
On Mon, 31 Oct 2022 11:37:43 +0100
Frédéric <ufosp...@gmail.com> wrote:
I tried to reinstall the nvidia drivers from rpmfusion:
$ sudo dnf install xorg-x11-drv-nvidia-390xx akmod-nvidia-390xx
I still have the same issue on the screen resolution and here is the
output of the commands:
$ lspci|grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GF116M [GeForce
GT 560M] (rev a1)
$ cat /proc/cmdline
BOOT_IMAGE=(hd0,msdos1)/vmlinuz-6.0.5-200.fc36.x86_64
root=UUID=4aab7630-84b2-4eae-9c5e-804ff8657b7f ro rhgb quiet
rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modeset=1
$ cat /etc/sysconfig/grub
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modeset=1 rhgb quiet
rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modeset=1"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
Is there anything in the journal?
journalctl -r
to look at messages in reverse order from the current time or
journalctl -b 0
to pick up the last boot messages. If it is failing to set a
resolution that it previously had no trouble with, there should be some
kind of warning or error, I think.
If you remove the rpmfusion nvidia drivers, and then enable nouveau,
and reboot, does the resolution work.
It shouldn't matter, but are you booting into text or gui, and what is
your desktop?
I did a quick search on your device and linux kernel and didn't find
anything, so it shouldn't be related to the kernel update. But, what
happens if you boot an older kernel?
I'm on F36 with the rpmfusion 470xx driver, and saw the same lower
screen resolution on reboot with the 6.0.5 kernel. The previous 5.19.16
kernel still booted as before.
A new version of 470xx in rpmfusion nonfree testing was announced around
midnight and I now have its kmod and akmod installed. atop showed
several cycles of akmods activity. After they appeared to have
finished, a 'systemctl reboot' has delivered a system that seems to be
ok.
There were reports from dracut-shutdown of 'failure to perform cleanup',
and akmods-shutdown.service took longer than might have been expected
given the earlier akmods activity.
Wait for a 390xx update?
John P
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
