Re: No console anymore. How to figure this out.
Michael <[email protected]>
| Newsgroups | gmane.linux.gentoo.user |
|---|---|
| Message-ID | <4722622.LvFx2qVVIh@rogueboard> |
On Monday, 16 March 2026 14:56:49 Greenwich Mean Time Dale wrote: > On 3/16/26 5:16 AM, Michael wrote: > > Your console device needs the nvidia-drm.ko module to be able to use > > nvidia's own kernel modesetting framebuffer functionality > > (modesetting=1). > > > > What I think is happening: your EFI framebuffer is providing the > > initial console display during boot, then it switches over to > > nvidia- > > drm. > > > > I suspect your problem manifests at the handover from kernel to > > nvidia's module, or vice-versa, when you try to go back to a > > console. However, I haven't used nvidia for decades now and have > > not kept up with their current driver's functionality to know with > > any certainty how this is meant to work. > > > > What does dmesg report at boot and thereafter when you switch to a > > console? > > > > Can you grep your running kernel's for 'DRM', to see if anything > > incompatible has been enabled/disabled? > > > > What does 'lsmod | grep nvidia' come up with? > > > > Also, 'modinfo nvidia-drm'? > > > > PS. I assume your have re-emerged your nvidia driver to match the > > kernel you are now running. > > That's my thinking to, the last part. I didn't think about the first > part. LOL This is lsmod. The drm part is loaded as is modeset. > > > root@Gentoo-1 / # lsmod > Module Size Used by > nvidia_uvm 1814528 2 > nvidia_drm 118784 40 > nvidia_modeset 1875968 161 nvidia_drm > nvidia 110895104 2122 nvidia_uvm,nvidia_modeset > root@Gentoo-1 / # > > > > So it appears the modules are loaded but not all are working. I > guess??? Here's the other info. > > > > root@Gentoo-1 / # modinfo nvidia-drm > filename: /lib/modules/6.12.31-gentoo/video/nvidia-drm.ko > version: 580.142 > supported: external > license: MIT > srcversion: 7C9FF03229E79984059FE07 > alias: pci:v000010DEd*sv*sd*bc06sc80i00* > alias: pci:v000010DEd*sv*sd*bc03sc02i00* > alias: pci:v000010DEd*sv*sd*bc03sc00i00* > depends: nvidia-modeset > name: nvidia_drm > retpoline: Y > vermagic: 6.12.31-gentoo SMP preempt mod_unload > parm: modeset:Enable atomic kernel modesetting (1 = enable, > 0 = disable (default)) (bool) > parm: fbdev:Create a framebuffer device (1 = enable > (default), 0 = disable) (bool) > root@Gentoo-1 / # > > > > Yes, I did rebuild the nvidia drivers however, I'm still on the same > kernel. Been using the current kernel for ages now. I think since > shortly after I built this rig. The kernel we were trying to adjust > never would finish the make process, compile I guess. > > Does anything there give a clue? Could it be the nvidia drivers have > a bug, in both versions in the tree? My card is older but I can't be > the only one that uses a card like that. Of course, some people that > use a GUI rarely switch to a console. So, it could be a bug that no > one else has noticed I guess. Unless you or someone else has some > more ideas to check. Your modesetting is disabled, nvidia's FB is enabled. As I suggested you can check dmesg for errors as you switch over to tty1. You haven't yet showed 'grep DRM .config' of your running kernel.
signature.asc
(application/pgp-signature, 870 B)
-----BEGIN PGP SIGNATURE----- iQJPBAABCAA5FiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmm4IhkbFIAAAAAABAAO bWFudTIsMi41KzEuMTEsMiwyAAoJELHqqvbClWcZnX0QALQrmUtZo2TU6ng6DK+i nZeg0WXPdk0tqfZIXj9wTaTWMzdWPZrSGNoQRFWRDW+aa8VOry8aT/ZPmvU9T48c LDchKCPfmrH/Jsh2kt1E6jihbjqX0EDlvzv3DRh5wIlPmlShBXeDTTPOF6JYGVDu UUF1d+GdWa05H9g4Ljlv2pVBjN+SrQWMeG3GonnpjlP6//GMNtx+9xhwyUiZEe/V Ab84FM7esWeUdBWTR6gMNTzn2bp5TJvkDv8RAKJMSnH2hey2QlL4m8DVyMpzUm5H b2UOrueKHvDX5TNV+ohhb+a906R6CmhCcCT2kc2iOE+71lFBB6HrA7GDR6BkQl5c pmN31+HnRDaf6z8QrV5pcvKiakDce47uYjyYEVImWzAyvPreziE21TxxHp9f4wfQ TYmrbppPVmunU8lpHf9m/AapZpkPsAaVkuDdO3lC98P95uEftwpL4xYmIlCPjfoW Z8/Z5f64FIQ+QrYr/6IgGLjUB2y5b2Y+uYCi//Blesjw9EkxvFfTDsMpoDDcA16r G93w+BtuJEcMsibuw+3kUv8gdLSegvZAMy++Sit/wVBiJ7cXylnYqM1LzA3iucg2 21vP8SbxcjlkelRsQsRP7SB1XkuYRDzCeTjFd4VRlv+ll+o8oydbZzl0G5dMWy9D GuaB33Xl9ZnYWzCoVtrrWQNQ =uEfz -----END PGP SIGNATURE-----