{"id":2227,"date":"2018-03-06T13:41:14","date_gmt":"2018-03-06T21:41:14","guid":{"rendered":"http:\/\/rglinuxtech.com\/?p=2227"},"modified":"2018-03-06T13:41:14","modified_gmt":"2018-03-06T21:41:14","slug":"nvidia-possible-fix-for-kernel-4-16","status":"publish","type":"post","link":"https:\/\/rglinuxtech.com\/?p=2227","title":{"rendered":"NVIDIA &#8211; Possible Fix for Kernel 4.16.."},"content":{"rendered":"<p>Thanks to the efforts of <strong><em>mlau<\/em><\/strong> on the NVIDIA Devtalk Forum, there is a possible fix for the <em>swiotlb<\/em> issue with Kernel 4.16..\u00a0\u00a0\u00a0\u00a0 See <a href=\"https:\/\/devtalk.nvidia.com\/default\/topic\/1030082\/linux\/kernel-4-16-rc1-breaks-latest-drivers-unknown-symbol-swiotlb_map_sg_attrs-\/\" target=\"_blank\" rel=\"noopener\">https:\/\/devtalk.nvidia.com\/default\/topic\/1030082\/linux\/kernel-4-16-rc1-breaks-latest-drivers-unknown-symbol-swiotlb_map_sg_attrs-\/<\/a> for details..<\/p>\n<p>For NVIDIA driver <strong>384.111<\/strong>, I had to increment all the <strong><span style=\"font-family: courier\\ new, courier;\"><span class=\"pln\">nv<\/span><span class=\"pun\">&#8211;<\/span><span class=\"pln\">linux<\/span><span class=\"pun\">.<\/span><span class=\"pln\">h <\/span><\/span><\/strong>patch line number references by 100 (so &#8216;&#8230;<strong><span style=\"font-family: courier\\ new, courier;\"><span class=\"pun\">@@<\/span> <span class=\"pun\">&#8211;<\/span><span class=\"lit\">1209<\/span><span class=\"pun\">,<\/span><span class=\"lit\">6<\/span> <span class=\"pun\">+<\/span><span class=\"lit\">1209<\/span><span class=\"pun\">,<\/span><span class=\"lit\">7<\/span> <\/span><\/strong><span class=\"pun\"><strong><span style=\"font-family: courier\\ new, courier;\">@@<\/span><\/strong>&#8230; becomes &#8230;<strong><span style=\"font-family: courier\\ new, courier;\">@@ &#8211;<span class=\"lit\">1309<\/span>,<span class=\"lit\">6<\/span> +<span class=\"lit\">1309<\/span>,<span class=\"lit\">7<\/span> @@<\/span><\/strong>..&#8217; and &#8216;..<\/span><span class=\"com\"><span style=\"font-family: courier\\ new, courier;\"><strong>@@ -1251,7 +1252,7 @@<\/strong><\/span>..&#8217; becomes &#8216;..<span style=\"font-family: courier\\ new, courier;\"><strong>@@ -1351,7 +1352,7 @@<\/strong><\/span>..&#8217;), and then the patch applied OK.\u00a0\u00a0 <\/span><\/p>\n<p><span class=\"com\">I then used this to create a patched runtime version of NVIDIA-Linux-x86_64-384.111.run, and used this on Kernel 4.16-rc4, and it compiled\/loaded OK, and &#8211; so far &#8211; is running without any problems..\u00a0 <\/span><\/p>\n<p><span class=\"com\">Tested with Kernel 4.16-rc4 (nopti), patched driver 384.111, on Fedora 27 with KDE\/Plasma, and VMware 4.1.1- running Win7 guest, with Photoshop CS6..<br \/>\n<\/span><\/p>\n<p><em>I should mention that I use VMware\/Win7\/Photoshop as a sort-of-benchmark-test for video drivers..\u00a0\u00a0 I have regularly tried using <strong>nouveau<\/strong>, but &#8211; although this runs OK in most cases &#8211; it causes all sorts of problems with Photoshop CS6 on a VMware 4.1.1 Win7 guest..\u00a0\u00a0 So.. I am staying with the proprietary NVIDIA drivers for the time being, on my main system..<\/em><\/p>\n<p><em>Robert Gadsdon.\u00a0 March 6, 2018.<\/em><\/p>\n<p><span class=\"pun\">\u00a0<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Thanks to the efforts of mlau on the NVIDIA Devtalk Forum, there is a possible fix for the swiotlb issue with Kernel 4.16..\u00a0\u00a0\u00a0\u00a0 See https:\/\/devtalk.nvidia.com\/default\/topic\/1030082\/linux\/kernel-4-16-rc1-breaks-latest-drivers-unknown-symbol-swiotlb_map_sg_attrs-\/ for details.. For NVIDIA driver 384.111, I had to increment all the nv&#8211;linux.h patch line number references by 100 (so &#8216;&#8230;@@ &#8211;1209,6 +1209,7 @@&#8230; becomes &#8230;@@ &#8211;1309,6 +1309,7 @@..&#8217; and &#8216;..@@ -1251,7 <span class=\"excerpt-dots\">&hellip;<\/span> <a class=\"more-link\" href=\"https:\/\/rglinuxtech.com\/?p=2227\"><span class=\"more-msg\">Continue reading &rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[1238,11,14,15,18,19,1533],"tags":[1833,1828,829,277,1832,1831],"class_list":["post-2227","post","type-post","status-publish","format-standard","hentry","category-fix","category-hacks","category-kernel","category-linux-2","category-nvidia","category-opinion","category-patches","tag-384-111-patched","tag-kernel-4-16","tag-nv-linux-h","tag-nvidia-2","tag-possible-fix","tag-swiotlb"],"_links":{"self":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/2227","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2227"}],"version-history":[{"count":1,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/2227\/revisions"}],"predecessor-version":[{"id":2228,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=\/wp\/v2\/posts\/2227\/revisions\/2228"}],"wp:attachment":[{"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2227"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2227"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rglinuxtech.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2227"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}