It should work fine in LE as well. The issue is as mentioned with the way LE autodetects nvidia/nvidia-legacy cards.
Posts by escalade
-
-
NFS works fine on LE8 both through Kodi and through mounting from command line (kernel).
The "RPC: Unknown host" is normally indicative of rpcbind not running on the remote host, but on LE this is actually an issue with the iana-etc package. Here's why:
LibreELEC.tv/package.mk at libreelec-8.0 · LibreELEC/LibreELEC.tv · GitHub
For some reason back during OE development someone thought it a good idea to change sunrpc to rpcbind, which breaks tools like rpcinfo and showmount.
Mounting should work though.
-
That's weird, it should work in my build without the autostart trick. Your pci id matches the one I've added: xf86-video-nvidia: add nvidia gt1030 pci id · escalade/LibreELEC.tv@94e2c5d · GitHub
Anything in the system log?
-
I assume you entered the commands without the "#" yes?
-
RPi doesn't need asound.conf. What you do need is dtparam=audio=on in /flash/cmdline.txt for ALSA to work at all.
-
-
The original logo is in the initial ramdisk embedded in the kernel.
-
I wouldn't know, I don't have an nvidia card
-
I've got 381.22 in my extended build:
LE8 "Extended" community build (Generic/RPi)
But since there's no 1030 pci id's in the supported chips doc, LE will not autodetect it and you'll have to force the use of the nvidia driver.
-
My extended build uses openssl as well if you want to test:
-
Yes. There's no need for both, even if there was a need there is no space for both especially in this build.
-
I thought you said Plex Media Player. The server part is included already, see first page.
-
Probably not, sorry. There's already Plex · GitHub and I can't see the need for running both at the same time.
-
Those logs were before forcing the driver to legacy, correct? X.org logs when using the legacy driver would be of interest. I also recommend you create your own thread (although I'm not sure what kind of support you can expect). Even though my build defers from LE8 at this point (regarding driver stack and kernel), the same changes are coming in LE9. You could try a Milhouse build to confirm that. Basically, you're on your own fixing this, as nobody really cares about 8 year old proprietary GPU's. Not even nvidia. There's already 3 separate patches required to get the legacy driver compiled on 4.11. Once 4.12 is out, I'm not sure it can be compiled anymore.
A raspberry pi starter kit is what, $50-$60? There's cheap cherry trail and apollo lake Intel hardware as well that'll blow the socks of your ION setup and work great.
-
If assignment is the issue, you can use the autostart trick posted earlier to force the driver. Nobody is going to guess your issue, your answer is in the logs.
-
Indeed, it doesn't work. I've found the issue to be link time optimization and disabled it. New builds are on the way.
EDIT: New builds have been uploaded. Kernel NFS, updated ntfs-3g drivers and fixed genesis-plus-gx-libretro are what's changed.
-
Looks to me like you've downloaded a mupen64plus core with the core downloader. Mine is linked with libpng16:
Code# ldd /usr/lib/libretro/mupen64plus_libretro.so /tmp/cores/mupen64plus_libretro.so | grep png libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f5dba64c000) libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007fa6a695c000)
New build 20170530 uploaded. I've replaced unfs3 with kernel NFS (supports both NFS3 and NFS4), which should be much faster and more compatible. Good news for anyone sharing media from their LE boxes
To enable:
-
I don't keep archives but perhaps someone has it. I'm guessing it was one of the builds I made with the older legacy drivers. Now I use kernel 4.11 and I don't think they even compile. In short, your cards could be made to work but it's a hassle. If your card isn't supported by 340.xx then you're out of luck unless you want to build yourself.