@gregeeh
Upgrade petitboot
Please use official, updated description:
https://wiki.coreelec.org/coreelec:odroid#solutionpetitboot_update
hxxps://forum.odroid.com/viewtopic.php?p=379379#p379379
1 Like
Option 2 from the linked page got me around the exact same problem. Make sure that petitboot is up to date tho.
Please use official, updated description:
https://wiki.coreelec.org/coreelec:odroid#option_cusb_otg
hxxps://forum.odroid.com/viewtopic.php?p=278010
Thanks for updating the link @Portisch, I wasn’t aware that this info was in the wiki.
2 Likes
Thanks for your reply.
Have updated petitboot and no will not boot. Giving a kernel dump:
Using the latest no nightly for N2 (CoreELEC-Amlogic-no.aarch64-21.0-Omega_nightly_20240209-Odroid_N2.img)
Thoughts?
EDIT: N2 is 4GB. 16GB uSD. Happens with or without eMMC installed.
EDIT2: Put the latest 20.4 onto the same uSD using the same version of Rufus and no issues at all.
I’m no expert here, just a dedicated user but I think I’ve read that the no versions will not run from petitboot. My guess is that you left your N2 in petitboot mode and tried to run it.
Yes, I don’t think so to. Try with MMC mode. petitboot is for 4.9 kernel DT, not 5.15.
Sorry, but that is not what I did. It was in MMC mode.
Same result in MMC mode, sorry.
That is not correct. “no” version on N2 boots and runs OK via Petitboot, but Petitboot must be updated to latest version. See here
You can download this new version from:
http://ppa.linuxfactory.or.kr/images/petitboot/odroidn2/spiboot-20231218.img
Btw, I mentioned this 2 months ago here
@gregeeh - I have been running my N2+ with “-no” version from uSD card for the past several weeks. During this time I had the eMMC card removed as it would not boot the new uSD kernel with the old 4.9 kernel installed on eMMC.
I followed the tips earlier in the thread and downloaded the 20231218 petitboot image and updated.
I now can boot my Nexus (4.9) image from eMMC (when no uSD card is in the slot) and boot Omega (5.15) from uSD even with eMMC card installed. The SPI switch is set to eMMC. The info given in the thread is good. I can only assume that your petitboot update may not have completed properly, perhaps? You may need to download a recovery image to fix it properly.
Thanks everyone for your input.
I have updated to the latest petitboot and I am booting with the switch in the eMMC position. Still getting the kernel dumps when booting “-no” via uSD.
I downgraded to petitbooot 2023.06.13.img and then upgraded, again, to 2023.12.18.img. Same results.
There seems to be something going on with my N2 as I’m very sure I’m doing all the correct things.
What else can I try?
TIA
EDIT; Just installed an N2 Recovery Image and then updated to petitboot to 20221703 before updating to 20231218. Everything still the same, cannot get “-no” to boot.
When you start in SPI mod - switch in SPI position - what version (on top of the screen) is shown?
All my booting different CE/Android version via Petitboot is done with SPI switch in SPI POSITION!
The SPI position is only useful if you need to multiboot from different OS/s or USB devices. In eMMC position it should automatically boot CE from eMMC or from uSD if one is present without invoking petitboot. I presume the petitboot update was to permit the CPU loader to handle the different kernel versions of CE.
Version 20231220.
Just took a video of the boot of “-no” and looked at it frame by frame, as the dump is really quick. The first message on the top of the screen is:
" failed to start systemd-hwdb-update.service"
Helpful - I don’t know.
Thought you downloaded 20231218?
I did, but that’s what comes up on the screen. Even checked the MD5 for 20231218 and it’s correct.
I didn’t actually check the version that came up on screen. Just did the update and flicked back to eMMC position afterwards! All ok on my system, though.
So what version do you get on the screen?
No idea - don’t use petitboot. My TV/AVR etc. are all switched off for the night. I’ll have a look tomorrow and report back.
My apologies - I should have realised that the .img file was on a folder on my PC. So, I checked it with a hex editor just now and 20231220 is the internal date in the file! @tobetter must have created a slightly newer version and not renamed the actual filename.
Nightly 20240221
Finally the new kernel 5.15.119 is ready for first tests.
Known issue is SM1 (S905X3, S905D3) and HDMI audio.
So please ensure to have HDMI multi channel LPCM enabled (default) in kodi audio settings until it’s fixed.
2 Likes