inttf NVIDIA 340.108 / 390.154 Patcher for Kernel 6.2/6.1/6.0/5.19/5.18/5.17/5.16/5.15/5.14/5.13 [BASH Script] - Comment Page: 7

This is a BASH script, which download NVIDIA installer, extract it, patch it and make new patched installer package. This is very quickly tested alpha version so if you have any problems please let me know or if this works as it should you can also let me know. I use here currently ARCH Linux Patches + my own patches. Currently this works with NVIDIA 340.108 / 390.154 / 418.113 / 435.21 drivers and latest 6.2, 6.1, 6.0, 5.19, 5.18, 5.17, 5.16, 5.15, 5.14, 5.13, 5.12, 5.11, 5.10 and 5.9 kernels. This should work with any distribution. You just need install wget and patch packages. Check video version of guide: Watch More Videos and Subscribe to Youtube...

257 comments on “inttf NVIDIA 340.108 / 390.154 Patcher for Kernel 6.2/6.1/6.0/5.19/5.18/5.17/5.16/5.15/5.14/5.13 [BASH Script] - Comment Page: 7

1 5 6 7 8 9
    1. the guide does not work in lenovo ideapad y410p. how to get it working & can be used for gaming & multimedia application in fedora design 36?

      the laptop has 2 vga..
      1. integrated intel HD 4600
      2. nvidia geforce gt 755M

      • Hello roke,

        Unfortunately this guide is not for NVIDIA Optimus users. If you can disable NVIDIA Optimus / Intel graphics, then you are normally good to go.

    2. Thank you for continually making these patches. They are keeping my Dell Precision running Manjaro Linux without any real headaches every Kernel update.

      I subscribed to your Youtube channel and will spam watch your vids.

    3. Hi,
      I am a longtime beneficiary of your patches and guides, So much so that I never think twice about upgrading my Fedora install because you always get a patched version of the 390 drivers out before I can even fish installing the O/S. I just updated my Fedora 36 to kernel 5.18 and cannot build the nvidia driver 390.151 successfully. I used your inttf bash script to create a patched installer however it is still erroring out before finishing install. looks like a couple symbols during compile are missing or mis-defined according to the install log, while these are only compile warnings the flag to treat warnings as errors is set in the Makefile and thus the make is aborted. any ideas on how to build 390.151 with kernel 5.18? this is a Dell E6420 with an NVS4200 graphics card on a docking station.

    4. As you know I’ve been using your patch system for a long time and am absolutely dependent on it for my favorite laptop.
      Love the work and can’t thank you enough!
      Quick question:
      I use XANMOD. Forever now, when I install the patch, I get the NVIDIA INSTALLER error that there’s a version mismatch between
      compilers but it’s just like .1 off so I usually just do EXPORT CC=/usr/bin/gcc-11 before the install and then select IGNORE
      VERSION DIFFERENCE and it has always worked. I don’t know if this is relevant to what I’m going to say next or not, but I
      thought I’d mention it.

      Since V5.18.X, I have only been able to get XANMOD 5.18.1 x64v2 working. All higher versions of XANMOD error out.
      However, all normal versions of the kernel work great. I’m currently on 5.18.10-051810-generic and it works great.
      I understand this is probably an issue with XANMOD, they must have done something different between version .1 and the
      higher versions, but any help would be appreciated.

      Again, thank you for everything! Looking forward to 5.19 and beyond!!! 8

      • I was finally able to get 5.18.10-xanmod1 working but not the 5.18.10-xanmod1-x64v2, although 5.18.1 x64v2 works.
        Hmm… Strange. I don’t really understand what the diff is between the 5.18.1 and 5.18.1 x64v2, they are both x64 afaik. Anyhow just saying I got the one without x64v2 working. Cheers!

    5. Worked like a charm in Pop OS after I blacklisted nouveau! You’re a lifesaver.

      • Excellent to hear Isaac! Thank you!

    6. I love your inttf site! Tons of useful information.

      There is a new versiom (390.154) Linux X64 driver. Would you be updating your NVIDIA Patcher to work with that version?

      Thank you in advnace for your time and all your help, Sir!

    7. Hi JR and thanks for the information that you are sharing with us and tools that you provide.

      There is a new NVIDIA driver ver. 390.154 which is available here:

      The current Patcher works with ver. 390.151, but fails on ver. 390.154.

      JR, please update your Patcher to work with 390.154!

      Thank you in advance for your time!

    8. Considering Kernel 6.0rc1 is out, is there any news on a patch for 5.19?
      I’ve checked several places where the patch sources come from and none of them seem to be updating. Is there a particular issue with 5.19?

      • After doing some research and discovering that some people
        were able to install the 5.18 patch on 5.19 without it needing
        any additional modifications, I went ahead and tried it with
        the latest script from JR and it works for kernal
        5.19.1-051901-generic! It appears 5.19 needs no modifications and the 5.18 script will work. 8)
        Still having issues with any Xanmod version that contains
        x64v2 in the filename but other than that, it’s working!

        Thought I’d drop a note here to let people know.

        • Hello MENTD,

          Sorry for the late reply. And thank you, you are totally right that 5.19 should work without any extra patch. I’m currently testing kernel 6.0-rc2, even latest NVIDIA 515.xx fails to install, but looks like it’s possible to get working.

          • I have been unable to get KERNEL 6.0 *anything* to install, even without NVIDIA drivers.
            Both the RC1 and RC2 automated builds for AMD64 at:
   have been failing, elsewhere as well.
            (If you go there, you’ll see that ARM64, ARMHF, and s309x versions complete, AMD64 & PPC64el fail.)
            And it appears the new 5.19.4 fails on AMD64, ARMHF, i386, PPC64el and RISCv64 so *something* must have
            changed with their mainline automated build system as I assume there should not be that much difference
            between 5.19.3 and 5.19.4 to cause so many different architectures to fail.
            I think the 6.0 failures may have something to do with a new version of libc being required?
            I’m running UBUNTU FOCAL v20.04.5 LTS. I remember I was able to upgrade libc years ago manually but
            it took days to get right and finally all night to compile and was a major pain in the ass so I’m hoping
            there will be a workaround as I really wanna stay on this version of UBUNTU, it is LTS after all.
            It’s perfect for my old VOSTRO 2510 laptop, newer versions run sluggish.
            I know Linux Torvalds says 6.0 is “just a number” but it seems there’s something funky with it.

            Anyhow keep up the good luck man, I’m happily using 5.19.3 for now. 8)

            • Finally got 6.0rc3 working with NOUVEAU but it gives an error when
              I use your script to try to get the patched NVIDIA drivers working.

              I assume you don’t have 6.0 completely worked out yet?
              You mentioned that even 515.xx fails but the site title lists
              6.0, is that a typo or is there a version that works?
              I’m on 340.108, the last one I have working with patched NVIDIA
              is still 5.19.3.

              Anyhow, the mainline finally successfully built RC3 for AMD64. 8)
              So I have the kernel running at least, just no NVIDIA drivers yet.
              Good luck!

              • Okay… Sorry for this long thread but I have yet more info!

                Woke up this AM and decided to update my main desktop to 6.0rc3 which is running an
                NVIDIA GTX 1060 with v515.65.01 and…. CRASH!

                I must have been half asleep last night but I now understand what you mean.
                When you mentioned 515 above, I didn’t realize at the time that you were talking about
                the latest official and supported NVIDIA drivers and that THEY are not even working!
                Even with the latest NVIDIA drivers, 6.0 doesn’t install.

                So… I used your FEDORA 515.65.01 patch and it worked great!

                My main desktop with the GTX 1060 is now running KERNEL 6.0rc3 with your 515.65.01 patch.

                It seems NVIDIA is really dropping the ball, didn’t I hear something about them supposedly
                finally releasing their drivers open source??? It sure is about time if so!

                Good luck on gettin’ it going on 340.108.

                • Exactly even latest 515.65.01 won’t work without patch with Kernel 6.0. I’m just doing some testing with this, but I think that it’s still long way to get 340.108 work with Kernel 6.0.

                  • Aren’t NVIDIA supposed to be releasing their drivers open source?
                    Maybe the next NVIDIA update will make it easier?
                    I’d hate to think that 5.19.4 is the last version 340.108 will ever run on… 8(

    9. I have no idea why the script keeps downloaing 5.18 kernel and patch It instead of 5.10 in Linux Debian 11 for 340.108 driver.

    10. I have tried the instructions for Rocky Linux 9 with kernel Linux version 5.14.0-70.22.1.el9_0.x86_64. Unfortunately the build of the module fails…
      see log..

      Regards rl

    11. Thanks for the patch, but after installation stay in black screen, with driver 340.108… The kernel is 5.18.0-kali5-amd64… I have the xorg.conf, you have a Idea?

      • Hello Damian,

        Could you post output of following command:

        lspci |grep -E "VGA|3D"
    12. It does’t work for Debian (Debian 5.10.136-1) and Kernel 5.10.0-17-amd64 and Nvidia driver 340.108.
      Same error: …kernel/nv-linux.h:139:10: fatal error: linux/ioctl32.h: No such file or directory.

    13. Why still no 5.19 patch for 340.108?

    14. So there is no patch for 5.19 kernel for 340.108 nvidia driver?

      • Yes there is. The 5.18 one works for 5.19.

1 5 6 7 8 9

Leave a Reply to Dan Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.