no Gamepads Detected

[yctn]

@mitu i see mupen64plus-glide64 as emulator

cat runcommand.info
n64
mupen64plus-glide64
/home/test/RetroPie/roms/n64/mario-kart.n64
/opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-glide64mk2 "/home/test/RetroPie/roms/n64/mario-kart.n64"

and

cat runcommand.log
Parameters:
Executing: /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-glide64mk2 "/home/test/RetroPie/roms/n64/mario-kart.n64"
grep: /opt/retropie/configs/all/retroarch-joypads/*.cfg: No such file or directory
grep: /opt/retropie/configs/all/retroarch-joypads/*.cfg: No such file or directory
grep: /opt/retropie/configs/all/retroarch-joypads/*.cfg: No such file or directory
/opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh: line 425: /proc/device-tree/compatible: No such file or directory

since the output was quite small i thought it would be okay if i post them here.

[mitu]

@yctn said in no Gamepads Detected:

grep: /opt/retropie/configs/all/retroarch-joypads/*.cfg

This means you have no gamepads profiles configured for RetroArch and thus the auto-configuration process didn't work since it uses those profiles to configure the gamepads in Mupen64plus (the standlone emulator). Did you disable the EmulationStation's auto-configuration scripts ?

[yctn]

@mitu no i did not disable Emulationstation auto-configuration scripts as far as i know. i just ran the retropie_setup.sh with all the default settings.

[yctn]

@yctn i checked in the ./retropie_setup.sh and auto-configuration is set to enabled perfectly fine.
would it matter if i ran ./retropie_setup.sh as root? but emulationstation is running as a non root user?
i already did chmod 777 /opt/retropi -R to make sure my non root user has access to everything there.

i am confused about how things should be exactly.

[mitu]

@yctn said in no Gamepads Detected:

@yctn i checked in the ./retropie_setup.sh and auto-configuration is set to enabled perfectly fine.

That's not where the auto-configuration is saved, but if you didn't explicitely disable it, I don't understand why the EmulationStation configuration of the gamepad hasn't created the corresponding RetroArch profile(s) - perhaps folder permissions at the time when the configuration was run ?

would it matter if i ran ./retropie_setup.sh as root? but emulationstation is running as a non root user?

While retropie_setup.sh needs to have root permissions - but it should run with sudo, not as root - , running EmulationStation/emulators is not.

i already did chmod 777 /opt/retropi -R to make sure my non root user has access to everything there.

Please don't change any permissions since they're not needed, retropie_setup.sh should handle any needed permissions. Did you ran EmulationStation as root as some point ? Or started as root the initial setup ? If the folders under /opt/retropie/configs do not have the correct permissions, then saving the controller profiles wouldn't work if the folders are/were owned by root.

[yctn]

@mitu i tried to run emulationstation as root but it refuses to do so. so i am running emulatorstation as a user.
no i did not explicitely disable it.
i already tried to reconfigure the controller in emulationstation but that does not seem to save the controller config.
when i open the retroarch menu it also looks pretty.... bugged/strange. i dont know how to proceed from here.

[mitu]

@yctn I recommend you reinstall the OS and re-do the installation. Start the installation as a regular user with sudo, as explained in the installation docs. Start EmulationStation from the rpi shortcut/icon added by the installer - as regular user also.

[yctn]

@mitu thing is. this is not a raspbarry pi its an a gigabyte brix. anyway its just a regular pc with debian 12. on top of that i have installed the retropi installer thing. i also have 10+ years experience with working with linux so overall i have a pretty good understanding of what i am doing. i just dont know the whole retropi system and what it exactly needs/wants. i can definitly do a reinstall. but i would actualy prefer to learn/understand what is going on and fix it.

[mitu]

This post is deleted!

[mitu]

Then use retropie-setup to uninstall RetroPie, then install it again.

[yctn]

@mitu after the recompile things are looking better. the n64 controller works. sort of inside an n64 game.
i have 2 problems tho. in Emulationsstation i chose the HOME button on my controller as the hotkey button. that does not seem to do anything while ingame.

also i have mapper A to the A button. but once inside mario kart it seems to be that i need to use the B button to actualy drive.
please advice.

[yctn]

@yctn i checked with jstest my HOME button = 12 and A button = 2

input_device = "SWITCH CO.,LTD. Usb Controller"
input_driver = "udev"
input_vendor_id = "3695"
input_product_id = "4371"
input_left_btn = "h0left"
input_state_slot_decrease_btn = "h0left"
input_right_btn = "h0right"
input_state_slot_increase_btn = "h0right"
input_r_btn = "5"
input_save_state_btn = "5"
input_down_btn = "h0down"
input_l_btn = "4"
input_load_state_btn = "4"
input_y_btn = "3"
input_x_btn = "0"
input_menu_toggle_btn = "0"
input_b_btn = "1"
input_reset_btn = "1"
input_a_btn = "2"
input_up_btn = "h0up"
input_select_btn = "8"
input_start_btn = "9"
input_exit_emulator_btn = "9"
input_l_x_plus_axis = "+0"
input_l_y_minus_axis = "-1"
input_enable_hotkey_btn = "12"
input_l2_btn = "6"
input_l_y_plus_axis = "+1"
input_l_x_minus_axis = "-0"

so it would seems to be that this correctly configured...

[mitu]

@yctn said in no Gamepads Detected:

i have 2 problems tho. in Emulationsstation i chose the HOME button on my controller as the hotkey button. that does not seem to do anything while ingame.

The hotkey_enable by itself does nothing, you need to press the corresponding action in combination with it in order to trigger something - see here.
NB: for standalone emulators, this doesn't work, though I think Mupen64plus makes an exception for the Exit hotkey combo.

also i have mapper A to the A button. but once inside mario kart it seems to be that i need to use the B button to actualy drive.

Use the libretro core and if you still get this assignment, you can open the menu and remap the buttons as you like, saving an input override for the game system.

[yctn]

@mitu it seems i was able to fix the A button by manualy editing /opt/retropie/configs/n64/InputAutoCfg.ini this is not the correct way to do it? when i hit ESC on my keyboard it exits the n64 game perfectly fine. but i dont know which key id the ESC button is so i dont know how to change that in InputAutoCfg.ini

hmm... i thought muten64plus-glide64 is not a libretro core and therefor i can not open the menu to remap the button using a UI?

[mitu]

@yctn said in no Gamepads Detected:

hmm... i thought muten64plus-glide64 is not a libretro core and therefor i can not open the menu to remap the button using a UI?

That's why i said to use the libretro core ...

[yctn]

@mitu i found out that the start + home button will quit the emulation and return to th retropi menu when i am in a rom. this is nice cause i notice that the graphics of mupen64plus-glide64 are better then with the ir/libretro core.

i am now facing issues with connecting my ps3 controller.
i installed the sixaxis driver. and tried to connect my ps3 controller many times.

[Tue Jan 21 11:00:21 2025] input: PLAYSTATION(R)3 Controller Motion Sensors as /devices/pci0000:00/0000:00:14.0/usb2/2-7/2-7:1.0/bluetooth/hci0/hci0:2/0005:054C:0268.0010/input/input39
[Tue Jan 21 11:00:21 2025] input: PLAYSTATION(R)3 Controller as /devices/pci0000:00/0000:00:14.0/usb2/2-7/2-7:1.0/bluetooth/hci0/hci0:2/0005:054C:0268.0010/input/input38
[Tue Jan 21 11:00:21 2025] sony 0005:054C:0268.0010: input,hidraw1: BLUETOOTH HID v80.00 Joystick [PLAYSTATION(R)3 Controller] on 6c:71:d9:b6:8b:8c

it seems that the controller itself is connected with bluetooth. but there is no entry in /dev/input so it seems to be that emulationstation does not see that there is a controller.
any advice?

[yctn]

@mitu ```
[Tue Jan 21 11:12:57 2025] sony 0005:054C:0268.0013: controller with MAC address 60:38:0e:2b:57:a3 already connected
[Tue Jan 21 11:12:57 2025] sony 0005:054C:0268.0013: hidraw2: BLUETOOTH HID v80.00 Joystick [PLAYSTATION(R)3 Controller] on 6c:71:d9:b6:8b:8c
[Tue Jan 21 11:12:57 2025] sony 0005:054C:0268.0013: failed to claim input

something is wrong cause that failed to claim input is a probem.

[yctn]

[bluetooth]# info 60:38:0E:2B:57:A3
Device 60:38:0E:2B:57:A3 (public)
	Name: Sony PLAYSTATION(R)3 Controller
	Alias: Sony PLAYSTATION(R)3 Controller
	Class: 0x00000508
	Icon: input-gaming
	Paired: no
	Bonded: no
	Trusted: yes
	Blocked: no
	Connected: no
	WakeAllowed: yes
	LegacyPairing: no
	UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v054Cp0268d0000

and

[Tue Jan 21 11:27:01 2025] sony 0005:054C:0268.0019: unknown main item tag 0x0
[Tue Jan 21 11:27:02 2025] input: PLAYSTATION(R)3 Controller Motion Sensors as /devices/pci0000:00/0000:00:14.0/usb2/2-7/2-7:1.0/bluetooth/hci0/hci0:1/0005:054C:0268.0019/input/input56
[Tue Jan 21 11:27:02 2025] input: PLAYSTATION(R)3 Controller as /devices/pci0000:00/0000:00:14.0/usb2/2-7/2-7:1.0/bluetooth/hci0/hci0:1/0005:054C:0268.0019/input/input55
[Tue Jan 21 11:27:02 2025] sony 0005:054C:0268.0019: input,hidraw1: BLUETOOTH HID v80.00 Joystick [PLAYSTATION(R)3 Controller] on 6c:71:d9:b6:8b:8c

[mitu]

@yctn said in no Gamepads Detected:

i installed the sixaxis driver. and tried to connect my ps3 controller many times.

Did you follow the steps in the documentation ? PS3 has an awkward pairing method that needs to be connected via USB and be sent a pairing request/authorization before pairing via Bluetooth.

[yctn]

@mitu
yes i followed the septs in the documentation. so yes i connected it by cable and pushed the button and the disconnecting again.
i think i have at least tried it like 40/50 times and kept checking the dmesg. something must be off. see the following output.

bluetoothctl
Agent registered
[CHG] Controller 6C:71:D9:B6:8B:8C Pairable: yes
[bluetooth]# devices
Device 60:38:0E:2B:57:A3 Sony PLAYSTATION(R)3 Controller
[bluetooth]# info 60:38:0E:2B:57:A3
Device 60:38:0E:2B:57:A3 (public)
	Name: Sony PLAYSTATION(R)3 Controller
	Alias: Sony PLAYSTATION(R)3 Controller
	Class: 0x00000508
	Icon: input-gaming
	Paired: no
	Bonded: no
	Trusted: yes
	Blocked: no
	Connected: no
	WakeAllowed: yes
	LegacyPairing: no
	UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v054Cp0268d0000
[bluetooth]# trust 60:38:0E:2B:57:A3
Changing 60:38:0E:2B:57:A3 trust succeeded
[bluetooth]# scan
Missing on/off/bredr/le argument
[bluetooth]# scan on
Discovery started
[CHG] Controller 6C:71:D9:B6:8B:8C Discovering: yes
[CHG] Device 60:38:0E:2B:57:A3 Connected: yes
[CHG] Device 60:38:0E:2B:57:A3 Name: PLAYSTATION(R)3 Controller
[CHG] Device 60:38:0E:2B:57:A3 Alias: PLAYSTATION(R)3 Controller
[CHG] Device 60:38:0E:2B:57:A3 Connected: no
[CHG] Controller 6C:71:D9:B6:8B:8C Powered: no
[CHG] Controller 6C:71:D9:B6:8B:8C Discovering: no
[CHG] Controller 6C:71:D9:B6:8B:8C Class: 0x00000000
[DEL] Media /org/bluez/hci0
	SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
	SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent unregistered
[DEL] Device 60:38:0E:2B:57:A3 PLAYSTATION(R)3 Controller
[DEL] Controller 6C:71:D9:B6:8B:8C test [default]
[NEW] Media /org/bluez/hci0
	SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
	SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[NEW] Controller 6C:71:D9:B6:8B:8C BlueZ 5.66 [default]
[NEW] Device 60:38:0E:2B:57:A3 Sony PLAYSTATION(R)3 Controller
Agent registered
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C Class: 0x0000010c
[CHG] Controller 6C:71:D9:B6:8B:8C Powered: yes
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001801-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001800-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Controller 6C:71:D9:B6:8B:8C Alias: BlueZ 5.66
[CHG] Device 60:38:0E:2B:57:A3 WakeAllowed: yes
[CHG] Controller 6C:71:D9:B6:8B:8C Name: test
[CHG] Controller 6C:71:D9:B6:8B:8C Alias: BlueZ 5.66
[CHG] Controller 6C:71:D9:B6:8B:8C Alias: test
[bluetooth]# info 60:38:0E:2B:57:A3
Device 60:38:0E:2B:57:A3 (public)
	Name: Sony PLAYSTATION(R)3 Controller
	Alias: Sony PLAYSTATION(R)3 Controller
	Class: 0x00000508
	Icon: input-gaming
	Paired: no
	Bonded: no
	Trusted: yes
	Blocked: no
	Connected: no
	WakeAllowed: yes
	LegacyPairing: no
	UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v054Cp0268d0000