No idea what chipset is in the device (and you provide no logs) .. but as a first blind guess, have you configured the correct wireless regulatory domain (country)?
Posts by chewitt
-
-
Start with reading: https://wiki.libreelec.tv/hardware/amlogic .. then stop trying to boot a 2023 upstream Linux kernel with the dtb file from a 2015 vendor kernel. Note that Realtek (RTL8189ES/FS) WiFi is not supported in official LE images.
-
Follow the settings advice here (ignore the 4K/HDR stuff, the rest is relevant): https://wiki.libreelec.tv/configuration/4k-hdr
-
Thought my best chances would be to ask reddit
Sounds like a good idea. Our expertise is in supporting our own Kodi oriented distro, not helping people flash old Android boxes to make a Plex server.
-
It doesn't explain it because in LE the NTP request comes from ConnMan not "ntpd" and there is no issue with the boot date/time starting in May and then being corrected to current time; unless the configured NTP server(s) fail to respond. Unless you explicitly define servers for a ConnMan service, it will use ntp.org servers. Some ISPs and network routers block requests to ntp.org (no idea why, but it does happen) and some routers will set themselves as the time source via DHCP. If you look at the systemd journal it will show requests being made, where they were made, and what the outcome was.
-
-
Does this version work with S805?
No, AMLGX is for S905 and up. The AMLMX image supports S805 .. although that's rather unfinished and I didn't find the enthusiasm to do any work on it in about two years now. There's a couple of older test images in my webshare but they are not supported (as I can't remember much about them at this point) and they're now rather dated.
-
-
Do cold boot not warm boot?
-
Code
ifconfig bond0 192.168.1.1 netmask 255.255.255.0 up ip link set eth0 master bond0 ip link set eth1 master bond0Something like that ^ might work? .. I've no ideas how ConnMan will react to a bonded interface, or whether it will be persistent, or whether it kicks you from SSH at the same time (likely). LE will support the "iproute2" command-set (see https://www.kernel.org/doc/Documentat…ing/bonding.txt) but we're not really designed for fancy network configurations. Our goal is less about having the fastest connection (although that's nice) but to ensure it's "fast enough" to play what you need without issues.
-
If there were general issues with SD card boot on RPi5 boards we'd be flooded with reports, and we're not, so it's likely to be something local. I'd start with updating to the latest board firmware, and experimenting with another SD card.
-
READ: https://wiki.libreelec.tv/hardware/amlogic (then use the correct image; hint, it's not the WP2 image).
-
Code
mount -o remount,rw /flash fdtput -t i /flash/rk3288-tinker-s.dtb i2c@ff140000 status okayIt's probably easier to use "fdtput" to make the modification. I think that's ^ correct.
-
-
As per our GDPR policy we don't delete accounts and associated posts, but we rename the user to anonymise posts and we remove any personal information (email etc.) from the forum DB. The final act is banning the account to prevent use. I'll do that shortly.
-
As long as you understand there is no hardware decoding and that limits things to 1080p, it'll run fine.
-
I asked for the debug log because it will show what resolutions and refresh rates are being advertised, and then we can either see what the issue is and/or advise how to set things up. There are no config.txt or dtoverlay things for x86_64 hardware, that's a Raspberry Pi only thing. The 4K-HDR wiki article advice still generally applies.
-
If you want more changelog info please go look at the full/original commit log on GitHub. We have no plans to bloat page load times and increase webserver load with more commit data that likely few people read.
