RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    L2 & R2 triggers not recognized in ES after update

    Scheduled Pinned Locked Moved Help and Support
    controlleremulationstaton
    9 Posts 3 Posters 1.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      corezon
      last edited by corezon

      Rasperry Pi 4 4GB
      RetroPie 4.7.3

      Updated yesterday and now Emulation Station will not recognize the L2 & R2 triggers on my wired 8bitdo SN30 Pro. This worked just fine before the update and jstest shows the triggers as Axis 2 & 5. Cannot put this controller in D input mode as it's the wired model. Reconfiguring input still doesn't detect the axis for L2 & R2. I will try to manually adjust the autoconfig, but the main concern is that... this shouldn't be normal, right? Updating RetroPie through the RP-Setup script shouldn't result in controllers just breaking.

      1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator
        last edited by

        Try to re-install the xpad driver. Did you use rpi-update in your update process ?

        C 1 Reply Last reply Reply Quote 0
        • Z
          Zel
          last edited by

          Same here, fresh install on RPI 4GB (former Lakka user here), 8bitdo SN30 Pro in X input connected via USB cable, l2&r2 were not recognized during initial setup

          1 Reply Last reply Reply Quote 0
          • C
            corezon @mitu
            last edited by

            @mitu I went through the gui setup script and selected the update option. I selected to update the underlying OS packages as well when prompted. I did not run rpi_update manually or anything like that.

            Removing and then reinstalling xpad from source finally fixed it. So thank you. I still think it's weird that this happened at all...

            1 Reply Last reply Reply Quote 0
            • mituM
              mitu Global Moderator
              last edited by

              The driver (xpad) should be updated when the kernel is also updated. Do you have a log from the update ? It should be one in the $HOME/RetroPie-Setup/logs, archived. If you could extract it and post it on pastebin.com, we might spot if any problems occurred during the update.

              C 1 Reply Last reply Reply Quote 0
              • C
                corezon @mitu
                last edited by

                @mitu Here's the full log: https://pastebin.com/1wyCgNmc

                But specifically at the end it has this nugget:

                = = = = = = = = = = = = = = = = = = = = =
                Configuring 'xpad' : Updated Xpad Linux Kernel driver
                = = = = = = = = = = = = = = = = = = = = =
                 
                modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/5.4.79-v7l+/modules.dep.bin'
                modprobe: FATAL: Module xpad not found in directory /lib/modules/5.4.79-v7l+
                /home/pi
                
                mituM 1 Reply Last reply Reply Quote 0
                • mituM
                  mitu Global Moderator @corezon
                  last edited by mitu

                  The actual install error is on the next statement:

                  DKMS: add completed.
                  Error! echo
                  Your kernel headers for kernel 5.4.79-v7l+ cannot be found at
                  /lib/modules/5.4.79-v7l+/build or /lib/modules/5.4.79-v7l+/source.
                  /opt/retropie/supplementary/xpad /home/pi
                  

                  Because the kernel was upgraded, there are no kernel headers for the current running kernel, so upgrading the driver fails here. Which is strange since the kernel headers package for the new version was installed already, so it should be set-up.

                  Can you run

                  systemctl status systemd-modules-load.service
                  

                  and post the output ?

                  C 1 Reply Last reply Reply Quote 0
                  • mituM
                    mitu Global Moderator
                    last edited by

                    Actually, there might be an issue with the driver update script when kernel also changes during update. We'll look into it.

                    1 Reply Last reply Reply Quote 0
                    • C
                      corezon @mitu
                      last edited by

                      @mitu here's the command output you asked for: https://pastebin.com/7P4XQALt

                      Let me know if I can be of any help.

                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post

                      Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                      Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.