Forum Replies Created
-
AuthorPosts
-
04/10/2015 at 09:08 in reply to: Frustration setting up RetroPie- Keyboard and gamepads not recognized #94372klausParticipant
I still did not get the keyboard to work but recently I purchased two gamepad and those work well.
04/06/2015 at 14:03 in reply to: Frustration setting up RetroPie- Keyboard and gamepads not recognized #93972klausParticipantfrom IRC I got the hint that MAYBE this might have something to do with the installation method. So instead of installing the binary packages, I ran retropie-setup doing a source install yesterday. This did not change the behavior.
Also changing the input driver to sdl2 makes the error message about udev not finding an input device go away but keypresses are still not recognized.
03/28/2015 at 23:12 in reply to: Frustration setting up RetroPie- Keyboard and gamepads not recognized #92994klausParticipantso I ran strace on retroarch and it seems that some links of udev are wrong or missing. The strace can be founde here: http://dl.ffm.freifunk.net/pastebin/aikohdohjo
I am running retroarch as user pi (the user is in the input-group) like this:
/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-gambatte/gambatte_libretro.so game.smc03/28/2015 at 18:59 in reply to: Frustration setting up RetroPie- Keyboard and gamepads not recognized #92968klausParticipantjust a me too. – I am experiencing the same problems. From readin the log of retroarch this is not surprising.
/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-gambatte/gambatte_libretro.so /media/evanas-snes/Super_Mario_Land.zip
RetroArch [WARN] :: patch_content :: Did not find a valid content patch.
MBC1 ROM loaded.
cgb: 0
rambanks: 0
rombanks: 4
RetroArch: rarch_log_libretro: [libretro INFO] :: [Gambatte]: Got internal game name: SUPER MARIOLAND.
RetroArch [WARN] :: gl_glsl_init :: [GL]: Stock GLSL shaders will be used.
RetroArch [WARN] :: udev_input_init :: [udev]: Couldn’t open any keyboard, mouse or touchpad. Are permissions set correctly for /dev/input/event*?I do have a USB-keyboard attached and it is working fine – I can type in the console. So I checked the permissions as suggested in the error-message.
pi@raspberrypi /dev/input $ ls -ltrachrR /dev/input
/dev/input:
insgesamt 0
drwxr-xr-x 4 root root 140 Mär 28 16:17 .
drwxr-xr-x 12 root root 3,2K Mär 28 16:31 ..
crw-rw-rwT 1 root input 13, 63 Mär 28 16:33 mice
crw-rw-rwT 1 root input 13, 65 Mär 28 16:33 event1
crw-rw-rwT 1 root input 13, 64 Mär 28 16:33 event0
drwxr-xrwx 2 root root 80 Mär 28 16:33 by-path
drwxr-xrwx 2 root root 80 Mär 28 16:33 by-id/dev/input/by-path:
insgesamt 0
lrwxrwxrwx 1 root root 9 Mär 28 16:17 platform-bcm2708_usb-usb-0:1.2:1.1-event -> ../event1
drwxr-xr-x 4 root root 140 Mär 28 16:17 ..
lrwxrwxrwx 1 root root 9 Mär 28 16:17 platform-bcm2708_usb-usb-0:1.2:1.0-event-kbd -> ../event0
drwxr-xrwx 2 root root 80 Mär 28 16:33 ./dev/input/by-id:
insgesamt 0
lrwxrwxrwx 1 root root 9 Mär 28 16:17 usb-046a_0021-event-if01 -> ../event1
drwxr-xr-x 4 root root 140 Mär 28 16:17 ..
lrwxrwxrwx 1 root root 9 Mär 28 16:17 usb-046a_0021-event-kbd -> ../event0
drwxr-xrwx 2 root root 80 Mär 28 16:33 .originally the event-devices had 660 set, I tried setting o+rw as you can see but the error message did not change.
Where should I go from here?
-
AuthorPosts