They are not Kodi addons, they are packages integrated into the image.
Posts by escalade
-
-
Not sure what went wrong there, as I didn't make any changes to the driver other than adding the 4.11 patch. /var/lib is supposed to be populated by /usr/lib/xorg/xorg-configure, you can look at the script to see what went wrong. From the build directory, it looks like the driver is in place:
Code
Display Moremodinfo build.LibreELEC-Generic.x86_64-8.0-devel/image/system/usr/lib/nvidia/nvidia.ko filename: /root/LibreELEC.tv/build.LibreELEC-Generic.x86_64-8.0-devel/image/system/usr/lib/nvidia/nvidia.ko alias: char-major-195-* version: 381.09 supported: external license: NVIDIA srcversion: 4E2FA9BF651D57316902AE7 alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00* alias: pci:v000010DEd*sv*sd*bc03sc02i00* alias: pci:v000010DEd*sv*sd*bc03sc00i00* depends: vermagic: 4.11.0 SMP mod_unload parm: NVreg_Mobile:int parm: NVreg_ResmanDebugLevel:int parm: NVreg_RmLogonRC:int parm: NVreg_ModifyDeviceFiles:int parm: NVreg_DeviceFileUID:int parm: NVreg_DeviceFileGID:int parm: NVreg_DeviceFileMode:int parm: NVreg_UpdateMemoryTypes:int parm: NVreg_InitializeSystemMemoryAllocations:int parm: NVreg_UsePageAttributeTable:int parm: NVreg_MapRegistersEarly:int parm: NVreg_RegisterForACPIEvents:int parm: NVreg_CheckPCIConfigSpace:int parm: NVreg_EnablePCIeGen3:int parm: NVreg_EnableMSI:int parm: NVreg_TCEBypassMode:int parm: NVreg_UseThreadedInterrupts:int parm: NVreg_MemoryPoolSize:int parm: NVreg_RegistryDwords:charp parm: NVreg_RegistryDwordsPerDevice:charp parm: NVreg_RmMsg:charp parm: NVreg_AssignGpus:charp -
-
Ok, I'll have a look thanks
New build 20170506, updated kernel to 4.11.
-
I do have CONFIG_AIO in my builds now, but didn't before. Where did you read this, I can't seem to find anything relating it to PCSX2?
-
Maybe. But there were multiple cases in the past where this didn't work as plan :s Better build as user and avoid one possible problem.Not maybe, I build as root every day
But sure, a borked package could write to /usr for example messing up your system. No problem for me as I do it in a container. Most people should definitely build as a user.
-
As long as you know what you're doing, there's no problem building as root. From the error above, it looks like docker wasn't unpacked to the expected directory of "docker-1.13.1", you could verify that by doing a "tar ztvf docker-1.13.1.tar.gz". Addons should be built with scripts/create_addon, correct, but that will build the addon first anyways.
-
New build 20170503:
Code
Display Moregcc: update to 7.1.0 parallel-n64-libretro: update to 571a477 and disable vulkan support f or now eventlircd: compile without -Werror kodi: update to 72cef60 elfutils: update to 0.168 nss: update to 3.30.2 and compile without -Werror mysql: update to 5.7.18 and compile with -std=gnu++98 pulseaudio: compile with -fopenmp linux: update to 4.10.13 retroarch: update to 8f25897 retroarch-joypad-autoconfig: update to d907d13 libretro-database: update to a9b42ef vice: update to 3.1 dolphin: update to e9ad0ec genesis-plus-gx-libretro: update to 365a28c beetle-saturn-libretro: update to 3f1661b beetle-psx-libretro: update to c481da0 vulkan-loader: update to 1.0.46.0 mesa: update to 72e52fa createlog: bring sanity to kodi log order busybox: enabling CONFIG_FEATURE_USERNAME_COMPLETION in busybox-targe t.conf fixes tilde (~) expand as described https://forum.libreelec.tv /thread-7874-post-47261.html timezone-data: update to 2017b kodi: remove zero-byte database files at startup connman: fix ip forwarding bug re-add patch for AE minimal sample rate misc-firmware: change repo and update to 0ed3d22 iwlwifi: udpate to ba301aa settings: bump to 0.8.11Dolphin issue should be fixed now.
-
Try my extended build in the general section, it's got an updated driver stack no flickering for me on haswell.
-
My extended build has an updated driver stack.
-
You could set up whatever cloud-solution you like through Docker which is available as an addon.
-
LE uses systemd, the equivalent would be "systemctl status sshd", see "systemctl --help" for more.
-
The technical answer would be that the cross compiler is trying to link against /usr/lib/libpthread.so which won't work, as the host libraries are for x86_64 and you are building for ARM. As mentioned, this doesn't happen on other distributions. One could argue that the toolchain should be able to handle this, but I think to find the root cause here you would need to be an expert in autoconf, a lot of time and it might involve black magic. Perhaps the linker could be patched to work around it.
-
Just get a wireless keyboard. Although kodi is designed to be used by a remote, other apps are not. Or get a ds4 which is configured and tested.
Sure let me know which driver supports it.
-
Learn how diff/patch works, make changes manually and update patch accordingly.
-
Sorry, I don't have one.
-
20170410:
Code- added back sabnzbd at version 2.0.0 and with multicore enabled par2 - updated llvm to 4.0.0 - updated xf86-video-amdgpu to 1.3.0 -
You would need to fix the patch, or wait for the LE team to update it. Why do you want to upgrade ffmpeg?