Posts by chewitt

<3>[   13.496949] squashfs: SQUASHFS error: unable to read id index table
<6>[   13.497211] F2FS-fs (loop0): Magic Mismatch, valid(0xf2f52010) - read(0xc71e53f1)
<3>[   13.497214] F2FS-fs (loop0): Can't find valid F2FS filesystem in 1th superblock
<6>[   13.497254] F2FS-fs (loop0): Magic Mismatch, valid(0xf2f52010) - read(0x41e10784)
<3>[   13.497256] F2FS-fs (loop0): Can't find valid F2FS filesystem in 2th superblock
<6>[   13.497265] F2FS-fs (loop0): Magic Mismatch, valid(0xf2f52010) - read(0xc71e53f1)
<3>[   13.497268] F2FS-fs (loop0): Can't find valid F2FS filesystem in 1th superblock
<6>[   13.497270] F2FS-fs (loop0): Magic Mismatch, valid(0xf2f52010) - read(0x41e10784)
<3>[   13.497273] F2FS-fs (loop0): Can't find valid F2FS filesystem in 2th superblock
<3>[   14.533541] squashfs: SQUASHFS error: unable to read id index table

The good thing about packaging the entire OS into two files is you only have two files (not thousands). The bad thing is you have one byte of corruption in the image and the entire OS doesn't boot. The lines above indicate something is bad with the SYSTEM file - which matches the error message you're seeing.

I'd guess it's time for a new USB stick?

cp /etc/connman/main.conf /storage/.config/connman_main.conf
nano /storage/.config/connman_main.conf

^ edit the order of PreferredTechnologies so wifi is before ethernet and then save and reboot to effect the change. When wireless is connected it will become the internet routed connection.

GB is correct.

Wait patiently until someone adds wifi support for that device to the mainline kernel .. or get coding.

Download and run the USB/SD Creator tool. Select Generic etc. and create a USB. Boot from the USB and clean install the OS. This will nuke whatever is currently installed, but you end up with a clean system and a 512MB boot partition.

You may have tons of space on /storage but the update requires 235MB ish space in the separate boot partition and yours is probably an older OE sized boot partition that's 230MB. Hence the error message.

If there is truly nothing on the box .. just clean install and start over. If there's something you want to save, make a backup in the LE settings addon and move it off-box and then clean install and restore the backup. This is considerably faster than trying to shrink/expand the existing filesystem.

It's not a driver problem. Bootloaders need to have an elementary understanding of physical hardware to see and present stuff for boot. When you boot from USB (which the bootloader understands) you end up in the kernel initramfs which has drivers/support for the eMMC/SD card so you can see it as an install target. Once you reboot and attempt to boot directly from that the eMMC/SD hardware (which the bootloader doesn't support or understand) .. you don't boot.

Hence the suggestion of using another bootloader. If you can boot an Ubuntu LiveUSB image on your device; whatever version of GRUB that the LiveUSB is using works on your hardware and you can use that to boot LE. The only thing you'll need to figure out is the GRUB boot config, but that's never too hard and there's probably some posts in this forum on the topic (i'm being lazy and not Googling it for you).

Something is screwed on your box then, because that /storage/.config/modprobe.d exists by default in all LE installs. The "configfiles" samba share maps to /storage/.config.

We have no idea (or our guess is as bad as your guess). There are multiple manufacturers of these generic boxes and some of them will save a few cents and put the cheaper S905W chip inside and there's no way to distinguish them without opening the case and looking at what's printed on the chip. S905W can do up to 4K30. S905X can do 4K60.

The "network error" bug is present since OE 3.2 ish but requires someone with python skills to debug it (so not me) and I've given up trying to entice someone on staff to look into it (90% sure it's an untrapped error message from dbus). It's not relevant. Also (for the record) changing the timezone in Kodi has zero impact on kernel wireless regulatory domain configuration - two completely unrelated things. What is relevant, is setting the correct regulatory domain. Which I already explained how to do.

echo "options cfg80211 ieee80211_regdom=DE" > /storage/.config/modprobe.d/cfg80211.conf

^ run that over SSH and change "DE" to the ISO country code for wherever you are and missing WiFI channels will normally appear.

You might get more success with GRUB as the bootloader instead of syslinux. ISTR those things have quirky boot.

LE includes the openvpn binary, but built for client use so missing capabilities needed to run as a server. Use a docker container.

Before you do anything with LE update the NUC firmware (which requires Intel's Windows-only updater).

If you force it to use /dev/sda1 and /dev/sda2 everything depends on device probe order (whichever gets probed first gets sda, next device gets sdb) and might change. If you want consistent behaviour use UUDI or LABEL instead.

[   28.101402] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.clm_blob failed with error -2
[   28.101410] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available

^ this stuff is harmless (most chipsets don't have clm_blob files) and can be ignored.

Not supported and no plans to support. Most of these STB boxes run Linux but with locked boot processes and code that prevent other Linux OS being installed.