![]() NOTE: I couldn't load or remove nvidia modules if I haven't blacklisted them.Īfter that the solution was simple. So it appears that I was able to circumwent that issue by rethinking all comments about blacklisting modules coming from wise people.Īt last I noticed that IF I blacklist all modules to prevent them from loading (by udev, from what I know), I can actually load modules manually via modprobe and somehow that works perfectly. ![]() I also think that this might be kind of hardware problem, because I received kernel panic when I did 'emerge to re-emerge nvidia-driver-410.73 after I tried to boot with 410.73. However, I made sure that I built 410.73 against the kernel that I load. Please\x0aNVRM: make sure that this kernel module and all NVIDIA driver\x0aNVRM: components have the same version. NVRM: API mismatch: the client has the version 410.73, but\x0aNVRM: this kernel module has the version 396.54. I also receive sometimes (again, sometimes) following messages in /var/log/messages: caller _nv001112rm 0xe3/0x1d0 mapping multiple BARsģ. nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 396.54 Tue Aug 14 23:08: nvidia 0000:03:00.0: vgaarb: changed VGA decodes: olddecodes=io mem,decodes=none:owns=io memĪnd successful load with ~ $ dmesg | grep nvid nvidia-nvlink: Nvlink Core is being initialized, major device number 244 nvidia: module license 'NVIDIA' taints kernel. nvidia: loading out-of-tree module taints kernel. Usually after successful launch of X, DE etc, I get the following output:Īnd when I fail to load with new driver, I get only "nvidia" module.Īccording to dmesg with ~ $ cat dmesg.log | grep nvid Builds fine, but doesn't solve my problem.ġ. ![]() ![]() I tried to build nvidia-drivers-410.73 with the patch from here: (with modified paths according to Chris Torske at ). I also tried to blacklist nvidia modules. I tried to make nvidia-xconfig with new driver (from tty1 after first boot with new driver) and reboot later. I tried to use every available from portage 410.xx drivers with 4.18.xx kernels and also tried 410.73 with 4.18.xx and 4.19.0. I expected to see X, sddm and KDE loading successfully.ġ. Found out that X server failed to start and I got tty1 promt. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |