Posts by VLouis

Quote from myshit

It shutdowns ok with SSH or from GUI. The only thing is the red LED that still keeps turned on preveting me from turn the Rpi again back on after shutdown - I have to manually press the button for few seconds.

I have a feeling, you want something what's never existed.

I have 3 RPi's and using with LE for years. And the red LED after shutdown always remains on, and to start again always needs to do a power cycle. That is how the RPi works with LE. It's not like a "normal" PC, with stand-by part in power source and with IO chip always powered, ready to react if the power button is pressed (and with a hidden power consumption in stand-by...).

The RPi have only a single GPIO input able to force to boot again if is activated with a button.

If you have concerns about the "LED red light", I think that LED can be disabled in config.txt.

If you have concerns about power consumption, after RPi "shutdown", the most part it's the power source itself (like any phone charger, have some consumption even if no phone connected), so switching of the main power can be the solution.

Quote from myshit

sometimes I don't turn it on like for a week so it's not necessary to keep it powerd on. Also every watt counts you know - some smart things, routers, standby device etc, it adds up.

In this case, it's a really simple solution, I'm using too:

Just shutdown from from the LE menu, wait few seconds, till remain only the red led on, than use the switch. If "every watt counts", switch off the power source too. And this can resolve an another question too: "How to start an RPI after full shutdown".

I'm even using something like this for my PC, I seen once a PC mainboard, burned badly in stand-by, because of a faulty PSU.

Quote from myshit

I can't access the file nor with ssh or from Windows PC when I remove the SD card. How can I do that? I turned on the logging before last shutdown like that: Settings>System>Logging>Enable debug logging, shouldn't it be in the log file when I use pastekodi?

To access files from ext4 partition: download a "live linux" like Ubuntu (or Xubuntu, is smaller), write it to a USB stick and run it from USB (without install). The easyest way is installing the "Ventoy" boot loader to a USB stick and booting the "iso" file directly (or almost any bootable iso).

About the RPi "full shutdown", I don't know in case of RPi4, but I measured once the power consumption of my RPi3B and was around 4-5W when playing video file. So if you too using daily your RPi, I don't know if worth the effort to "shutdown" it every times.

Quote from kronton

There is definitely no short circuit and other problems with the power supply. I have previously used Raspberry PI OS and everything was fine. The red background on Kodi appears at random moments. Depending on the connection and disconnection of various add-ons. I don't notice any devices.

Only the keyboard and monitor from the PC via hdmi are connected to the Raspberry.

Hi, I'm using 2 RPi3 with LibreElec (was 3, one I replaced with RPi4 recently) for years and didn't noticed any similar issue, even when had power source issue. And I didn't know to exist any "recovery mode" for RPi3 version of LE. Did you installed to SD card using the "LibreELEC USB-SD Creator"? A fresh install, without any addon, could be done, better if you have an another SD card to exclude the card issue too...

About the power source, if you can to try with another, just to be sure is OK... Try to change the USB (power) cable too, a short cable is better.

Quote from Dr. Seltsam

As I am on LE 11.0.1 I believe I have the infamous invalid-key-bug: https://github.com/LibreELEC/LibreELEC.tv/issues/7166

Is there anything I can do to fix this?

Hi, I had in the past something like this for a short time, before to change to LE nightly versions (RPi3).

Did you tried to update to the 11.0.3 (stable) version? Or use another SD card to install and try newer versions (nightly 11 or 12).

Hi,

For any version of RPi, the simplest way for IR remote is using an 3 pin IR receiver component with 3 short wire. You can find a lot of documentation about it.

The default IR remote codes set in LE is the "MCE" codes. I'm using my 3 RPi's with HP MCE remotes.

But can be used almost any IR remotes, with more or less works in settings.

About keyboard, I'm using only for first setup, mostly a simple USB keyboard. After that, in the seldom case of the text typing, I realy don't know what could be more anoying and complicated, a remote full with miniature buttons or the LE's virtual keyboard...

Quote from precocious phosphorous

fwiw I have used OSMC in RPIs for years. But since I upgraded to RPI4, OSMC has become unusable hence my attempt at getting Librelec to work on a X86 architecture.

Hi,

If you have an RPi4B, why don't simple use it with LE, as many other people do?

I think the same device for Windows and LE... could be difficult, because of uefi bios, secure boot...

Hi,

Could you have any possibilities to check the cable and monitor with another video source (laptop, PC with HDMI output)?

One of possibilities is to have EDID issue (cable or monitor), the device can't read from display the accepted resolutions.

What I don't know, if that 1480x900p is too "exotic" for LE or is able to provide video in that resolution.

Probably one of these two will be the issue.

Quote from nico2001

I've intalled LE (instead of Ubuntu).

Kodi is there, it's all great.

I switched it off then on again, still working.

Then tried to lauch it again, but it remained on the "Intel NUC" screen for a while...

I switched off and on again, and this time, the "Failed to read blocks 0x7" is back...

Hi,

I'm using the LE with Raspberry Pi (2x RPi3B, one RPi4B), I'm just writing the image to SD-card, put in the RPi and working.

So if I understod correctly, you prepaired an USB stick with the LE and installed the LE to the NUC internal SSD (HDD?)?

You successfully started once or more the LE from NUC internal storage, and after that happen the "Failed to read blocks 0x7" issue?

That looks to me as the installtion went OK, and something happen when you (re)start the LE.

Maybe some kind of BIOS or SSD boot issue in case of LE?

Ubuntu use the Grub as boot manager, maybe the LE use something else?

Could be possible to use two USB sticks? One with the LE "Installation kit" and to be install to another?

Maybe could be useful to share more inrmation about your NUC device, like model, processor, RAM, storage (SSD/HDD), if somebody else using same device and have any idea what is happen.

Quote from nico2001

Then, i should try to install LE instead of Ubuntu, right ?

I didn't know i could strat the LE image creator with admin rights... And i tried with the two UBS sticks i have... But as i could write the image with other tools, i really think something goes wrong with the LE image creator...

Let's see after your reply... Can i have Ubuntu AND LE ? Two OS ?

LE image creator with admin rights - Windows, right click to the program icon and select the "Run as administrator" - to force running as admin.

Then, i should try to install LE instead of Ubuntu, right ? - Depend what you want to do with you device. Yes, if want to use only as a very smart media player (and you will clarify why you can't install it).

Can i have Ubuntu AND LE ? Two OS ? - For this first you should manage to install the LE... make free space... than install the Ubuntu with dual boot settings. But you can have Ubuntu and Kodi. Just install the Kodi under Ubuntu: HOW-TO:Install_Kodi_for_Linux

Hi, if you managed to install the Ubuntu and working well... it's a good news.

If you still want to install the LE, you should focus to that issue when you tried to write the image to USB.

Maybe that "another tool to write" wasn't able to write the image exactly how should to be?

Did you start the LibreELEC image creator with admin rights? Or tried with another USB stick?

Hi, I suggest to you to try that "brand new intel nuc" with something else. Like try to run a live linux (Ubuntu) from an USB stick, try to install it, reboot few times. I think, as it's a number of peoples using the LE with Intel NUC or similar, in your case a defective device can't be excluded, even for a brand new hardware.

Quote from jazzlpunk

In fact, I did a reinstallation where everything looked as it should on the monitor untill I added video=HDMI-A-1:1280x720@60D to cmdline.txt. After that, I got no picture at all, not even after removing that line, so this is the point where I did another reinstallation. I did not try vc4.force_hotplug=1 at any point though.

Hi, What kind of monitor did you use for RPi4 setup, and what is the max. supported resolution? The 720p resolution is something standard for TV's. Something very strange happening with your RPi4 setup. Could be the HDMI cable, was few cases with poor quality HDMI cables what isn't supported higher resolutions (the monitor resolution?). Or the power source, I had something similar with my RPi3, when I connected something to RPi, after reboot wasn't had picture. Or TV EDID detection, could you try with another TV? Or after fresh TV setup, when the screen setup is done, try to send thru SSH the "getedid create" command. That will save the TV display parameters (EDID data) and will use it at every startup.

Quote from wyup

Havent gone to 11 stable to rule this out, I think I should, but too much work to undo.

That's the nice thing in the case of RPi, the all system is installed on an SD card, what is easy to replace.

Why you don't simple use an another SD card to try another versions?

I have a card with the latest LE 11 stable (in the case if the LE12 beta have any serious bug - doesn't got any yet...) and another card for playing with the new beta versions.

Quote from permheaddamage

Another thought: Since that user "petrel-p1" in serial console of stock fw has root previlege, maybe I can compile a Linux executable to play with efuse there.

If the efuse can be written again, I can write secure boot control bit 0 to disable it.

Hi, usually the e-fuse is OTP type ("Electrical Fuse, A one-time programmable memory"), can be write only once. I don't have the documentation of that Allwinner SOC, is not impossible to be in this case is something different, but usually this is the way how the e-fuse works.

Hi, maybe try this: After the LE installation finished, run a live linux from USB (Ubuntu...), use a partition manager (gparted) to resize the LE "user" partition to free up some space and create a new partition... About the NTFS partition... If that partition do you want to use with the LE too, perhaps you should use EXFAT instead, the NTFS sometimes isn't handled well in case of linux OS. Or if that PC will be used only for LE, the EXT4 is the best choice.

Quote from HiassofT

Random write speed is also important, especially if you use PVR which regularly updates the EPG database.

After the upgrade to LE10 - 11 I observed, the EPG update at every boot takes anoying seconds while was writen to SD card.

In LE9 was option to disable the caching of EPG data, removed in the next versions.

As I don't need any persistent EPG database (and to take care of my SD card life), I changed the path of the EPG database file to /tmp/ (advancedsettings.xml). Now the EPG is loading almost instantly (writing to RAM is always faster than any SD card)...

Quote from Operations8

will be also noticable slower?

Hi,

Not too many people have both devices to be able to compare for you... and the "noticable slower" is not an exact measurement...

Install the latest LE11 stable or the latest LE12 beta to a not too old (to not have slow read speed) SD card, insert in your RPi4 and check it. Will took for you less than one hour and you will have the answer...