fdtput -t s /flash/dtb.img /i2c@c1108500/pcf8563@51 status "okay"
echo "aml_i2c" > /storage/.config/modprobe.d/rtc.conf
echo "rtc_pcf8563" >> /storage/.config/modprobe.d/rtc.conf^ run than and reboot and it should be all that's needed to make it work (famous last words). It updates the device tree with the node required and then sets the modules to be loaded on boot. The dtb.img change should persist until something replaces the file (e.g. an OS update).
Also check List of built-in functions - Official Kodi Wiki .. you can start the screensaver (and any other command will stop) .. so maybe a combination of "sed" to change the setting and then "kodi-send" for the start command.
You need to create the profiles.xml file and stash it somewhere in the image, e.g. /usr/config/profiles/profiles.xml, and then you need to modify the Kodi startup script (kodi.sh) to check whether /storage/.kodi/userdata/profiles.xml exists, and if not (because it's first boot) copy it from the /usr/config location before Kodi is started. You can do this within the Kodi package.mk.
Well.. even if you don't know what's there, the module list would mean something to other people.
If you degrade your Win boxes back to SMB1 and use a wildly out of date OE image .. sure it works. If that's all you want .. fine. If you want to use a secure Win setup your boxes need to disable SMB1 (and with that .. browsing them is dead) and use SMB2/3. At this point the old OE image will fail to work because it has no support for SMB2/3. You'll need an LE image which supports SMB2/3 just fine. Get the current Beta.Create a Kodi user/pass on Windows and assign read rights for that user to the shares (and forget that guest access ever existed). If your Win boxes allow SMB2/3 all you now need to do is manually configure the sources in Kodi to use the same kodi user/pass credential.
Or you can keep wildly changing stuff and hoping it works. Or stick to OE (but then future posts should be in the OE forum not here).
I'm just one of the two people who implemented SMB2/3 support in Kodi. I think i'm under-qualified to help further.
"lsmod" will list the active kernel modules
LE settings addon = embedded Samba *server*
Kodi settings = embedded SMB *client*
The current complexity is caused by Microsoft not ourselves, but it's not particularly hard to configure things as long as you stick to a couple of basic principles. The main one is that all connections must be authenticated with a username/password. The second is YOU CANNOT BROWSE from Kodi (on LE) to a Windows server so sources must be configured manually. I find it easier to manually edit /storage/.kodi/userdata/sources.xml over an SSH connection than fiddle with an on-screen keyboard in the Kodi GUI. The format is simple:
<source>
<name>MEDIA</name>
<path pathversion="1">smb://username:password@WINDOWS/MEDIA/</path>
<allowsharing>true</allowsharing>
</source>Edit the user/pass and paths to suit - the format of the file is simple.
If you force Kodi to use insecure SMB1 the browse feature works. If Kodi uses secure defaults (SMB2/3) there is no browsing. OpenELEC "works" because it's old and outdated - the latest version is from May 2017 which pre-dates the SMB2/3 features being added to Kodi (after the WannaCry problems) so it's using SMB1.
The SMB client in LE 8.2 based releases defaults to SMB2 and SMB2 does not support browsing so this will always fail. If your server supports SMB2+ you can configure it manually - use an authenticated connection (use username/password). If it does not support SMB2 your only option is to force Kodi to use SMB1 .. set the SMB client to min and max SMB1. If it's really crap and ancient, you might need to set the legacy security option.
Smart TV's will have a locked boot environment and a SoC chipset that we don't support. You can ask the question another three ways but the answer will still be NO.
The installtointernal scripts in 3.14 kernel images (from wherever you find them) will not work on mainline kernel images because the mainline kernel does not support Amlogic's proprietary (Android) partition labelling scheme, so /dev/system and /dev/boot etc. do not exist and the script fails.
FYI, the Kodi developer who authored raw support is currently on a long vacation so you might not get a quick answer.
BeneDicT there's no specific project development fund for S912 work .. only general project donations.
Where could this bug come from ?
Probably the big fleshy thing that pulled the power cord out of the computing device without shutting it down first? You'll get away with that sometimes or even most of the time, but never all of the time.
LibreELEC 9.0 builds for S905 (semi official)
that script is just trouble though ..
The post has been seen .. not sure if anything has been done yet though. Reboot and have another look.
