Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raspberry PI5 not supported #212

Open
nonuser666 opened this issue Feb 3, 2024 · 9 comments
Open

Raspberry PI5 not supported #212

nonuser666 opened this issue Feb 3, 2024 · 9 comments

Comments

@nonuser666
Copy link

I have tried the latest v.2.7 – January 2024, does not work on PI5

I tried the recommended OS, not working.

Lastly tried the modify the config.txt---> os_check=0.

Resulted to black screen.

Feel free to contact me for testing the .img.

@christiansievers
Copy link
Contributor

Hey, thanks for the feedback. Just to be sure - do you mean both the ready-made image and the default Raspbian OS legacy image (as recommended in the readme here) don't work?

@nonuser666
Copy link
Author

nonuser666 commented Feb 4, 2024 via email

@tofuSCHNITZEL
Copy link
Collaborator

tofuSCHNITZEL commented Feb 4, 2024

Install works fine? Have you tried to enable fake kms via rpi config? (https://fydeos.io/docs/knowledge-base/recipes/enable-fake-kms-for-raspberry-Pi/)

@nonuser666
Copy link
Author

nonuser666 commented Feb 4, 2024 via email

@tofuSCHNITZEL
Copy link
Collaborator

okay please try fake kms and report back

@nonuser666
Copy link
Author

nonuser666 commented Feb 4, 2024 via email

@tofuSCHNITZEL
Copy link
Collaborator

I need few days. Can send me a how to for the fake kms i am new to Pi. A video or an article would be great.

On Sun, 4 Feb 2024, 21:11 Tobias Perschon, @.> wrote: okay please try fake kms and report back — Reply to this email directly, view it on GitHub <#212 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATCPFOVNUCTF5HRGZPRK5IDYR7TQVAVCNFSM6AAAAABCYKTLU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRVHEYDANZXHA . You are receiving this because you authored the thread.Message ID: @.>

see above https://fydeos.io/docs/knowledge-base/recipes/enable-fake-kms-for-raspberry-Pi/)

@AaronMcEntire
Copy link

Any follow up on this? I've ordered some 5's and was hoping to use Looper...

@tofuSCHNITZEL
Copy link
Collaborator

nope. but you could try to install the image mentioned in the readme update the drivers on the sd card following this instructions:
with luck the old software will boot on the new pi5

Updating only the firmware
Sometimes, going through the standard upgrade procedure may not be possible. For example, you may have a
customised distribution with no update facilities, or that cannot be upgraded without causing further issues. In these
circumstances, and possibly others, you will need to update the firmware files in the distribution manually.
You can download the firmware files from the following location:
https://github.com/raspberrypi/firmware/archive/refs/heads/stable.zip
This zip file contains a number of items, but the ones we are interested in at this stage are in the boot folder. The firmware
files have names of the form start*.elf, and their associated support files are fixup*.dat.
The basic principle is to copy the required start and fixup files from this zip file to replace the same named files in the
destination OS image. The exact process will depend on how the OS has been set up, but this is an example of how it
would be done for a Raspberry Pi OS image:
1. Extract or open the zip file so you can access the required files.
2. Open up the boot folder in the destination OS image (this could be on an SD card, or a disk-based copy).
3. Determine which start.elf and fixup.dat files are present in the destination OS image.
4. Copy those files from the zip archive to the destination image.
The image should now be ready for use on the latest Raspberry Pi Ltd hardware.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants