It's nVidia's responsibility to support Linux standards; not our responsibility to re-engineer our entire distro to support nVidia.
Posts by chewitt
-
-
Create a script that checks at 1 second intervals for the drive being mounted or until a suitably large timeout value is reached, and then create a systemd service required by the Kodi service to run the script. The combination should see Kodi 'delayed' until the drive has mounted.
-
How do I tell Kodi to scan media files to MiniDLNA Library instead?
You don't (and can't) because MiniDLNA has nothing to do with Kodi.
-
Not possible. Non-binary Python components can be packaged into an addon by the addon author. Binary components need to be compiled and embedded into the OS at build time. There are deliberately no packages managers in LE.
-
Kodi is one of 380+ code components that are combined to make a LibreELEC image. Kodi is in Beta. LE is still working through a long list of items that need to be nailed down before we move the collective whole to a Beta state.
-
GBM/V4L2 is all about laying the technical groundwork for the future of Kodi on Linux. Kodi today is not really designed for the 4K media that is slowly becoming mainstream, and it's a massive technical effort (and reinvention of the wheel) to support new hardware. It's unlikely that these changes will deliver significant tangible benefits for the devices of today (particularly with Pi hardware which already has very heavily optimised software). You'll see the benefit in future devices; because a) they will be possible, and b) you'll have a wider choice of devices that are more 'open' and better supported than before.
-
Hey, can you add terrarium TV apk in Libreelec? If so, can you tell me please?
Thank you
No. Go read the forum rules, then take your filthy pirating habits someplace else.
-
At the moment devices that need to do an aarch64 > arm change like WeTek Hub/Play2 and Odroid C2 aren't showing a manual update option because the settings addon filters the list of available options according to the current device/arch. An experiment needs to be done duplicating and renaming the arm image so it has an aarch64 filename (e.g. LibreELEC-Odroid_C2.arch64-8.90.004.tar) then rebuilding the JSON data file. The update process isn't sophisticated enough to detect that the file is a different arch so it will just download/unpack/reboot/update as normal and you should get the same result.
NB: I'd go test this myself but I'm currently on vacation and can't .. but one of the other staff should be able to check the theory.
-
Thanks, that's good to know. I'm not due much credit though .. it's all working nicely due it being an RPi in disguise.
CvH if you need a tester for the 005 alpha while I'm on vacation!
-
NB: Current milhouse 'Generic' releases will have that fix included if you want to test something.
-
input: LibInputTouch: Switch to get_seat_slot() to fix single touch device input by superna9999 · Pull Request #14400 · xbmc/xbmc · GitHub might be the same issue you're seeing with the touchscreen crash. If yes it will be included in the next Alpha release which is being brewed. No idea about the reversed axis .. or how to configure libinput things (sorry).
-
Kodi 18 only just reached beta, so it will be a while before all the skins catch up. Most skin developers wait until beta releases start before they do any real work to support the new version; before then you're chasing a moving target.
-
You have a large number of banned piracy addons/repos installed so I'm not surprised that you have reboot issues (as crap addons are the most likely cause). No further support will be provided until you provide a debug logfile that shows a clean system.
-
"journalctl -b 0 --no-pager | paste" after a clean boot and share the URL here
-
No log = no problem
-
I did but those are all Img files, I need a Tar file to update as I'm away right now. So i thought Millhouses's would
work ??
LE supports update from .img and .img.gz as well as .tar files.
-
Read the Alpha blog post(s) on the front of our website for download URLs
-
It's tested in vmware Fusion, Workstation and ESXi, e.g. the 'real' vmware apps. Player is not a fully featured vmware app and nobody on staff uses it so I'd make an educated guess that's where the issue lies. To be crystal clear.. we create the OVA for dev/test work only. If it happens to work for anything more that's nice but we don't provide any end-user support for it.
