Everything is possible with appropriate time, effort and skills. It's not a simple task though. Supporting a new device platform requires a lot more than rebuilding a couple of drivers.
Posts by chewitt
-
-
Just read an online howto/guide for the "tar" command.
-
also to write on nand-Flash on Amlogic Devices is not in Wiki...
Good. It reduces the opportunity for people to make the LE install process even more complicated.
-
milhouse images exist today with pre-alpha Leia code; current ETA for first alpha releases from Kodi would be around year end.
-
You can also upload/share a sample file somewhere
-
If it's no WSL .. just clean packages and remove ccache and try again. I build official releases on 16.04.3 and there are no known issues.
-
Not possible - You need to reboot to change between LE and Lakka. If this is an x86_64 box you can use a milhouse Leia build and use the Game functions there which are different, but also based on Retroplayer.
-
LE has no issue with GPT partitions and although it's not impossible we run a fairly current version of parted so it's unlikely the issue is there. I've no idea whether F2FS is fully supported though. If the kernel is trying to mount partitions there is clearly some config in the kernel but we don't use it ourselves (we use EXT4) so you might want to check and see if everything required is set.
Go back and test in Ubuntu (on a LiveUSB stick) before attempting anything else.
-
It requires a different graphics stack to our current one for nVidia and probably requires a different EFI bios, e.g. MrChromebox.tech (which does not list that Acer device as supported). I don't want to sound negative, but from past experience this is one of those situations where "those who can, get on with it" and "those who can't, ask us how to do it" .. i.e. if you don't already understand our build-system and what needs to be done in detail the chances of success are low, because there are no howto guides or scripts or instructions for this. Sorry..
-
Code
mv /storage/.kodi/userdata/advancedsettings.xml /storage/.kodi/userdata/advancedsettings.old wget http://chewitt.libreelec.tv/advancedsettings.xml -O /storage/.kodi/userdata/advancedsettings.xml systemctl restart kodi < wait until it hangs on restart > cat /storage/.kodi/temp/kodi.log | paste^ then share the URL generated
-
The technical answer is "depends on what combination of patches are on the Win10 box" .. hence the release notes cannot be explicit, but in the long-term MS is pushing the removal of guest and unauthenticated access so the sooner you bite the bullet and move to authenticated shares, the sooner you (probably) don't have to reconfigure things again
-
Any ideas ?
Sharing logs from the box would be a good start. Ideally a Kodi debug log (set logging from advancedsettings.xml)
-
-
Amlogic is top-dog at the moment due to a complete absence of competition but Amlogic devices are ~7% of our userbase and 80% of the support issues. Installation complexity is the root cause of a large percentage, but the prehistoric dog of a Linux kernel we are currently stuck with drives the remainder. RK development is progressing nicely and joint development is building a solid and sustainable foundation for Kodi based on Atomic DRM and V4L2 decoding. In comparison Amlogic are *miles* behind and although there is some work, the visible activity level is low. The long-term plan is to drop amcodec support in Kodi, so they either need to pick up pace and show progress or there is a significant risk they are the only SoC/GPU vendor holding things back. That would mean we get to make a decision on whether to throw Amlogic support under a bus and move everything else forwards, or continue with something that "works" but has many unresolved (and unresolvable) issues that drive most of our support traffic. It's not exclusively my decision, but I'd currently describe it as a simple decision.
-
No idea, but we're not going to debug Linux mint issues here. It's really not our forté.
-
It would be more appropriate to ask for Tvheadend (on Windows) support in the Tvh forum. People here have experience with our own Tvheadend server (on Linux) which is not comparable. In future please also pay more attention to the formatting of your post - it's basically unreadable.
-
What version of Ubuntu?
-
So it worked?
I'm not too interested in adding the txt files to our main distro as the driver-named file is not enough and I'd be concerned that the brcmfmac-sdio named files will conflict with other brcmfmac devices. I'd ask you to test a current milhouse release as well, as those will have newer kernels with newer versions of the brcmfmac driver. Plan C .. you need to learn how to self-compile an image to repeat the process I did (which is trivial).
