Posts by chewitt

Kodi debug log and "dmesg" log

Old laptops are not target hardware so there is no PCMCIA support in the OS, which narrows your choices. On the USB Ethernet front, it's always a bit of a gamble as it's never possible to tell which chipset is used from the box/packaging, but in practice there are only 2-3 usb ethernet chipsets in use and the drivers for those are included.

1.5GB should be fine

If you can understand and isolate where the issue is:

a) OS things should be resolvable through a software update. Eminent (or their maintainer) can choose to fix anything they like as this is under their direct control and they can release their software as required. That said, in recent times they have been loosely tracking our releases, and 8.2.2 is the last release we intend to make for Krypton so I wouldn't expect miracles.

b) Kodi issues will not be resolvable in the current (Krypton) codebase. All fixes in the last ~6 months have gone into the Leia codebase and this will require Eminent to create/ship an image based on Leia in the future.

Make sense?

GDPR-1 I asked spiff and he has no plan to submit vfs.sacd to Kodi until there's been some decent field testing .. so there's a chicken vs. egg situation there

To adhere the letter of the GPL license you must ship an offer to provide sources on request. The definition of 'sources' includes everything that goes into the shipped software, i.e. original LE code and the sources for all packages used in the image. If we submit a formal request for sources, we should be able to reproduce the software in its entirety with what you provide.

The GNU GPL was written in an era when sources were distributed primarily on CD. In the modern world where an LE image can be downloaded in seconds the Linux community norm is for sources to be provided online and without request, and ideally in a way that allows modified sources to be easily compared against the original so the differences can be isolated and understood.

The GPLv2 terms of our license apply to *everyone* who publishes an LE image. In practice we are not going to raise concerns over the niche-use and small audience images that appear in these forums. However, commercial entities must be compliant.

Tanix have shipped software with no offer of or provision of sources, so Tanix are violating our GPLv2 license. The normal practice in this situation is to request the offending party to cease distribution of software whlie the violation is investigated and resolved.

Publishing changes would be a good first step towards compliance. It doesn't take much effort for an experienced Engineer to create a GitHub account, fork our repo (so changes are in a child repo that shows inheritance from upstream) and then push changes back.

If you didn't restart since installing, that may have been the issue.

Commits · Eminent-Online/OpenELEC.tv · GitHub shows no updates since Oct so I pinged the historic maintainer of their images. Their repo is not 'forked' from ours on GitHub so you cannot compare code across forks easily to see what changes were made.

SSH in and run:

connmanctl

agent on

scan wifi

services

connect wpa_blah_blah_psk

Enter the password when prompted. If this works (using connman's own dbus agent) the issue is in LE settings code. If it barfs here, the issue is somewhere else.

UTC time is set using NTP over the network. Display time is then offset from UTC according to whatever timezone you set in Kodi.

You already have SSH access. You have a console.

Time for a PSU with a higher current rating.

pastebin a Kodi debug log

"systemctl restart kodi" is much nicer than kill commands

Our long term technical direction will be to use the in-kernel framework and we are actively collaborating with Hans Verkuil who maintains that part of the Linux kernel. At the moment the kernel parts hook into the libCEC support within Kodi, but at some point code needs to be reworked to drop that dependency. I'm not directly involved or sure whether this will happen in v18 as GBM/DRM and V4L2 graphics support has a higher priority, but it's a firm item on our long-range to-do list.

Connect via Ethernet (temporarily) and run:

connmanctl

agent on

scan wifi

services

connect <name of service>

Copy/paste the password string when required.

WPS could technically be supported, but there is currently no support in our settings add-on for it, and that's unlikely to change.

"journalctl -b 0" <= current boot

"journalctl -b 1" <= previous boot

The journal has limited buffer though, so logs often rotate before anything useful is captured. Add "debug" to kernel boot params to make things more persistent.

Make sure you have an HDMI cable that supports 2.0 specs.