@mitu said in usb boot from 5tb hdd:

@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 ?

I do not have a certified rpi power source available to me however I find it hard to believe that there is insufficient power supplied as the ROG ally oem charger should be sufficient at the following specifications:

The ROG Ally OEM charger is a 65W USB Type C power adapter.
Here's a breakdown of its specifications:
Model: ADP-65JWY2A or ADP-65SDD2A.
Power: 65W.
Voltage: 20V.
Amperage: 3.25A.
Connector: USB-C.
Plug Type: US (American).

I did find a different link when googling some of those errors and found that it’s possible it is the data to usb chipset on the external hdd (source: https://forums.raspberrypi.com/viewtopic.php?t=330384 )

The above site does list a few things to try and to try to eliminate the still potential power problem an maybe the data to usb controller problem I ordered a different external enclosure that is independently powered as well ( this enclosure: https://a.co/d/fWlN5rW ). I already have a different sabernet data to usb adapter that is NOT independently powered that works ok with my (off brand and for some reason slow) 2.5 ssd hdd so hopefully the powered one solves my issues.

If I still have problems I will try some of the other remedies mentioned there as well as the way back machine link that is in that thread as well.

If you have any other feedback or ideas please feel free to post them and feel free to have a read on that thread as well.

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.

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

@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 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

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.

@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)

@duglor

The only thing I can think is to enter the runcommandmenu when you start a game and try to select a different resolution.
Really a long time ago since I used this stuff and no time to look into it.
Might be that someone else has an idea.

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

I just started to begin with DSi Emulation, using lr-LemonDS, and came to the point the tutorial ends: games will only start via the DSi-Menu, so "boot directly into rom" has to be disabled in the core-options.
Only difference: i have full access to the DSi-Roms in the /ROMS/DS-Folder from there and dont have to use prestuffed NAND-Files (would also be a fishy way imo, not the way it should work)

And this is an issue:
first of all on the official FAQ-Board it is recommended to keep this option at its default (=off/boot into rom), in special when the DSi-Bios is used.

Secondly the Retroachievements for DSi-Games only launch up when booting directly into the rom, you can see the widget, everythings fine.
Only problem: the screen keeps being white and silent.

Booting into menu works as mentioned, so the BIOS-Files are good for sure.
I can start all my games from there, but without Retroachievements Support, so i hope to find a way to boot directly into the game (as it should work :)).
I allready tinkered with further core-options, but had no luck.
If anyone has an idea it would be much appreciated.

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

It works on the 2010 MAME core in Retroarch.