remlei

you may actually want to extract the dtb file on the android side of the tvbox you have just to get the OS to get recognize that chipset (but may not work due to missing driver).The odds for this kind of tv box to have a working wifi chipset is a lottery, most likely you better off not waste that effort and just buy a USB WiFi dongle instead, at least it works far better than a SDIO based wifi chipset like that.

can someone please reupload the legacy images, all links aside from the armbian community github page returns a 404

its probably just your client side OS. try using the "use sendfile = yes" option on your smb.conf and see if theres performance improvement. else, try using the legacy image (if your board is old enough to support it) as that one im using.

what filesystem your drive using? usually if its WIndows Filesystem, that's where you get some performance penalty and NTFS is the one being the worst of all. Last time I tried using a ext4 formatted usb3 flash drive and was able to read/write to drive at 11MB/sec over wired LAN, no tweaks on samba server were done other than setting up some shares.

This is nothing new, its Windows related issue. Probably had something with the drivers. But ultimately I just use a older windows version, I had a machine running a Windows 10 1809 LTSC and for some reason it works there. One thing that also works is using a ubuntu live CD and using the upgrade_tool for rockchip.

I assume thats the proper format because armbian-config is the one put that there so I never questioned about it. so far all of the NAND models seems to have USB OTG working but not all my eMCP boards, it always throw that error I posted earlier. also for some reason, in NAND models with jumpstart installed on NAND, overlay option on /boot/armbianEnv.txt for some reason do not work and have to resort editing the dtb file manually, all of it from led config to wifi stuff, also enabling the peripheral mode as well. I guess those overlay stuff only works when that u-boot bootscreen on emcp boards I had only have those overlay stuff working but not on the NAND models with jumpstart. After all those dtb shenanigans, I went ahead and install https://github.com/srepac/kvmd-armbian skipping all the way to step 3, a hour and 2 reboots later, yep its all working now. with 256GB USB flash drive mount on /var/lib/kvmd/msd and running that msd fix sh script to get that USB storage stuff working. sheesh, this box sure is really hell of a work. if I dont have extra time, id probably not doing this and just buy a cheap orange pi instead.

Yes I verified that its there. But im suspecting something though. I have a NAND rk322x and using jumpstart to boot armbian using sd card, can that possibly causing this issue? edit: nah scratch that, I snag my on emmc model and tried it there but this time uboot did throw some useful stuff it relates that it cannot load the dtbo file? I cd to the directory and it was there. edit2: managed to partially get the OTG port working, just have to edit the dtb file on my own instead of relying on armbian-config now the otg functionality kinda works? I ended with this error and basically clueless at this point [ 76.310374] dwc2 30040000.usb: new device is high-speed [ 76.310458] dwc2 30040000.usb: dwc2_hsotg_enqueue_setup: failed queue (-11) pi-kvm is partially working, the usb capture and everything works except for the USB OTG so no remote keyboard/mouse functionality.

Anyone managed to get the OTG port do USB peripheral stuff (gadgets)? I installed the latest armbian for rk322x on github armbian community. Looking at the kernel config, it looks like all the OTG stuff are set to Y by default now, execute armbian-config and set the dtb to rk322x-usb-otg-peripheral and reboot the system but alas, it still doesnt work with dmesg output pertaining that "Can't find any UCD" when executing "modprobe g_mass_storage file=/test.img luns=1 stall=0 ro=0 cdrom=0 removable=1". A little bit googling someone managed to get it working, I tried to follow what he did (but in more recent build of armbian instead of the legacy one), alas didnt managed to get it working. Using the provided rk322x-4.4 dtb file result of bricking my armbian install. My main goal here is to get that kvmd (pi-kvm port for armbian) working with rk322x.

I wish this was the case but as soon as armbian is installed on emmc, any image in the community repo from github do not boot the SD card first, for it to boot to sd card, I need to short that maskrom to ground. but for some reason, the old images does actually what you said, it boots to sd card first before anything.

this is expected specially for eMMC models unfortunately. its still possible to boot multitool after the emmc install but you need to find out how to put the board to maskrom mode. If you have SD card inserted to the board and and you perform maskrom, it should boot to SD card.

well you also need to know how to put the board in maskrom mode, with eMCP boards, this can be very challenging to do. I learned this in a hard way. Board bricked due to for some odd reason, it kernel panicked during emmc install process. and that managed to brick the bootloader as well. luckily I easily found that out by shorting a capacitor near the eMCP module, that basically put the board in maskrom mode. rockchip based tv boxes usually have these maskrom test pad placed somewhere in the board but amlogic tv boards is just bad. for people who wants to run armbian on tvbox board, just use the SD card/USB, the emmc install is just too risky.

while you can do a supervised install of Home Assistant on this box, I recommend getting a 2GB RAM variants specially if your going to run esphome to compile the firmware, 1GB RAM will literally crash the box during firmware compilation, all of that because of the very limited 1GB RAM. Else, if you can run HA without esphome, it works fine. Make sure to use a high endurance SD card as your storage for all the database logs, configurations. etc... just spare the eMMC for system use. Heck there are times that its actually much better to run armbian on SD card with home assistant because eMMC on these cheap boxes are really slow, specially the eMCP variants.

TV Box Status Information Template Version 1.0 TV Box Name: MXQ Pro 4k 5G (fake 16GB RAM/128GB ROM) CPU: Allwinner H3 Armbian build file name: Armbian_21.08.1_Orangepipcplus_focal_current_5.10.60.img.xz / Armbian_21.08.1_Orangepipcplus_buster_current_5.10.60.img.xz (both works) DTB file used: <none> Kernel Version: 5.10.60 Distribution Installed: focal and buster Working Ethernet (Yes/No): yes Max Ethernet Speed that works (100/1000): 100M Does wifi work (Yes/No): yes Does bluetooth work (Yes/No): not available Does HDMI audio work (Yes/No): yes Additional Comments (provide any additional information you feel is important): all other functionalities for Orange Pi PC Plus is not available (eg OTG function of USB and no GPIO). You can also run "nand-sata-install" command to install armbian to emmc, works fine, no issues.