# CONFIG_SND_VIA82XX is not set
There is no kernel driver set in the current kernel. I'll ask milhouse if he can add this to his next build so you can test.
Posts by chewitt
-
-
There's already thousands of pages on the internet that explain how to use tar so to eliminate PEBKAC issues it's probably easier to stick with the GUI tools in Kodi. So: Restore the backup. Install the add-ons from the Kodi GUI. Take a new backup. Job done.
-
linux: add PL2303 serial support to Odroid_C2 by chewitt · Pull Request #858 · LibreELEC/LibreELEC.tv · GitHub <= so it should be in v7.90.008 which is pending Kodi v17b4 release.
-
Dora are you using WeTek Play or some other hardware?
-
The OS is booted and Kodi is running so you can SSH in and get log files. Heck you don't even need to log-in, you can access the logfiles samba share and it will create a zip file with everything - although I'd prefer to see the "cat /storage/.kodi/temp/kodi.log | paste" URL as that's easier for me or any other staff member to work with.
btw, I hope you mean 'Add-ons' on the TV and not TVaddons .. because anything to do with that crapware repo is an automatic support refusal.
-
Code
Option "UseDisplayDevice" "DFP-0" Option "ConnectedMonitor" "DFP-0" Option "CustomEDID" "DFP-0:/storage/.config/firmware/edid/edid.bin" Option "UseEDID" "true" Option "IgnoreEDID" "false" those are all nVidia-specific instructions, xorg.conf files are nowhere near as standardised as you're assuming. -
The xorg.conf you are/were using will only work on an nVidia GPU not Intel.
-
vpeter is using the same based version of Kodi that all other LE builds are using which will include that fix, so it may be a different issue?
-
How old is the OE release? How much space do you have on the boot device?
-
Manual update to the current v7.90.007 alpha (as nothing will be fixed in Jarvis now) retest. If the problem remains share the URL for a debug log + mediainfo for a file that doesn't work. If possible upload a 30-60 second except of the file that demonstrates the problem somewhere so we can download and test the file.
-
Can the boot screen/splash screen be changed to customised animated or GIF kind picture?It can be done in milhouse images for Raspberry pi where there are custom patches for the pi bootloader to add the capability. It is not something easily ported over to other bootloaders so is unlikely to become a mainstream feature.
-
Which version of OE are you upgrading from and how large is your audio/video library? .. and if you SSH in to the box (note: password has changed to libreelec) run "cat /storage/.kodi/temp/kodi.log | paste" and share the URL here so we can see the log file. If it's an older OE and the library is large it can take a while to process multiple old databases. If something got stuck (usually due to corruption) the log will show where.
-
Change cables/ports. Turn everything off and on again. There's no issue in the build (else we'd know.. too many thousands of users are running it) so it's something to do with network environment or hardware.
-
drieschel is building .. look around the Amlogic forum area
-
For an Intel based box you need to use LibreELEC-Generic.x86_64-7.0.2.tar
-
Once changes to add $DEVICE support to our build system are merged I will adjust things to Slice/Slice2 are sub-devices of the RPi/RPi2 projects and then PR support to our main git repo. That should make long-term maintenance of Slice things fairly trivial regardless of who does the image building and publishing part.
For community/official status: There's no current plan, but there's a plan to have a chat about plans which might lead to a plan
-
chewitt Is there a wiki for submitting the addons to your repo? I think zap2xml is at the point of being ready for a 1.0 release.No wiki. You can submit a pull request (PR) to add the add-on to our main git repo, or if you'd prefer to manage your own repo, i.e. rates of change are still higher and you want direct control over changes and publishing, you can PR your repo installer to our repo. If you want to go the 'own repo' route we'd be happy to provide some edit4ever.libreelec.tv webspace to serve files from, or you can abuse free github hosting. Whatever works for you and users works for us
-
It's good to hear all is okay with the packaging; thanks for testing that. The alpha splash is used in all LE alpha builds. It will change again in beta and then revert to the "clean" one for final release. I still need to adapt Gordon's lirc enable/disable function into the settings app. Subject to me finding the time it will probably appear in the next alpha build.