Use raspi-config to change the Hostname of one of the Pi systems. You can do it from System Options -> Hostname.

@Isolved: the solution of the problem was throw away 2.4 dongle and connect gamepad through standard pi Bluetooth - work fine

Thanks for (re-)testing.

Will do some more detailed testing, but assume this is fine now. Any idea why the change did not apply to the binary?

Probably wasn't rebuilt after the change or something else occured during the binary build which didn't update it. We're looking into it.

And is there a place I can toss a coin for coffee or similar for the support? 😉

See the bottom of the forum pages for the donation link.

@mitu said in PieMarquee2 compiled for a Pi5 or source available?:

maybe it can be adapted to work with EmulationStation's scripting system ?

Unfortunately the PieMarquee2 scripts relies on omxiv (depreciated and not compatible with arm64) to place the image on the second display. fbi doesn't seem to be a good replacement and I haven't found a way to make cvlc display to a specific hdmi port.

if I find an app or you know of one I'd love rework the scripts to get my 64bit P5s marquee going.

@drog1998 I use an Arduino Leonardo (Atmega32 chip) to connect an Amiga keyboard to my Raspberry PI. It works very well, no bug at all. I never have to unplug and replug for instance. I use it with every emulator of computers.

I use a self-powered hub to connect it to my Raspberry Pi 4 (actually, every USB thing is connected to this self-powered USB hub in my configuration).

@mitu sorry topic. freudian slip.

@Qiset I didn't like the way that model information was presented to me so I did some checking.
Your first assessment is correct, I think. The model B is not a model 2 even though it has a rev 2 listed. Time to do a head slap.

@sleve_mcdichael Thank you! Turns out multiple is the key name I needed.

@mitu whel it was working when i first use it zo 4 or 5 years ago bad now it dosend work

@mitu Thanks for the suggestions! First I need to stress that this subject (overall) is still relevant as many people have this manufacturer's hardware. I found several solutions, including a driver and script that modifies the device controller to enable rumble, but all these solutions aren't for my particular hardware ID (2563:0526). I actually did manage to enable rumble on Linux once, I played around with xboxdrv, loaded the custom driver and used the script, and eventually rumble did work - until I did a reboot. So far, I can't get rumble to work again, despite modifying a bit the driver source code. Whatever I did worked, somehow. I had properly working rumble which I tested with fftest and in-game using an emulator. My gamepad is generally supported by the usbhid driver, all axes, buttons and HAT work properly, but not rumble (fftest says functions not implemented). But my successful attempt proved that that the gamepad can be fully supported under Linux, it's just a matter of slight driver modification. It's a good gamepad, better than much more expensive alternatives which claim to have superior design. That being said, I did send an email to the manufacturer (link) and my local seller. There are many posts on the web about this hardware type, I'm searching everywhere. Those who have the product ID matching the script or driver have full hardware support on Linux. So this hardware can be fully working under Linux. Maybe future updates to usbhid will provide rumble.

@ExarKunIv
Shame,
guess im sttuck with the pi4 for now.
Thanks

@mitu I tried now with config.txt

dtoverlay=vc4-kms-v3d,nohdmi

and emulationstation and mpv are working on display! (Only vlc makes troubles)

root@rpi5:/opt/videos# mpv --no-audio simpsons.mp4 (+) Video --vid=1 (*) (h264 640x480 25.000fps) Audio --aid=1 --alang=deu (*) (aac 1ch 48000Hz) [vo/gpu] VT_GETMODE failed: Inappropriate ioctl for device [vo/gpu/opengl] Failed to set up VT switcher. Terminal switching will be unavailable. VO: [gpu] 640x480 yuv420p V: 00:05:28 / 00:22:15 (25%) root@rpi5:/opt/videos# mpv --drm-connector=help Available connectors for card 0 (/dev/dri/card2): SPI-1 (connected) Available connectors for card 1 (/dev/dri/card1): Available connectors for card 2 (/dev/dri/card0): Cannot retrieve DRM resources: Operation not supported root@rpi5:/opt/videos# drmdevice --- Checking the number of DRM device available --- --- Devices reported 3 --- --- Retrieving devices information (PCI device revision is ignored) --- device[0] +-> available_nodes 0x01 +-> nodes | +-> nodes[0] /dev/dri/card2 +-> bustype 0002 | +-> platform | +-> fullname /axi/pcie@120000/rp1/spi@50000/panel@0 +-> deviceinfo +-> platform +-> compatible wavesku19650 panel-mipi-dbi-spi --- Opening device node /dev/dri/card2 --- --- Retrieving device info, for node /dev/dri/card2 --- device[0] +-> available_nodes 0x01 +-> nodes | +-> nodes[0] /dev/dri/card2 +-> bustype 0002 | +-> platform | +-> fullname /axi/pcie@120000/rp1/spi@50000/panel@0 +-> deviceinfo +-> platform +-> compatible wavesku19650 panel-mipi-dbi-spi device[1] +-> available_nodes 0x01 +-> nodes | +-> nodes[0] /dev/dri/card1 +-> bustype 0002 | +-> platform | +-> fullname /axi/gpu +-> deviceinfo +-> platform +-> compatible brcm,bcm2712-vc6 --- Opening device node /dev/dri/card1 --- --- Retrieving device info, for node /dev/dri/card1 --- device[1] +-> available_nodes 0x01 +-> nodes | +-> nodes[0] /dev/dri/card1 +-> bustype 0002 | +-> platform | +-> fullname /axi/gpu +-> deviceinfo +-> platform +-> compatible brcm,bcm2712-vc6 device[2] +-> available_nodes 0x05 +-> nodes | +-> nodes[0] /dev/dri/card0 | +-> nodes[2] /dev/dri/renderD128 +-> bustype 0002 | +-> platform | +-> fullname /axi/v3d@2000000 +-> deviceinfo +-> platform +-> compatible brcm,2712-v3d --- Opening device node /dev/dri/card0 --- --- Retrieving device info, for node /dev/dri/card0 --- device[2] +-> available_nodes 0x05 +-> nodes | +-> nodes[0] /dev/dri/card0 | +-> nodes[2] /dev/dri/renderD128 +-> bustype 0002 | +-> platform | +-> fullname /axi/v3d@2000000 +-> deviceinfo +-> platform +-> compatible brcm,2712-v3d --- Opening device node /dev/dri/renderD128 --- --- Retrieving device info, for node /dev/dri/renderD128 --- device[2] +-> available_nodes 0x05 +-> nodes | +-> nodes[0] /dev/dri/card0 | +-> nodes[2] /dev/dri/renderD128 +-> bustype 0002 | +-> platform | +-> fullname /axi/v3d@2000000 +-> deviceinfo +-> platform +-> compatible brcm,2712-v3d

@mitu Thank you very much! Updating the kernel and redownload the package did it! 🤗

@hank it worked thank you