Posts by johnny depp
-
-
good evening
the "LibreELEC-RPi5.aarch64-13.0-nightly-20250427-34e4c98" seems to have a "bug"
after the update from LibreELEC-RPi5.aarch64-13.0-nightly-20250426-07a8ef5 to LibreELEC-RPi5.aarch64-13.0-nightly-20250427-34e4c98
Nighly always wants to search/start some "recordings" that I have not made (TV and radio) spinning "spinner" (?)if I go back to the LibreELEC-RPi5.aarch64-13.0-nightly-20250426-07a8ef5 the behaviour is not present
sorry this is translated with Deepl (german to english)

mfg jd
-
thanks
I have just added
"Changelog
2025-02-07 (92fefae): #9772 Revert \"curl: update to 8.12.0\"mfg jd
translated with DeepL
-
I hope it is correct
LibreELEC-RPi5.aarch64-13.0-nightly-20250207-5d50e8d made as update via LibreELEC-RPi5.aarch64-13.0-nightly-20250205-b876ad8
https://paste.libreelec.tv/hopeful-imp.log
https://paste.libreelec.tv/shining-rooster.log
-
Hi
I don't know if I'm right here "Bug Reports"
or I should write it in "Development" Nightly.LibreELEC-RPi5.aarch64-13.0-nightly-20250205-b876ad8.img ist ok
since the version (update)
LibreELEC-RPi5.aarch64-13.0-nightly-20250206-b83a91c & LibreELEC-RPi5.aarch64-13.0-nightly-20250207-5d50e8d
no more "streams"
Kodi crashes immediately when I want to call up a "contribution"
ARD&ZDF Mediathek, YouTube and Twitch e.g. films and music from HDD.Films and music from HDD is no problem
[Geekworm X1001 PCIe to M.2 Key-M NVMe SSD PIP TOP for
Raspberry Pi 5 (8GB)]
if I should attach a log please say/write
kodi.log
kodi.old.log
kodi_crash.logmfg jd
meanwhile go back to LibreELEC-RPi5.aarch64-13.0-nightly-20250205-b876ad8.img
translated with DeepL
-
-
-
-
-
question
why don't I read that he "flashed" or copied a (BS) Kodi on the NVMe and changed the config to NVMe!??
e.g. with https://www.raspberrypi.com/software/operating-systems/
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 deutschNVMe SSD boot with the Raspberry Pi 5 - Geekworm Wiki
External Content www.youtube.comContent 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.External Content www.youtube.comContent 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.External Content www.youtube.comContent 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.External Content www.youtube.comContent 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.

I apologise if I have misunderstood
-
hello
ist nur eine info
https://www.raspberrypi.com/documentation/computers/configuration.html
Example config.txt
Code
Display MoreBoot_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 -
-
Good morning
in the YouTube addon settings
Settings wizards
(Userdata - addon_data - plugin.video.youtube - api_keys.json/settings.xml)
everything under reserve
jd
translated mit DeepL
-
thanks for the new .img
for /13.0/RPi/RPi5/
Good work!
jd
-
hello ( heitbaum)
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 updatesWhat could be the reason for this (I have 0 idea here)?
with best regards jd
(info translated with DeepL)
-
-
-
good morning That's right - there was a bootloader update in the Nightly Rpi5 for the first time "yesterday".
great and keep it up
(translated with Google)
jd