@mitu

I use this config file now and it works:

# For more options and information see # http://rpf.io/configtxt # Some settings may impact device functionality. See link above for details # uncomment if you get no picture on HDMI for a default "safe" mode #hdmi_safe=1 # uncomment this if your display has a black border of unused pixels visible # and your display can output without overscan #disable_overscan=1 # uncomment the following to adjust overscan. Use positive numbers if console # goes off screen, and negative if there is too much border #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 # uncomment to force a console size. By default it will be display's size minus # overscan. #framebuffer_width=1280 #framebuffer_height=720 # uncomment if hdmi display is not detected and composite is being output #hdmi_force_hotplug=1 # uncomment to force a specific HDMI mode (this will force VGA) #hdmi_group=1 #hdmi_mode=1 # uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes #hdmi_drive=2 # uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4 # uncomment for composite PAL #sdtv_mode=2 #uncomment to overclock the arm. 700 MHz is the default. #arm_freq=800 # Uncomment some or all of these to enable the optional hardware interfaces #dtparam=i2c_arm=on #dtparam=i2s=on #dtparam=spi=on # Uncomment this to enable infrared communication. #dtoverlay=gpio-ir,gpio_pin=17 #dtoverlay=gpio-ir-tx,gpio_pin=18 # Additional overlays and parameters are documented /boot/overlays/README # Enable audio (loads snd_bcm2835) dtparam=audio=on [pi4] # Enable DRM VC4 V3D driver on top of the dispmanx display stack dtoverlay=vc4-fkms-v3d max_framebuffers=2 [all] #dtoverlay=vc4-fkms-v3d gpu_mem_256=128 gpu_mem_512=256 gpu_mem_1024=256 overscan_scale=1 #Pi Zero 2 W GPi Config dtoverlay=audremap,pins_18_19,swap_lr display_rotate=1 dtoverlay=dpi24 overscan_left=0 overscan_right=0 overscan_top=0 overscan_bottom=0 framebuffer_width=320 framebuffer_height=240 enable_dpi_lcd=1 display_default_lcd=1 dpi_group=2 dpi_mode=87 dpi_output_format=0x6016 #hdmi_timings=320 0 28 18 28 480 0 2 2 4 0 0 0 60 0 32000000 6 hdmi_timings=240 1 38 10 20 320 1 20 4 4 0 0 0 60 0 6400000 1

Cannot use the Bluetooth and RetroPie-setup menu in Armbian, any input and it crashes while trying to navigate. If you preset Bluetooth connections within the OS, it runs all games and controls really well.

PSX, all runs well
N64, mid range games run well.
Dreamcast, lower end games run well.

Sadly not perfect yet due to Bluetooth imperfections in the menu and need N64 resolution manual preset when swapping to different quality monitor... Just that :(

#________________________________________#

Managed to install RetroPie successfully on Dietpi OS.
Still working out:

[solved] why the N64 hotkey doesn't work, can't exit
... Disabled '0' mupen64plus hotkey in ~/all/autoconf.ini
... Added J0B12/B11 at emulation Stop in ~/N64/autoconf.ini [solved] why PSX doesn't launch, black screen
... Replaced all my BIOS files [solved]why NES doesn't run, returns to ES
... Used corrupted roms without headers [solved] why Dreamcast won't show in ES
... Had .7z files in the rom folder. Unzipped the files

@Dr-Klein it is the difference between running roms from a USB drive vs. transferring roms using a USB drive.

When you run roms from the USB drive they remain on the drive, and are only accessible while it is attached.

You want to transfer the roms from the USB stick onto the SD storage. Name the folder retropie, instead of retropie-mount.

https://retropie.org.uk/docs/Running-ROMs-from-a-USB-drive/

https://retropie.org.uk/docs/Transferring-Roms/#usb-stick