Posts: 8
Threads: 1
Joined: Oct 2018
Reputation:
0
(10-30-2018, 05:29 AM)Flavor Wrote: That's interesting. Okay. Please try this, then.
Code: sudo dkms remove -m mk_arcade_joystick_rpi -v 0.1.5 --all
sudo dkms remove -m mk_arcade_joystick_rpi -v 0.1.5.5 --all
sudo dkms remove -m mk_arcade_joystick_rpi -v 0.1.5.6 --all
sudo dkms remove -m mk_arcade_joystick_rpi -v 0.1.5.7 --all
sudo dkms build -m mk_arcade_joystick_rpi -v 0.1.5.7
sudo dkms install --force -m mk_arcade_joystick_rpi -v 0.1.5.7
I have seen it once or twice before where it somehow gets confused about versions. The above commands should try to remove all the potential old versions. Then it should build the latest version and then try to install it (forcefully). I sure hope this works. I don't know why it would be confused, though.
EDIT: Actually, I know why it had a problem when you first did the update. I wonder if after that you ended up accidentally trying to install an old version and that's what got it confused about which version it was supposed to install and use.
Code: root@retropie:~# sudo dkms remove -m mk_arcade_joystick_rpi -v 0.1.5 --all
-------- Uninstall Beginning --------
Module: mk_arcade_joystick_rpi
Version: 0.1.5
Kernel: 4.14.71+ (armv6l)
-------------------------------------
Status: This module version was INACTIVE for this kernel.
depmod.....
DKMS: uninstall completed.
------------------------------
Deleting module version: 0.1.5
completely from the DKMS tree.
------------------------------
Done.
root@retropie:~# sudo dkms remove -m mk_arcade_joystick_rpi -v 0.1.5.5 --all
Error! There are no instances of module: mk_arcade_joystick_rpi
0.1.5.5 located in the DKMS tree.
root@retropie:~# sudo dkms remove -m mk_arcade_joystick_rpi -v 0.1.5.6 --all
-------- Uninstall Beginning --------
Module: mk_arcade_joystick_rpi
Version: 0.1.5.6
Kernel: 4.14.71+ (armv6l)
-------------------------------------
Status: This module version was INACTIVE for this kernel.
depmod....
DKMS: uninstall completed.
------------------------------
Deleting module version: 0.1.5.6
completely from the DKMS tree.
------------------------------
Done.
root@retropie:~# sudo dkms remove -m mk_arcade_joystick_rpi -v 0.1.5.7 --all
-------- Uninstall Beginning --------
Module: mk_arcade_joystick_rpi
Version: 0.1.5.7
Kernel: 4.14.71+ (armv6l)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
mk_arcade_joystick_rpi.ko:
- Uninstallation
- Deleting from: /lib/modules/4.14.71+/
rmdir: failed to remove '': No such file or directory
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod....
DKMS: uninstall completed.
------------------------------
Deleting module version: 0.1.5.7
completely from the DKMS tree.
------------------------------
Done.
root@retropie:~# sudo dkms build -m mk_arcade_joystick_rpi -v 0.1.5.7
Creating symlink /var/lib/dkms/mk_arcade_joystick_rpi/0.1.5.7/source ->
/usr/src/mk_arcade_joystick_rpi-0.1.5.7
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...sud... make -j1 KERNELRELEASE=4.14.71+ all KVERSION=4.14.71+...................
cleaning build area........
DKMS: build completed.
root@retropie:~# sudo dkms install --force -m mk_arcade_joystick_rpi -v 0.1.5.7
mk_arcade_joystick_rpi:
Running module version sanity check.
- Original module
- Found /lib/modules/4.14.71+/updates/dkms/mk_arcade_joystick_rpi.ko
- Storing in /var/lib/dkms/mk_arcade_joystick_rpi/original_module/4.14.71+/armv6l/
- Archiving for uninstallation purposes
- Installation
- Installing to /lib/modules/4.14.71+/updates/dkms/
depmod....
DKMS: install completed.
Thx for your help again. Still not working. :/
Do you have another idea?
Posts: 1,610
Threads: 19
Joined: Feb 2012
Reputation:
29
(10-31-2018, 04:17 AM)majestictragedy Wrote: Thx for your help again. Still not working. :/
Do you have another idea?
The output that you showed seems to suggest that all of the commands worked properly. Even at the end, it says, "DKMS: install completed" without showing any errors.
There is a bit about "rmdir: failed to remove '': No such file or directory" which seems a bit off, but I'm not sure.
After you did all that, did you reboot the machine? After you reboot, could you please tell me the output from these commands?
ls -la /dev/input
dmesg | grep mk_arcade
dmesg | grep js
/etc/modprobe.d/mk_arcade_joystick.conf
sudo modprobe -r mk_arcade_joystick_rpi
sudo modprobe mk_arcade_joystick_rpi
Also, this next command should allow you to test the joystick.
jstest /dev/input/js0
After that, if we still can't figure it out, the next step may be to make an image of your SD card and send it to me. Debugging this remotely is proving to be quite tough, I think. Typically the dkms build/install just works.
Posts: 8
Threads: 1
Joined: Oct 2018
Reputation:
0
Code: root@retropie:~# ls -la /dev/input
total 0
drwxr-xr-x 4 root root 200 Nov 3 10:06 .
drwxr-xr-x 14 root root 3360 Nov 3 10:06 ..
drwxr-xr-x 2 root root 100 Nov 3 10:06 by-id
drwxr-xr-x 2 root root 100 Nov 3 10:06 by-path
crw-rw----+ 1 root input 13, 64 Oct 30 18:18 event0
crw-rw---- 1 root input 13, 65 Nov 3 10:06 event1
crw-rw---- 1 root input 13, 66 Nov 3 10:06 event2
crw-rw---- 1 root input 13, 67 Nov 3 10:06 event3
crw-rw----+ 1 root input 13, 0 Oct 30 18:18 js0
crw-rw---- 1 root input 13, 63 Oct 30 18:18 mice
root@retropie:~# dmesg | grep mk_arcade
[ 3.497067] mk_arcade_joystick_rpi: loading out-of-tree module taints kernel.
[ 3.498250] mk_arcade_joystick_rpi: Freeplay Button Driver
[ 3.498261] mk_arcade_joystick_rpi: pad type : 1
[ 3.498266] mk_arcade_joystick_rpi: pad type : 1
root@retropie:~# dmesg | grep js
root@retropie:~# /etc/modprobe.d/mk_arcade_joystick.conf
-bash: /etc/modprobe.d/mk_arcade_joystick.conf: Permission denied
root@retropie:~# sudo modprobe -r mk_arcade_joystick_rpi
root@retropie:~# sudo modprobe mk_arcade_joystick_rpi
root@retropie:~# ls -la /dev/input
total 0
drwxr-xr-x 4 root root 200 Nov 3 10:10 .
drwxr-xr-x 14 root root 3360 Nov 3 10:06 ..
drwxr-xr-x 2 root root 100 Nov 3 10:06 by-id
drwxr-xr-x 2 root root 100 Nov 3 10:06 by-path
crw-rw----+ 1 root input 13, 64 Nov 3 10:10 event0
crw-rw---- 1 root input 13, 65 Nov 3 10:06 event1
crw-rw---- 1 root input 13, 66 Nov 3 10:06 event2
crw-rw---- 1 root input 13, 67 Nov 3 10:06 event3
crw-rw----+ 1 root input 13, 0 Nov 3 10:10 js0
crw-rw---- 1 root input 13, 63 Oct 30 18:18 mice
root@retropie:~# dmesg | grep mk_arcade
[ 3.497067] mk_arcade_joystick_rpi: loading out-of-tree module taints kernel.
[ 3.498250] mk_arcade_joystick_rpi: Freeplay Button Driver
[ 3.498261] mk_arcade_joystick_rpi: pad type : 1
[ 3.498266] mk_arcade_joystick_rpi: pad type : 1
[ 263.240093] mk_arcade_joystick_rpi: exiting
[ 283.690231] mk_arcade_joystick_rpi: Freeplay Button Driver
[ 283.690251] mk_arcade_joystick_rpi: pad type : 1
[ 283.690256] mk_arcade_joystick_rpi: pad type : 1
root@retropie:~# dmesg | grep js
root@retropie:~# /etc/modprobe.d/mk_arcade_joystick.conf
-bash: /etc/modprobe.d/mk_arcade_joystick.conf: Permission denied
root@retropie:~# sudo modprobe -r mk_arcade_joystick_rpi
root@retropie:~# sudo modprobe mk_arcade_joystick_rpi
root@retropie:~# jstest /dev/input/js0
Driver version is 2.1.0.
Joystick (GPIO Controller 1) has 2 axes (X, Y)
and 9 buttons (BtnA, BtnB, BtnX, BtnY, BtnTL, BtnTR, BtnSelect, BtnStart, BtnMode).
This was the output i got after reboot. The command to test the joystick works fine. So I guess this means the buttons should work. But still not in the emulation station interface...sooo what can I do next? Do you need a image of my sd card?
Posts: 1,610
Threads: 19
Joined: Feb 2012
Reputation:
29
That’s interesting. It seems like the joystick is working, as you said, in jstest.
In EmulationStation, if you have a usb keyboard plugged in, you can hit Start (maybe space bar?) at the main menu. Then select Configure Input. Then on the Freeplay hold A when it asks.
There’s another way to delete the current config and have it ask to config the inputs at bootup, but I don’t recall offhand. I’m just out on my phone right now.
Posts: 8
Threads: 1
Joined: Oct 2018
Reputation:
0
(11-04-2018, 03:28 AM)Flavor Wrote: That’s interesting. It seems like the joystick is working, as you said, in jstest.
In EmulationStation, if you have a usb keyboard plugged in, you can hit Start (maybe space bar?) at the main menu. Then select Configure Input. Then on the Freeplay hold A when it asks.
There’s another way to delete the current config and have it ask to config the inputs at bootup, but I don’t recall offhand. I’m just out on my phone right now.
Thx for the information. I can configure the input but EmulationStation only reconize the usb keyboard...how is this possible?
Posts: 1,610
Threads: 19
Joined: Feb 2012
Reputation:
29
11-06-2018, 03:27 AM
(This post was last modified: 11-06-2018, 03:27 AM by Flavor.)
(11-04-2018, 10:27 PM)majestictragedy Wrote: (11-04-2018, 03:28 AM)Flavor Wrote: That’s interesting. It seems like the joystick is working, as you said, in jstest.
In EmulationStation, if you have a usb keyboard plugged in, you can hit Start (maybe space bar?) at the main menu. Then select Configure Input. Then on the Freeplay hold A when it asks.
There’s another way to delete the current config and have it ask to config the inputs at bootup, but I don’t recall offhand. I’m just out on my phone right now.
Thx for the information. I can configure the input but EmulationStation only reconize the usb keyboard...how is this possible?
I really don't know. I'm pretty confused about it, now. If you could image the SD card and somehow share the file with me, I can try to investigate. I don't even know what next step to take for the remote diagnosis.
I just checked, and here's where the joystick configs are stored.
in the /opt/retropie/configs/all/retroarch/autoconfig directory
and in /opt/retropie/configs/all/emulationstation/es_input.cfg
Maybe show the output of
ls -la /opt/retropie/configs/all/retroarch/autoconfig
cat /opt/retropie/configs/all/emulationstation/es_input.cfg
You could also do this:
cd /opt/retropie/configs/all/retroarch/autoconfig
rm *
rm /opt/retropie/configs/all/emulationstation/es_input.cfg
Then, after you reboot, at the next bootup it should start up and go directly into the joystick input. I think that's probably worth a try, but it could mess other joystick/keyboard configurations that you might have. Who knows, those could be what's messing things up here, too???
|