redream not working

mitu

My best guess would be that this appears to be a problem with a dependency, specifically dpkg-query. Doing some googling revealed this:

No, it's a problem with the redream launch script (/opt/retropie/emulators/redream/redream). It invokes dpkg-query with an empty argument. In the script:

MESA_DIST_VER=$(dpkg-query -f= --show libgl1-mesa-dri)

should be

MESA_DIST_VER=$(dpkg-query -f="\${Version}" --show libgl1-mesa-dri)

The script comes from upstream (@inolen), so we'll be reporting the issue there, hopefully an update will fix the issue.

c0un7z3r0

@mitu

That's fantastic, I found that file myself based on the error message (line 9) but was not sure what that should be changed to, to have valid syntax. The dpkg-query documentation wasn't much help without context as to what that particular line did. Thanks for the help, I'll manually update in the meantime and try it this evening.

Thanks again!

mitu

Try updating now redream, without modifying anything, and see if you still get the same error.

c0un7z3r0

@mitu @inolen

I updated which fixed the previous issue but brought about a new one:

dpkg: warning: version '""' has bad syntax: version number does not start with digit
redream: line 9: ./redream.aarch64.elf: No such file or directory

so presumably the ${Version} variable is not being set.

windg

Here Redream is working fine, i did a full update, RetroPie packages and system packages(underlying). Did you build RetroPie on top of Bullseye?

c0un7z3r0

@windg

No I ran the official raspberry pi imager software and wrote directly to an SSD so it's the stock image file

It's buster and if I do

Sudo apt-get update
Sudo apt-get upgrade

Then it says all packages are up to date

c0un7z3r0

@windg

the immediate problem is that the $Version variable in the

/Opt/RetroPie/emulators/redream/redream

Script is undefined so dpkg-query falls down when trying to set META_DIST_VER

mitu

@c0un7z3r0 said in redream not working:

[...]
so presumably the ${Version} variable is not being set.

Yes, there's still an issue. We'll spin the dreidel again. My original fix should still work.

c0un7z3r0

@mitu

Yes, there's still an issue. We'll spin the dreidel again. My original fix should still work.

What do you mean by the original fix? The suggestion above or the changes that were pushed to the latest build?

Please let me know if any further fixes get applied? (Also, if you can, let me know what repo these changes are happening in so I can track it?)

Thanks again for your help and persevering.

mitu

@c0un7z3r0 said in redream not working:

What do you mean by the original fix? The suggestion above or the changes that were pushed to the latest build?

I was referring to my first reply.

Please let me know if any further fixes get applied?

Try updating now.

(Also, if you can, let me know what repo these changes are happening in so I can track it?)

redream is not open source, so there's no public repository to track. You can watch the downloads page for new versions, but I don't think there's any detailed changelog for the development builds. I just reported the issue to @inolen and they have added some fixes to the RPI package.

c0un7z3r0

@mitu

Thanks again

This is getting weird, it now gives this error

Executing: /Opt/RetroPie/emulators/redream/redream "/home/pi/RetroPie/ROMs/Dreamcast/myromfile.chd"
/Opt/RetroPie/emulators/redream/redream: line 9: /Opt/RetroPie/emulators/redream/redream.aarch64.elf: No such file or directory

But that file does exist.

Damn this is frustrating. Sorry to keep coming back with this, I appreciate your help

mitu

@c0un7z3r0 said in redream not working:

This is getting weird, it now gives this error

This seems to be something related to your system. /Opt/Retropie doesn't exist on a standard RetroPie installation, RetroPie is installed in /opt/retropie . Since Linux filesystems are generally case-sensitive, in this case the folders are not the same.

c0un7z3r0

@mitu sorry the capitalisation was mine. I manually typed it out on my phone

It is lowercase as you said.

mitu

Then I suggest you reinstall again redream. The package does contain the file not found in your error (/opt/retropie/emulators/redream/redream.aarch64.elf).

c0un7z3r0

@mitu

It does contain redream.aarch64.elf, it's referenced in the redream script we were having problems with. See image for my directory structure and files

alt text

mitu

You say you installed RetroPie using the RPI Imager image, but your image shows a newer kernel and a 64bit system (?), which we don't include. Did you use rpi-update to update your system by any chance ?

c0un7z3r0

@mitu

I don't specifically remember doing so but it's quite likely i have at some point done rpi-update.

I noticed an issue with the symlinks last night so I'm going to investigate that but I'm AFK right now. I'll come back with my findings.

mitu

@c0un7z3r0 said in redream not working:

I don't specifically remember doing so but it's quite likely i have at some point done rpi-update.

Why ? rpi-update is not meant to be used for regular updates, it even tells you so when you run it. Your bootloader and kernel have been upgraded to the latest beta and that's why your system is running a 64bit kernel, but with a 32bit system. it's most likely the reason redream doesn't work since it thinks the system is 64bit, but the aarch64 (64bit) executable cannot run on a 32bit userland.

You can either re-install the relevant packages to remove the beta kernel/bootloader or add arm_64bit=0 to the booloader configuration file (config.txt, in the /boot folder).

c0un7z3r0

Thanks @mitu

I'm going to check to see if the symlinks issue is the problem first (it seems as tho the bios files symlinks are not working, I've not fully investigated but it seems nothing happens if I try to 'cat' the bios files). If that's a red herring then I'll try to force 32bit mode as advised. I'll update the post as usual. Thanks again for your help.

Cheers.

c0un7z3r0

@mitu

I finally got it sorted out thanks to you, the issue was indeed was the 64/32 bit mismatch. Forcing 32 bit mode with arm_64bit=0 and fixing the issue with the symlink that points to the bios fixed it. Thanks so much for your help and patience, im so releived to have finally got it fixed. I couldnt have done it without you! Cheers!