-
Notifications
You must be signed in to change notification settings - Fork 125
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
Update Kernel #849
Comments
The new CM5 units are finally shipping and my 4GB Ram, 32GB eMMC is posting the same Async error as the 2GB pi5 units when trying to run PINN. Do you have a beta version of the 3.9.3 update available? |
I shall make the 3.9.3 version available again shortly. |
Great! Thanks for all the work you put in |
I have uploaded 3.9.3 again for updates. Although it seems it was available via Rpi Imager all along. 😉 |
So far, I have been able to install PINN on an NVME attached to the CM4 with 3.9.2 installed and perform the update, then switch the CM4 out with a CM5. Does the current version of PINN not have DWC2? RPOS is using otg_mode=1 for CM4, but DWC2 for CM5 and as of now I can’t get any USB to work, I can only access via SSH or VNC. I’m pretty sure previous versions of PINN had DWC2, so maybe it’s a different USB issue. The first version of RPOS that works with CM5 is November’s and PINN is still on the October version. AOSP and Lineage work but only the versions that were released a few days ago. For some reason, I can’t get 3.9.3 to work at all on the eMMC of the CM5 only on the NVME I brought over from the CM4. When using that NVME along with the CM5, the eMMC doesn’t show up as a second drive option. |
Thanks for reporting. Unfortunately, I don't have a CM5 to test with, but I'll look into it. |
My official Raspberry Pi CM5 board just arrived and I will revise this to say that I don't think DWC2 is necessary. Older CM4 boards work with the CM5, but boards specifically made for the CM5 should have USB3 and not need the drivers. I will try installing PINN directly on the CM5 again later this week to see if it's able to boot with the official carrier board. Many of the OSes on PINN will need to be updated to newer versions as the CPU stepping on the CM5 and the Pi5 2GB is different than on the original Pi 5. |
The text was updated successfully, but these errors were encountered: