The unpacked image is always 549MiB. Use this for your calculation.
The compressed size differs from platform to platform, e.g. ~211MiB for Generic or ~123MiB for RPI4.
Posts by mglae
-
-
Disk/image size is constant (read: changes in calculation are very rare): https://github.com/LibreELEC/Libr…pts/mkimage#L25
-
Test of Generic-legacy disappeared in https://github.com/LibreELEC/Libr…canupdate.sh#L5 after latest update.
-
Instead of messing around /etc/issue you may consider using /etc/os-release.
-
dmesg is only showing kernel messages. Use journalctl to see all system messages.
-
This can all be related to the memory, I/O or disk errors you see. Without any RPI experience I'm unfortunately unable to give any help.
-
There is no vdr backend user.
For the vdr live plugin default user/pw is admin/live (really hidden in the docu).
-
What if I told you that wifi reception on the rpi3b (as shown under libreelec settings > connections) is equally bad with an external usb wireless card too?
It's just a number. Unfortunately in current included connman 1.41 signal strength from iwd is computed different to formerly used wpa_supplicant.
In the meantime there is a fix. Expect higher numbers after next connman update.
-
-
Hi there. I am just wondering where I need to enable autoconnect to get this fix to work?
Open Connection tab of LibreELEC Configuration Addon. Select your connection and open menu with Enter. Choose Edit, enable autoconnect and Save.
-
AFAIK Intel has implemented a HD4600 hybrid HEVC driver for Windows but not for Linux.
-
I see crash logs since ~2 weeks by just rebooting.
The crash on exit is already fixed in kodi master. LE needs an update.
1. is it a "buildin feature" that the box reboots into "safe mode" after a fixed (?) number of LE crashes ?
Yes.
2. does the directory ~/logfiles/ only gets filled when a "safe mode"-reboot is triggered ?
It is at least filled when accessed via samba.
-
Use tar xf 20220414162636.tar -C /Edit: this does not work reliable.
Do:
Codemkdir -p /storage/.restore cp 20220414162636.tar /storage/.restore reboot -
I researched a little about this uas x usb-storage drivers and if I understood correctly the difference between them is basically some speed gain, right?
Theoretically speed gain but I doubt you do have an use case where you can notice it.
is there any way I could load this module before the mounting of the external drive, so that I could keep using it?
Both drivers are build into the kernel image there are no modules to load. The UAS firmware of the device is incompatible to the kernel implementation but luckily you can choose a different protocol.
-
There are errors in detecting your external SSD. Due to the time delay it is not automatically mounted:
Code
Display More[ 1.685265] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd [ 1.706852] usb 4-1: New USB device found, idVendor=174c, idProduct=1153, bcdDevice= 1.00 [ 1.706876] usb 4-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 1.706890] usb 4-1: Product: Ugreen Storage Device [ 1.706902] usb 4-1: Manufacturer: Ugreen [ 1.706914] usb 4-1: SerialNumber: 26A1EE8393E4 [ 1.715808] scsi host0: uas [...] [ 33.775391] sd 0:0:0:0: tag#17 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN [ 33.775428] sd 0:0:0:0: tag#17 CDB: opcode=0x9e, sa=0x10 9e 10 00 00 00 00 00 00 00 00 00 00 00 20 00 00 [ 33.802274] scsi host0: uas_eh_device_reset_handler start [ 33.926055] usb 4-1: reset SuperSpeed Gen 1 USB device number 2 using xhci-hcd [ 33.945820] scsi host0: uas_eh_device_reset_handler success [ 33.962119] sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB) [ 33.962891] sd 0:0:0:0: [sda] Write Protect is off [ 33.962910] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 [ 33.964012] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 33.964931] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes [ 33.994086] sda: sda1 [ 33.997500] sd 0:0:0:0: [sda] Attached SCSI diskTry to disable UAS with usb-storage.quirks=174c:1153:u kernel parameter.
-
Add debugging to the kernel command line to see mount command messages/errors.
And check dmesg for oddities.
-
On the client side ssh -vvv ... will show what is going on.
On the RPI create a log via LE Settings Addon or Samba share and check for errors.
-
dmesg|less or blkid in the debug shell may show more information.
