Posts by chewitt

LE is a complete OS not an App, so you cannot run it from within Windows. And nano is a Linux text editor; like notepad, but run from the Linux command shell, it's not a GUI app.

It's hard to comment on what's happened, but either the SD cards are old/bad/dying which leads to corruption and issues or perhaps you're powering off the machines without clean shutdown and causing filesystem problems on the cards. Linux is a lot more sensitive to that kind of thing than Windows; it will fail loudly and early whereas Windows sort of blindly continues giving the appearance of normal while secretly trashing your data.

Install LE 9.2.8 (as you need optimised HEVC support). Install inputstream.adaptive from the LE repo. Install the Netflix add-on repo. Install Netflix add-on from the repo. Setup the user/pass and on first play inputstream.adaptive should install the widevine.helper add-on which will download and install the needed Widevine CDM library for Kodi use. This takes a while, but once done you should be able to play something (720p max). That's how it worked last time I did it (some time ago, I don't use Netflix often).

Linux makes things read-only to prevent filesystem damage when it detects corruption or the filesystem in an unclean state. On removable drives this is normally due to not disconnecting/ejecting the drive cleanly. If the filesystem is NTFS or eFAT, reconnect to Windows, use chkdsk and then eject properly. Assuming that resolved the issue, Linux should then mount the drive in RW mode. If the drive is HFS+ (Apple) then you're screwed because Linux doesn't support RW access and will always mount RO, and you'll need to reformat the drive to exFAT to use the drive with LE.

Please give a link to the fixing kernel commit.

If you want to place something in /storage you first need to create a package (or ammend an existing one) to embed the file(s) somewhere in the SYSTEM file and then embed and execute a script (or systemd service which executes a script) at boot time that checks if the file(s) exist on /storage and if not, copies them there. You cannot create files directly on /storage via the buildsystem because that path doesn't (and should not) exist in the SYSTEM or KERNEL files.

NB: There is no direct mapping from /storage/.config to /etc .. we typically configure a package to run from /var/run/something which is symlinked to a location in /etc and then systemd services (which run scripts) copy the content from /storage/.config/something to /var/run/something at boot time to make things appear as if they are mapped. There's lots of prior art for this in the systemd package.

HBO max should depend upon inputstream.adaptive which should depend upon widevine.helper .. which should download and extract the widevine CDM lib file from a ChromeOS file (how these things are obtained) and install it to the required place. The Kodi log shows that you have inputstream.adaptive installed, and the pic shows that the CDM lib is installed. However it gets a 400 error when requesting a license from the HBO servers .. so the process fails.

I'd probably start with reading the Kodi forum thread for HBO max add-on to see if there are transient issues (it happens) or if there's an issue with specific versions of the widevine lib (it also happens from time to time).

Quote from 2Old2Slow

chewitt Do you have an earlier Matrix box version...seems some of my matrix addons don't show up in this Kodi 20 alpha version. Android Kodi 19.3 on my shield works fine.

I haven't build against Matrix for some time (more than 6-months) now so there are no builds stashed anywhere. From what I see in Kodi team chat most add-ons should be Matrix/Nexus compatible by now .. there might be some exceptions.

Names to the pirate IPTV service have been removed and this thread is locked. Any further posts about that service will be binned.

LE packaging makes a downgrade easy (same process as an upgrade, just using an older image) *but* Kodi does not support downgrades (only upgrades) so it's best to stop Kodi, rename the existing /storage/.kodi folder out of the way, then download the 'update' file to the update folder /storage/.update and then reboot. On restart you'll have a clean 9.2.8 install, but now you can stop Kodi, move files over from the LE10 install and then restart Kodi to restore the essentials. You should be able to move shares, thumbnails, add-on settings (but not the add-ons themselves due to Python3/2 changes). DB files depends on how you updated. If you ignored our advice and just updated then Kodi preserved/orphaned the old DB files during update so they won't be current but will exist. If you followed our advice and clean installed as part of the LE10 move there was nothing to preserve and the new DB files aren't backwards compatible (wrong versions). In theory you can export everything in LE10 and reimport to LE9, but (again due to downgrades not being supported) that may or may-not work. You can try it but if there are issue you'll need to just rescrape.

Old IT proverb: There are two types of computer user; those who make proper backups and those who didn't lose all their data yet.

4K@60/59.94 with a high-bitrate audio stream might be pushing the limits I guess (not that I'm knowlegeable on what the limits are). Do you have "certified" HDMI cables between the RPi4 and AVR? .. the total HDMI bandwidth required for this will be above average and cable quality does become a factor at some point.

Do you have the correct number of speakers for Atmos? (5.1.2, 5.1.4, 7.1.2, 7.1.4)

Kodi supports pass-through of Atmos/DD+/TrueHD audio on hardware that supports the respective formats. Not all hardware does.

What happens if you select the 5.1 audio surround stream instead of the TrueHD 7.1 stream?

I have a hunch that the {special} filename is incorrect as normally the filename should match the full path to the mount. However I have no clue how to represent a path with folders that start with or contain periods and underscores. Create a more simple path like /storage/xmltv to mount to, and name the file storage-xmltv.mount. If that works you proved the theory and can hit Google for documentation.

cp /usr/lib/udev/rules.d/40-modeswitch.rules /storage/.config/udev.rules.d/40-modeswitch.rules

^ Copy the existing rules file to the udev.rules.d overlay directory and edit (append/add) another rules section with the device IDs for the chip. If you installed usb_modeswitch from one of our tools add-ons it's normally usable without the other files or just have udev eject the /dev/sr0 device like the existing other devices in the rule flle - which works with most WLAN devices.

ConnMan allows you to set persistent preferences for interface type, e.g. prefer Ethernet over WLAN but not which interface; largely because in Linux the interface identifier is dynamic and determined by probe order. It is also possible to reorder the priority of interfaces (move them once probed). So if the devices consistently probe to the same identifiers you can use systemd.d to run a shell script late in the boot process (after network is up, but before Kodi starts) to detect if /dev/wlan1 is present, and if yes, run a connmanctl command to order wlan1 above wlan0 in the interface list. It's fiddly to create, but do-able and normally reliable once done. You'll find some prior art for the reordering commands in wireguard VPN threads.

I can tell from the original report that Kodi is falling back to CPU decoding; hence the suggestion to try a newer kernel which might have more functionality added (as upstreaming codecs takes time). If the situation didn't improve you won't see magic happen - no codec driver means Kodi will CPU decode and this probably requires a high-end i7 or i9 chip to work. If the HEVC driver exists under Windows and you need to play 4K HEVC media .. use Windows.

Download, Yes. Install and run, No.