Posts by chewitt

It sounds like the repo wasn't available (or refreshed) before; now that's fixed there is content to get-more from, so it shows.

I tweaked the thread title.

areq1987 You need to set the full name of the filename.dtb to use in extlinux/extlinux.conf. If you rename files to dtb.img boot does not work. This is probably why you end up in the Android recovery app.

S905L has a reduced spec Mali 450 MP2 GPU instead of the normal Mali 450 MP3 GPU found in S905D/W/X/Y devices and no VP9 codec support. If you use the wrong device tree the kernel locks-up when the lima driver is loaded. Otherwise there are no major differences with S905X devices. There is initial support for S905L in the AMLGX image.

NB: I have 0% interest in Android ROM flashing issues. No support for that in this forum.

ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="0b95", ATTR{idProduct}=="1790", ATTR{bConfigurationValue}!="1", ATTR{bConfigurationValue}="1"

Manually adding that ^ to /storage/.config/udev.rules.d/99-asix.rules results in the driver probing:

RPi5:~ # lsusb  -t
/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/2p, 480M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/2p, 480M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M
    |__ Port 001: Dev 002, If 0, Class=Vendor Specific Class, Driver=ax88179_178a, 5000M

but "ethtool eth1" initially shows the device with no link and ifconfig shows no interface. If you wait long enough that changes and everything comes up and starts working, but it takes a long time; so far I've no idea as between boot (and checking) I had to go do something else for some hours, and on return (and checking again) it's come up. I'll need to see if I can script the check to see if it's a consistent or random time before the NIC is available, and then I'll report findings to the kernel maintainers for input. Something isn't right, but I'm not sure what yet, it's most odd.

NB: The udev rule should work on any LE11/LE12 image; the one in my test share is updated but there are no changes/patches for the NICs included (as none needed).

Quote from bylderup

Any News?

Clocks and Pinctrl are now merged but that process took forever. They're starting to add other bits now, but I wouldn't expect LE images anytime soon.

I only have the Estuary skin installed, so when I navigate to Settings > Interface > Skin and select the current skin (Estuary) the next screen shows the list of installed skins and offers "Get More.." to find more. If you have all the available skins installed (the screen pic looks like there are lots/all installed) there are no additional skins to add so the button is not shown. Make sense?

Quote from TopQuark

Do not use the LE SD Creator

Why?

Skins evolve and change over time

Have a read here: https://kodi.wiki/view/Video_library

If all you want to do is transfer files from laptop to HTPC, the Samba (SMB) server is enabled by default so you can browse to the box and copy/paste files. It's not always the fastest method, but usually the easiest.

Complex cryptography requires compute effort. It's not for free.

The main thing that changed is Kodi, so you need to look at the commits/changes merged upstream between the Kodi versions included with the LE 11.0.4 and 11.0.6 releases.

Run "journalct | paste" and share the URL once the connection works so we can see the system log (and what went wrong, maybe)

Wrong. You need to edit the kernel defconfig for the correct Rockchip device. Generic is only used with x86_64 hardware.

Windows updates might update the Windows Defender definitions, but those aren't active once you install an alternative AV app (as only one can be active per. Windows security rules). So it's more likely to be a heuristics update on the AV app.

Quote from JohnWayne111

https://github.com/xbmc/xbmc/releases/tag/20.4-Nexus

There's nothing in Kodi 20.4 for Linux/LE users except the controller addon keyboard and translation changes which will be picked-up and built (and pushed to the add-on repo) separately. Everything else is for Android or Windows.

No debug log = No problem to investigate