Seth

oh thats why i never encountered the ch341/ch340 error, i started with the cli/minimal install

please post output of the following commands while the printer is plugged in the usb and is turned on. ls /dev/tty* and lsusb i never had problems with usb serial communication with armbian before. please check your klipper make menuconfig settings and that it is exactly what is intended for your printer mainboard. here is the guide for your printer.

open nvram_2734с.txt copy and paste all the contents and in the loaded config. bcmfmac4330* or brcmfmac4334* in /lib/firmware you can install klipper with kiauh just fine with this build of armbian i've been using it for 3 years now. you just need git installed and clone kiauh repository for a very convenient klipper install.

thanks, will try it out and upload serial logs after i solder the wires on it. got a bit distracted since i'm currently cleaning up the other box from junk and trying to reflash and reinstall pihole.

links on first post.

hello, i got a new rk3328/3318 box and it is an MX10 box. board is MXQ-RK3328-D4_A ver: 2.0 date:20181219. i was wondering if anyone has the same board as mine and got armbian running on it. here are pics of the board. https://photos.app.goo.gl/ikSCNH7s59f2v5EE7 if serial logs are needed i can solder some wires to gather the info. thanks.

works like a dream @jock. here's my freshly installed/updated hk1 max box dmesg using latest libreelec hdmi patched 6.3.13 kernel. i hope mainline gets around to updating hdmi timing stuff. brcm 6334 2.4G and 5G works out of the box. using it currently as pi hole box. for those having problems with rtl 2734c (rtl8237cs). wireless module that gets detected but cannot connect to AP, here's a reuploaded nvram you can try out (no guarantees though), it solved my problem way back with the rounded h96 max i am using as klipper host. file is not mine, credits to the original uploader. dmesg.log nvram_2734c.txt

@FatalWorld there is a kernel oops about swapper being tainted. your board is the same as mine albeit with different wifi chip. these are the things i would try if that was my board: 1. backup original firmware and try flashing different firmwares on the emmc chip from the github page. 2. if running from sd card, i would try a different sd card just to test filesystem stability. 3. i would also try ram testing. 4. upload logs for different test image used. just do a "dmesg >> dmesg519.log", download that log using winscp and include it in your next post, it would help jock and others with debugging where your problem is coming from. got mine solved that way. cheers and good luck!

please indicate box type and board version, if posible attach top and bottom images of the board.

board version? sometimes those 4 pads do not work for me, what i sometimes do when i'm feeling lazy is i try connecting the ground on the board first then i try connecting the rx pin of usb serial to different pads of the board while booting to find its tx pin. you only need two pins to capture serial debug logs. i found mine at the back of the board. i think i posted the pics in this post at page 26. you get very low chances of bricking your board if you do it this way. other method i use is a low cost stm32 o-scope and a multitester which a is way safer method in my opinion.