Have the problem. My AMD system is also not working on 10.0.3 just splash screen and nothing happens.
could you try that version if it works again ?
Have the problem. My AMD system is also not working on 10.0.3 just splash screen and nothing happens.
could you try that version if it works again ?
could you try that version if it works again ?
Seems to work, no problems yet
Just updated by selecting 10.0.3 under channel. Seems OK.
BUT ...... the firmware update refuses to update.
selected and rebooted twice to no avail.
Still offers update from the installed January edition.
On reboot a screen does indicate update available and then rapidly disappears.
Remind me what are the commands to update via the terminal ?
Display MoreJust updated by selecting 10.0.3 under channel. Seems OK.
BUT ...... the firmware update refuses to update.
selected and rebooted twice to no avail.
Still offers update from the installed January edition.
On reboot a screen does indicate update available and then rapidly disappears.
Remind me what are the commands to update via the terminal ?
I assume you are using an RPi4 and try to update bootloader firmware (which doesn't work with USB boot yet). In this case run
and then reboot.
so long,
Hias
autoupdate is not turned on yet, its done starting next week
CvH I haven’t gotten an auto update prompt yet - still on 10.0.2
Don‘t hang in there, 10.0.3 is really worth the update and 10.0.4 is around the corner (i suppose)
Ok but is it an auto update or do I have to update manually?
I am on Pi4
Given that AMD users are recommended not to upgrade, what are we supposed to do instead?
wait for 10.0.4 as Kodi update is out since yesterday.
Given that AMD users are recommended not to upgrade, what are we supposed to do instead?
running a LE10 nightly (that has all the fixes included) or wait for LE10.0.4 or LE11
any ETA on 10.0.4 ?
any ETA on 10.0.4 ?
When its done.
I knew the answer
Happy new year.
Can anybody confirm that this release actually reads the config.txt. Because even when i add the line "hdmi_force_hotplug=1", i can't get any output on my tv if i turn the tv on "after" the pi. That wasn't the case before. After adding this line, i could turn the tv on anytime (before or after the pi is on) and could get tv output. Now i have to first turn the TV on and then plug in the pi. Which makes me think that this version ignores the lines added to config.txt.
Can anybody confirm that this release actually reads the config.txt. Because even when i add the line "hdmi_force_hotplug=1", i can't get any output on my tv if i turn the tv on "after" the pi. That wasn't the case before. After adding this line, i could turn the tv on anytime (before or after the pi is on) and could get tv output. Now i have to first turn the TV on and then plug in the pi. Which makes me think that this version ignores the lines added to config.txt.
Hi,
Start with TV on, SSH to RPi and use the "getedid create" command. That will save your display/TV parameters and will use it at every startup (even if the TV is off). If you want to know more: https://wiki.libreelec.tv/configuration/edid
Hi,
Start with TV on, SSH to RPi and use the "getedid create" command. That will save your display/TV parameters and will use it at every startup (even if the TV is off). If you want to know more: https://wiki.libreelec.tv/configuration/edid
Thanks for the tip. I'll try it.
Hi,
Start with TV on, SSH to RPi and use the "getedid create" command. That will save your display/TV parameters and will use it at every startup (even if the TV is off). If you want to know more: https://wiki.libreelec.tv/configuration/edid
I did try this. However, after experiencing performance problems, especially on live streams, i had to delete the edid file. So i think it is safe to say that it affects some other aspects of the system that i do not know of.
I did try this. However, after experiencing performance problems, especially on live streams, i had to delete the edid file. So i think it is safe to say that it affects some other aspects of the system that i do not know of.
It's extremely unlikely that using the edid file is the cause of live streaming issues.