Linux network development - Patchwork
^ shows that that patches I flagged were accepted, meaning they are queued for Linux 5.9, and there are no new patches which means the chipset is still not supported in the kernel. Your next move is to wait patiently.
You can use WinSCP to transfer files over the network to the booted device. It's slower than a local copy to USB, but can run in the background.
Go read post #2 again, then if that does not match your experience, post again with some evidence of a problem. LE is not Retrpie so comparisons with an entirely different distro are not particularly relevant. Yes they are both Linux OS, but Ferrari and Nissan are both cars, if you get the point.
LE will mount the HDD device to a consistent path based on the disk label (if it has one) or the UUID (if it doesn't).
LE embeds multiple nVidia (vendor) drivers to support different generations of GPUs, but the 304.xx series is the last one to support 7-series cards and this no longer supports the ABI version we need to support current Xorg with other GPUs (Intel, AMD, etc.) so it was dropped and the oldest driver we include now is the 340.xx series which stops at the 8-series cards. As 7-series cards are now 15+ years old we're comfortable with that - never in our history have we ever pitched ourselves as something to use with old or recycled hardware, and our focus is on current and bleeding edge HTPC kit. In the future we might drop nVidia drivers completely and default to nouveau, but nouveau hasn't been tested (by nouveau developers) on cards that old for a long time either so I wouldn't guarantee it works. Time for a GPU upgrade, or swap to a Raspberry Pi 4 which will probably be cheaper and will out-perform anything that shipped with a GeForce 7-series card.
Install the system-tools add-on from our repo and configure "hdparm" over SSH to configure a spin-down time. There should be lots of how-to guides on hdparm if you Google for them.
The Khadas boards have built-in broadcom WiFi which avoids the problem although no wireless device is brilliantly fast. Note that hardware decoded HEVC is the one thing that LE (on mainline Linux) does not currently support on Amlogic hardware (still WIP). Older LE images (and CE) which use the legacy vendor kernels are the current workaround. Amlogic boards with S922X, A311D, S905X3 (e.g. VIM3L) are also capable of software decoding 1080p HEVC content (but not 4K) which is the other workaround.
Cranial there is nothing to prevent LE being a WireGuard server, but there is no packaging/scripts/etc. in the distro to support that so you'll need to handle it yourself. NB: Our SSH daemon listens on all interfaces by default so if the elderly user "client" end connects to a WireGuard "server" when support is needed you can always SSH from the server to the private (remote) IP of the WG client in a "reverse tunnel" arrangement.
Restore bootsector.img to the card using our USB/SD app or Win32DiskImager, Etcher, etc. and then have another go.
It's possible to run Rasbian on the device instead of LE and that opens the door to many things. The original CM board isn't speedy, but that may or may not count depending on what you want to do. Retro gaming would be one alternative to Kodi.
P282 is S905W .. so the Tanix TX3 is the closest matching device.
I've no idea, but if you drop into the #librecomputer channel on freenode @lvrp16 (who owns LibreComputer) can either answer the Q or task on the Baylibre developers he pays to work on his boards to comment/investigate.
CM3 and CM3+ are the same thing .. with minor thermal imrovements and the options for larger eMMC storage - the 8GB version of the CM3+ offers some extra space over the 4GB in the CM3 which would be nice for Kodi, although when you look at the pricing of the modules an RPi4 is still a better overall investment.
Add "ssh" to cmdline.txt and the SSH service is forced on at boot. Now connect Ethernet to the RPi and the HDMI cable to the projector. Find an app called "Discovery" in the macOS app store (see Tildesoft) as this shows Bonjour devices and makes finding the IP address of the RPi and it's SSH service simple (look under SFTP). SSH into the RPi and run "kodi-remote" and you have a basic commandline remote control for the GUI to control the GUI with. You can also use numerous mobile phone remote apps to control Kodi. Installing and trying to use a VNC server is one of the most awkward ways I can think of to control things.
Find the name of the udev rule that mounts and sets options, copy to /storage/.config/udev.rules.d/<name> then edit the rule with whatever changes are needed, then save and reboot so the modified rule overides the embedded one.
The upstream kernel drivers for DesignWare HDMI have no support for HBR audio, only PCM, so there is no pass-through at this time.
Your link doesn't result in a logfile to view.
