Werner

Since when its Armbian problem if your computer is infected by malware?

I haven't build Armbian for some time now, I'm just the guy who works on upstream U-Boot and Linux support for H616. I build all components separately and then manually put them together.

To get rid of all the tails that are now on your SD card, I recommend doing a clean check. Download the image from the link, unzip it and burn it to the SD card. Do not change anything on the SD card, connect to the device and check the launch.
 
https://users.armbian.com/balbes150/firefly_station_p1/
 
Model Fyrefly Station P1 = ROC-RK3399-pc-plus + eMMC module.

You can also check all the certification and conformity document for the PSU we provide with Helios64 : https://wiki.kobol.io/helios64/docs/#psu
 
We have designed Helios64 with safety and protection in mind... no shortcut.

You cannot. Happens very rarely but sometimes electronics in general can end up in magic smoke or even worse.
 
Best you can do is to look ahead and think about what would happen IF. Are flammable objects close by? Does the device lie on a wooden table? Are other devices close by that radiate heat and cause the concerned devices to heat up additionally?
How is your local public power supply? Do voltage spikes occur often? If so think about installing devices in the building connection that prevents such spikes from hitting your stuff. Kind a lightning conductor but way more sensitive against voltage above rated.
 
Try to look for more general information about fire hazard prevention. Maybe ask your local firefighter station.

Good news.
SATA works on mainline focal 5.10.6.
Also my 5Ghz wifi dongle works out of the box. I've got everything I could want. After that ordeal I'm so happy to have things working as should

There was actually an attempt to bring Armbian and Kali together and release it as images for SBCs. However the project is not very active. I guess they underestimated the effort needed to put in for maintenance
https://github.com/GoVanguard/karmbian

I'll continue to help with PBP..   As you all are familiar my work usually comes in bursts..  But yeah i'd like to build kind of a specific community up for it.. almost wonder if its worth a subforum under RK3399 or osmething.

I'm getting a PBP bare motherboard that i can use for the bare metal testing of liek uboot etc... and @Rich Neesehas a PBP coming in the mail
 

Sorry, my USB-C to DP/HDMI converter is broken, and I have no plans to make room in my budget for a new one, at least for now. So I cannot debug or fix this problem.
 
TBH, I am very surprised there is people using the Helios64 as a desktop device, I always considered it a NAS

Here is fixed v2 version: https://github.com/jernejsk/u-boot/commits/h616-v2
 
Note - it's not finished yet, so it will still change (force pushes).

There was actually an attempt to bring Armbian and Kali together and release it as images for SBCs. However the project is not very active. I guess they underestimated the effort needed to put in for maintenance
https://github.com/GoVanguard/karmbian

We will have some spare stock to sell soon.
Yes we ship to China.
 
As for the next batch we will announce our plan soon.

If it was a cheaper board I'd do that. This is one of the most expensive I've bought. PSU is also a 15V 60W brick. Adds to the cost.
I rather save my money to buy an Odroid Go Super next month. I never wanted a handheld so much, except when the Gameboy came out maybe.
HC4 also suddenly became a gaming rig with 500GB of retro games on HDD. Too many games, I can't find the ones I want since thousands to browse thru.

I also got my Odroid HC4. Doing my first tests. USB seems very buggy with the Ubuntu Mate 20.04 from Odroid.
This seems better with Armbian focal legacy desktop. Tho there no sata is found, while that does work with the Odroid HC4 Mate image.
I'll try a lot more images to see if/what difference there is.
Haven't checked any mainline yet.

It does seem to have performance issue's when overclocked(2Ghz/2.1Ghz). It sometimes performs worse than with default clocks. Weird.
I'm a bit surprised about how good it is for gaming.
I like it a lot, but it did cost me a lot. Tho also bit my own fault.
I first bought it from AmeriDroid. It was stuck in transit for a +month. So I got my money back and bought another at a Belgian seller. A lot more expensive. A day after I got my HC4 from the Belgian seller the one from AmeriDroid arrived. If only I had waited a few more days I'd have saved about 40euro. Buying from Hardkernel would have been even more cheap I'd guess.
I may send it back to AmeriDroid without fees. Luckily. I really wanted a HC4, but 2 is too much

@hannah You have a lot to learn about armbian on TV boxes and dtbs and kernels.  I plan to write a longer response this weekend when I have more time, but for now the short answer to your most specific question: no audio over hdmi is that you need to use a different dtb file.  Your box is s905x3 based (i.e. the sm1 architecture).  You are using based on what you reported a dtb for the s905x2 (g12a).  While much is the same, some things are also different.  Now what you may find is that if you use one of the very few available sm1 dtbs (I use and have only tested meson-sm1-sei610.dtb - the sei610 is the reference board for the s905x3 chip) that other things you have working on your current install (like wifi) will probably no longer work.
I believe you have likely already read the following: https://forum.armbian.com/topic/16407-please-read-first
as it was referenced in the last thread you started.  The current state for armbian on TV boxes is limited especially for amlogic cpus.  There are many reasons for this and that deserves a longer explaination of how dtbs and kernels interact and the overall goals of the armbian project.  (and how they differ from other projects out there like coreelec you reference above).
 
But I have already spent an hour of my day (we are all volunteers around here) setting up a test system to verify that audio does indeed work on a TX3 X3 box (as I thought it did, but because I don't normally run desktop environments as the current state of support really isn't working well yet, I didn't have an environment I could quickly test).  What I did just do is downloaded a clean copy of the 2020-10-14 balbes build of focal 5.9.0 desktop, used the meson-sm1-sei610.dtb and the u-boot-s905x2-s922 uboot file copied to u-boot.ext, booted and played the test.mp4 file and had correctly working audio via hdmi.  I then changed the dtb to meson-g12a-x96-max.dtb, which I believe you are using, rebooted and had no audio.
 
What I don't understand is that if you have read the Please Read First post, why you would post four posts in this thread within a day, seemingly demanding support for the 2 or 3 volunteers around here that monitor this forum?  Especially when you are asking about things like bluetooth, wifi, etc on the amlogic platform that we say you shouldn't expect to work, and if they do you are lucky.

You can use "dwc3-0-host" overlay in /boot/armbianEnv.txt to enable it now - it switches to port from otg to host mode.
 
overlays=dwc3-0-host  
I will prepare some corrections to the device tree soon and will enable the host by default to make it consistent with vendor's configuration.

@aprayoga will help answer in details @retrack question on what is the blocker right now to have WoL working on Heliso64. But in a nutshell is because suspend mode is not supported yet properly.
 
I think we all understood that the question is addressed to us Kobol team, no one was expecting the core Armbian team to follow up on this.
So let's move on and not hold any grudge against each other...we are only one to blame to not have answer quickly enough this thread.
 
@Igor Maybe we could delete this exchange above, put that being us.

Aight, I will lock this then.
If you have any further Helios64 to sell by chance you can then use our brand new section for this purpose: https://forum.armbian.com/forum/55-market-place/

Confirmed:
 
Armbian 21.02.0-trunk Focal with Linux 5.9.16-rockchip64
 
The one in the middle works:
 
[ 922.891909] usb 6-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd [ 922.913139] usb 6-1: New USB device found, idVendor=090c, idProduct=2000, bcdDevice=11.00 [ 922.913162] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 922.913178] usb 6-1: Product: Intenso Flash Line [ 922.913193] usb 6-1: Manufacturer: SMI Corporation [ 922.915257] usb-storage 6-1:1.0: USB Mass Storage device detected [ 922.917468] scsi host0: usb-storage 6-1:1.0 [ 922.969173] usbcore: registered new interface driver uas [ 924.022772] scsi 0:0:0:0: Direct-Access Intenso Flash Line 1100 PQ: 0 ANSI: 6 [ 924.024647] sd 0:0:0:0: [sda] 245760000 512-byte logical blocks: (126 GB/117 GiB) [ 924.025007] sd 0:0:0:0: [sda] Write Protect is off [ 924.025029] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 [ 924.025382] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 924.033101] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 924.058523] sda: sda1 sda2 sda3 [ 924.060440] sd 0:0:0:0: [sda] Attached SCSI removable disk  
The left one (corner) does not:
 
[ 463.509617] usb 6-1: USB disconnect, device number 2 [ 463.515097] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 463.515366] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00  
 
 
 

Just make a PR to the master and try not to create special things for this board such as dedicated kernel config or similar. Kernel is shared, u-boot can be per board.
 
If it's done the way that it can't break anything, we accept it. config/board/thisboard configuration must have .CSC suffix that its clear we don't maintain it.
 

Thank you!  Welcome to join. It's a lot to do and we are always short on people.

A build system that gives you superb option to boot your hardware with a specially prepared kernel and its not called Buildroot or Yocto. I would kill for having x86 Armbian when preparing our Threadripper server. Or my desktop machine - both are based on latest hardware which doesn't just work OOB on Ubuntu or Debian based distros, Arch is too reckless on the other hand. Just about every kernel out there sucks and preparing custom build with userland of choice is what we have achieved here. I would also use Armbian on other x86 builds, if this would be simple, since those possibilities and has important tweaks that are ignored in generic distros such as Debian / Ubuntu. 

If anyone is willing to bring x86 build support to the armbian build system and maintain it, it wouldn't be that stupid after all.

Typo: "roperly" power your board

Yes it works on version 13.0-CURRENT, and there is OpenZFS in it.

Here is the boot log. 
Boot.log
 

 
Welcome to FreeBSD!
 
 

I can confirm that it fixed the issue here.   You guys rock!
 
Thanks, Eric

I don't see any particular problem installing FreeBSD on Helios64.
It works for me.
The question is - how to properly test this?