Posts by escalade
-
-
20170831:
Codelinux: update to 4.12.10 udevil: remove "nonempty" option from exfat options parallel-n64-libretro: update to 1662062 media_build: revert hauppauge second tuner support brcmfmac_sdio-firmware-rpi: set BT MAC as new firmware uses a fixed MAC wlan-firmware: update to wlan-firmware-34a47d9 kernel-firmware: don't install brcmfmac43430-sdio.bin brcmfmac_sdio-firmware-rpi: update to brcmfmac_sdio-firmware-rpi-0This build now uses the exFAT-nofuse driver, which is much faster than the FUSE driver that ships in regular LE.
-
You should post in feature requests. I don't think there's much interest in doing a zabbix-agent addon though, most people don't need to monitor their HTPC with such a tool. There is however an SNMP addon which you could use.
And no, you can't compile anything under LE. You would need to download the source and build a toolchain.
-
You're in the "PC" section. Why should there be a separate NUC section, you want a subforum for each PC model? That's going to be a whole lot of subforums. Those that exist are for special hardware that runs LE.
-
If you want to be helpful, read and follow what the first post says. Developers don't come here looking for bugreports.
-
It has nothing to do in this thread if the same problem exist in regular LE builds, which you would have known if you had read the OP. There's already a bug reports section. You're very close to be on my permanent ignore list.
-
No need to report unconfirmed problems that your son told you.
-
And you have of course cross checked that it works on regular LE 8.1 builds? Where is the logs?
-
Using the build from the archive should only be necessary when upgrading from regular LibreELEC. When doing a new install and writing my .gz to a stick you should not need it. The reason for this is that the compression algorithm the squashfs in my build uses (Zstd) is not in the default Linux kernel, so it can't be mounted if the running kernel does not support it. Thank you for the feedback, I should probably revise the README to make it more clear when the archive build is needed.
Like I said, for a crash you would need to do a "journalctl -f" from console when it happens, because the log is only in memory and does not get stored after a crash.
Most likely it's a memory allocation failure. There's a couple of things you can do:
1. LibreELEC copies the root filesystem to memory during boot, which for the RPI amounts to about 370MB. You can avoid this by editing /flash/cmdline.txt and adding "noram" to the end. It'll look something like this: "boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 quiet noram". This will free up the same amount of memory, at the cost of boot and SD card access speed. You may not want this if you have a slow SD card.
2. By default LibreELEC does not have any swap. You can enable swap by copying /etc/swap.conf to /storage/.config, then edit it and change SWAP_ENABLED="no" to SWAP_ENABLED="yes". When you reboot, a swapfile the size of SWAPFILESIZE (default is 1024 you can increase if you like) will be generated in /storage/.config/swapfile.
All those downloading apps you are using are quite memory hungry, so it's only n4tural for the RPi (which has only 1GB RAM) to have this issue with your use. Best of luck
-
If that's what it says, that's what you should do. Can I reword the text to make it more clear somehow?
-
Because the upgrade process failed and you're not running my build. You missed the README in the download directory
-
I've made adjustments to natively run Chrome in my community build. As mentioned, it's also possible to run it (and anything else) in Docker.
-
Can't see anything out of the ordinary.
-
-
I wouldn't call anyone stupid as I don't expect everyone to be an expert, but I do expect people to have the courtesy to read and follow instructions of the thread that they are posting in. Providing support in a forum is indeed challenging, which is why I encourage people to stay on topic and create new threads for whatever other issues they have with LE. Just having a blowout as every new post the last few days had ignored the OP.
-
You're in luck, I've added cryptsetup and lvm2 tools to my latest community build. You could either use my build, roll your own or create addons using my packages as a starting point. LE versions >9 do not include the necessary kernel modules though, but in the next major version there will be kernel module overlay support thanks to HiassofT.
Encrypting /storage would require quite the rework of the initramfs /init, and I'm pretty sure nobody would be interested in that. What usecases is there for encrypting /storage?
-
20170829:
Code
Display Moreoem: include cryptsetup (and lvm2 by dependency) cryptsetup: initial package lvm2: initial package oem: install openssl-compat for both projects SDL2: update to adfae6e par2cmdline: update to c246258 from https://github.com/BlackIkeEagle/par2cmdline dbus: update to dbus-1.11.16 LibreELEC-settings: update to 2ef3940 libpng: update to 1.6.32 libdrm: update to 2.4.83 libva: update to 1.8.3 gtk3: update to 3.22.19 ncurses: update to 6.0-20170827 glibc: add upstream fix for unsafe IFUNC system/longjmp in libpthread -
Haven't seen that, though it's quite some time since I actually had an RPi device. For a system crash, what would be useful is the output of "journalctl -f" during the crash. Does it happen during unpacking or verification/repair? A new version is uploading in a few minutes, which includes an updated par2cmd. I switched to a version that includes openmp multithreading some time ago, perhaps the code is unstable with RPi. Worth giving the updated version a shot.
EDIT: I noticed a different issue in your log, the dispmanx_vnc addon was looking for libssl.so.1.0.0 which was missing for the RPi build. It's included in the latest.
The "06_varlog" file will contain every logfile from /var/log. There won't be a /var/log/retroarch.log until you start that application (obviously?). So what you'd do is launch RetroArch, cause it to crash then access the logfiles share which will generate a nice logfile that you can upload here. Everything one needs to troubleshoot something is in there. System log, kernel log, hardware info, Kodi log, application logs, etc.
I don't want to be a stickler, but I've made every effort to make it as clear as possible what I need from you. It seems so easy, yet nobody does it. How can I help with a problem without having any information about it? I'm just tired of asking every person for what's clearly written in the OP. If there's anything I can do to make it any more clear, do let me know.
