Connman checks it is online as part of startup. It is harmless and there is a public declaraction that access to ipv4/6.connman.net is not logged. It can be disabled if needed. Copy /etc/connman/main.conf to /storage/.config/connman_main.conf and edit "EnableOnlineCheck=true" to false, save the file and reboot. The reason it's logged so many connection attempts is you're probably blocking it and thus it retries multiple times before giving up. If you allow it to succeed it doesn't need to retry.
Posts by chewitt
-
-
LibreELEC is an OS not an App. It cannot be installed on mobile phones.
-
How do you spin down an SSD?
-
-
I read the README.md in the fifteenhex repo and I think that driver is best not added to images. Good research tho
-
Tegra devices are fairly well supported under mainline Linux so there's probably nothing to stop someone from figuring out an image. It's never been on the official project radar because a) all the Tegra SBCs are crazy expensive, b) Shield is cheaper (but still expensive) and marketed as the premium Android product, so nobody buys it to run an experimental Linux image, and c) it's nVidia, who insults us elsewhere in the open-source world, which doesn't encourage anyone to take an interest in their stuff.
-
Next stable release will be v9.2.4 and this will still have the Linux 4.19 kernel (that didn't work). The test image uses the kernel that will go into the next major release (LE10) which is still some way off.
-
There are solutions to add EXT2/3/4 support using FUSE drivers, but those are slow, so the alternative (unless you're conofident with macOS CLI partitioning commands) is to boot a Linux VM and use GParted to shrink the /storage partition to 6-8GB for Kodi data, and then create a third "Media" partition that can be exFAT and cross-platform.
-
-
I can look into the vendor-binary driver, but as r8169 already detects the chip (but cannot make it work) we'd also have to patch out that behaviour to avoid a driver clash. This might acheive that: [net-next] r8169: rename RTL8125 to RTL8125A - Patchwork but that patch also shows support is being worked on (albeit at an early stage) so something might appear upstream sooner than later, in which case it would be preferrable to wait patiently for a few weeks and then backport some patches instead of adding a vendor driver to our codebase.
-
He probably means that nobody on staff (e.g. the release manager) ever remembers to update the auto-update config after releasing a new version so e.g. 9.2.3 is not pushed to people (auto-update is still on 9.2.1). Hence why I want to remove that piece of infrastructure and move the logic into the settings add-on so there's nothing to (forget to) update when releases are made.
-
Please test a current development image with newer kernel on a spare SD card, images are here: Index of /
-
macOS does not support EXT4 partitions so it can see "disk20s2" (the /storage partition) but cannot mount it or display anything meaningful. Windows is equally stupid.
-
You can dump EDID from a TV to file and then configure the RPi to use the file. Then Kodi "sees" a TV connected (even if it isn't) and it will start, and VNC will be able to show the screen. It all sounds like complete overkill when you can use the Kodi web interface or mobile phone "remote" app to browse the library and select something to play though.
-
On first boot the 32K (K, not MB) /storage partition on the SD card is automatically expanded to fill 100% of the available space. So I guess you didn't boot the SD card yet and are looking at the 512MB boot partition.
-
You can add "textmode" to kernel boot params to boot to a console. It's not interactive, but then even if you have a console you will not be able to add drivers due to how LE is packaged (the OS is uncompressed into RAM from a read-only file on each boot). In the past CTRL+ALT+F3 was supported on x86_64 hardware (can alse be enabled with "debugging" in boot params) but this was removed to improve security and because nobody used it, and there is no equivalent on ARM SoC devices.
-
Take the current Raspberry Pi OS and then copy the compiled device-tree bits from an LE 9.2 image. It's the same kernel version (4.19) and core sources so it should be compatible. I wouldn't use anything from the FiveNinjas repo now .. it's not been maintained for years.
-