Posts by chewitt

VFD displays are simple serial devices and you can literally do "echo 'my text' > /dev/serial-device" to write content to the display in some cases. VGA output will need an app that runs under X11 to output to a second display device, which is quite a bit more complicated.

It's not impossible, but I'm not aware of any existing tools/plugins in the LE ecosystem. Our mid-term technical direction will also see us move from X11 to GBM/V4L2 running directly on the framebuffer so even if you get something working under X11 this will have a short shelf-life in LE.

IMHO dual-display would be easiest to achieve under Windows or a desktop distribution, perhaps with a web-based touch GUI.

leandrotsampa It looks like you are hacking a vendor-proprietary rendering system into Kodi similar to Amcodec, iMX6, etc. which have now been exorcised from the codebase. If HiSilicon have V4L2 support, this is the technical direction to invest time into, as your current approach will not be accepted upstream.

cp /etc/connman/main.conf /storage/.config/connman_main.conf

^ edit to allow the list of "TetheringTechnologies" to include "ethernet,wifi" instead of just wifi.

That's up to the Kodi developers. K19 alpha1 release is due soon, allegedly.

Yes, more coffee required at that time of the morning

Quote from aelray

Sorry I couldn't edit the extlinux.conf as my system is on eMMC and I do not have a SD card ready, but I will try to get one

mount -o remount,rw /flash

nano /flash/extlinux/extlinux.conf <= make changes

mount -o remount,ro /flash

reboot

^ there's no need to reboot from an SD card to edit extlinux.conf

Kodi supports output to a single screen - period. It's possble to mirror content between two connected screens, but that's all, and getting that to work when the two displays are radically different sizes will require crippling the HDMI output to the resolution of the VGA output. Add "using an AMD GPU" into the mix and even getting dual-output might be a challenge.

That's probably not the answer you were looking for .. but that's the answer

Yes, the plan is to support SM1 (S905X3) devices in LE10 (K19).

The only way to stop that behaviour is modifying packages/mediacenter/kodi/tmpfiles.d/kodi-userdirs.conf in the build-system and then building a custom image with the modification. In our standardd image they will always be recreated on boot (by systemd not samba).

You can probably hack a delete via /storage/.config/autostart.sh but since this runs at the start of userspace boot you'll need to background the task for aa few seconds, e.g.

(
sleep 10
rm -rf /storage/tvshows
rm -rf /storage/videos
rm -rf /storage/music
)&

It will depend on how the touchscreen is connected to the motherboard (HDMI, USB, ???) and whether this requires drivers?

We are not a Synology NAS forum so how you configure Hyperbackup is not something we have experience with, but it's likely you need to configure the rsync command to use; in which case you will need to know where (after installing the network tools add-on) the binary is located. If you insist on looking in /storage/.kodi/userdata/addon_data/ you will not find it. If you look in /storage/.kodi/addons/virtual.network-tools/bin/rsync (as clearly show in post #2 and hinted again in post #4) you will find it. The rest is up to you.

Is your router configured for US or DE, or another country? .. the country setting should be matched to the router.

Addon binary code will be under /storage/.kodi/addons/name.of.addon as indicated clearly in the example that lrusak provided. I'm not sure how much clearer we can make it.

If /storage/.config/samba.conf exists it is used exclusively for the samba server configuration. The sample file in /storage/.config is recreated on each boot from the embedded file so it always remains current for the version of samba we're shipping. If you base you config on the sample file, you'll get the default config plus your addiions (or removals).

The method still works and the command line instructions above are still valid. Suggest you read Accessing LibreELEC [LibreELEC.wiki] first.

Your box is booting some Android kernel .. it is not booting LE.

You can create a custom conf in /storage/.config but use an include to add content from the embedded file.

What kernel is Debian using? .. we're on mainline 5.4/5.5 now and I suspect they're still using the RK 4.4 kernel.