on usb and then reboot to the NVMe (without sd card copy) only because of the config and boot order
unfortunately I only have instructions in german
Display Spoiler
frage (deutsch) warum lese ich nicht das er ein (BS) Kodi auf der NVMe "geflasht" bzw. kopiert hat und die config auf NVMe umgestellt hat!? zb. mit https://www.raspberrypi.com/software/operating-systems/ auf usb und dann mit reboot auf die NVMe zu kommen (ohne sd Card Copy) nur wegen der config und bootreienfolge leider hab ich nur anleitungen auf deutsch
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
Content embedded from external sources will not be displayed without your consent.
Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.
Boot_Order options:
The BOOT_ORDER property defines the order for the different boot modes. It is read from right to left and up to 8 digits can be defined.
In the example set above “BOOT_ORDER=0xf416” this is 6-1-4-f:
6 = First boot attempt from NVME
1 = Second boot attempt from SD card
4 = Third boot attempt from USB
f = Loop – start again at the first boot attempt
############
BOOT_UART=1
POWER_OFF_ON_HALT=0
BOOT_ORDER=0xf146
PCIE_PROBE=1
dtparam=pciex1
dtparam=pciex1_gen=3
include distroconfig.txt
Display More
Code
Run
sudo raspi-config -->raspi-config.png
Select Advanced Options.
Select Bootloader Version.
Select Default for factory default settings or Latest for the latest bootloader release.
Reboot with sudo reboot.
it seems to be "Something is rotten in the state of Denmark" again for /12.0/RPi/RPi5/ is being built LibreELEC-RPi5.aarch64-12.0-nightly-20240819-7e0b15d.img.gz (last)
and for /13.0/RPi/RPi5/ not LibreELEC-RPi5.aarch64-13.0-nightly-20240816-018c547.img.gz (last)
Display Spoiler
Changelog 2024-08-19 (a25491a): #9202 ffmpegx: arm: allow 32-bit arm compile with binutils 2.43 2024-08-18 (5e1c06f): #9201 kodi: update to cdfc755 2024-08-18 (984e99a): #9200 gcc: 14.2 upstream fix for building libaom on arm64 2024-08-17 (14951f7): #9198 linux (RPi): update to 6.6.45 2024-08-17 (93b49f6): #9194 systemd: add ZTERCR21 BT remote device to 70-local-keyboard.hwdb 2024-08-17 (58ae4a6): #9195 update_binary-addons: add -x option to skip no tag updates 2024-08-17 (43f76dc): #9193 kodi-binary-addons: update to latest versions 2024-08-16 (018c547): #9192 mesa: drop unnecessary kmsro option 2024-08-16 (35a05c8): #9190 Package updates 2024-08-16 (d0f92f4): #9186 proftpd: update addon (1), convert HTML special entities 2024-08-16 (a05f732): #9103 mesa: update to 24.2.0 2024-08-15 (f02cf5d): #9185 inputstream.ffmpegdirect: update 22.0.0-Piers to 22.0.1-Piers 2024-08-15 (b0a8fed): #9184 Package updates
What could be the reason for this (I have 0 idea here)?
Hello Since the "LibreELEC-RPi4.aarch64-12.0-nightly-20240118-0af59b4.img" there are again problems (error messages) with "script.embuary.helper" (https://github.com/sualfred/script.embuary.helper ) and is thereby “deactivated” have you noticed that yet?
Good morning I format the SD card, USB stick or ... under Windows in NTFS and so far the "LibreELEC.USB-SD.Creator.Win32" version 1.4 tool has always recognized everything
no matter whether LE 11 or Nightly 12 (translated with Google) greetings
Good evening (translated by Google) First of all, I'm excited about it LibreELEC-RPi4.aarch64-12.0-nightly-20230911-e17bf16 no error found yet (yet ;-)) Kind regards