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.

@mitu said in usb boot from 5tb hdd:

@korn16ftl3 said in usb boot from 5tb hdd:

After that I use a windows machine and the pi image writer to write retries (and I’ve even tried raspi os) to the usb hdd. The problem im finding is that it just turns the hdd back to MBR.

You need to do the conversion after you write the image, otherwise writing the image again will just re-initialize the disk with a MBR boot signature.

So I've tried a couple things:

wrote retrope image to HDD then used MiniTool Partition Wizard (windows) to change the MBR to GPT try the first boot of retropie (where it resizes) and it stalls after post with the following 3 lines on screen

[ 1.494426] mmc1: controller never released inhabit bit(s)
[ 3.839951] sd 0:0:0:0: [sda] no caching mode page found
[ 3.840041] sd 0:0:0:0: [sda] assuming drive cache: write through

a. I've taken the previous results (just for fun) with a fresh image write of retropie on the hdd, wrote a pi OS 64 bit image to an sd card, installed gparted, to pi os changed the MBR to GPT with pi OS and got the same results from above.

b. I used gparted to play with the boot partition flags.
The boot partition flag WAS originally set to msftres so i obviously tried setting the boot flag first and still got the same 3 lines above. Ive also tried setting the boot partition flag to lba (just because) again same results as well with that.

wrote a fresh retropie image to the hdd booted it up to receive the unable to resize partition error loaded to controller settings hi F4 then used sudo shutdown now to shut the pi down. I then plugged the pi into a windows pc and again used MiniTool Partition Wizard to convert the hdd to GPT and tried to boot up the retropie hdd again but this time it entered some kind of boot loop at post (the pink screen) complaining about the hdd though it scrolled so quickly I didn't catch it all. Also note i have only attempted this particular method once so perhaps user error?

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.

it seems I'm getting part of this correct somehow as its doing something it does on a normal boot but what am i missing here?

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