Posts by chewitt

Quote from rdorsch

Interesting, do I get that right that there are two drivers in staging for this USB adapter? A working one from Realtek and a non-working one from Jes Sorensen?

Not correct. Debian is building with the older vendor driver, the staging driver is not enabled in their kernel. LE is building without the vendor driver, and with the staging driver enabled. However, staging = experimental drivers that are still in actively development and/or not feature complete enough to exit staging and be included in the main kernel tree. So the staging driver could be 95% complete or .. 55% with lots still to work on (and I have no idea which).

I'd expect Debian to have a policy of only enabling finished drivers (makes sense for a large distro) and you wouldn't enable both as that will cause conflicts. LE is happy to enable the staging driver(s) as we aren't including the vendor ones (on principle; they break often) so there is no change of conflict .. and if it happens to work that's great.

Not yet, I've been tinkering with u-boot 2023.04 and 6.2 kernel on the LE11 codebase. Once I push the next updates to master official nightlies should be created and then I'll switch test/dev work to LE12.

Kodi add-ons are "third-party" from LE perspective (not part of our build-system). As add-ons iterate frequently I wouldn't attempt to bundle them into an image as they'll be out of date within a month. It's easier to script-configure things post-install.

This is modinfo from the Linux 6.2 staging driver: http://ix.io/4sGP .. so Debian is using the older vendor driver (which is GPL code, but not upstream code). There is probably a way to put the driver into debug to get more info from it.

Quote from Arathonk

Since today NordVPN stopped working, I reinstalled and correctly filled in my login, but its giving me an message saying it can't connect.

Banned add-ons are installed. No support to be provided.

I don't think the RHEL article is relevant because the 4.18 kernels are ancient (even though RH backports a ton to them). That also doesn't correlate with the OP who broke his setup by updating the kernel on his OMV install.

You can also look at Kodi changes for NFS and filesystem caching. I have fuzzy recall that there are some between K19 and K20, but as I never use NFS myself (as SMB works fine) I never pay any attention to them. Some differences to an LE9 install would be expected since the entire codebase is different, but we aren't seeing general user whinging about NFS issues with LE11 and that usually means the reported issues are more localised to a specific other software (are you also using the same OMV version?) or something else niche/environmental.

NB: I've deleted the other thread you started and moved this one.

Once you're in safe mode you will remain in safe mode unless you manually revert back to the previous Kodi setup. That can be done by stopping Kodi and renaming folders to restore the previous Kodi instance to the right location. That will also restore the crashing though, but in 99/100 cases the reason for repeated crashes is a bad add-on, so watching the logs and seeing which add-on causes the crash; means you can then delete the add-on folder from /storage/.kodi/addons (and the packages folder) to get things running again. The fix of the problem then depends on what the problem was, but some kind of add-on update (new version, etc.) is usually the way forwards.

"lsusb" reports whatever is connected to the bus, it has zero meaning for the device being probed and working. The staging driver is enabled with `"CONFIG_R8188EU=m" in the RK3328 kernel config and it appears to result in the module loading (as you found) but then nothing. I would expect to see the firmware loading and such. Are Debian using the staging driver or the vendor driver? (the module might be the same name but could would be completely different). Are Debian using any patches?

Item 1 "git grep estouchy" should help you find the places you need to edit to prevent it being bundled. Items 2/3/4 are addressed via advancedsettings.xml configuration (more git grep will help that). Item 5 you can add packages to the image if they are LE add-ons. If they are third party add-ons it can be done, but we intentionally avoid providing instructions as there are people out there keen to bundle pirate add-ons and repos and that shitware is bad for our name. Item 6 is solved by adding "UBOOT_SYSTEM=box" to the build command.

Kodi does not support interlaced output, only progressive. Anything you force via kernel DRM during boot will be overriden later.

We aren't fans of RTL chips that have no upstream support (assuming that's the issue).

Feb 16 18:10:58.938037 LibreELEC kernel: Linux version 6.1.14 (docker@af3b48037063) (aarch64-none-elf-gcc-12.2.0 (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39) #1 SMP PREEMPT Mon Feb 27 21:44:00 UTC 2023

^ This tells me that you aren't booting the LE 11.0.0 image that I linked so there is no Realtek driver included. There is no support for the RTL chip in our main releases and that is unlikely to change. It is currently included in my private image.

https://chewitt.libreelec.tv/testing/LibreE….arm-11.0.2.tar <= don't pay too much attention to the version number, it just means it's ahead of LE 11.0.1 official images.

Note that "xrandr" is no longer available in the default Generic (x86_64) image as it switched to GBM/V4L2 graphics with LE11. You would need to use the "Generic Legacy" image which uses the older Xorg graphics stack.

I'm sure there are many happy users, and it's been a popular case. However our (forum moderator) experience with it is mostly all-bad. The case requires internal connections between HDMI and other connections on the board and the external ports on the case and these cause problems. The standard protocol when we see 'Argon' anywhere in the issue report is "remove the board from the case, all working now?" and in 9/10 situations users refuse to believe it's the case, but when we insist and they finally cave in and remove the board; the problem was the case. Caveat Emptor

There's a DNS resolution error with api.pluto.tv and then a series of Python errors with missing dependencies; all of which are quite obvious if you search for 'error' in the logfile. It's not an issue with LE code, so the errors need to be reported to the respective add-on authors via the add-on support threads in the Kodi forum.

The "invalid-key" error is probably bugs in iwd affecting a small number of users. We've bumped iwd to the latest release in LE11 nightlies and this appears to resolve it for most users. Update to the latest nightly here: https://test.libreelec.tv/11.0/Amlogic/wetek-play2/ and report back. The issue is tracked here: https://github.com/LibreELEC/LibreELEC.tv/issues/7166

The dmesg messages are correct and harmless.

For double results; an educated guess is that connman is scanning in the background so its results are visible to the dbus agent in the LE settings add-on, and then you're running scans via iwd and its results are also visible. If you don't run the manual iwd scan do you still see duplicates?