Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.slackware    |    I think its the one without Selinux crap    |    87,272 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 86,397 of 87,272    |
|    Henrik Carlqvist to User    |
|    Re: External HDMI Monitor and Kernel Upd    |
|    17 Jul 23 06:23:53    |
      From: Henrik.Carlqvist@deadspam.com              On Sun, 16 Jul 2023 11:53:53 -0400, User wrote:       > Anytime I do an update which changes the kernel I lose display to the       > big external monitor. To fix this I have to uninstall the nvidia-kernel       > and nvidia-driver packages and then go rebuild them from slackbuilds.              Yes, any third party kernel module has to be recompiled and reinstalled       when the kernel version is changed as Rich explained.              > The whole process can be rather tedious and cumbersome.              Yes, I agree that this sucks as it adds complexity to updating the kernel.              > Wondering if anyone else deals with this or has a greatly simplified       > solution (e.g. not even needing the nvida-driver to connect a monitor?)              Your need for the binary nVidia driver depends upon your choice of       hardware. I have an alternative approach, but for a single system like       yours it is not really simplified...              When Slackware releases a new kernel as a security update, the       ChangeLog.txt lists a number of CVEs that are fixed. Another approach to       updating the kernel is:              1) Evaluate every CVE to see which ones apply to you. Some of them might        only affect hardware that you don't have or features that you don't        use.              2) Trace down the kernel source fixes for all the CVEs that you are        affected by.              3) Apply those kernel source patches to the source tree of your kernel        version. Some of the patches might need to get modified to fit the        differences between different kernel versions. Some of the patches        might not be possible to fit into your kernel with a reasonable amount        of work, if so, think again if that CVE is important enough to really        go and update the kernel version.              4) Rebuild your kernel with the patched source tree.              5) Rebuild any kernel modules that are affected by the patches.              6) Install your patched kernel modules              7) Install your patched kernel              8) Update boot loader to point to your new kernel              For only a few systems the above is a lot more work than updating the       kernel and nVidia drivers. However, for a whole bunch of systems running       with or without different versions of the binary nVidia driver and       possibly also other third party kernel modules it is less work than       updating the kernel to a new version number.              regards Henrik              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca