Poor WiFi signals? - RPi4 is better than RPi3 for WiFi but with no antenna the connection is never brilliant. Also check the reegulatory domain setting as the default "world" config may not be fully compatible with the radio transmission requirements in your country.
Posts by chewitt
-
-
Worst case you can install LE 9.2.6, update to LE 10b1, then use the hard reset option in the LE settings add-on to nuke all traces of Kodi v18. Sounds a bit complex but with a fast NUC it's probably under 5 mins effort.
-
I answered several questions that you asked. I didn't claim to solve the problem.
-
Please share the URL from "journalctl | paste" and "mount | paste" about 20-30 seconds after boot so we can see how the drives are being mounted and if the kerrnel logs any error messages. Ignore lrusak message - it was late when he replied and his eyeballs didn't make it past the /dev/loop0 device to where the real issue is
-
If you're able to boot one of the mainline u-boot-using LE or Armbian images from SD card, installing them to eMMC is as simple as dd'ing the .img file to the eMMC /dev/mmcblkX device the same as you'd write an SD card under Linux. GXL and newer boards look for the Amlogic signed boot header in the same places on both SD and eMMC so the images will (or should) boot from either.
If you want Android on eMMC you'll need to track down either a more recent version of the Amlogic burning tool (or an older era-appropriate one that matches the image age) and a "ROM" image from somewhere like Freaktab. The ROM image format uses .img file extension but this is an Amlogic proprietary format so you cannot simply dd it to the eMMC device.
-
Kodi does not support downgrading so the best approach is to clean reinstall LE 9.2.6 and restore the backup you made before updating. If you do a direct downgrade you'll have the reverse issue with add-ons; the ones that auto-updated to new Python3 versions will not be compatible with older Python2 in LE 9.2.6.
-
Please try installing/running the LE10 beta release.
I'm wondering if it detects any network card. It is possible to add "textmode" to kernel boot params in syslinux.conf on the USB and then it will boot to a local console (not Kodi GUI) where you can attach a USB keyboard and run commands to see the output on screen. The output of "systemctl status connman.service" will probably reveal what the issue is.
-
GBM (V4L2) is the new video pipeline that all ARM based LE devices are using for LE10.0. Codec licenses are not availaable as they are not needed: the RPi4 has enough CPU grunt to software decode all the media formats that historically needed them.
-
LE 9.2.6 or LE 10b1 ?
-
But for future reference/updates which version of this should I be on the lookout. Because there are several builds in this topic?
Future images using Linux 5.12 kernel or newer should include the content that's merged in that branch.
-
Run "lsusb | paste" and "dmesg | paste" and share the URLs generated.
-
What am I missing?
We looked in our crystal ball but couldn't figure out your undocumented boot issue. UART logs would be more informative.
-
-
There are users who've wanted centralised logging before so if you have Logstash in your stack we have an existing rsyslog daemon add-on in our repo. I don't recall ever hearing/seeing someone capture logs with Filebeat, but since we can run Docker and there is probably an ARM container with Filebeat on a docker repo somewhere, it should be do-able.
-
-
There is no list - we've always refused to create one on the principle it will be immediately out of date and it's yet another thing we'll have to (and forget to) maintain over time. Anything that has driver support in the upstream Linux kernel is or can be supported today, and anything that needs "out of tree" vendor drivers will be politely refused. LE has some vendor drivers only for a subset of Realtek devices that shipped as official WiFi cards for older Pi boards (as they didn't have on-board WiFi at the time). Over time the percentage of these boards in active use is declining (and RPi0/1 are no longer supported) and at some point we will switch from wpa_supplicant to IWD which will drive a large nail in the coffin of those drivers.
-
-
Most of the time the upstream focus on "board" devices is making the HDMI output work and you only see support for the 3.5mm Jack on devices that run ChromeOS. Does the upstream kernel (device-tree) for your board support the 3.5mm audio jack?
