@Aterlom said in LR-FBNeo Diagnostic Input (dip switches) not working:

I have modified the line of the retroarch-core-options.cfg Diagnostic Input = “shift” in case the combination HK + Y would work.

Core options are lists of available choices, you can't just throw random arbitrary values at them and expect it will work. Neither shift nor hk+y are valid choices

@Aterlom said in LR-FBNeo Diagnostic Input (dip switches) not working:

I have tried all the options offered by the diagnostic input in the core options menu.

Assuming you really did that at some point instead of trying to force random stuff by editing files, and pressed the correct inputs matching your choice, i'm not 100% sure what's your problem here. I know not using a dedicated button for retroarch's hotkey button (the one you use to open retroarch's menu) can cause various problems if the core is using holding mecanisms with the same button (let's say you are using start as your retroarch hotkey, using "hold start" as your diagnostic input might not work because retroarch won't send the input to the core when it is held), maybe that's what you are doing. The only other logical conclusion would be that your "keyboard" device can't hold keys for the 60+ frames required and/or is affected by some kind of ghosting.

@Aterlom said in LR-FBNeo Diagnostic Input (dip switches) not working:

I have read a lot of documentation

The only documentation you are supposed to read is a 1-liner though : https://docs.libretro.com/library/fbneo/#dipswitches

Great. The output means software side is working as expected.

Now, if you let sudo evtest running and then connect a button or GPIO pin to Ground (GND) you should get a signal from evtest on the screen. Any button is low active (i.e. when the voltage level is 0 it means a button is pressed). When a button is unpressed (open) the voltage is 3.3V.

The game has been updated

@mitu created the folder and copied the file

pi@retropie:/lib/modules/5.10.103-v7+/updates/dkms $ ls
hid-sony.ko

pi@retropie:/lib/modules/5.10.103-v7+/updates/dkms $ sudo modinfo hid_sony
filename: /lib/modules/5.10.103-v7+/kernel/drivers/hid/hid-sony.ko

restarted

but still controller not recognized

too bad..

@Jiryn said in Manual Installation Broken at GitHub level:

Remote: Support for password authentication was removed on August 13, 2021

The issue was caused by your typo for the repository URL. Instead of RetroPie-Setup you entered RetroPie-Steup and Github assumed is a private repository and tried to authenticate you.

@hoeveler If core input remapping doesn't work, you can either do a configuration override (per-game) or manually add the input configuration in a game dependent configuration file (explained also on the same page).

@Folly

Cool thanks ill give it a try

@ldeveraux damn, sounds logic haha

@barbudreadmon oh ok I didn't realize they all should be uncompressed, I will try uncompressing them.

I will try the dmesg command and see what it shows, thanks

@CaptRobovski said in Can I backup current emulator state - corrupted memory stick:

A quick question - should the filename under etc/udev/rules.d end in the suffix '.rules' ? I have other files in there, such as 99-input.rules, 99-bluetooth.rules.

No, the extension is not needed. Only the lexically order may be relevant of all rule files (cf. man udev -> RULES FILES).

The memory stick has left the factory mostly fine I would assume. It is the firmware that make things worse in use cases like this (as likely the USB spec has not been implemented by the letter by the vendor).

If you change make and model of the memory stick you may leave the power control rule enabled (adapt to the VID/PID). Does not have an impact unless you run on battery.

Or you can make a backup of you new memory stick and run it without the power control rule. If things repeat restore the memory stick and enable the rule.
However, if it repeats on a different make/model the issue could also be caused by the RaspBerry Pi Kernel USB implementation.

Unless you're running under X/Desktop/Wayland, there's no control over the which display comes 'first' at runtime. You can use config.txt to enable/disable the LCD (is it a DSI display ?) or HDMI, but that requires a reboot.

@mitu and @Thorr69

I found the TV setting. Thank you very much its perfect. Will also test out the cmdline.txt method since that setting was not easy to find on the TV!!