Debug log, or you will step in the dark forever. ![]()
Posts by Da Flex
-
-
There are different Pine64 hardware versions. Which LE image do you use?
-
Use a kernel parameter. For RPi the file for kernel parameters is /flash/cmdline.txt. Editing steps on SSH session:
- mount -o remount,rw /flash
- nano /flash/cmdline.txt
- mount -o remount,ro /flash
- reboot
Append the needed resolution as kernel parameter (syntax here). All kernel parameters have to be on the same line.
Do you also have a cmdline.txt at your Pine64 file system?
-
Post another log with the other PSU, and at log level 1. You're still at log level 0:
Code2022-04-26 10:49:16.271 T:837 INFO <general>: Disabled debug logging due to GUI setting. Level 0.Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
I'm using a 3.1A PSU on my RPi 3B+. The benefit of a 3A+ PSU is that you can also use it for RPi 4 (with USB-C adapter). In case you're thinking about upgrading in the future, this comes in mind. Your choice.
-
Hmmm, I guess it has been 5 years, too long?

If the RPi is often used, then this could be too long. The under-voltage warning is in your log, so I suggest to buy a new PSU with 3A.
-
How old is your PSU? After some years they can lose wattage.
-
gekoch Thanks for checking the HDMI cable. We definitely need a debug log (see above) to track down the issue.
-
Thread moved to Hardware sub-forum.
-
So you want to use a switch button instead of a push button. In that case you can't use dtoverlay=gpio-shutdown, and you have to implement your own script to check the GPIO states. Here is a script that does the same like dtoverlay=gpio-shutdown. Start it from autostart.sh. You have to adapt it for your needs:
Python
Display More#!/usr/bin/python # This script was authored by AndrewH7 and belongs to him. # (www.instructables.com/member/AndrewH7) # You have permission to modify and use this script only for your own personal usage. # You do not have permission to redistribute this script as your own work. # Use this script at your own risk. import sys sys.path.append('/storage/.kodi/addons/virtual.rpi-tools/lib') import RPi.GPIO as GPIO import os # Replace YOUR_CHOSEN_GPIO_NUMBER_HERE with the GPIO pin number you wish to use. # Make sure you know which rapsberry pi revision you are using first. # The line should look something like this e.g. "gpio_number = 7". button_gpio_number = 3 led_gpio_number = 13 # Use BCM pin numbering (i.e. the GPIO number, not pin number). # WARNING: this will change between Pi versions. # Check yours first and adjust accordingly. GPIO.setmode(GPIO.BCM) # It's very important the pin is an input to avoid short-circuits. # The pull-up resistor means the pin is high by default. GPIO.setup(button_gpio_number, GPIO.IN, pull_up_down = GPIO.PUD_UP) GPIO.setup(led_gpio_number, GPIO.OUT) # Switch LED on. # LED will switch off automatically at shutdown by using normal GPIO state. GPIO.output(led_gpio_number, True) # Use falling edge detection to see if pin is pulled low to avoid repeated polling. # Send command to system to shutdown. try: GPIO.wait_for_edge(button_gpio_number, GPIO.FALLING) os.system("shutdown -h now") except: pass # Revert all GPIO pins to their normal states (i.e. input = safe). GPIO.cleanup() -
Also, choices for what to install seem to depend upon the box's h/w level as to RAM, S805 or 905, etc. - and I don't know any easy way to determine those needed specs.
Open the box and make a sharp photo. Sharp enough to read the print of the chips.
-
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
You can't buy 8K hardware. Such consumer standards still have to be developed.
-
Seems like your trouble starts with higher data rates. The HDMI cable can be a bottle neck. So make sure it's conform to HDMI 2.0 or 2.1. That's needed for any 4K playback.
-
Add the line dtparam=audio=on in config.txt.
-
It's an AAC audio error. Expect the same error on RPi 4. So I don't suggest to purchase one. Install latest LE 10.0.2 from scratch (don't upgrade), play some free AAC demos, and report.
-
If "pastekodi" doesn't work, then your system is broken. I suggest to install LE from scratch. Your current log is incomplete.