Posts by HarryH

MatteN ,

if he has a NVMe to USB adapter and the luck, that his Luxar NVMe is supported by the RPi5 bootloader too you are more than right.

But that the NVMe is detected by the kernel is unfortunately no guarantee that it boots from.

appliedthinking,

If have such adapter, that would be the easiest way. Depending on your experience with the Linux CLI and your goals there also other possibilities with dd and so on.

Do you want remove the SD card and use the NVMe as boot device or only for /storage ?

Because your kernel was already able to find the NVMe the line dtparam=nvme could be obsolete. The dtparam=pciex1_gen=3 is only to force PCIe bus to higher speed level. This speed is not official supported and can make additional trouble. My recommendation: activate these settings as the last step after all other things are ready and observe your dmesg log for sporadic PCIe error messages, to be safe and prevent data corruption.

https://wiki.libreelec.tv/configuration/config_txt

Perhaps the changes regarding Bluetooth in kernel 6.6.21?

Are you able to boot your Mint with an older kernel like 6.5.0-21?

I can confirm, that strange behavior. After some attempts without success, I had let the port assignment in the default position 0. The things like remote control of KODI, TV off/on seems to work most of the time. I hoped that it was fixed with LE12, but I can say „currently no“.
But it seems now a unexpected „feature“ of self sorting and self hiding of entries in the settings menu implemented. So I thought it's currently under construction...

Only to be sure: You doesn‘t use a case like Argon40 One or some like that, which has a separate power on/off switch?

Do you have made some changes at the EEPROM settings? Something like this combination:
POWER_OFF_ON_HALT=1
WAKE_ON_GPIO=0

That prevents the RPi4 from boot, until you shorten GLOBAL_EN to ground - if I understand the documentation right.

Version 0.0.13 released

• added option for displaying temperature in Fahrenheit
• added SSD/NVMe temperature observing option for fan control

Be aware: switching the display units between Celsius and Fahrenheit behaves like 2 different temperature profiles. There is no transfer of the values (no migration) from one profile to the other.

Regarding the SSD/NVMe fan control: The settings are only shown, if the GUI is set to Advanced or Expert ! The temperature profile with the highest required PWM value wins.
For example if you set value for SSD/NVMe too low, than the fan will starts regardless if the CPU temperature is over the 1st threshold or not.

Version 0.0.12a released

• bugfix: works again with LibreELEC 11

The other day I was concentrating on getting it to work with LE12 and accidentally put a line of code in 0.0.12 that prevented it from working with LE11. However, I'm surprised that no one here has complained about it. Have you all switched to LE12 yet?

I asked this because I had stumbled upon this information::

https://www.raspberrypi.com/documentation/computers/configuration.html#mini-uart-and-cpu-core-frequency

But it seems, that the described behavior regarding the reduced/fixed core clock is not true in all cases and because of some open bugs in the firmware is not predictable.

enable_uart=1 NOT fixing core_freq to 250MHz · Issue #4123 · raspberrypi/linux

Is this the right place for my bug report? I hope so, apologies if that's not the case. I've also posted on the RPi forum (See…

github.com

I understood that VC-1 is not hardware decoded with a RPi4. But at a desktop computer ffmpeg tries to use some common acceleration functions to decode newer formats, which not directly supported by the GPU. It could be wrong, but my idea was, you should check if the VPU of the RPi4 has switched to 500 or 550MHz, to ensure that you get the maximum performance and not work against an additional limit.

vcgencmd measure_clock core

No, the kernel in the master branch (LE12) seems to be the most recent one and not in a hold state.

6.1.74 (LE11) vs. 6.6.21 (LE12 current)

Commits · LibreELEC/LibreELEC.tv

Just enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.

github.com

But, after reading your initial post the 2nd or maybe the 13th time ... Do you have used LE12 the last months without any trouble? Only after you updated the bootloader, you have this issues? Why you don't change the bootloader to the old version (if you know the date) or go forward to the recent version 2024-02-16?

It should be possible in both directions (older / newer), as long as you use a version which supports your RPi5. In the worst case you must use the recovery.bin, but what is without a risk?

I think this should be the way. You should only ensure, that you use a binary for the RPi5:

rpi-eeprom/firmware-2712/default at b745226b41ac202976ee8307fcb179a1193fab3c · raspberrypi/rpi-eeprom

Installation scripts and binaries for the Raspberry Pi 4 and Raspberry Pi 5 bootloader EEPROMs - raspberrypi/rpi-eeprom

github.com

Post

RE: How do I downgrade Pi 4B bootloader/firmware?

I wouldn't do it but it's up to you... Try this:

(Code, 13 lines)

Please note you may need to change the bootloader config as there're some changes in recent bootloader revisions.

ghtester

January 11, 2022 at 3:04 PM

It could depends on my bad English, but what should I expect under a „Multi USB powered hub“ ? It‘s a powered hub? Or a USB hub which gets the power from 1 or multiple USB ports of the RPi5 only? No external power supply?

If the answer for the last question is „yes“, it sounds critical to me, because the RPi5 alone needs a stronger power supply 27W than the RPi4 (18W). And you will drive 4 additional USB drives. This could be far away of the official current specification for a USB port or the RPi5 board itself.

If you are still below the current limit of the RPi5 USB ports and your power supply is powerful enough, do you know about this config.txt settings?
https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#differences-on-raspberry-pi-5

usb_max_current_enable=1

and in EEPROM config:
https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#PSU_MAX_CURRENT

PSU_MAX_CURRENT=5000

One of the other possibilities is, that something regarding the NTFS support was changed with the recent kernels.

Zygmunt,

only a curious question regarding the VC-1 performance at your RPi4: Do you have additional lines in config.txt like this?:
enable_uart=1

Version 0.0.12 released

• switches from gpiozero to pure lgpio if available (workaround for lgpio GPIO busy error message)

Version 0.0.11d released

Original this version should only be a debug release, but I corrected many things under the hood so I don't hide.

• “Handle power button events” is honored without reboot
• remote control shutdown exception fixed
• fan settings now adjustable in 1 degree steps
• added debug messages
• freeing of power button detection GPIO pin forced
• code cleanup
  

Edit:
Known issues:

• LibreELEC 12 -> gpiozero makes some trouble in combination with lgpio
  If the add-on was disabled and enabled again, the GPIO pin for power button monitoring can't be freed. To workaround a reboot is needed, to work again.
  It's a general issue, not specific for this version. It affects all versions until now. I'm currently investigating to find a solution for that.

Version 0.0.11b released

• explicit firmware detection during power off procedure to reduce this call to one
• attempt to fix the permission issue for lgpio workaround
  The problem must have existed from version 0.0.7 to 0.0.10, but unfortunately no one here reported that the add-on does not work properly in combination with LE12. In such cases, I would be happy to receive feedback and, if necessary, a kodi.log.:
  https://wiki.libreelec.tv/support/log-files

You need to force gpiozero to initialize lgpio with the correct chip. For this you need LE12 nightly, because lgpio is only part of the RPi tools from LibreELEC 12. This combination is currently the only one that supports RPi5 out of the box.

To initialize the RP1 at the RPi5:

from gpiozero.pins.lgpio import LGPIOFactory
from gpiozero import Device, PWMLED
Device.pin_factory = LGPIOFactory(chip=4)

Additionally you have to circumstand this lgpio bug:

Post

RE: Raspberry Pi Tools - GPIOZERO - LE12 Issues

Great, that lg-gpio issue was already reported almost 2 years ago https://github.com/joan2937/lg/issues/12 but hasn't been addressed yet.

I've opened a gpiozero issue https://github.com/gpiozero/gpiozero/issues/1106 so gpiozero will (hopefully) add the recommended workaround

so long,

Hias

HiassofT

January 9, 2024 at 2:24 PM

Quote

Can the addon be configured so it doesn't override /storage/.config/rc_maps.cfg on boot? I've changed it to support the remote I'm using but after a reboot its back to the argon40 remote.

Before I look deeper into the code, does this "touch /storage/.config/argon40_rc.lock" don't work for you?

Regarding the range. I have seen your post in Argon40 forum. I can only report from a buddy of me, who is owner of a Argon One V1 and has added the IR Receiver manually. He reported a bad response to the IR signal until he has made a slot/hole in the transluent red plastic cover. Before made such irreversible changes you should check without the bottom assembled.

Edit:
In a short test with my universal remote control, I got a distance of about 4m/13 feet when I pointed the remote control frontal to the argon case. The further you go away, it seems more important to keep the remote control at the same heights as the case/IR sensor.

Version 0.0.10 released

Please read the additional informations in post 25 [RPi4B] Argon One Case Shutdown

• switched from lircd to rc_maps/keytable for argon remote
  if you use a own remote control profile please make a backup before install and/or add a lockfile to prevent overwriting.
  touch /storage/.config/argon40_rc.lock
• faster shutdown/reboot
• workaround for remote control shutdown

Version 0.0.9a released

• includes the fix for power button recognition with RPi5 + LE12
  (double tab) -> Reboot
  (hold > 3 seconds) -> graceful shutdown
  (hold > 5 seconds) -> enforced shutdown with power cut Pi

A fix for the power button recognition with RPi5 + LE11 is currently not possible, because lgpio is only available with RPi-Tools Add-on for LE12. The LE11 RPi-Tools Add-on provides the backend RPi.GPIO which doesn't support the RPi5.

The hopefully fixed version 0.0.8 is available. Please report if it's working now without fan fluctuation with the Argon One V3 case.

Can someone with a Argon One V3 case check if a "Double Tap" at the power button triggers Reboot like with Argon One V2 case?
If not, I need some information if it works after changing these lines in /flash/config.txt from:

dtoverlay=gpio-ir,gpio_pin=23
dtparam=i2c=on
enable_uart=1

to

dtoverlay=gpio-ir,gpio_pin=23
dtparam=i2c=on
dtparam=uart0=on

Followed by a reboot.