Kodi logs aren't going to capture any useful information for a WiFi issue. The problem is way below Kodi in the software stack and you'd need ConnMan and IWD in debug mode to capture anything in the systemd journal.
All of which is moot when the most likely cause requires 10 seconds of effort to run one CLI command, and then reboot.
Yes, correct. It's now zstd compressed and saving you space.
Will the nightlies work on Ugoos SK3 powered SoC RK3588S2-DV and 8/128 GB on board?
I don't think so. I've not seen any mention of RK3588S2 support in the upstream kernel (only RK3588/RK3588S). The SoC differences are likely minor, but as there is no u-boot defconfig or board dts in the kernel for that box, LE will want to see those pieces in-place before offering support. NB: AFAIK there is no 8K support for RK3588 at the moment (in the to-do list, but not at the top) and DV will likely require some proper reverse engineering. I wouldn't rush out to buy one just yet.
Test the modprobe file please.
LE 12.2 or LE13 nightly? .. If on LE12 still, update to LE13.
echo "options brcmfmac feature_disable=0x2000000" > /storage/.config/modprobe.d/brcmfmac.confIf you run that ^ over SSH and then reboot, does this restore previous behaviour?
This should functionally effect a revert of https://github.com/LibreELEC/LibreELEC.tv/pull/11785 which is a direct feature/capability change for the wireless stack that would have rolled out in RPi5 nightlies around September 19/20.
HiassofT FYI
I went for 4GB to be safe, have enough headroom for heavier skins, larger movie/TV libraries.
Heavier skins tax the CPU, GPU, and I/O performance, not RAM. Libraries do impact on RAM.
An NVME HAT with a small M2 drive is a nice upgrade.
dale I'd guess some changes are needed in the kernel. I'm currently up to my neck in Amlogic things but will add it to Claude's worklist once I circle back on Rockchip topics.
There is no forum rule banning CE from being mentioned. However comparison discussions have a habit of attracting trolls, and we prefer to avoid that kind of behaviour. Just keep the discussion sensible.
It has 32 GB of flash storage and (theoretically) 4GB of RAM, but LE can only see 3 GB, I still don't know why.
Open the box and see whether you have 2x 2GB or 3x 1GB DDR RAM chips on the board. The 3GB RAM config is quite common on Android boards, with stickers lying about the installed RAM size (and Android hacked to show 4GB) also not unusual.
RPi5:~ # sysctl net.ipv4.tcp_window_scaling net.core.wmem_max net.ipv4.tcp_wmem net.core.rmem_max net.ipv4.tcp_rmem
net.ipv4.tcp_window_scaling = 1
net.core.wmem_max = 4194304
net.ipv4.tcp_wmem = 16384 16384 4194304
net.core.rmem_max = 4194304
net.ipv4.tcp_rmem = 16384 131072 33554432Default values from LE13 at current master branch HEAD state ^
What hardware are you trying to use?
The cleanest route would be zero'ing the boot media first as that clears backup tables too, but that can take ages on a large sized drive and it's not essential. DD'ing the image (after gunzip'ing) overwrites/nukes any pre-existing partition and filesystem state so formatting first makes no real-world difference. No wiki hint required.
Edit the syslinux.cfg file in the LIBREELEC partition on USB/SD boot media and add ssh to the boot params line. This will force the daemon to start on boot. However if this is a clean LE12.x install, something is wrong for the add-on to be faulting or not running and SSH access probably won't solve that, and I'd recommend retesting with a current LE13 nightly first.
If dd was used correctly, writing the LE image to the card overwrites the first 512MB and the first sector (512 bytes) contains all the primary partition and filesystem structures that describe layout. It will leave backup partition tables intact at the opposite end of the drive; but that's true of your magic formatting step too.
like the infamous 12/10 bit issue on N100
Which has been patched in LE13 images for quite a few months now..
It's a moot point. If one person (or LLM) is the analyser of the existing design, writer of the specification, legal reviewer, and clean room implementer the result is almost certainly not clean. See https://en.wikipedia.org/wiki/Clean-room_design
In the v7 submission everything below the first paragraph should have been placed under the --- separator so that it is visible to reviewers but not merged into the codebase along with the description.
I normally place things above --- during development so that testing commentary is easily edited and not forgotten, but then you need to remember to tweak the final patch files before sending to move the --- above it.
