Raspberry Pi 5 - official announcement

zaphod24

@PiBoyyy Certainly can, but I already have 2 8bitdo USB gamepads which worked fine on pi4

retropieuser555

@zaphod24 certainly seems strange. Not sure I have any USB controllers although I might try and plug in my 8bitdo Bluetooth gamepads via USB to test and see if it gives me the errors that way

zaphod24

@retropieuser555 I'd appreciate knowing how that goes.. I even went as far as ordering a usb hub to try and put both gamepads on the same USB controller for the pi5 since they changed things from the pi4 and have 4 buses, one for each usb connector on the back instead of one usb2 and one usb3 for the pi4.

mitu

@zaphod24 where did you read about the USB buses being 1 per port ?
The RP1 chip, which drives almost all I/O on the Pi5, has 2 USB buses - see https://hackaday.com/wp-content/uploads/2023/10/rp1-block-diagram.jpg or https://www.raspberrypi.com/documentation/microcontrollers/rp1.html#content.

abj

Because im using Pi as a desktop right now. i test my controllers (Logitech 710 & 310) with this page https://hardwaretester.com/gamepad and both are working at the same time. Maybe the issue affect two same controllers or same brand ?

pjft

@abj I have played Saturn Bomberman 8-players on the Pi5 in both wired and hybrid (4 wired and 4 wireless PS3 pads - original and Shanwan) and all has gone well, so while it's a good hypothesis, I'm not sure about that angle.

zaphod24

@mitu

lsusb on pi5:

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 045e:028e Microsoft Corp. Xbox360 Controller
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsusb on pi4:

Bus 002 Device 004: ID 152d:1561 JMicron Technology Corp. / JMicron USA Technology Corp. JMS561U two ports SATA 6Gb/s bridge
Bus 002 Device 003: ID 18d1:9302 Google Inc.
Bus 002 Device 002: ID 05e3:0626 Genesys Logic, Inc. USB3.1 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Conclusion, 4 buses on pi4, 2 usb2 and 2 usb3 and 2 buses on pi4, one usb2 and one usb3. It's possible lsusb is reporting incorrectly or I am misinterpreting the results.

mitu

@zaphod24 said in Raspberry Pi 5 - official announcement:

It's possible lsusb is reporting incorrectly or I am misinterpreting the results.

Niether - there are 2 physical connections for each pair of USB2/3 ports. But regardless, I don't think that's a problem per-se and it's not the cause of your issue. Maybe your unit has a problem ? Do any other USB peripherals exhibit the same issue (i.e. keyboard/mice) or it's just the gamepads ?

zaphod24

@mitu so far keyboard and mice have been fine, it's just when using 2 gamepads at the same time

zaphod24

I gave up and got 2 bluetooth SN30 pro controllers. They work without issue except both light just the first LED which makes it look like both are player one when in fact one is player 2.

abj

i sumarized the instructions for the Dolphin standalone emulator.

Update RetroPie-Setup script.
Install Dolphin emulator from experimental packages.
Add to this file:
/opt/retropie/configs/gc/emulators.cfg

this line:
dolphin-editor = "XINIT-WMC:/opt/retropie/emulators/dolphin/bin/dolphin-emu"

In the end, the file it will be like this:

dolphin = "XINIT-WM:/opt/retropie/emulators/dolphin/bin/dolphin-emu-nogui -e %ROM%"
dolphin-gui = "XINIT-WM:/opt/retropie/emulators/dolphin/bin/dolphin-emu -b -e %ROM%"
dolphin-editor = "XINIT-WMC:/opt/retropie/emulators/dolphin/bin/dolphin-emu"
default = "dolphin-gui"

Start a game and choose from runcommand menu the dolphin-editor. This will open Dolphin menu, where we can change the parameters of the emulator and configure the controller(important).

mitu

@abj said in Raspberry Pi 5 - official announcement:

Installed from terminal, a recommended package:
gldriver-test.

This should be handled automatically now - as part of the 'xorg' installation.

abj

@mitu
I did a fresh install yesterday and the package was installed normally when I tried the above command. I will remove it and try again.

Update: I remove the package and reinstall the emulator and it's working! Thanks @mitu

abj

Did someone else have the same error with beetle-psx?

[ERROR] Requesting OpenGL context, but RetroArch is compiled against OpenGLES. Cannot use HW context.
[ERROR] [Environ]: SET_HW_RENDER - Dynamic request HW context failed.
[ERROR] [Environ]: SET_MESSAGE_EXT: Unable to find or open hardware renderer for frontend preferred hardware context. Falling back to software renderer.

The weird things is that the emulator is running the games without issues with hardware enable. I know that because i can set higher resolution.

retropieuser555

I attempted to install pixel desktop from the raspbian tools, in doing so it's knocked the runcommand XINIT:WM functionality:-

Parameters: 
Executing: xinit /dev/shm/retropie_xinitrc -- vt1 -keeptty


X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
Current Operating System: Linux raspberrypi 6.1.0-rpi8-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64
Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1  smsc95xx.macaddr=D8:3A:DD:A6:F5:1B vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000  console=ttyAMA10,115200 console=tty1 root=PARTUUID=819f3faa-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=GB
xorg-server 2:21.1.7-3+rpt2+deb12u5 (https://www.debian.org/support) 
Current version of pixman: 0.42.2
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/pi/.local/share/xorg/Xorg.0.log", Time: Sun Mar 10 19:09:43 2024
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
modprobe: FATAL: Module g2d_23 not found in directory /lib/modules/6.1.0-rpi8-rpi-v8
/usr/lib/xorg/Xorg: symbol lookup error: /usr/lib/xorg/modules/drivers/fbturbo_drv.so: undefined symbol: shadowUpdatePackedWeak
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Any ideas how to revert what pixel's installed/changed? It should only apt install xorg and ldxe no?

Edit: Solved it, pixel installs /usr/share/X11/xorg.conf.d/99-fbturbo.conf which has something funky going on. Removing it and now pixel & xorg runcommand works again

ecto

Has anyone tried installing eduke32/ionfury? It doesn't start for me, instead it seems to segfault.
I don't know what I could try to make it work.

ExarKunIv

@ecto i have both on my, they are working.
the only thing i have done is added

/boot/firmware/config.txt this line : kernel=kernel8.img .

not sure if that did anything or not. but both are working for me.
i just did this install a few days ago

RapidEdwin08

@ecto Indeed try kernel8 first as mentioned above.

If that still gives you trouble (not segmentation fault), I personally used a sirlemonhead's fork previously to overcome video issues, although it may not be needed anymore.
Mentioned here

skankieflank

Are we still a long way off from an official image for Pi5? From all the testing it seems like a lot of emulators are working as expected.

abj

@skankieflank

I believe we are far from a stable release, but maybe devs will release a beta image sometime when some critical parts are ready. Something similar happen with the support of Rpi4 as i remember.

System is working very well in the current situation.