Posts by chewitt

At one point we were looking to absorb the capabilities of the OE era config add-on, but since RPi3 came along with enough CPU to decode MPEG2 in software without the license, the need for it among our userbase greatly reduced. There is also a strong correlation between providing a tool that encourages people to overclock their device and the number of people reporting random issues caused by overclocking.

There activity on supporting RK chips, but efforts are focussed on their current generation devices like RK3328 and there is low appetite for trying to accommodate their older ones. Things are also dependent on the Kodi Leia codebase so there's nothing that we'll show in public for a while yet.

Quote

[ 3.143965] sd 2:0:0:0: [sdb] 7761920 512-byte logical blocks: (3.97 GB/3.70 GiB)

[ 3.144376] sd 2:0:0:0: [sdb] Write Protect is off

[ 3.144382] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00

[ 3.144788] sd 2:0:0:0: [sdb] No Caching mode page found

[ 3.144792] sd 2:0:0:0: [sdb] Assuming drive cache: write through

[ 3.157644] sdb: sdb1 sdb2

[ 3.159528] sd 2:0:0:0: [sdb] Attached SCSI removable disk

[ 5.092941] EXT4-fs (sdb2): couldn't mount as ext3 due to feature incompatibilities

[ 5.094643] EXT4-fs (sdb2): couldn't mount as ext2 due to feature incompatibilities

[ 6.661835] EXT4-fs (sdb2): recovery complete

[ 6.666472] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null)

[ 22.312011] ### sdb2 is removable. suspend/resume may not work

[ 22.312794] ### sdb1 is removable. suspend/resume may not work

Display More

^ looks like a 4GB card device being detected.

The error is clear in the first two images. The syslinux.conf or extlinux.conf is configured for boot=LABEL=System and disk=LABEL=Storage and those partition labels do not exist on the boot device. It should be using boot=UUID=blah something like below:

DEFAULT virtual
TIMEOUT 50
PROMPT 0

LABEL virtual boot=UUID=2605-0052 disk=UUID=c1d54db6-83d0-4a9e-b662-e7099f9edbf0 quiet tty vga=curren

So i'm wondering if another bootloader and traces of an older OE install are present on the 1TB /dev/sda device? - because using disk labels in the boot config is how things used to be done. LE has only ever used the UUID method.

thread moved to the Amlogic support area

No log .. no problem

False. Our default disk layout for the Generic image is two partitions in a GPT partition scheme. If you want to install to the disk manually boot the installer in live mode or use an Ubuntu LiveUSB to create a GPT disk, first partition is 512MB and second is remaining space. Make both ext4 and install syslinux to the first partition. Now copy the KERNEL, SYSTEM and extlinux.conf to the first partition. That's all the installer does.

Not possible as-is or out of the box. It would need someone to repackage the code as a binary add-on. That means it's possible, but unless you write the code or find a willing volunteer it's unlikely to happen.

You probably need to tweak the key-repeat time settings for the remote control. We set some sensible defaults but some devices need a little adjustment. As there are multiple device-dependent methods for doing this you'll need to explain what you're using?

It's not an add-on that we provide or create so our ability to diagnose/support the issue is limited. You're better off posting the question/issue to the Kodi forum support thread for the add-on - where its author will see the post.

In what previous release were they working?

[    1.297421] scsi 0:0:0:0: CD-ROM  PIONEER  BD-RW  BDR-TD05 2.00 PQ: 0 ANSI: 5
[    1.338136] sr 0:0:0:0: [sr0] scsi3-mmc drive: 62x/62x writer dvd-ram cd/rw xa/form2 cdda tray
[    1.338140] cdrom: Uniform CD-ROM driver Revision: 3.20
[    1.338657] sr 0:0:0:0: Attached scsi CD-ROM sr0
[    1.338870] sr 0:0:0:0: Attached scsi generic sg0 type 5

^ that looks like a Blue-Ray drive in /dev/sr0 (the normal place for one under Linux).

NB: Kodi does not show the 'disc' menu unless there is a readable disc inserted, and if you are inserting encrypted BR media you will need to add a KEYDB.cfg file to /storage/.cache/aacs/ else the media remains encrypted and unreadable. It is not possible to legally play your legally owned BR media under Linux as there are no legally licensed player apps (they only exist on Windows/macOS). We cannot provide the KEYDB file and we will stop short of providing URLs to them to avoid violating laws, so you will need to Google and source the file and violate them yourself

Do you have that code in GitHub anywhere?

Kodi versions are not cumulative, i.e. stuff gets removed as well as added, so Krypton != Jarvis.

LE 8.2 will go into private team testing in the next week or so with the aim of a public beta towards end of July (after some team people are back from vacations) and all being well, release in August.

Kodi "builds" and "wizards" exists to bulk-install pirate streaming add-ons. We follow the same general principles as the Kodi forum and refuse all support regardless of issue to any user with pirate streaming add-ons installed. You now need to show us a Kodi debug log to prove your system is free of pirate add-on crapware before support will continue. Thanks.

The Piracy Box Sellers and Youtube Promoters Are Killing Kodi | Kodi | Open Source Home Theater Software

Official:Forum rules/Banned add-ons - Official Kodi Wiki

Kodi has a general bug where it returns to the first item in the list after completing a video library item. The bug is in Krypton which is why an older OE release with Jarvis/Helix etc. didn't have the problem.

The connection manager (connman) service manages the functionality of the hotspot and aside from the options I mentioned above all behaviour is internal and hard-coded. There is no config file hidden somewhere that you can tweak.

As a broad rule NUC's are plentiful in number so issues are seen early in testing so we're not aware of any major issues. Current OE and LE releases should be using the same kernel series and driver/firmwares so will be broadly the same. Older OE and current LE will have larger differences. I'd start by making sure all have the latest BIOS/firmware available as that's what the newer drivers etc. are developed against. Then if that didn't cure anything run "dmesg | paste" and share URLs so we can see boot processes and look for error messages.