@00Hugo said in Xpad driver installation issue - not existing commit:

One question regarding that: The controller is paired now in Bluetooth setup, but why it is not visible as device in "Configure Input"?

Maybe it needs another driver (xpadneo) ? As I said, xpad is used only for wired Xbox compatible drivers.

@Jezzer said in Compiling drivers for Deskpi:

I tried to install cmake from buildessentials but it appears that you need buster / bookworm / whatever it's called. I wasn't sure what I should be installing here... Anyone know how to do this?

cmake is already installed on the RetroPie image for the Pi4 and the buildessential metapackage is installed aswell, so compiling shoudn't be an issue. Did you try compiling and got an error - if so, can you post the actual error message here so that we can help fix it ? Do you have a link to the instructions/documentation of the drivers where the installation/compilation is explained ?

Older devices (GL2/OpenGLES2) cannot use glcore, since it needs at least GL3/OpenGL3 to work.

Can you elaborate on that sentence above, though?

Some cores need a specific OpenGL and/or Vulkan version to work and if the front-end driver (i.e. RetroArch's) does not support that version, the core won't work.
For instance, Flycast can be compiled for Vulkan and when started will request a Vulkan context from RetroArch. But if RetroArch doesn't support Vulkan, the core cannot start and the emulation stops.

@Boum-01 Thanks! I will use this to further improve the driver.

@Chef-Otis, have you followed the steps in the README? Were you able to start the service, or what issue are you facing exactly?

I usually respond faster when the error is reported through this channel: GitHub Issues.

It turns out the issue was between the controller and the chair.

I'm posting my resolution here in case someone else ends up with the same issue and goes looking...

I miswired the controller (it came with no documentation), but I came across this blog post (https://cy-822b.blogspot.com/2016/08/the-cy-822b-usb-led-joystick-controller.html) that showed this image:
c0fb63ff-f849-4c20-b512-ae2dd514b54c-image.png

The controller board looks like:
856a91fc-99f3-4ced-b08c-acd40ff39054-image.png

The buttons have a 2-pin connector on them so I figured the connected to the lower edge of the image above. But the connection actually happens in the button housing and the 3-pin connector is more than just for the LED, it also contains the switch wiring. So the 2-pin connector connects into the button housing and the 3-pin wire from the housing connects into the controller board.

I went back to the original Amazon page and found that there are some pictures that describe the wiring, but not terribly clearly:
cd4a53c7-a851-42b4-875b-919802fd6439-image.png

In the end all on me. I hope this helps someone else in the future.

Cheers,

Steve

Could someone publish this patch on
RetroPie-Setup/scriptmodules/supplementary/customhidsony ?

@mitu the thing i should know do is to open the retropie datas in which the retropie folders are is it right?

I'm not sure what you mean. If you're referring to the installation of the Nintendo HID driver I mentioned before, that can be done outside of any RetroPie folders, since it's not directly related to RetroPie.

Post Update:
With this command I can display without problem "image-test.gif" in this case, I think the problem is something in the retropie configuration that I can't see

pi@raspberrypi ~ $ sudo apt-get install fbi pi@raspberrypi ~ $ wget https://ozzmaker.com/piscreen/image-test.gif pi@raspberrypi ~ $ sudo fbi -noverbose -T 1 -a -d /dev/fb1 image-test.gif

config.txt.PNG
(/boot/config.txt)

@buzz thank you for your response and sorry for posting on wrong forum. Cheers !

@pscotto1234 said in Question about Mesa (Vulkan) Driver:

@dankcushions ok, thanks. Do you think it will be added to retropie?

yes at some point Retropie will be able to use it. when.... thats the question.

best not to hold your breath for it.

I see this topic is quite old but I had this problem as well. Perhaps adding it here will help others find it more easily. My hubpiwi stopped working when I upgraded my raspberry pi zero (no W) with the hubwipi to raspbian bulleye. The thing I finally stumbled on to was to add wext to the wpa_supplicant options. Here are the details with thanks to those who wrote this up:

https://www.linuxbabe.com/debian/connect-to-wi-fi-from-terminal-on-debian-wpa-supplicant

The following is needed for hubwipi using rtl8188EUS
lsusb ->
ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter

You can get the wifi working from the command line using this:

sudo wpa_supplicant -B -D wext -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf

Unfortunately, it will be gone after a reboot. To get it to start at boot time see (with my thanks here as well)

https://superuser.com/questions/1434621/set-wpa-supplicant-default-driver-on-startup

Here is what worked for me: To the end of the file /etc/dhcpcd.conf. add:

interface wlan0 env ifwireless=1 env wpa_supplicant_driver=wext

Your interface name may be different from wlan0. Running the command

ip addr

will tell you the name.

I have tried this on other raspberry pi zero w's and adding the "wext" did not seem to bother them. I did not do too much testing here so I only add the wext when I need it.

One of the notes I saw warned that the network speed of the rtl8188eus was low and I experienced this as well but it was sufficient for my purpose and let me update the OS on the rpi zero with the hubwipi.

I hope this helps someone searching for how to get the hubwifi to work again with a newer Raspian OS release.

The project at https://github.com/swkim01/waveshare-dtoverlays offers only the new driver setup for the display, it doesn't provide any scripts.

can you elaborate?

Sure. You want to handle 2 video configurations - output to HDMI (which is default) and via the LCD. Save the default config.txt in /boot/ as /boot/config-hdmi.txt. Install and configure the LCD drivers (modify the config.txt) accordingly, make sure it works, then copy the config.txt to /boot/config-waveshare.txt.

Create 2 scripts in /home/pi/RetroPie/retropiemenu

hdmi.sh, containing #!/usr/bin/env bash cp -f /boot/config-hdmi.txt /boot/config.txt lcd.sh, containing #!/usr/bin/env bash cp -f /boot/config-waveshare.txt /boot/config.txt make the scripts executable by running chmod +x /home/pi/RetroPie/retropiemenu/hdmi.sh chmod +x /home/pi/RetroPie/retropiemenu/lcd.sh

Now, when starting EmulationStation, you'll have 2 new entries in the RetroPie system - HDMI and LCD, executing one of them will switch the video output configuration. After running one of the entries, you'll have to reboot to activate the new configuration.

@mitu OK thanks

if anyone is still interested in this, check out these cool devices on icode.com. they allow you to have up to 4 paddles or joysticks connected to you PC via usb. There is even a bluetooth version.

Atari paddles and joysticks usb adapter

All right I'll try that!