@BlackLord
note : my understanding is that this modified genplus-gx core is breaking some stuff, so it is not recommended to replace the original genplus-gx core by it (which is probably what you did)

@mitu Thanks for the comment!! Of course I will mention to whom it corresponds! And I will gladly agree to improve whatever they want and is within my reach, such as the theme of Pajarorrojo, who is aware of my adaptation of his theme for retropie

@roslof Do you have a folder with "lr-mame" 0.278 for rpi5 64bit that you can share? Thanks

Well, the OP should just move to MAME current tbh, not only it has support for TATE in both directions, but it probably also has better support for cocktail mode (i highly doubt all cocktail fixes from the past 22 years were backported to MAME2003+).

As for FBNeo, it is not suitable at all for cocktail setups : some games had their 2P mode and cocktail mode tied together, and ended up being un-cocktail-ified so that 2 players could play them without requiring a cocktail setup.

@gilllig said in Retropie doesnt boot with changed config:

Ive installed raspOS and retropie, but now they dont even run))

What exactly does this mean - they're both not running ?

I tried to choose emulationstation at the settings, I tried to add line "/usr/bin/emulationstation" in the /home/pi/.bashrc, but its not working...
I cant understand how to make autostart for raspOS or for retropie

You're running in an unsupported configuration, as I mentioned in my previous post, so you should not use the normal RetroPie auto-start options from the menu.

If you have installed the RaspiOS with Desktop, then just use the default option to boot to the Desktop. You can start EmulationStation from a terminal by typing emulationstaton. If you wish to automatically start Emulationstation after the boot to desktop is done, then

create the $HOME/.config/autostart folder add a .desktop file with the command to start the terminal and EmulationStation (lxterminal -e emulationstation).

@korn16ftl3 said in usb boot from 5tb hdd:

Anyhow I'm curious what those 3 lines mean? i know 3 lines show up on a successful boot at that portion as well then continues to boot but once again they go by so quickly I'm not sure what they say....like at all.

The sda related messages means the disc has been read by the system and I would expect to see a list of partitions found on the disc in the following messages ( referring to sda1, sda2 since there are 2 partition).
Maybe there's not enough power supplied by the 'charger' you're using and the disc cannot be initialized ? Can you try with a RPI certified power source ?

@barbudreadmon
Sorry, when I said I got both monitors working, I meant that Retropie was displaying on both. The left monitor has the game, the right monitor was displaying scripts. I just can’t get the actual game screen to display over 2 monitors. No game play on the monitor on the right even though Retropie seems to be recognizing it.

Thanks!

neither of these things (permissions or starting clean) seemed to resolve. I also @ByteThis did not seem to rectify this by only configuring player 1 (but good idea) With a clean install and remapping all the input settings I am getting to where the select and start button only work in the retropie menu (scrolling diffrent consoles exploring settings etc.... But when I launch a rom NONE of the bottons work.

I ran some more jstest output today....

davis@raspberrypi:~ $ jstest --normal /dev/input**/js0**
Driver version is 2.1.0.
Joystick (DragonRise Inc. Generic USB Joystick ) has 7 axes (X, Y, Z, Rx, Rz, Hat0X, Hat0Y)
and 12 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6).
Testing ... (interrupt to exit)
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off

davis@raspberrypi:~ $ jstest --normal /dev/input**/js1**
Driver version is 2.1.0.
Joystick (DragonRise Inc. Generic USB Joystick ) has 7 axes (X, Y, Z, Rx, Rz, Hat0X, Hat0Y)
and 12 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6).
Testing ... (interrupt to exit)
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off

So it sees both controllers, but does not detect any button or axis input events. I think It is time to just replace them. Ive had them over a year and the more I think about it the more I think I possibly damaged these things. They used to be mounted in a metal cabinet and the opening I cutout for the control panel was very tight. (see attached called "old") old.jpg

New cabinet.......

new.jpg

I think its time to just replace the usb encoders.

Thank you!!!

@mitu thank you problem solved:
Deleted 1st partition (unused 16mb)
And now /dev/sda1 is correctly mounted ...on my hdd2...465gb
Retropie boots quickly and without warnings.
Thanks

And yes, in hope rather than expectation I did try changing:

config_version=3.6.0

to

config_version=5.7.1

It did not, of course, help, except that instead of dumping to a Workbench 1.3 "insert disk" screen, the game now dumped to a Workbench 1.3 "insert disk" screen in the wrong aspect ratio.

For the record the 'X' button on my XBox360 Controller is detected as 003 via hypjsch

So I doubled checked that against the Joystick API config:

KEY_BUTTON2 = SDLK_LALT 0 3

And again 'X' was FEET and played fine.

@mitu thank you man!
you are great! ( as always....))

@mitu

I’ve tinkered with clrmamepro before but my results kind of sucked with it. The last time I had to do any of this was with the good tools way back in the original Xbox one days.

Any direction for a good tutorial on how to use Clrmamepro the proper way as I obviously had no idea what I was doing even tho I followed a guide lol.

Any other noob friendly sorting by .dat tool recommendations would also be appreciated, like I said it’s been a long long time since I’ve had to do this or anything like it and things appear to have come leaps and bounds since then

This means the system is not powerfull enough to emulate the game/system at full speed. Given it's a Pi3, it's not unusual since N64 emulation is not fullspeed on it.

Does this have anything to do with RetroPie or is it a general Raspberry Pi question ?

You can force the Raspberry Pi to output a certain video mode suited for a 15khz monitor forcing an EDID which contains that video mode - see for instance https://forums.raspberrypi.com/viewtopic.php?t=370192.

@BurndtJamb said in help installing screen driver on pi zero 2 w with retropie:

. I can't get ssh working since i don't know the ip address due to not having a screen. is there either a way I can install the necessary stuff without ssh?

If you don't have a direct interface (i.e. monitor + keyboard) to the RPI, then you need SSH. If you don't know the IP, you can try connecting using the hostname instead - for the RetroPie image the hostname is retropie (you can also try with retropie.local)

It's a closed source 32bit app. You're on a 64bit OS, so it won't run

Please include all the info requested in https://retropie.org.uk/forum/topic/3/read-this-first to be able to assist you.

@Mrobot said in ControlBlock issue on Raspberry Pi 4B:

I can access the bash interface on it, but that is about it.

if you have shell access, can't you just run the setup script again and choose to remove the package ? Run

cd $HOME/RetroPie-Setup sudo ./retropie_setup.sh

to get to the setup dialog and remove the package.