HOW-TO:Modify automatic watch and resume points - Official Kodi Wiki
^ see the diagram at the bottom of the page, it's all configurable
Posts by chewitt
-
-
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..
-
I FIXED IT I DO NOT NEED YOUR UNHELPFUL ADVICE ANY LONGER KTHX
Your caps lock key appears to be stuck.
-
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.
-
Can you give me the URL generated by "lspci | paste" .. and I'll see if I can find the ID's in kernel code to create a patch.
-
What kind of log entry are you expecting to see?
-
Code
cp /usr/share/kodi/system/keymaps/keyboard.xml /storage/.kodi/userdata/keymaps/keyboard.xml nano /storage/.kodi/userdata/keymaps/keyboard.xml <make changes> systemctl restart kodiCopy the default keymap ^ and edit things. Also see HOW-TO:Modify keymaps - Official Kodi Wiki
-
LePotato is a nice board (similar, but better designed than C2) but it has core weakness of all S905X devices; only 10/100 Ethernet. The better option would be an S905D device with GB Ethernet, but beware that some also ship with 10/100. Odroid N1 was cancelled. N2 will be along in a bit (but no ideas on it) and the H1 that HK have just announced probably isn't cheap but will have the advantage of being x86_64 and thus less exotic to support compared to ARM hardware. NUC's are good too.
NB: If it works, don't fix it
-
@Ae3NerdGod any further comment like that and you are banned. We do not tolerate that kind of language and behaviour in this forum.
-
SO .. basics. What card are you trying to use? .. and what GPU's models are physically present in the box?
-
It's not clear which device you do want to use, but assuming it's the AMD card the following will blacklist the nVidia driver module and prevent it from being loaded at boot time; at which time only the AMD card should be usable and xorg.conf(s) shouldn't come into play.
Codeecho "blacklist nvidia" > /storage/.config/modprobe.d/nvidia.conf reboot -
Looks like the device ID exists in both drivers (bcma and wl) so whichever one happens to be loaded by the kernel first (roll dice) tries to claim the device. We should probably patch out the device ID to prevent that.
-
I wonder if there's a workaround or if there's a working addon somewhere.
It only works on LE 9.0 images. Update.
