Posts by chewitt

ping jernej ^

I've some some Google searching on the error messages but didn't find anything conclusive. The card is using the unmtaintained Broadcom "wl" driver and there's been a few issues reported recently that just seem to point to kernel drift as a cause. In short, the kernel keeps moving forwards and this (not in-kernel) vendor driver has been in a static state for some years (at least a decade, maybe longer) and the phrase "if you're not moving forwards, you're going backwards" applies. Eventually the kernel has moved forward far enough that random stuff just starts breaking, and that seems to be the pain zone where we are now. The main option for LE will be to drop "wl" and swap to the in-kernel "b43" driver, but that's not brilliant (not really maintained since forever too) and lacks 5GHz support which will break some people's setups. It's probably the lesser of evils though.

If you can swap the card for something else, it might time to investigate doing so. Most of the devices I've seen this cards in use some kind of PCIe card or mini-PCIe daughter-card so they can be pulled and inexpensively replaced with something better.

Have a read: https://wiki.libreelec.tv/configuration/…ration-advanced

Please share a debug log that demonstrates the problem. Thanks.

It's been reported. You should be able to install 11.0.6 and then update to 12.0.0.

I'd guess it will be in the /storage/.kodi/userdata/addon_data/<nameofaddon> folder somewhere.

See https://github.com/LibreELEC/Libr…ment-2247708149 .. there are plans, but Jonas is a contributor who is usually a little optimistic about available time.

Boot Debian or Ubuntu in Live mode. Erase the drive and:

- Create a GPT partition 512MB in size with a VFAT or EXT4 filesystem labelled BOOT and enable it for boot

- Create a GPT partition with EXT4 filesystem that fills 100% remaining space

- Install Grub (not syslinux) to the internal drive and create a boot entry (crib the APPEND content from the LE installer usb).

- Copy KERNEL and SYSTEM to the BOOT partition

Shutdown Debian and see if it boots?

Our forum is regularly targetted for product placement posts and although they are caught by moderation (and thus you don't see them) it's a chore and staff would rather help with an issue than deal with user-generated makework. The reason we exorcise those kind of posts is .. the more you allow, the more you're targetted. Kodi has a much larger moderation team and it's up to them to set their own rules, and CE can similarly do whatever it likes; but they don't support x86_64 hardware so not much point.

You're welcome to post a simple link to the Radxa product page. I've already edited the original post to leave only the link to the CNX review, which being a formal product review, has a ton of info. Reposting the entire review or the entire product page; not welcome.

Quote from Grmpf

My guess would be that those aren't actually "override", but they are always "fallback", and DHCP happens no matter what. That would totally explain what is happening at least.

That would make sense to me, and does indeed explain the current behaviour.

Quote from Grmpf

i'd prefer some script to issue that ntpd command

The problem with that is you cannot disable ConnMan NTP checking so regardless of what date/time you set via a boot script (or cron task) there will be times when ConnMan runs an NTP check against the router and reverts the device to router time, until the next scheduled script NTP check that will correct it again.

The better solution is to use a router that keeps time. The best solution is to author code that modifies ConnMan to optionally ignore NTP responses from routers (there are overrides for some other things, but not NTP). You can always submit the problem to the ConnMan mailing list and hope someone helps with that, but "You can have it fast or cheap, pick one" applies and $free requires someone on the list to feel kind or inspired enough to code something. Usually $free has a long waiting period.

Nice. I had a hunch it was that (not the first time I've seen the issue). I'm not sure why the override isn't working, other than I'm probably imagining it worked that way and in reality it doesn't, or that ConnMan used to but changed behaviour, which has happend a few times in a few areas, over time.

Then it's a skin issue and should be reported to the skin authors via the skin support threads in Kodi forums.

- Do not post or promote external URL links to products, a name description is enough
- Companies who create "advertorial" postings for their products in our forum are not welcome

MediPi Your enthusiam for the Radxa X4 is noted. However this forum isn't interested in hosting full-page adverts for products and this has already been pointed out when I've deleted the advertorial content in two posts to this thread. If you want to ask in the N100 thread if anyone has an opinion on the device, you are welcome to do so. However if asking involves you posting another full page advert for the product at the same time the post is going to be deleted (again). And if I need to delete a fourth post I'm going to assume you are working for Radxa to promote the product and your account will be banned (final warning). NB: We are happy to have Radxa staff active in our forum; as long as the accounts are tagged (and they stick to support not promotion).

It would be helpful to see a full Kodi debug log that demonstrates the issue and how the source is configured in sources.xml. Note that Windows requires you to use username/password authentication (anonymous shares no longer exist). This means even if you configure a share as open and accessible to anyone, the connecting client still needs to present itself as 'someone' else you are 'no one' and access is denied.

If the intention is to boot/run from a USB drive (not an internal drive)? - Write the LE image to the 2TB USB drive then boot from the drive but interrupt boot at the syslinux prompt and type 'run' to boot from the USB drive instead of booting into the installer which is used to install to another drive target. I can't explain why the normal installer approach isn't working (there are no errors in the log file you shared) but if the device is booting to the installer from a USB device, see if that continues?

Random guess: Is your router acting as an NTP source (some do) and is its clock correct?

The LE settings add-on will allow you to configure NTP servers, so perhaps force {0,1,2}.pool.ntp.org and see what happens. They are the default ones we use anyway, unless something like DHCP configures an alternate (like when the router sets itself as one).

I'm not sure RK3399 supports 10-bit output at the current time, so you'll have 8-bit output which results in banding.

There are improvements being submitted to the kernel, but these things take time.

Switch back to Estuary and check whether it works there? If it does, the issue is with the skin and you need to report it to the skin author via Kodi forums. If it's broken in Estuary too, then it's either something in Kodi or LE. Please check.