Posts by chewitt

No debug log = no problem

Hashes are worthless and are not the solution. We are working on a proper solution. Go poke in GitHub for more info.

I downloaded the driver from the link on the advert/listing but can only see references to using it on Android. It might compile on Linux but we don't have that driver in our images and honestly we have low/no desire to add more sh1t quality realtek drivers that are hard to maintain.

And I don't make hardware recommendations, sorry.

Realtek_RTL8812BU_USB_Module <= there are no known linux drivers for this chipset, so no it won't work

^ in this context "recognised" means the kernel can see there is a USB device attached, but because there is no driver in the kernel (because no driver exists for this chipset) nothing more happens.

SSH into the box and run "lsusb | paste" then share the URL generated here. Then we can tell you which unsupported chipset in the device you bought. I can see from the driver that it has a realtek chipset, but we need to see the actual USB device ID's to comment further.

I renamed the thread because it has nothing to do with the Chromebox.

Your clean install of Win10 has no SMB1 support (only SMB2/3). Your clean install of LE 8.0.2 has no SMB2/3 support (only SMB1). You need to update to LE 8.1.2 (or 8.2.0 once released) and then OS/Kodi has newly-added support for SMB2/3 connections.

You should be able to connect a USB keyboard and mount the boot partition to correct the boot command. The initramfs boot environment that you drop into when that error shows has "vi" as a text editor.

en:users:drivers:brcm80211 [Linux Wireless]

^ there is no linux driver for this chipset; throw it out (or return it if you can) and get something something else

Assuming "error in mount_flash: mount_common: could not mount LABEL-LIBREELEC" is a typo and LABEL=LIBREELEC is correct the issue is quite simple; you are trying to mount using disk (partition) labels and there is no partition with the label LIBREELEC. This is probably the boot partition, which is rather fundamental.

Add-on bumps happen because people care and take the time/effort to contribute. The more people who do this, the easier everything becomes.

I forget when we added the option but it is definitely in the 8.1.2 release, so update.

Some ISP's block NTP requests in their router firewalls. Some ISP's block NTP in their network. It's stupid, but it happens.

You can try configuring 0.br.pool.ntp.org, 1.br.pool.ntp.org, 2.br.pool.ntp.org and see if those work? - also set the LAN IP of the router and see if that works as an alternative - you'll be at the whims of the router clock but at least you'll probably get something within the same day.

No .. and the thread is now locked because I am becoming bored of repeating myself.

HD audio is a known issue with the Intel GPU drivers. There are fixes in circulation but they are only suitable for inclusion on newer kernels so we are not able to patch things in LE 8.2 without causing problems. It will be resolved in LE9.0 (which will use newer kernels). Although the lights don't show on the AVR display (which causes OCD issues for people) multichannel PCM output works fine and 99/100 users are probably unable to tell any difference in audio quality.

Requests for Kodi functional changes should be made to Kodi developers via Kodi forums. For these things LE is just a dumb consumer of upstream code, so we don't get too involved in these kind of requests.

No debug log = no problem.

AFAIK the only allwinner images in circulation are based on a collection of OpenELEC era patches ported over to the LE build system. Nothing in that image has been created with our knowledge so we have no idea what can be configured on the image with your unknown soundcard and unknown (and to us, unsupported) hardware. It's probably best to ask the unknown creator of the unknown image.