@hellothere don't want to leave this unanswered.

Prereq:
Have a USB drive or SSD with same or larger capacity than your SD card.
When using an SSD SATA to USB adapter make sure it is fully UASP to get max. transfer/access speed. Here are some hints [1] - also this site has more details as I do provide below.

It goes like this:

Make a full backup of your SD-card (eg. with Win32DiskImager (<- easiest), Clonezilla, ...) to your desktop PC. Put that backup at your USB drive / SSD (again using Win32Diskimager or the tool of your choice) on your desktop PC. Resize the USB partition (only if the USB drive is larger than SD card). Advise the pi to use a different partition after initial booting from /boot, handing over to the USB drive.

When you are done with the backup (Step 1 and 2 from above) attach both (SD card and USB drive) to the Rpi.
Remove any additional USB storage attached to the pi to avoid confusion.
Boot/Power up.
Nothing has changed up to this point.

Note: Following steps are the crucial part - but no worries you have a backup. If something derails, you can back out by using the backup.

Step 3: Optional: Resize the USB partition (if USB drive is larger than SD card).

SSH to your pi as user pi. Type

sudo su

Issue blkid /dev/sda*

blkid /dev/sda* /dev/sda: PTUUID="e006ca92-3704-44b9-a15f-bc56e2171825" PTTYPE="gpt" /dev/sda1: UUID="4832bb70-bb77-4a4a-9d68-5541559df133" TYPE="ext4" PARTUUID="9ec38a7c-ff79-413f-bddc-fc66de260c13"

Note the partition number /dev/sdN on the left which has the TYPE="ext4".

Run with that number resize2fs /dev/sdN (replace N with your number identified, most likely it will be 2).
Wait for process to finish.

Step 4: Advise the kernel to mount a different partition as "root-filesystem".

I underlined the items to REMOVE in RED and those to ADD in GREEN.

The red and green values are different on your machine. Use those. Not those from the example!

SSH to your pi as user pi. Type

sudo su

gets you root.

Issue blkid /dev/sda*
B1.jpg

Will give you a similar output as above.
Note down the value of PARTUUID of partition with TYPE="ext4" (in the example 9ec38a7c-ff79-413f-bddc-fc66de260c13). There should be only one with this type.

Edit fstab (with editor nano (<-- easiest) (or editor of your choice)):

mount /dev/sda1 /mnt # <-- this should be the same sdN as used in resize2fs, will mount the partition from the USB drive. nano /mnt/etc/fstab

You will find something like this:

B2a.jpg

These current PARTUUID point to partitions on your SD card.( You can verify it with blkid /dev/mmcblk0*)

The second entry has to be altered to contain the PARTUUID you noted down before. For example:

B2b.jpg

Again: Use your identified PARTUUID value.
You don't have to keep the lines starting with # (=comment)
Save the file.

Almost done: Then edit cmdline.txt, last step before rebooting:

nano /boot/cmdline.txt

You will find something like:

B3a.jpg

This instructs the kernel to look for the root filesystem at the partition PARTUUID, currently the SD card.

Make it read, change only the PARTUUID, leave everything else as is:

B3b.jpg

Save the file. Reboot... Drum roll, please!

After reboot, ssh to your pi, then check with mount command:

mount | grep sda

Should output something like:

/dev/sda1 on / type ext4 (rw,noatime)

That's it. Revel in your success.

[1] https://jamesachambers.com/raspberry-pi-4-usb-boot-config-guide-for-ssd-flash-drives/

@sleve_mcdichael said in Mame-libretro marquee issue:

Theme: "TMNTurtleGuy/ComicBook" (/etc/emulationstation/themes/ComicBook). Same issue in "Arcade" (arcade/theme.xml and mame-libretro/theme.xml are identical).

I think I found it. Edit your mame-libretro/theme.xml file with:

sudo nano /etc/emulationstation/themes/ComicBook/mame-libretro/theme.xml

Step 1, line 46:

<image name "classic_logo" extra "false">

Change "false" to "true".

Step 2: comment or remove the "marquee" section from lines 60-64. Comment html with <!-- and -->, as in:

<!-- <image name "md_marquee"> <pos>0.74 0.086</pos> <maxSize>0.26 0.1</maxSize> <origin>0.5 0.5</origin> </image> -->

With these two changes, save the file and restart EmulationStation; you should be all set!

arcade/theme.xml has a "marquee" section that genesis/theme.xml, for example, lacks. However, commenting out this section, while it did remove the marquee game logo, also removed the system logo from behind it.

In addition, line 46 is set differently between the two. Changing this from "false" to "true" restored the system logo.

Additional notes:

I think wheels and marquees are enabled by default, so you need to explicitly make them "false" (not just comment out the "true") in config.ini if you don't want to download them.

You have marquees disabled in the command-line options; however, while that game logo is called "marquee" by EmulationStation, it's the "wheel" art from the scraper that goes here. So if you wanted to disable these logos, you need to disable "wheels" in the scraper instead of "marquees." Then you'll need to purge your cache of the already-downloaded wheel arts.

Of course, this isn't necessary now that you know how to fix the theme, but just for general knowledge.

I appreciate you helping me understand the difference between the marquees and wheel arts. I did what you said there and it fixed it! Thank you!

I've updated my config.ini to not cache marquees and wheelarts for now. Thank you again!

@mitu
Wow !!! solved !!! Thanks , you have hit the bullseye !

@damoos You can override the controller order on a per-game basis, you'll need a separate .cfg file for the game where you can change the order of the controllers:

input_player1_joypad_index=1 input_player2_joypad_index=0

The above will switch the controller order, so 2nd controller gets to be Player1 and vice-versa. See here how that works.

Try installing the xpadneo driver from RetroPie-Setup (see here on how to install things in RetroPie) and try re-pairing the controller again via Bluetooth.

@sleve_mcdichael ah, ok ok now i get it!! thanks!!!

@mitu
Just reinstalled them, same thing.

Ah well, it doesn't seem to be RP or upstream in retroarch, seems to be entirely at my end. .

The only thing I can think of is I installed some Ubuntu-studio stuff to get jack/Guitarix working, though I had it before too. I'm guessing whatever is different and is allowing them to work (sort of) this time is some how breaking something else.

Hello , i have more problems GTA games , Vice City , Burnout dominator and some other i think the most recent PSP games boots fine and menus are ok.
But in the game the graphics are broken and unplayable. Cars and people falling trough the road and grass etc.
Same roms / dvd content are fine on ppsspp win10 desktop machine.

Tried vulkan on the PI4 but more and the same problems, also tried booting retropie standalone image and on twister os same result.

PI4 / 8GB
32 bit or 64bit kernal on twister os same problem.
ppsspp without retropie same problem.
Al on the latest updates of may 2021

Can anyone give some advise.

@wolfie1968 Unsafe shutdowns can result in data corruption, In my experience I had a few sd cards go bad on me even though Ive been careful about handling them and doing safe shutdowns. so it can be the quality of the sd cards you are using. Which type of sd card are you using? I tend to use Samsung's Evo Select cards.

If you do your research on file systems some of them are documented to be more resilient to data loss/ data corruption.

@mitu You're totally right, the ROMs I have just aren't the two control set versions, I just tried Gauntlet and everything worked fine. Thanks for your help!!!

@mitu Thats great, it worked, just added an & at the end. Thanks very much!

@blackshadow said in Screen rotation for Retropie GUI:

quick copy and paste from another site to save me writing it out lol

Step 1 – Edit Config.txt

Start by editing the config.txt file ether via the sd or with:

sudo nano /boot/config.txt

Add one of the following lines to the bottom of the file :

display_rotate=0
display_rotate=1
display_rotate=2
display_rotate=3
0 is the normal configuration. 1 is 90 degrees. 2 is 180 degress. 3 is 270 degrees.
If you are using the Official Raspberry Pi touch screen you can use “lcd_rotate” rather than “display_rotate”.

Save the file by using CTRL-X, Y then ENTER.

as the site you linked references the 7inch pi screen ill assume thats what your using you can use the lcd_rotate that is mentioned as apposed to display rotate

Thanks. This needs the thumbs up as all other routes didnt work. This. Yes. Thanks

@mitu said in My Xbox controller stay off when my raspberry pi 4 get turned on:

The Pi4 and Pi3 are different hardware and have different USB controllers, hence the difference. That's not why your controller behaves this way.

There must be some difference somehow. I tried 2 different controllers: Xbox One Series X controller and Xbox One S controller ("S" not "Series S"). I tried all 4 usb ports. Everything work fine on my Pi 3 but none of them get turned on when my Pi 4 boot.

I think I will move on, anyway I planned to use the Xbox One wireless dongle and buy batteries + a docking station for refilling the batteries, so this problem shouldn't bother me anymore after that. I'm just leaving as much information as possible in case someone else encounter the same problem in the future.

Thanks for your help.

@bulbisaur685 said in Pi Zero - screen and i2s using same pins, no sound:

I have both devices connected to the pins on the Pi Zero, but when going into the settings for audio I am getting information that the audio is disabled

That message is shown because the audio configuration utility only knows about the on-board audio. For any other configuration - where you disabled the on-board - you'll need to configure the audio yourself.

My suggestion would be to start with the audio configuration first (in config.txt) and then try to configure the screen once you've got audio working.

@greenhawk84 Download the latest image and open it with 7zip to look in the boot partition and read it. This is what it looks like, extracted from the PI4 image:

# 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 overscan_scale=1

For the PI2/3 models, I think there's a memory setting added that's extra, the rest should be identical.

Nvm i figured it out

@g30ff thanks!!!!

@marukotenada the poster hasn't been here in 4 years - there's a slim chance it will reply back. Please don't bump old topics - open a new topic instead and explain your issue.