open-gpu-kernel-modules
open-gpu-kernel-modules copied to clipboard
NVIDIA
Missing SimpleDRM Support which is needed by Fedora and NobaraOS
NVIDIA Driver Version 515.43.04
GPU 3070 Max-q/GTX 1070
Describe the bug https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers These Changes have broken TTY on fedora 36 and it causes a black screen for most if not all users. more info here https://www.reddit.com/r/Fedora/comments/ucnqet/fedora_36_nvidia_blank_ttys/
Another issue is nvidia users are also getting a black screen at boot some having to wait 5 mins for the screen to kick in.
To Reproduce install any driver on fedora 36 and try to switch to TTY
Expected behavior No black screen on TTY
The issue I'm experiencing is not only TTYs, but everything after boot finishes is completely black.
This is an example of such a user: https://www.reddit.com/r/Fedora/comments/ueq4jm/internal_laptop_screen_black_in_discrete_graphics/
The issue I'm experiencing is not only TTYs, but everything after boot finishes is completely black.
This is an example of such a user: https://www.reddit.com/r/Fedora/comments/ueq4jm/internal_laptop_screen_black_in_discrete_graphics/
Also part of the same issue
Let me add this here. This is a major problem when you run into issues with your fstab or one of your disks refuse to mount for some reason. https://www.youtube.com/watch?v=SS0A-XvM8RI
Might do a video covering this as well to warn the fedora nvidia community
Apparently Fedora has a fix out per below thread: level 2 paidhi · 4 days ago Fedora has implemented a fix with kernel package 5.17.11-300.fc36.
Also the Rpmfusion akmod-nvidia package was updated to reflect this. You will need akmod-nvidia version 3:510.68.02-2.fc36 which is now in the rpmfusion-nonfree-updates repository.
Yup! Can confirm. The 5.17.11-300 along with 510.68.02-02 fixed the issue.
Do note the fedora kernel does not fix the issue per say, simply bypasses it.
@YusufKhan-gamedev can you maybe work on this if possible?
I think this might be that this might be something to do with ogk(these modules) not supporting fbdev emulation? My fbcon patches would probably fix the issue if thats the case(remember to set the kernel module param). I dont fully understand the problem though, im more into getting userland drivers for ogk but if I knew what the underlying issue is i would at least look into it.
The issue is @fedora screwed up and replaced the drm they where using with simpledrm some weird emulation thing and amd supports it and intel but not nvidia
The issue is @fedora screwed up and replaced the drm they where using with simpledrm some weird emulation thing and amd supports it and intel but not nvidia
Simpledrm is just a drm driver, so is amdgpu, nvidia_drm and i915(intel), there has to be some bug. Could this be related to https://github.com/NVIDIA/open-gpu-kernel-modules/issues/341? In that case you may have a conflicting drm driver, perhaps it could be simpledrm? If its simpledrm you might want to blacklist it until the kernel issue it fixed. There is also probably some way you can get simplefb or vesafb on fedora, perhaps an external repo?
if its completely as you say though, you can get fbdev emulation with my fbcon patches I mentioned before.
Nobara added a fix in kernel but it doesn’t always work and for regular fedora its just screwed the blacklist doesn’t always work Rpm fusion added a fix but that breaks just hoping someone adds support for it
Nobara added a fix in kernel but it doesn’t always work and for regular fedora its just screwed the blacklist doesn’t always work
Could I see the fix?
They just reverted simpledrm Sent from my iPhoneOn Aug 23, 2022, at 11:33 PM, YusufKhan-human @.***> wrote:
Nobara added a fix in kernel but it doesn’t always work and for regular fedora its just screwed the blacklist doesn’t always work
Could I see the fix?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
They just reverted simpledrm
So they put simpledrm.modeset=0 in the kernel boot options? That should fix any conflicts with simpledrm...
Hi @YusufKhan-gamedev I'm one of the maintainers of Nobara. To clarify, we disabled simpledrm in the kernel config and re-enabled fb_simple and fb_vesa, essentially reverting Fedora's changes:
# CONFIG_DRM_SIMPLEDRM is not set
CONFIG_FB_SIMPLE=y
CONFIG_FB_VESA=y
This allows us to freely swap between rpmfusion and negativo17 nvidia drivers without messing with people's boot options (other than still needing the nouveau blacklist ofc.). However, this is just a revert, not an actual fix. nvidia-drm.modeset=1 is -required- as a kernel boot option if simpledrm is enabled. (See this which was merged upstream: https://github.com/negativo17/nvidia-driver/issues/129#issuecomment-1132029649). Setting it as a module config is not enough (ie /etc/modprobe.d/).
Ah that makes sense, im guessing simpledrm is a conflicting framebuffer though. Or there is some conflicting framebuffer somewhere...
Either fbdev emulation is required or there is another driver trying to take control of the framebuffer, cant think of anything else.
@RyzenDew you might wanna checkout my drm/aperture_control branch to see if it fixes your issue.
https://github.com/YusufKhan-gamedev/open-gpu-kernel-modules/tree/drm/aperture_control
Yeah, none of them solve it, perhaps its a duplicate of #341 ? In that case maybe try a older kernel??
This has once again become a problem on the 6.1 kernel on Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=2161104
Apparently given the comment on the Fedora dev their goal is not to ship any fbdev, and won't block any release on the NVIDIA driver, classic Fedora behavior, as they seem to be hoping for Nouveau to improve.
sigh. Been nothing but problems with the drivers since moving to the 6.x kernels. It appears fedora has stopped supporting the nvidia workaround with the latest kernels. There is a patch in testing linked to the bug. I couldn't tell if works or what needs to be done to make it work (per some comments). Might just have to give this GPU the Office Space treatment.
Fedora devs readded the kernel hack (it was accidentally dropped during an update), and the Nvidia driver works again as of 6.1.7-200.fc37.x86_64. Hopefully the driver will be properly fixed before this happens again.
On Nobara we manually reenabled simpledrm a long while back since this happened. on fedora as mentioned a kernel patch/hack is used. The only way to test this is without simpledrm being enabled and without the hack.
Wasn't this fixed?
Judging by this comment https://github.com/negativo17/nvidia-driver/issues/129#issuecomment-1445376122, support was silently added in 525.60.11.
Stable 525.105.17 release also has this in notes:
Added support for console restoration when using simpledrm.
https://www.nvidia.com/download/driverResults.aspx/202504/
