Posts by Da Flex
-
-
-
Your options:
- provide a log file, and we will investigate what's wrong with your current WiFi dongle
- buy an Ethernet-to-WiFi adapter to avoid any WiFi driver issues in the future
VONETS WiFi to Wired WiFi Bridge Ethernet/Signal Repeater Mini Industrial 2.4GHz 300Mbps 1 RJ45 Male USB/DC Powered for Monitoring,Electronic Scales,IP Printer,Robots,Medical Devices VAP11G-300VONETS WiFi to Wired WiFi Bridge Ethernet/Signal Repeater Mini Industrial 2.4GHz 300Mbps 1 RJ45 Male USB/DC Powered for Monitoring,Electronic Scales,IP…www.amazon.com -
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 -
Support rejected due to usage of banned add-ons.
ThreadForum Rules
General Conduct- Be polite and respectful to forum staff and other users
- Be polite and respectful towards this project and other projects
- Be patient, user and staff are spread all over the world, an answer may take time
- One topic per thread
- Posts should be written in English (add text in your native language if needed)
- Be as descriptive and detailed as possible. We are not mind readers!
- If AI tools have been used to create your post or triage an issue, name the tool and version in the post
- Do not
newphreakMarch 15, 2016 at 1:02 AM -
What hardware is this?
Please answer that question.
PS: Sometimes a partition has errors, and due to those errors unmount fails. Check your partitions for errors. If you did hard shutdowns in the past (long-pressing the power button), there is a chance that you created errors on a partition.
-
If you can't handle it on LE's audio settings (expert mode), then we need info about the codec...
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 -
The "failed to unmount..." error is normal, and not related to the issue.
Try this: RE: LibreElec on Wyse 5010 does not properly shut down
-
For such hard cases I suggest an Ethernet-to-WiFi adapter. Something like this:
VONETS WiFi to Wired WiFi Bridge Ethernet/Signal Repeater Mini Industrial 2.4GHz 300Mbps 1 RJ45 Male USB/DC Powered for Monitoring,Electronic Scales,IP Printer,Robots,Medical Devices VAP11G-300VONETS WiFi to Wired WiFi Bridge Ethernet/Signal Repeater Mini Industrial 2.4GHz 300Mbps 1 RJ45 Male USB/DC Powered for Monitoring,Electronic Scales,IP…www.amazon.comThe cheaper ones of that site only have 2.4GHz, the newer, expansive ones also have 5GHz. They use the Ethernet driver, so they have to work.

-
Do you mean you see the power-off menu instead of instant power-off?
-
But this must be the same as me putting the file into the folder update as well right?
Yes.
-
Update to Generic-legacy on SSH:
- cd .update
- wget https://releases.libreelec.tv/LibreELEC-Gene…4-11.0.3.img.gz
- reboot
-
True. HDR is technically impossible on Generic-legacy due to X11 window system.
-
Raspberry Pi? Reinstall LE on another microSD, and use Etcher to write the image.
-
If it boots correctly after the third attempt, it's the same error.
-
RPi5 is a brand new device, so problems and log requests are normal.

-
I forgot to mention that after reboot kodi.old.log is what we want to see. To my knowledge, nobody else had that issue before.
-
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 linkThere is a chance that pastekodi command doesn't work (third party server problem). In that case copy & paste the log (/storage/.kodi/kodi.log) into the attachment of your next post. Devs are working on our own log server to fix it.