Posts by chewitt

It should be fine in Leia releases because we're still using the same Xorg based graphics stack and nvidia drivers. Right now it's unclear whether we will have nvidia support post-Leia but that's a longer story.. and nothing definite yet.

Current estimates on availability of a mainline kernel do not align with Kodi Leia schedules so Leia will need to use amcodec and the existing 3.10 and 3.14 kernels. That breathes a stay of execution on MX chipsets but it makes the decision to expend effort on generic kernels harder. There are benefits to unifying some of the community efforts further; IMHO too many community builders are "developing in the release branch" with a high rate of release iteration so providing a project for things to focus on will stabilise things. However, all work on the 3.10 and 3.14 kernels is ultimately "lipstick on a pig" as the second we have a viable mainline kernel we will drop support for anything that cannot run it. Right now S805 era boards will probably survive (no guarantee, but they have a lot of IP in common with S905 and newer) while MX based devices will bite the dust.

So it's possible, but much is in the hands of community builders agreeing to align their efforts. So far no PR's have been received on GitHub.

en:users:drivers:brcm80211 [Linux Wireless] <= states there are no Linux drivers for the BCM43231 chipset so I am interested to know which driver and version is reported in Ubuntu?

I'm asking about which LE image, e.g. Raspberry Pi or Generic? .. not the Apple stuff

It's worth experimenting with a current milhouse release. This bumps major components that impact performance/behaviour of Intel GPUs and also provides a codebase that is still in development; i.e. if there's a bug it can be triaged and fixed, whereas Krypton has not been touched for months and only receives occasional (simple) backports from Leia now.

if the 340.xx driver works, use it, problem solved

LE compiles OpenVPN for client use so it cannot be used as a server. I can also guarantee that PPTV will not be making a comeback.

The alsa configuration in Amlogic kernels is a hack, so don't expect things to work correctly. Things should improve once we move up to a mainline kernel from the 3.14 Android based crapfest we are currently stuck with. There is no schedule for that yet.. before you ask.

the options method is correct for persistence, but if there is no wireless regdom in the kernel it won't have any effect

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.