Kodi moved archive support to an addon some time ago so you need to install the binary addon for "archive support" (zip) or "rar archive support" (rar) from the LibreELEC binary addon repo; assuming whoever created the C1 image provides a repo for the image (as we have never officially supported the C1 so there's nothing in our repo).
Posts by chewitt
-
-
Multichannel audio support needs an alsa plugin creating. It's on the to-do list, but it's a major piece of work so it makes more sense to do this on a mainline (modern) kernel codebase where it will also benefit Amlogic and Allwinner hardware instead of sinking the effort into the older (current) Rockchip 4.4 kernel codebase which we view as temporary and not a long-term solution.
TL/DR; better audio support will come, but not for a while yet.
-
Older EFI firmware mac's are crap at USB booting. It's easier to burn an Ubunto ISO to CDROM and boot from that, and do a manual install of LE to the internal drive. It's years since I did one, but basically you need to create a GPT partition scheme with two EXT4 partitions for boot and storage and then copy the files from the first partition of a "Generic" USB image to the first (boot) partition on the drive. Then install a bootloader (syslinux or grub) and possibly rEFInd as a boot manager.
-
Microsoft "Media Centre Edition" was a short lived version of some older Win release. Lots of manufacturers shipped "MCE" compatible remotes with their boxes and Harmony can replicate the standard remote. I can't give more specific instructions about configuring Harmony devices as I have never owned one (nor do I plan to get one).
-
I've no idea what triggers udev to match on nvidia-legacy rules (and why nvidia rules are evaluated separately and before other GPU rules is lost in the history of the project somewhere), but clearly it does match, so overriding the file should work and avoids anyone needing to learn new things about udev. It's either an exceptionally rare kernel/udev bug or there's something odd about your specific hardware. I'd guess the latter. It's not a scenario I recall seeing before and I've been hanging around various incarnations of the project since ~2011.
-
Code
wget https://raw.githubusercontent.com/denilsonsa/udev-joystick-blacklist/master/51-these-are-not-joysticks-rm.rules -O /storage/.config/udev.d/51-these-are-not-joysticks-rm.rules reboot
^ run those commands and see what happens. If nothing changes you need to find the USB device ID's with "lsusb" and crib the format to add them to the rules in the file (only one rule is needed, for your ID's).
untested file found in 10 seconds by searching Google with "51-these-are-not-joysticks-rm filetype:rules"
-
-
If the LE box has a wireless card that supports AP mode, enable the wireless hotspot and connect the phone to that instead of the mobile router. Or get a normal wireless router/bridge and connect to the Cable network. DO NOT CONNECT LibreELEC TO THE INTERNET.
-
i had installed CoreELEC-S912.arm-8.95.3.img on my H96 Pro+ with a Black Mainboard.
You're asking questions to the wrong forum then. We stopped supporting their stuff when they fcuked off to do their own thing and stopped contributing to our codebase (not necessarily a bad thing).
-
HOW-TO:Modify automatic watch and resume points - Official Kodi Wiki
^ see the diagram at the bottom of the page, it's all configurable
-
The default Kodi keymap uses the enter key in keymaps.xml so that you press enter while highlighting a movie to play, and during a movie if you press enter the OSD comes up with play/pause pre-selected so pressing enter pauses, pressing enter again unpauses.
I'd set the harmony to be a normal MCE remote and it should "just work" with a standard-ish LE image using meson-ir that understands MCE command, or worst case you can create a custom keymap on the LE side that understands all the harmony keypresses. You won't be able to teach the harmony play/pause without something that sends play/pause.
-
No idea, but there's so much dumb crap in the 3.14 kernel it's completely possible.
-
The only other major difference is S905X supports HDR. If you have no HDR media, C2 is fine and you gain nothing from LePotato.
"Edit Thread" button (top right) and "Mark as resolved" .. visually less messy than editing the title
-
My bad .. "lspci -nv | paste" .. I'm looking for the device ID's and it's not shown by default
-
No idea what the error is caused by, but you can use the .img file with Rufus, Win32DiskImager, Etcher .. any similar app which writes SD cards.
-
Code
Display MoreOct 22 01:36:32 kernel: ACPI: RSDP 0x00000000000F7C10 000014 (v00 Nvidia) Oct 22 01:36:32 kernel: ACPI: RSDT 0x00000000BFEF3040 000038 (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000) Oct 22 01:36:32 kernel: ACPI: FACP 0x00000000BFEF30C0 000074 (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000) Oct 22 01:36:32 kernel: ACPI: DSDT 0x00000000BFEF3180 0061A6 (v01 NVIDIA AWRDACPI 00001000 MSFT 0100000E) Oct 22 01:36:32 kernel: ACPI: MCFG 0x00000000BFEF9740 00003C (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000) Oct 22 01:36:32 kernel: ACPI: APIC 0x00000000BFEF9380 000072 (v01 Nvidia AWRDACPI 42302E31 AWRD 00000000) Oct 22 01:36:32 kernel: Nvidia board detected. Ignoring ACPI timer override. Oct 22 01:36:33 systemd[1]: Starting configure Xorg Server for nvidia-legacy... Oct 22 01:36:34 Xorg[325]: creating needed directories and symlinks for driver: nvidia-legacy Oct 22 01:36:34 kernel: nvidia: loading out-of-tree module taints kernel. Oct 22 01:36:34 kernel: nvidia: module license 'NVIDIA' taints kernel. Oct 22 01:36:34 kernel: NVRM: No NVIDIA graphics adapter found! Oct 22 01:36:34 xorg-configure[315]: insmod: ERROR: could not insert module /var/lib/nvidia.ko: No such device Oct 22 01:36:34 systemd[1]: Started configure Xorg Server for nvidia-legacy.
^ the systemd journal clearly shows that udev detects an nVidia card so xorg-configure for nvidia-legacy is invoked according to:
So create /storage/.config/udev.d/96-nvidia.rules with the content below and then reboot and the updated rule file (which if present overrules the embedded one) should prevent the nvidia card from triggering the xorg-configure process:
CodeACTION!="add|change", GOTO="end_video" SUBSYSTEM=="pci", ATTR{class}=="0x030000", ATTRS{vendor}=="0x10de", GOTO="subsystem_pci" GOTO="end_video" LABEL="subsystem_pci" GOTO="end_video" LABEL="end_video"
The next rule to be evaluated is 97-xorg.rules which should now match against the AMD card:
LibreELEC.tv/97-xorg.rules at amlogic · chewitt/LibreELEC.tv · GitHub
In theory..
-
-
It sounds like the HTPC device is running in a different IP subnet to the NAS and there are no routing rules (or gateway) to handle routing data between the two subnets; hence the "no route to host" message. If you added a WIFI router to an existing network (a hunch) it will be easier to configure it as a wireless bridge so it simply provides a wireless extension to the existing network instead of creating a second (routed) network for wireless devices. If you use it as a router (which will also result in NAT being used) you will need to configure routing rules (either manually on each host or pushed via DHCP) so devices in each subnet know how to route data to each other.