No game pad detected, no js0, js1, js2, js3

alphaquail

Hi BuZz

Apologies

Pi Model or other hardware: RP4
Power Supply used: (If using a Pi) Official USB C, DC 5.1V 3A
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): v4.7.1
Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used) Retro Pie Website link https://github.com/RetroPie/RetroPie-Setup/releases/download/4.7.1/retropie-buster-4.7.1-rpi4_400.img.gz
USB Devices connected: Wireless USB keyboard and mouse (single dongle)
Controller used: CHeap USB Meagdrive style https://www.amazon.co.uk/gp/product/B07PZ8F7F6/ref=ppx_yo_dt_b_asin_title_o06_s00?ie=UTF8&psc=1
Error messages received: No Game Pad detected on boot
Verbose log (if relevant): ???
Guide used: (Mention if you followed a guide) YouTube
File: (File with issue - with FULL path) NA
Emulator: (Name of emulator - if applicable) None as yet
Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS) Not sure how to get these I'm new to this
How to replicate the problem: download the image file and boot up the pi with USBs plugged in

sleve_mcdichael

Guide used: (Mention if you followed a guide) YouTube

That's a great way to find information that was relevant a year ago. Technically you "should" only use the official docs but the controller config is pretty basic stuff. As you said, just boot up with the controller plugged in.

If that's not working, have you made sure the controller itself works, i.e. on a PC?

alphaquail

@sleve_mcdichael

Ok. I feel like it should be basic stuff but I'm falling at the first hurdle with this

I can say the pad works on a PC. I also have an xbox style Bluetooth controller (again works on pc) but this doesn't work on the Pi

BuZz

@alphaquail Please can you boot without the controllers connected. Then once booted drop to a command prompt (F4) or SSH in (see docs). Connect a controller, then write in the terminal dmesg >~/dmesg.txt - this should create a file dmesg.txt in /home/pi which you can copy off with SFTP/SCP. Please post the file here via a pastebin site.

(If using SSH you could also just write dmesg on its own then copy the last lines off the terminal)

Do you have a manual for the controller - maybe it has different modes of operation you can switch between?

alphaquail

@buzz so I ran dmesg and it has created a file but I'll need to work out how to move it from the Pi to my PC. My command line knowledge is close to zero currently. This may take a while but I'm getting there...

alphaquail

dmesg.txt

mitu

The log file is ok, but it doesn't show any devices except the Telink Wireless Receiver, which keeps disconnecting and re-connecting over and over:

[ 2760.616988] usb 1-1.1: new full-speed USB device number 5 using xhci_hcd
[ 2760.757016] usb 1-1.1: New USB device found, idVendor=248a, idProduct=8367, bcdDevice= 1.00
[ 2760.757036] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2760.757053] usb 1-1.1: Product: Wireless Receiver
[ 2760.757069] usb 1-1.1: Manufacturer: Telink
...
[ 2800.973031] usb 1-1.1: USB disconnect, device number 5
..
[ 3012.909866] usb 1-1.1: new full-speed USB device number 6 using xhci_hcd
[ 3091.670661] usb 1-1.1: USB disconnect, device number 6
...
# etc

Remove the wireless dongle for the keyboard/mouse and try again to connect the gamepad(s), see if they get detected.

alphaquail

@mitu gamepad still not connected with a wired keyboard and when no keyboard is attached

Similar usb output in command line explaining a USB keyboard being attached when I run dmesg

mitu

@alphaquail dmesg shows the messages since boot, so if you're running it again (without rebooting) you'll see again the keyboard messages.
Run dmesg -w from the command line and plug in the controller - it should show only the current system logs. You can terminate the dmesg command with Ctrl + C.

alphaquail

@mitu - This is what I get for dmesg -w. I can;'t see the controller in the command line output?

mitu

The controller doesn't seem to be detected at all, it's just the keyboard that shows up in the logs. Looks like it's not working with the Pi at all, there's no message in the log except for the USB keyboard.
Not sure what could be done in this case, get another controller or try pairing the Xbox controller via Bluetooth.

alphaquail

@mitu ok so probbly a cheap controller. I'll look at another. Meanwhile I have ran dmesg with the wireless Bluetooth controller plugged in. Looks to be recognising it although running the jstest command I dont get anything. See pastebin here

mitu

I see another disconnect after the gampad is plugged in. Does the log shows continuously connects/disconnects or the gamepad stays connected ?
First connection recognises the device as an input device, but the 2nd one doesn't.

I'm wondering if there's something wrong with the USB on the Pi - is your TV a 4k model ? Can you try lowering the resolution to 1080p (see here how) and retry ?

alphaquail

@mitu it's an old Samsung TV it won't go to 4k. I can't believe how difficult it is to set up a controller. I'll try an approved wired controller I know people have had some success with, if not I'll give up on this and make another NAS. That I can do. thanks for all you're help it's really appreciated.

mitu

@alphaquail said in No game pad detected, no js0, js1, js2, js3:

I can't believe how difficult it is to set up a controller.

It's usually not that difficult, the most issues we have reported are from wireless (Bluetooth) controllers. What you could try:

update your system, including kernel/firmware/packages. Use the update function from RetroPie-Setup.
try connecting the gamepad to the USB2 ports, not the USB3 ones.
last resort: if the PI is in a case, take it out and try without the case.

alphaquail

@mitu ok So I tried the above and still no joy. Something is recognised when I go with the wireless controller running dmesg and dmesg -w as you said but it's not connecting fully. Nor can I detect the device through js0 as per my original post title. I've taken it out of the case too.

I have another Raspberry Pi 4 and have tried the controller detection on that. Different board, different OS (Raspberry OS) and still no joy on the XBox style controller. I get an odd message when running jstest /dev/input/event0 in the command line (not js0 as no file found, going into the file directory only files in this folder are event0,1,2,3), which says 'jstest is not full compatible with your kernel' unable to retrieve button map'.

I have ordered a wire, Retro Pie compatible controller from Amazon. if that doesnt work I'm putting it down to me doing something wrong or both Pi's are broken (despite being brand new).

alphaquail

This post on Reddit might have something to do with joystick configuration?

mitu

@alphaquail yes, it does, but how is this related to your issue ? You say your controllers are not detected at all, the post in question talks about calibrating the controllers, after they've been detected and configured by the OS (Linux).

alphaquail

@mitu I dunno I'm very new at this I thought I failed to install something related to joystick detection (one of the tools in that post). The fact that neither Pi I own detects neither controller I have is odd. Has to be a controller compatibility issue surely then. I've ordered this Raspberry Pi compatible controller on Amazon. Fingers crossed this works.

alphaquail

@mitu thanks for all you help and tuition on command line earlier. FYI the recently purchased Retoflag Controller IS detected by Retopie and it allows me to set this up. Two buttons aren't being detected in the configuration but are in jstest so one for me to delve into but think I have half a clue what I'm doing now thanks to you.

Morale of the story here is make sure you purchase a recognised, compatible gamepad first....