12:35 <benoitm974> Little update on the homelab with S905X3, I was able to run a 5 nodes kubernetes on mainline linux, I even made it only with the default u200-gt12 dtb from the current mainline (you just loose audio, CPU is throttled a 1.8) but the rest works

12:36 <benoitm974> little home labs stack for kubernetes training https://usercontent.irccloud-cdn.com/file/Kp9vFuun/PXL_20210125_120100578.jpg

12:38 <benoitm974> The fan when running more than 2 nodes is mandatory ... anyway thanks for the help here, little fun

12:38 <chewitt> benoitm974 it would be better to use an SM1 device as the base for that, u200 is S905X2

12:39 <benoitm974> Yes of course this was just to report that even with a 'bare' mainline linux with no patch at all you can run it.

12:39 <chewitt> is that the H96 max box that I made a dts for, or the "other" one?

12:42 <benoitm974> No that's the H9 X3 which is really bad :( I was sold for a 4G / Gig Ethernet and turn out to be a fake only 2Gb. / 100mB ... But since I can't return them for huge shipment cost, I tried them anyway... I think the existing meson-sm1-x96-air-2g.dts or meson-sm1-a95xf3-air-2g.dts would be the same

12:43 <chewitt> yup, should work

12:43 <chewitt> the main difference between the boxes is the SDIO WiFi/BT and neither are upstream so the dts differences are mostly the box names

12:44 <chewitt> one is RTL8822CS and the other is MT7668

12:44 <benoitm974> The H96 max is realy better it also have the blue led as the odroid C4, a reall 4G, a nice UART soldering pad, and nicer broadcom BT/Wifi with well supported 1Gig ethernet Realtek

12:45 <benoitm974> I'll see if can spend a little time finishing the testing of the DTB adding the led and fine tuning audio;

12:45 <chewitt> what's to fine tune with audio?

12:51 <benoitm974> ALSA sont show the card at boot the same it does on odroid linux I wondering if its dtb tuning or something else ?

12:52 <benoitm974> sont=don't

14:47 <chewitt> benoitm974 see https://github.com/chewitt/alsa-lib/commits/amlogic and https://github.com/chewitt/LibreELEC.tv/blob/amlogic/packages/audio/alsa-utils/scripts/soundconfig#L131

14:48 <chewitt> in a conventional distro you don't need to rebuild anything .. just steal the confs

14:49 <chewitt> rename AMLOGIC-HDMI.conf (and sed the contents) to match H96-MAX (or whatever model name you're using

15:45 <BlueMatt> chewitt: btw are the patches that you have on the libreelec.tv build that fix reboot on odroid-c4 making their way upstream?

15:48 <chewitt> "arm64: dts: meson: switch TFLASH_VDD_EN pin to open drain on Odroid-C4" is submitted to the mailing list but not merged yet

15:49 <chewitt> the equivalent patch for u-boot is already merged

15:51 <chewitt> the kernel patched is "suggested by" one maintainer and "acked" by another so I don't see an issue with merge :)

15:51 <BlueMatt> ah, ok, good to hear :)

15:55 <BlueMatt> chewitt: also, i dont think this worked on either, but the amlogic-thermal driver doesn't register properly with hwmon

15:55 <BlueMatt> so sensors gets sad trying to find the temperature, even though its in /sys/class/thermal

15:57 <BlueMatt> (and snmpd, in my case, is too stupid to find it)

16:50 <chewitt> I've seen something about hwmon recently.. but can't remember where

16:50 <chewitt> best to Zzz on it, then I'll memory jog

17:05 <narmstrong> http://lore.kernel.org/r/20201115190658.631578-1-martin.blumenstingl@googlemail.com

18:16 <ballerburg9005> strange .. when I write to /dev/mmcblk0 I can see the changes but they are lost after a reboot

19:02 <narmstrong> ballerburg9005: check if the mmc is mounted, if mounted you need to "sync" before reboot

19:22 <ballerburg9005> narmstrong: never mind, I was writing with dd but it is busted. The driver must have been caching. I am getting errors all the time.

19:24 <ballerburg9005> I mainly did this because I was looking for a way to easily switch to booting from sd card first, without pressing the reset button, to boot Linux

19:25 <ballerburg9005> I still have not figured out how to detect the "env" partition location to change the uboot "script" that does this

19:27 <ballerburg9005> on the stock kernel, it prints the partition offsets but not on the 5.11 kernel

19:30 <ballerburg9005> installing Linux on ARM seems to be fiddly in general

19:31 <ballerburg9005> my project is to make a one-click method to flash an image that works well for endusers, at least for a single $30 tv box

19:32 <ballerburg9005> and I will document everything I did, so that others can reproduce it

19:32 <asdf28> ballerburg9005: this happened to me using the stock kernel

19:32 <asdf28> changes not being written

19:33 <asdf28> but it worked with a generic linux system

19:33 <ballerburg9005> right now I feel like it is a joungle of things, with images provided by Armbian and such not working well for amlogic especially - and no documentation on how those images are created

19:34 <ballerburg9005> asdf28: what do you mean by "generic"

19:34 <asdf28> any system that does not use the legacy kernel and u-boot

19:35 <ballerburg9005> hmm, I have read that the 5.X kernel sets the voltages wrong as a cause 6547

19:35 <ballerburg9005> https://archlinuxarm.org/forum/viewtopic.php?f=23&t=13495

19:35 <ballerburg9005> but I am not sure, the mmc of the only box I have it is really damaged it only reads mostly

19:36 <ballerburg9005> doesn't boot android anymore

19:37 <ballerburg9005> have to wait for the new box

19:38 <ballerburg9005> man

19:39 <ballerburg9005> right now, we almost got everything most people ever wanted with Linux on a TV box

19:39 <ballerburg9005> the Android ecosystem just sucks in comparison

19:41 <ballerburg9005> if we worked the few quirks out, and made it install easily, then everyone would be jumping after Linux and TV boxes as a PC replacement, media center, and server for self-hosting data and the fediverse

19:41 <ballerburg9005> that is my dream, it is the second coming of Linux so to speak

19:42 <ballerburg9005> a $30 box that does all the things and more

19:42 <ballerburg9005> it runs Linux, people want it for freedom

19:43 <benoitm974> Asfd28 I have had a lot of trouble with mmc and temperature... Everytime it starts with mmc error when temp is too high

22:31 <benoitm974> ballerburg9005: you could just add an aml_autoscript once with the reset bouton which contains a change to the u-boot env, which later could always be easily revertable with a "env default -a" or "defenv" command on u-boot. The box I have rely on 2015 u-boot and have 3 things:

22:31 <benoitm974> A) if you mess with the MMC partition or DTB it will by default revert the u-boot env and your env changes will be lost

22:33 <benoitm974> B) just before u-boot it first launch the 'preboot' env script which is the place when the test the GPIO of the reset button with the "run upgrade_key" part so if you want to change the sequence and still keep the option to boot an aml_autoscript from mmc or sd you need to keep this in preboot

22:33 <benoitm974> C)then it looks for "bootcmd" as usual with standard u-boot

22:36 <benoitm974> for example this script allow me to first boot on the sdcard, but will next time boot from internal MMC, I use this to install linux on the internal MMC (the only issu I have is that if I format the MMC in between I need to re run once more the aml_autoscript otherwise the bootloader detect the partition change and revert the u-boot env.

22:37 <benoitm974> https://www.irccloud.com/pastebin/Do9shi70/

22:39 <benoitm974> The aml_autoscript is compile with mkimage -A arm64 -O linux -T script -C none -d aml_autoscript.src aml_autoscript

22:40 <benoitm974> also I've notice better success with. double saveenv ... It might works with only one for others.

22:41 <benoitm974> it safe to dump/save the printenv somewhere before playing with this ...