Yes that is correct, however it is recommended to blacklist the kernel for slackpkg upgrades.
Generally speaking (and there are exceptions) you should avoid updating the kernel unless you have a specific reason to do so. Nobody running a mission-critical system updates anything without first looking at the changes. The reason is what you just found out, stuff breaks. if this is a home system, then blacklisting kernel updates from the normal slackpkg system is reasonable. You can always specify kernel updates if and when you need to. Take a look at the files in /etc/slackpkg/. These are the configuration files for slackpkg, you can modify the behavior of the upgrade-all command by blacklisting stuff. It even has an example of how you would blacklist the kernel packages, since it is common practice. Remember that this isn't blacklisting all kernel updates, you can always upgrade when you feel the need and have time to do so. I don't have it blacklisted. I just have a mental todo list when I do updates. if the kernel was updated .. I copy the new one to my EFI partition and re-run the nvidia install script (I don't actually use the slackbuild). On Sun, Feb 3, 2019 at 1:13 PM Dick Steffens <[email protected]> wrote: > On 2/3/19 12:01 PM, Ben Koenig wrote: > > Responding publicly now, since I found the problem. It's an nvidia bug, > > they are supposedly tracking/fixing the problem on their end. > > > > For anyone who is curious, I did a duckduckgo search with these terms > > "nvidia 390 4.4.172" > > > > and read through the second search result: > > > https://devtalk.nvidia.com/default/topic/1046451/linux/linux-4-4-168-and-nvidia-linux-x86_64-410-93-and-get_user_pages-/ > > > > it matches the errors in the log you sent me. > > Okay. I'm not in a rush. > > Generally speaking, though, whenever I upgrade the kernel, after I boot > I'll have a single monitor because the nVidia kernel won't be there. > Then I upgrade the nVidia kernel. Right? > > -- > Regards, > > Dick Steffens > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
