Posts by chewitt

HK provide their own version of wiringPi, which almost certainly means they have adjusted it to match the GPIO layout. I doubt the Pi add-on can be ported directly.

and, please stop wallpapering the forums with the same question

Quote from Isi_San

For your information, this pc has Linux Mint Mate 18.2 Sonya as OS installed and is doing good.

Kodi 17.5 for linux was installed on this old pc and kodi is running fine, no big issues, no hardware problems, no graphic card complaints !!!

LE deliberately targets current/recent generation hardware and we have no interest in supporting 2005 era things. I'm surprised it even worked in our 7.0 release. Your solution is to run ^ Kodi 17.5 on Linux Mint .. or stick with LE 7.0.3.

wget http://addons.libreelec.tv/8.2/RPi2/arm/virtual.rpi-tools/virtual.rpi-tools-8.2.104.zip
or
wget http://addons.libreelec.tv/8.2/RPi/arm/virtual.rpi-tools/virtual.rpi-tools-8.2.104.zip

I've no idea whether RPi (0/1) or RPi2 (2/3) will be binary compatible with an Odroid_C2, and most other SBC manufacturers lie through their arses about Pi compatibility for their boards (form-factor compatible but almost never GPIO compatible) but ^ those are the URLs for the add-on zips.

If things work it's great. If things don't work, it's not our problem to solve

Keymap editor is in the Kodi add-on repo. Make sure there are no old(er) custom keymap.xml and keyboard.xml files installed.

Jayge91 the "Pi Tools" add-on is only built for Raspberry Pi images (hence the name)

What hardware are you using?

LE is not a general purpose distro and we like small un-bloated images. We enable things if they are needed, not in case they might be needed.

Section "Device"
    Identifier     "nvidia"
    Driver         "nvidia"
    Option         "DynamicTwinView" "False"
    Option         "NoFlip" "false"
    Option         "NoLogo" "true"
    Option         "ConnectToAcpid" "0"
    Option         "ModeValidation" "NoVesaModes, NoXServerModes, NoEdidModes"
    Option         "HWCursor" "false"
    Option         "UseEDID" "true"
EndSection

Section "Monitor"
    Identifier     "Samsung_LN46A850"
    Gamma          1.0 1.0 1.0
    Option         "DPMS"
    Option         "ExactModeTimingsDVI" "true"
    Option         "PreferredMode" "1920x1080_60.00"
    HorizSync      26-76
    VertRefresh    23-61
    Modeline       "1920x1080_60.00" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
    Modeline       "1920x1080_59.94" 148.3515 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
    Modeline       "1920x1080_50.00" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
    Modeline       "1920x1080_29.97" 74.1756 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync  
    Modeline       "1920x1080_25.00" 74.25 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync    
    ModeLine       "1920x1080_24.00" 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
    ModeLine       "1920x1080_23.976" 74.1756 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync
EndSection

Section "Screen"
    Identifier     "screen"
    Device         "nvidia"
    Monitor        "Samsung_LN46A850"
    DefaultDepth    24
    Option         "ColorRange" "Full"
    Option         "ColorSpace" "RGB"
    SubSection     "Display"
        Depth       24
    Modes           "1920x1080_60.00" "1920x1080_59.94" "1920x1080_50.00" "1920x1080_29.97" "1920x1080_25.00" "1920x1080_24.00" "1920x1080_23.976"
    EndSubSection
EndSection

^ This is the xorg.conf I used to use to set specific (more accurate) modelines (actually on an Ultra2 board, but it's the TV that's relevant not the board being used). It's slightly different to yours - have a play.

Another thing to try is the older nvidia driver, run:

wget http://chewitt.libreelec.tv/96-nvidia.rules -O /storage/.config/udev.rules.d/96-nvidia.rules
reboot

^ this will force the 340.xx driver to be used, which might behave differently.

If you know the full URL of the add-on (to download) and know how to fiddle with the contents of the sqlite add-ons DB file (to enable the add-on after rebooting) it's possible. If not it will take 20 seconds once you have access to the GUI.

Your box has a large number of piracy add-ons installed. No further support will be provided until a clean Kodi debug log is provided that shows them removed.

Over time lots of people who were working in the Intel driver team either moved on to other things inside Intel or moved on from Intel. There were some layoffs too. The net result is the Intel driver team are ~10% of their former strength and while the chipsets are fine as "it works on Windows" we see persistent issues with Intel Linux driver quality and performance. Ho hum..

Wrong log. Wrong thread.

"none" means Samba default which is SMB3, so you need to force SMB1

There are no official images for RK hardware at this time. That will change in the mid-term future, but how our currently unwritten code runs on that box needs a crystal ball and some imagination.

Logs are not debug logs so they don't contain anything on the URLs being called.

Sounds like an issue with EDID and modelines. Pastebin a Kodi debug log after clean boot for a starting point.

Some boxes have slow loading network drivers that cause the initial repo update check to fail, which can result in there being "no add-ons in the repo!!!" .. so if it happens again just force refresh the repo and/or add a startup delay to Kodi via LE settings, and all will be fixed.