00:30 <appas> chewitt: thanks, by those instructions and https://www.reddit.com/r/Emuelec/comments/hxrggg/dtb_list_for_your_device/ this dtb list, i got it to boot... but i need "that shitty WiFi chip"!

04:10 <mack> Ain't nobody got time fo' shitty WiFi chips.

04:32 <LEBot> [slack] <chewitt> appas: some Armbian folks started a fixup/rewrite for the chip on Rockchip hardware

04:33 <LEBot> [slack] <chewitt> but to hack it work on RK, they removed all the hardcoded support for Amlogic registers and such

04:33 <LEBot> [slack] <chewitt> and I’m told “it runs, but it still sucks”

04:34 <LEBot> [slack] <chewitt> pick up a cheap WiFi/Ethernet bridge device and connect Ethernet

04:35 <LEBot> [slack] <chewitt> I have some old Apple Airport Express units that I use for testing .. my workbench is nowhere near Ethernet

04:35 <LEBot> [slack] <chewitt> but that allow me to just connect Ethernet and .. the board/box/thing is on the network

04:36 <LEBot> [slack] <chewitt> no need to configure WiFi on clean installs, no need to mess about with WiFi drivers

07:52 <appas> chewitt: i actually got a cable cover, so now i can have the box connected with ethernet and not worry about the wire... but, the next problem is: the remote doesn't work. i put the remote.conf into the root, 9.2.5 worked with this config, but with the latest, it doesn't work. i get some "Remote Control... failed to start" on boot. I would give logs, but I also can not log in with SSH, even though I can

07:52 <appas> ping the device, and have SSH enabled in the conf

08:06 <LEBot> [slack] <chewitt> appas: the remote.conf from legacy kernel image will not work on upstream kernel images

08:07 <LEBot> [slack] <chewitt> it’s not hard to transcribe things though

08:07 <LEBot> [slack] <chewitt> pastebin the file somewhere

17:56 <appas> chewitt: https://paste.debian.net/1267102/ this is the remote.conf from 8.2.3.1