NicoD

It seems to me like outreach efforts over the years (by people like @NicoD, etc.) have been putting us on the map.  I also tried to help get the word out on last release announcement, which ended up being picked up / re-posted more places than ever before (including LWN, Tom's Hardware, r/linux, etc.) which I think probably helped, too.

https://imola.armbian.com/archive/rock64/  ???

Me, me meeeeee

We have community member in France who needed an RPI3 for $dayjob.  They found one and dont need one.
 
But it turns out @NicoDhas some RPIs for sale and more.
 
Help support Nicod and channel by purchasing all the crap in his office so he can clean up his camera angles !   😂😂😂

Hi all.
In my latest video I make an Armbian Build server out of my old x86 PC. And I set up an extra Odroid HC4 as NAS with the old hard drives from my PC.
I hope you'll like it, greetings.
NicoD
 
 

Take care of yourself and those around you. Best of luck. These things can wait. Cheers.

Not AFAIK, and also ISP camera support was planned but I am not sure of the current status. I think those are the two main points why someone would like to stay using legacy.
 
I wanted to do some standard packages for all distros in mainline, but I have been overloaded since some time ago, and I am not sure when will I be able to have a look at it. I will announce if it becomes ready.

Is there any chance to get access to the gpios on the pin header again?
 
In /sys/class/gpio only two "banks" are listed "gpiochip378" and "gpiochip497". From searching around the net, I think that gpiochip378 is for configuring HDMI and gpiochip497 only has 15 entries. I'd also expected to find the gpios in "gpiochip0" as on other platforms.
 
Was this just an oversight in the device tree, when moving to a newer kernel or is it left out on purpose?
 
P.S.: for me it's not required to access the gpios via /sys/class/gpio, any method to write to pin 40 (aka RasPi gpio21) would work for me.

@NicoD was looking for a video thumbnail just the other day in fact.  Maybe you guys can eventually link up and do some collaboration?  Besides other things mentioned.
 
Thanks for reporting back.  Don't worry, we all come and go.  I disappear for weeks and months some times.  We all do what we can.  Cheers!

Hi all.
In my latest video I test the new Armbian 22.02 images on RK3399.
I use the NanoPi M4. But it should be about the same for other RK3399 devices.
 
 

Long story short.
Jammy xfce 5.16 performs better. And has the better performing browser.
Focal xfce 5.15 firefox is not HW-acc. Chromium is, but performs badly. Also bad blender result. Not all cores are used to the max. I've never seen this behaviour.

So I would use the Jammy xfce 5.16 image. But I'm still using an older image that work. So I'm not upgrading.
Greetings, NicoD

This is not so much a 'Tutorial' as it is an overview (and/or starting point for further research) of some things to consider when setting up a file server, some in general and then some more particular to SBC.
 
In the simplest case, you could attach almost any drive to almost any board, by any number of ways, and you have yourself 'a file server.'  However with even a small amount of effort, there are so many better ways to do things nowadays.  We have a lot more interesting hardware choices, advanced filesystems, etc. and so those are mostly what I want to talk about.
 
But first, some context.
 
Dedicated distros vs simple directory sharing
 
Personally I am not a fan of dedicated distros like FreeNAS, OMV, etc. as I consider them to be too 'heavy weight' and single solution specific.  I mean, if you need some/all of those features, or you like them or whatever, then great, use them.
 
However, a 'file server' is one of the simplest use cases of a 'server' and I am sure one which almost everyone buying a SBC will do at some point.  IMO, all one needs to do is simply share some folder(s) via either NFS (if your network is mostly GNU/Linux machines) or Samba/SMB (if your network is mostly Windows machines).  And that's it, you're done!  Simple, lightweight, and using standard protocols (well, a little less 'standard' in case of Windows, but I digress ).
 
You could also add any of the software included in the 'all in one' solutions in first paragraph on a 'piece by piece' basis, if/when you need them.  Personally I am more of a fan of starting small (vanilla Armbian base) and then adding things you need one by one.  But you are of course free to do whatever you want.
 
Setting any of that up, or debating about it, is considered off-topic for this thread, as there are tons of resources already around the Internet about those things.  So I want to focus on other, (IMO) more interesting, aspects.  You are welcome to make your own thread with a different focus, of course.
 
Important note about hardware RAID
 
RAID, in case you were unaware, means "Redundant Array of Independent Disks."
 
For a looooooong time, I (and I think many others with SOHO NAS perspective) thought that 'hardware RAID was the only proper way to do it' but in the course of researching ZFS I eventually became convinced otherwise.  In fact, apparently, historically 'big-iron' filesystems (Solaris, others) were always run with software RAID in the enterprise as there are a lot of advantages to that.
 
Just think about it.  If your hardware RAID card dies, you need to replace it with exactly the same model, before you can even begin to recover your data.  With software RAID, you just re-connect drives and you are back in business (with ZFS, you can even connect them in any random order, amazing!).
 
In particular if you are using ZFS, hardware RAID controllers are not recommended.  I am not sure how much this applies to other similar software RAID systems, but it would stand to reason that it does (IMO).
 
Hardware controllers are also typically very expensive and proprietary.  Where software RAID uses readily available and inexpensive commodity hardware (while actually increasing reliability).  All of which is why I have become such a big fan of it, whether we are talking about ZFS (which I like) or some other software RAID solution you may prefer instead.
 
Now, with that out of the way, onward!
 
Filesystem
 
Assuming you came to similar conclusions as I did in previous section already, this is where our decision making process really begins in earnest IMO.  As the way I see it, choice of file system will dictate topology, which will in turn dictate choice of hardware (which SBC to buy).
 
Of course if you already bought some SBC, you are in a different boat (and working backwards, from my point of view ).  Anyway, you will have to adapt accordingly (and/or buy different hardware).  However, if you are already there, go to 'Historical Overview' section, and maybe you can find some solution there which will work with the hardware you already have.
 
Now, back on track, we are really lucky nowadays, thanks to F/LOSS, to have some industrial grade, software based filesystems available to us mere mortals! 
 
I like ZFS, but certainly, opinions will differ.  Some people like btrfs, in fact I got into a lengthy (but IMO informative) debate with @tkaiser about that.
 
Then there are other distributed things like Ceph (and others) which I will admit to knowing less about.  If you do, kindly add your thoughts to the thread when you have a moment.
 
Point being, hardware setup for someone like me (using ZFS) or even someone using btrfs will be perhaps quite different than someone using something distributed like Ceph.  Just keep that in mind.
 
Historical Overview (SBC Hardware)
 
I want to cover some of things which came before, as I think they are relevant to understanding where we are today.
 
In the beginning, there was darkness.  Wait, let me fast forward a bit. 
 
I will start with the creation of Armbian.  Which happened, in fact, because Igor was trying to set up a file server on a cubietruck.  True story (and like I said, you are not alone, this is a common use-case)!    Anyway, many of us bought (A20 based) cubietruck back then, because they sold a small power adapter board which made this easy and they also had a SATA connector right on the board.  I think they were one of first to do this in fact (I could be wrong).
 
After that, a lot of us used (more powerful Samsung Exynos5 based octo-core) ODROID-XU4, along with a good quality USB to SATA adapter with UASP.  That one in particular was recommended by tkaiser a long time ago, however -- as of time of writing this post -- PINE64 still sell it in their store(!).  And it may be an 'okay' solution if you have some (especially, USB3 capable) board laying around that you just want to use.  Some people are still using this today.  But we have a lot better options now.
 
Then RK3399 came on the scene.  Which was very exciting, because these support not only PCIe, but they are also 64-bit (which is required for ZFS).  Unfortunately, it took literally years for these to become really stable.  Lucky for you, this is all in the past by now.  And so, currently, many people will probably recommend RK3399 as a file (or other) server.
 
There are a lot of other boards out there, which I do not have as much experience with.  But I also try to note only historically significant developments here (at least the way I see them).  If you have any to add, please comment below or contact me somehow (PM or IRC) and I will edit this post and add them.
 
Usage (other than file server)
 
As I already stated, almost any cheap board can be a (minimal) 'file server.'  From that point of view, more powerful boards (like RK3399, or others) are overkill.  However maybe you want better throughput.  Or more disks.  Or, like me, you want to run advanced filesystem like ZFS (also with more disks).
 
Another thing which happens is that, once you handle the simple case of serving files, before you know it you will probably want to start doing more than that.  You may already have some more demanding requirements in mind beforehand.
 
For all these reasons, a slightly more powerful (and more expensive) board may be a better choice, as you will not be limited in the future.  But if you are very sure about your needs and wants, and have perhaps other boards on your network to handle processing intensive tasks, this may not apply to you.  Just something to consider.
 
Hardware Recommendations (RK3399 based)
 
For reasons mentioned at end of 'Historical Overview' section, many of us are fans of RK3399 based devices nowadays.
 
Within this subset, you will get a lot of opinions.    I know because I spent literally years asking people (including developers), while I was waiting for RK3399 to mature.  Some developers think certain vendors make crappy hardware (and maybe they are right).  Or they prefer the boards they know and develop on (naturally, IMO).  Some vendors support the project a lot more than others (PINE64, notably, do not support Armbian at all to my knowledge).  So you will have to do some amount of your own research, and form your own opinion here.
 
I don't want to discount any of the above criteria too much.  However, in the end, at least for me, one criteria bubbled to the top.  And that was direct PCIe (or SATA) support.  Since we are talking about RK3399 here, this means PCIe support.  Which of course is in the SoC, but that is not what I am talking about.  I am talking about putting a standard PCIe physical interface directly on the board.
 
This way, you can buy any standard cheap/dumb PCIe to SATA adapter card.  You can keep spares.  You will be able to obtain them for the foreseeable future.
 
By contrast, you can certainly rig up your own adapters, cables, etc. from GPIO.  But personally, I find that fiddly and it doesn't strike me as the most reliable.  I know some people are doing this just fine though.
 
Another way, is that many vendors sell some sort of HAT, which provides SATA connectivity.  However I find this short-sighted and -- quite frankly -- self-serving.  What if they are out of stock, or stop making them?  You are out of luck.  Or you would need to revert to the above option (rigging up cables and adapters).  It's good for them selling add-on hardware though I guess -- hence my 'self-serving' comment -- but maybe not the best for you and me in terms of keeping our important data available and up and running, on a long term basis.
 
Therefore I say, skip all of that and go with a board that has a standard physical PCIe right on the board.
 
ROCKPro64
 
And AFAIK, there is only one (standalone SBC) RK3399 that meets that description, which is ROCKPro64.  Of course, I am not the first to come to same conclusion, in fact there is a whole thread where myself and some other like-minded folks discuss using ROCKPro64 as NAS.
 
I say 'standalone SBC', because I almost forgot...
 
Helios 64
 
These of course are no longer made, and Kobol, our once partners, have unfortunately closed up shop.  However they still come up for sale on the forums from time to time (usually in Kobol Club (subforum is no more) but could be anywhere).
 
Here you would be getting a more integrated solution, often including a nice case, for perhaps a bit more money.
 
Some people have had problems with stability though, which I am not sure were ever fully worked out.  As of mid-2024, it seems the community have finally got this device stable.  Which I personally find pretty remarkable, given the circumstances.
 
Having said that, I am sure these devices are only getting harder and harder to come by, especially now.  Not only that, but keeping it that way is always going to require ongoing maintenance, as the Linux kernel (and other parts of the OS) never stop moving forward.
 
Hardware Recommendations (not RK3399 based)
 
ODROID HC4
 
ODROID HC4 was also brought up today, when this subject came up in IRC, by @rpardini as that is what he uses.  This is an interesting alternative to the above, except Amlogic (S905X3) based (like a lot of TV boxes).  Which to me means two things:
 
1. It almost certainly requires blobs.
2. It's probably cheaper than RK3399.
 
Well in fairness ROCKPro64 probably requires some blobs, too.  But somehow I get the impression that Amlogic are really obnoxious with their blobs, and I am not a fan of them as a company because of this.  Surely a developer will need to correct me here. 
 
Anyway, I am not sure how it compares in processing power.  I suspect less than RK3399(?).  However for media transcoding, it may actually be better (perhaps hardware decoders(?), speculation on my part).
 
Also for simple 'file server' use-case, in particular with Ceph or something like that, it becomes more interesting IMO.  Again, quoting rpardini from IRC today: "scale out, not up."
 
Future
 
There are newer SoCs, like RK3566 and others.  At this time, they are a lot like RK3399 was early on.  Very exciting, but not able to realize their full potential due to lack of (software/Linux) development.
 
The consensus among developers seems to be that RK3566 development should go faster/easier than RK3399 development, because of all the ground work that was laid in the course of the latter.  Maybe that's true, but we are still talking about some time.  Maybe less years, but still significant time.
 
If/when this changes, I will try and remember to update the post.  Feel free to ping me by posting, I should get notified.
 
Others?
 
Possibly anything in NAS category.  Which I mostly covered already (above, in more detail) but can always change in future.
 
Certainly I forgot (or don't know about) some others.  I have shared what I learned from my research the last several years while looking for solution for myself.  However I do want to make this a more general resource that we can all point to, so please discuss, and I will be happy to edit this post later on and add relevant info.
 
To clarify, I am not talking about 'any SBC which can be made into a file server' which is almost any of them, but rather particular hardware which is interesting for some specific reason(s), especially currently (or perhaps historically, which I would add to that section).
 
Cheers!
 
 

And here the video I made about the new release.
 

I came across these recently and found several interesting things within, so thought I would share them.
 
I debated posting this in Development, but wanted anyone to be able to see and reply to the thread.
 
Anyway some parts I felt were important enough that I actually took down some notes and quotations, which I will include.
 
Open drivers for Arm GPUs
This looks like it was presentation LVC21-318 at  Linaro Connect '21 on 2021-03-25.
 
Video is available at above page, and also on ThemTube here.
 
I found this a fascinating presentation.  Alyssa contrasts the (proprietary) 'before times' with current situation which is apparently quite different.  In fact, I was quite surprised to learn that:
 
 
She then goes on to give 3 case studies, one of which was VideoCore, where I was more than a little surprised to learn that Broadcom at some point actually hired someone to work on their F/LOSS driver.  Now this was only after that guy was well into his own (night and weekend) reverse engineering effort, followed by a lot of public pressure, but still.  End result apparently is that this driver is now shipping in production RPi 4.
 
Next case study was about Freedreno.  I will quote my favorite part from here:
 
 
Of course being firmly in the camp with the 'looney Free Software types' myself, this comment warmed my heart quite a bit. 
 
Finally she gives the Panfrost case study, where she points out that things are apparently moving away from the 'reverse-engineering underdog' model, and:
 
 
And so reverse engineering is apparently no longer needed.
 
Apparently this is the driver that ships in PineBook Pro for example.
 
Of course I must admit to being more than a little bit (pleasantly!) surprised at all of this.  And also starting to soften my stance towards Broadcom (just a little though, lol). 
 
If you are the least bit interested in any of this, I can highly recommend watching the full presentation.  It's only 19 minutes long, anyway, but I personally was riveted the entire time.
 
The Open Graphics Stack
I think this presentation was given at Embedded Linux Conference '21 on 2021-09-29.  So, about 6 months after the above.
 
But honestly I came across it on ThemTube here.
 
In the beginning, she makes a good point about the tension between embedded devices with perhaps 20 year life cycles, and devices with proprietary drivers which may be EoL in 5 years, and how this tension can be alleviated by using F/LOSS drivers.
 
But what got my attention the most was:
 
 
She then goes on about details of particular platforms (including x86, ARM, etc.) and then finally:
 
 
Which is a quite bold (and again, pleasantly surprising) statement IMO, but then again I do consider her an authority on the subject.
 
After that she goes into quite some detail about the nuts and bolts of all the various parts of the stack, which you may or may not be interested in watching as much.
 
 

And here the video I made about the new release.
 

And here the video I made about the new release.
 

Hi @yang and @TRS-80,
 
If it's not too late, I'd like to pick up OrangePi Zero Plus2 H3 as a maintainer.
I have two Plus2 boards with expansion boards, and can to test for releases and troubleshooting.
Don't have much experience in SW development, but have some as Linux basic admin.
 
As an experiment built an image for "BRANCH=current KERNEL_ONLY=no BUILD_DESKTOP=yes RELEASE=bullseye", all seems to work: http://ix.io/3Qdm.
I like the board and would like to keep it in the game.

Maybe @NicoDwants to test those.

You are violating the startup order, this is a test version and it does not contain startup scripts from the desktop. It needs to be run as an independent software. After booting the system, DO NOT log in to the desktop. Switch to any console (Ctrl+Alt+F1). We log in as a user (but it's better to use root, then there will be more control options) and launch kodi. The problems of a long startup may be related to new KODI packages or the latest version of the image with the 5.10.88 kernel (you can try earlier versions from yandex disk, there is a version with the 5.10.62 kernel). I have a system with the first versions of these packages, everything works quickly with them and the splash works.
 
I recommend using the correct package installation order.
 
 su -
 apt update
 apt install <full_patch>/kodi-mainline-bin_18.9-final-18.9bullseye0armbian1_arm64.deb
 apt install <full_patch>/kodi-mainline_18.9-final-18.9bullseye0armbian1_all.deb
(installing additional packages if they are needed)
 reboot

@balbes150I'm unable to make it work.
I downloaded the Armbian_21.11.0-trunk_Station-p1_bullseye_current_5.10.88_xfce_desktop
Downloaded the deb files. https://users.armbian.com/jmcc/packages/kodi-mainline/arm64/
First tried with only the kodi-mainline-bin and kodi-mainline files
 
sudo apt install libcec6 libfmt7 libfstrcmp0 libgles2 liblirc-client0 libmariadb3 libtinyxml2.6.2v5 libmicrohttpd12 libpcrecpp0v5 libpython2.7 sudo dpkg -i kodi-mainline-bin_18.9-final-18.9bullseye0armbian1_arm64.deb sudo apt install libaacs0 libboost-python1.74.0 libshairplay0 libxxf86dga1 python3-bluez python3-gattlib python3-simplejson x11-utils sudo dpkg -i kodi-mainline_18.9-final-18.9bullseye0armbian1_all.deb When I try to start Kodi it kind of crashes the desktop. Mouse and keyboard stop working. Can't do anything. It does stay on the desktop, and the desktop is still running. I tried with a terminal window with htop running and htop was still running. But I was unable to do anything. Also couldn't switch with ctrl-alt-Fx
This is the same with either sudo kodi or without.

I then also tried with installing all the deb kodi files. But no change here.
I tried again with a fresh install and the same.
Did I download the wrong image? It is an older image, but the most recent 5.10 bullseye as you said.

Some other things. It takes a long time before it starts booting. About a minute after power on you see the first things on screen. And the led isn't on. It blinks one time when boot initiates. But then it stays off.
I think I remember this was working in the past.

I also notices the black spots in windows that other people talk about. Seems a graphical glitch, composer or GPU. I don't have that on my M4 with 5.14(old image).
And Firefox also crashed out of the blue. Just to let you know. Cheers.

You are behind the current state of rk3399 support. Now there is already support for HW GPU and VPU. I'm testing this on Firefly Station P1 (rk3399), everything works fine (kernel 5.1x), including 4k.
 
 
info glmark2 for Station P1
 
https://forum.altlinux.org/index.php?topic=36166.msg364846#msg364846
 
 

Hi all. In this video I show how to install Open Media Vault on your SBC with Armbian Buster.
I've used the Odroid HC4, this is the same for any board you'd like to use. 
Here my video.
Greetings.
NicoD

Hi,
Many thanks for your thorough and informative review. In a difficult year, and with two of my development machines failing, I rashly bought 3 4Gb Pi-400s and 2 of the pi keyboard/hub units.
I too, had problems with under-voltage on both machines. Fortunately, I have installed an uninterruptible DC 14v ring in my house, and use DC-DC converters to step the voltage down to around 5.3, for these machines, which as you have noted, gets around the problem. As for the keyboard? All 5 of the keyboards have at least one consistent problem - 'h' key, and lesser so, some of the number keys.
By far the worst problem, and one which you haven't mentioned, is during editing - particularly cut & paste using the mouse. I'm using 'Buster', and no editor is safe, whether it is geany, Thonny, Visual Studio or editing a WordPress post. 'cut sections get dropped into inappropriate places in a file or in BOTH files if I'm transferring from one to the other. The only 'safe' option is VIM, which points very strongly to the mouse and/or it's driver.
raspberry.pi.org have apparently lost the plot. There are other issues, especially with the Raspian OS'es. The last decent version of Raspbian was jessie. Everything after it is a mess.
My main development focus is on monitoring and control, and this includes website development, backend server, plus wifi-connected slaves such as the pi-zero, and latterly WEMOS D1.
Your review has prompted me to do two things: 1 - try Manjaro on thhe Pi400's, and 2: examine using Armbian on an Odroid XU4 which is currently unemployed.
Many thanks again NicoD.
 

Why don't you use flatpak?
I used it in my RK3399 board and it runs great. I got the latest release of PPSSPP on Armbian Focal.
But because the lack of OpenGL ES 3.2 and Vulkan Driver, a demanding game like God of War Chain of Olympus only get around 16-18 fps (2x res, autoframeskip).
For a middle game title it runs almost full speed. Like DragonBall Z Shin Budokai 60 fps, Daxter 30 fps with the same setting (2x res, autoframeskip)
sudo apt install flatpak flatpak search ppsspp flatpak install org.ppsspp.PPSSPP I also got Dolphin & Flycast Emulator with quite great performance from flatpak. But maybe dolphin need the driver for OpenGL ES 3.2 or Vulkan to get a higher framerate. Currently the only two-emulator that don't work from apt package or Flatpak are N64 Emulator and RetroArch (Installing core is disabled).

Yes, after running your script manually in Armbian Focal. I have a lot of dependencies conflict especially from armhf package vs. arm64 package. As a result almost all my 64bit program that has dependencies conflicts were removed from the system.
 
After a while, I looked at how TwisterOS do this beautifully without any dependencies conflict. When building Box86 in TwisterOS, I just realized that TwisterOS only need this "arm-linux-gnueabihf" library files. Then I copied this library and pasted them to my Armbian Focal in /usr/ folder.
 
After that I fixed all dependencies conflict by using "sudo aptitude install" and remove all armhf package that has conflict.
 
Magically, all the conflicts were gone and as what I suspected that Box86 could compile successfully even without armhf package dependencies.
 
Now I am very happy because I can run both Box86 and Box64 without interfering each other. even wine32, wine64 and winetricks are working.

I'll say that this Library Method is better than the Schroot Method. But I am not sure for some distributions that do not support Multiarch like Manjaro, whether this Library Method is working or not. If it isn't then they have to stick with the Schroot Method.
 
I am not good at github and scripting. I trust you, maybe you can try first. If it works, then you can update the armbian-config on Github with the command that I wrote.

Many Thanks @NicoD

Dear All,
I just want to share my workflow of successfully installing Box86-Box64, Wine32-Wine64 and Winetricks on Arm64
Big thanks to @NicoD for sharing his source code of Armbian-Gaming. I modified some of his code to be used in Armbian Focal (or any Arm64 distro) and fix the armhf dependencies issue by using the "arm-linux-gnueabihf" Library from TwisterOS. I also used some of Box86 Manual. So many thanks to all of them.
 
Ok Let's Start:
 
1. Add armhf multiarch
sudo dpkg --add-architecture armhf sudo apt-get update 2. Install dependencies for box86 & box64
sudo apt-get install git cmake cabextract gcc-arm-linux-gnueabihf libc6-dev-armhf-cross
Then download these "arm-linux-gnueabihf" files and extract them on folder /usr/
(Alternatively, you can manually copy paste the "/usr/arm-linux-gnueabihf" folder from TwisterOS and transfer it to your arm64 OS. This file contains dependencies for Box86)
*NOTE: I split the files because Armbian site doesn't allow me to upload more than 1,5MB.
arm-linux-gnueabihf.7z.001 arm-linux-gnueabihf.7z.002 arm-linux-gnueabihf.7z.003 arm-linux-gnueabihf.7z.004
 
3. Compile box86 for general ARM64 board (read box86 manual for more info about your board)
cd git clone https://github.com/ptitSeb/box86 cd box86 mkdir build cd build cmake .. -DARM_DYNAREC=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo make -j3 sudo make install sudo systemctl restart systemd-binfmt cd 4. Compile box64 for general ARM64 board (read box64 manual for more info about your board)
cd git clone https://github.com/ptitSeb/box64 cd box64 mkdir build cd build cmake .. -DARM_DYNAREC=ON -DCMAKE_BUILD_TYPE=RelWithDebInfo make -j3 sudo make install sudo systemctl restart systemd-binfmt cd 5. Restart your Computer
6. Install Wine32 & Wine64 (Merged is the best option, and please follow the sequence accordingly. Currently at the time of writing, wine 5.21 & Wine 6.0.2 have the best support from Box86-Box64. You can also try a different version of wine if you want)
    #Wine 5.21
cd cd ~/Downloads wget https://dl.winehq.org/wine-builds/debian/dists/buster/main/binary-i386/wine-devel-i386_5.21~buster_i386.deb wget https://dl.winehq.org/wine-builds/debian/dists/buster/main/binary-i386/wine-devel_5.21~buster_i386.deb wget https://dl.winehq.org/wine-builds/debian/dists/buster/main/binary-amd64/wine-devel-amd64_5.21~buster_amd64.deb wget https://dl.winehq.org/wine-builds/debian/dists/buster/main/binary-amd64/wine-devel_5.21~buster_amd64.deb dpkg-deb -xv wine-devel-i386_5.21~buster_i386.deb wine-installer dpkg-deb -xv wine-devel_5.21~buster_i386.deb wine-installer dpkg-deb -xv wine-devel-amd64_5.21~buster_amd64.deb wine-installer dpkg-deb -xv wine-devel_5.21~buster_amd64.deb wine-installer mv ~/Downloads/wine-installer/opt/wine* ~/wine rm -rf wine-installer cd     #Wine 6.0.2 Stable
cd cd ~/Downloads wget https://dl.winehq.org/wine-builds/debian/dists/buster/main/binary-i386/wine-stable-i386_6.0.2~buster-1_i386.deb wget https://dl.winehq.org/wine-builds/debian/dists/buster/main/binary-i386/wine-stable_6.0.2~buster-1_i386.deb wget https://dl.winehq.org/wine-builds/debian/dists/buster/main/binary-amd64/wine-stable-amd64_6.0.2~buster-1_amd64.deb wget https://dl.winehq.org/wine-builds/debian/dists/buster/main/binary-amd64/wine-stable_6.0.2~buster-1_amd64.deb dpkg-deb -xv wine-stable-i386_6.0.2~buster-1_i386.deb wine-installer dpkg-deb -xv wine-stable_6.0.2~buster-1_i386.deb wine-installer dpkg-deb -xv wine-stable-amd64_6.0.2~buster-1_amd64.deb wine-installer dpkg-deb -xv wine-stable_6.0.2~buster-1_amd64.deb wine-installer mv ~/Downloads/wine-installer/opt/wine* ~/wine rm -rf wine-installer cd  
7. Create Symlink to Wine
sudo ln -s ~/wine/bin/wine /usr/local/bin/wine sudo ln -s ~/wine/bin/wineboot /usr/local/bin/wineboot sudo ln -s ~/wine/bin/winecfg /usr/local/bin/winecfg sudo ln -s ~/wine/bin/wineserver /usr/local/bin/wineserver sudo chmod +x /usr/local/bin/wine /usr/local/bin/wineboot /usr/local/bin/winecfg /usr/local/bin/wineserver 8. Setting Wine32 Folder in ~/.wine (set win32 as wine default, because currently winetricks doesn't work in win64. I would gladly use win64 as my default setup only if winetricks works in win64 in the future).
 
WINEPREFIX=~/.wine WINEARCH=win32 wine winecfg 9. Setting Wine64 Folder in ~/.wine64
WINEPREFIX=~/.wine64 WINEARCH=win64 wine winecfg 10. In Home Folder Create alias in .bashrc (to make shorter command for wine64)
cd nano .bashrc        --> enter this command
alias wine64="WINEPREFIX=~/.wine64 wine"       --> then save (ctrl+x, choose yes)
      --> then logout & login
 
11. Installing & Running 32bit Windows app
wine uninstaller wine /File/can/be/drag/and/drop/32bit.exe 12. Installing & Running 64bit Windows app
wine64 uninstaller wine64 /File/can/be/drag/and/drop/64bit.exe  
13. Install Winetricks
sudo apt-get install cabextract -y cd ~/Downloads && wget https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks sudo chmod +x winetricks && sudo mv winetricks /usr/local/bin/ 14. Using Winetricks (ex: Corefonts & Dotnet 4)
BOX86_NOBANNER=1 winetricks BOX86_NOBANNER=1 winetricks corefonts dotnet40 15. Creating Wine Desktop Launcher
Now create a launcher in the desktop with this code in the command section:
wine explorer /desktop=shell,1280x720 explorer.exe  
As an alternative, I personally like explorer++ mainly because of its GUI and additional feature compared to the original wine explorer. You can download it from here: https://explorerplusplus.com/software/explorer++_1.3.5_x86.zip and then extract it, and then rename to "explorer++.exe" (with small e, not capital E), then copy-paste it to the ~/.wine/drive_c/windows. Then create a launcher in the desktop with this code in the command section:
wine explorer /desktop=shell,1280x720 explorer++.exe  
 
 
**NOTE:
- With this setting I am able to run Box86 and Box64 without having dependencies conflict between armhf package and arm64 package.
- I used the win32 as my default wine. Alternatively you can also use win64 as your default ~/.wine setup. It is up to you (In fact, by default it will create win64 setup in your ~/.wine folder).
- For RK3399 users, you can use these scripts to Install and Update Box86 & Box64:
install_box86.sh install_box64.sh update_box86.sh update_box64.sh
 
I hope this could help somebody out there. Have a Nice Day!
RNA