balbes150

Throw away this intel shit. use the native build on rk3399. This is faster and without any stupid Trojans in Intel x86.
 
You use the source code from Friendlyelec , they are significantly worse. It is better to use the ones that go for rockchip64-legacy (there are also sources for analog audio 8323\8388)
 
https://github.com/150balbes/build/blob/armbian-tv/config/boards/station-p1.conf#L3
https://github.com/150balbes/build/blob/armbian-tv/config/sources/families/include/rockchip64_common.inc#L51
 
And the kernel config that WiFi works with.
https://github.com/150balbes/build/blob/armbian-tv/config/kernel/linux-rockchip64-p1-legacy.config
 
PS I wanted to create a PR with the change, but so far I have suspended it until we discuss and agree on these changes.

Throw away this intel shit. use the native build on rk3399. This is faster and without any stupid Trojans in Intel x86.
 
You use the source code from Friendlyelec , they are significantly worse. It is better to use the ones that go for rockchip64-legacy (there are also sources for analog audio 8323\8388)
 
https://github.com/150balbes/build/blob/armbian-tv/config/boards/station-p1.conf#L3
https://github.com/150balbes/build/blob/armbian-tv/config/sources/families/include/rockchip64_common.inc#L51
 
And the kernel config that WiFi works with.
https://github.com/150balbes/build/blob/armbian-tv/config/kernel/linux-rockchip64-p1-legacy.config
 
PS I wanted to create a PR with the change, but so far I have suspended it until we discuss and agree on these changes.

i have everything working. i recommend trying really tested images on p1.
 
http://bbs.t-firefly.com/forum.php?mod=viewthread&tid=2781&page=1#pid13344

I never know what to get anyone.  If I'm being honest I have more than a little disdain for how commercialized the holidays have become nowadays.  We were not raised in a materialistic way growing up.  A lot of gifts were socks and other actually useful things like that (which I only appreciate now as I get older ).  Anyway...
 
So when some of the guys shared some pictures of themselves with some Armbian swag in IRC a while back, a little light bulb went off in my head. 
 
So this morning, I went nuts and spent > 400 USD sending everyone in my family some Armbian swag.    I figure, it's a good way to get the word out there to friends and family about a project I care a lot about, while supporting the project a bit financially at the same time.
 
   
 
I don't expect anyone else to spend that sort of money, in fact I am a tight wad and rarely do, myself.  But a coffee mug or something might be nice?
 
I also don't like to rush people (because I don't like to be rushed, myself), however if you are going for delivery before the holidays I would place your order ASAP, maybe even today.
 
One final gotcha, their credit card processor apparently only allow 2 orders per day.  Luckily I had sent orders to other family first, because my third order was denied.  I called their customer support and they confirmed this issue and told me to try again after 24 hours.  So the stuff that is coming here for us I will place that order (again) tomorrow.  I just wanted to give everyone a heads up about that though.

Results of a quick test of the native build using the Desktop version. For tests, I tried to build several options - XFCE \ MATE \ KDE in the "minimum" and "maximum" configuration for Station P1\M1 with the current and legacy core. The "minimal" configuration is an option where no group is selected on the last package selection screen. "Maximum" configuration-all package groups are marked. The build (native) runs without errors and the output is working images. Offer. Add the "standard" options in the settings (the necessary packages are selected automatically without additional user steps), this option is equal in the set of installed packages to the current position (the set of packages is equal to those that are currently installed in DE XFCE master branch). The "maximum" is automatically marked for all the available this DE packages (options). Custom setting ("minimum") when entering it, as now, no packages are marked, the user can, not specify anything, then the output will be the "minimum" version of DE or the user chooses the necessary groups\packages.

Results of a quick test of the native build using the Desktop version. For tests, I tried to build several options - XFCE \ MATE \ KDE in the "minimum" and "maximum" configuration for Station P1\M1 with the current and legacy core. The "minimal" configuration is an option where no group is selected on the last package selection screen. "Maximum" configuration-all package groups are marked. The build (native) runs without errors and the output is working images. Offer. Add the "standard" options in the settings (the necessary packages are selected automatically without additional user steps), this option is equal in the set of installed packages to the current position (the set of packages is equal to those that are currently installed in DE XFCE master branch). The "maximum" is automatically marked for all the available this DE packages (options). Custom setting ("minimum") when entering it, as now, no packages are marked, the user can, not specify anything, then the output will be the "minimum" version of DE or the user chooses the necessary groups\packages.

Results of a quick test of the native build using the Desktop version. For tests, I tried to build several options - XFCE \ MATE \ KDE in the "minimum" and "maximum" configuration for Station P1\M1 with the current and legacy core. The "minimal" configuration is an option where no group is selected on the last package selection screen. "Maximum" configuration-all package groups are marked. The build (native) runs without errors and the output is working images. Offer. Add the "standard" options in the settings (the necessary packages are selected automatically without additional user steps), this option is equal in the set of installed packages to the current position (the set of packages is equal to those that are currently installed in DE XFCE master branch). The "maximum" is automatically marked for all the available this DE packages (options). Custom setting ("minimum") when entering it, as now, no packages are marked, the user can, not specify anything, then the output will be the "minimum" version of DE or the user chooses the necessary groups\packages.

Perhaps this information will be of interest to someone. 
 
https://www.stationpc.com/forum.php?mod=viewthread&tid=109&extra=page%3D1%26filter%3Dlastpost%26orderby%3Dlastpost

Well, I guess I would consider maintaining download links, documentation, etc. and other things you mention as a part of "support."
 
I think you are very lucky to have @SteeMan helping you.  Which I would also consider "support", by the way...  And also why I don't understand the slightly snide / passive aggressive comments like
 
 
directed toward people who are trying to help you.
 
As I said in my first post to you, I can empathize with your frustration, we have all been there.  Please, really stop and consider that for a moment.
 
Because speaking to other members of the community (especially those rare and valuable people like SteeMan who so selflessly contribute their time and efforts to help others) is not going to be tolerated.  Consider this an official warning from a Moderator.  So maybe take a break or whatever, go for a walk, or at minimum think about how you are talking to people, especially those who are trying to help you, before making your next reply.
 
Cheers.

already done.  Igor merged native into desktop the other day.  https://github.com/armbian/build/pull/2404

Merged.

Bugfix v1 was already pushed out:
 
[AR-551] - Update fan configuration, enable network LED and enable UPS timer Updated Helios64, Rockpi 4* images and rockchip64 kernels  
Bugfix v2
 
Let's try to patch other critical things before Christmas. I already addressed ZFS problem on Focal by adding most recent DKMS package, but to solve it also for Buster it requires all kernel recompilation - in case you want to push some late changes, now it's the time. The Beast can handle that in no time  We hopefully fixed Odroid HC4 (don't have HW to test), added KVIM2, DVFS on mvebu will be disabled from now on to secure stability (moving to 5.9.y ?) ... What will fail if we update Allwinner to 5.9.y? Mvebu? Rockchip.hf is ready. 
 
@Myy @TonyMac32 @balbes150 @piter75 @sfx2000@ebin-dev @Heisath@chwe@ning@lanefu@gprovost@aprayoga@5kft @JMCC@karabek@Igor@martinayotte@tkaiser@selfbg@Siraj@jock@going 
 
What else can be squeezed into this mini quick release? Smaller, almost done, things only.
 
I would also like to point out that we are progressing nicely with:

- updated Desktop variant (sits in our main build repository under the branch "desktop"), where also some other general things has been changed. Merge into master is estimated 2/2021, early adopters are welcome. There are other changes, not just desktop.
- native ARM building. Need more testing, but basics are working.
 
Today +7 days?

We recently made some improvements and I hope this will not happen again.
https://github.com/armbian/build/pull/2400

Links to theft and hacking are removed.

Links to theft and hacking are removed.

As far as I understand, both options (kvim1\kvim2) require complete removal of the regular u-boot-2015 from eMMC to run. This is a dangerous approach with serious problems for users. U-boot-2015 AML has a serious difference from RK\AW - it uses a specific solution for writing \ updating firmware in eMMC, which is only available in u-boot-2015. This is the main way to work with firmware on AML. Its absence will cause a flurry of complaints and tantrums from users when they encounter serious problems and start blaming Armbian.

Hi all.
I wanted to put some light on the fact that you now can run some x86 Windows and Linux programs and games on the RK3399 with Box86.

I have a topic about it in my lonely "Gaming on ARM club"
I've made a preview video about it last week.
I've done some further tests. It is just amazing. Plays way better than the RPi4. Tho not yet as many things work.
@Salvador Liébana made prebuild images with Box86 preinstalled, and with many other emulators.

You can download it here : https://drive.google.com/file/d/1gQtgWz2pH2TX9Qs_bcDU9zn7w4edfcVf/view?fbclid=IwAR0SRSC8M_1_qm825n4Bd7bqjLmO30qTpFo73qQQga-TC_LRuc2BVFcGzKU

Has been tested on many RK3399 devices.

After burning on the SD-card/eMMC. Set /boot/armbianEnv.txt to point to the correct .dtb file.
On first boot change the user password and the root password. Default password is 123456
 
passwd Type default password 123456 and 2x your new password sudo passwd Type user password and 2x new root password Update and upgrade
sudo apt update sudo apt upgrade Then update Box86
Applications -> Emulators -> Update Box86

For HDMI sound you might need to disable the other audio device since it always defaults to it on reboot.
Volume control -> Configuration -> disable the one that's not HDMI audio

With M4/M4V2 you might need to set the governor to performance. Otherwise it is unstable. Be sure to use heatsink + fan to keep it cool. Or clock it lower with big cores for lower temperatures.
Best to use "sudo armbian-config", you can also set your locales with it.
Or set manually by changing /etc/default/cpufrequtils

To start a windows program or game
wine program.exe For Linux x86 something like
wine start.sh
You can switch Windows versions if something doesn't work. For older games/programs for example Windows 98, newer XP...
To do this go to Applications -> Emulators -> Wine Configuration

You can also mount virtual drives there.

Not only is this amazing to be able to play your favorite old games n an RK3399.
It can also be a way to replace old x86 machines running legacy x86 software.
So this really is "a game changer" for ARM.

Now this works I can't wait to see this working on the Odroid N2/N2+. But for that we'll have to be a bit more patient.

Cheers.

As an assumption, it is possible that u-boot specifies the name of the DTB file, which is not suitable for recent kernels. You can try to force the use of a different DTB (via armbianuEnv.txt) and try to check other DTB options. Sometimes there are "miracles" and someone else's DTB can work.

I tried the latest night image of Focal 5.9.8 from November 13, running from an SD card. In startup mode with SD \ emmc, I didn't find any problems with rebooting (I rebooted many times).

For giving you free advices and explaining you how thing are.  Obviously you thinks FOSS community is a bunch of slaves waiting for you to show up.

Ver 20201014 kernel 5.9
 
Pay attention. This is the latest version of ArmbianTV images, where there are files for AML. The following images will not contain this data.

ver 20201014 for rk3288 kernel 5.9

Hi all.
I've just finished a long video special where I talk about all my SBCs. In the order how I got them.
I show the specs of all of them. Say what I like, what's bad about them. What I use them for. What SBC is best for your goal.
Here's my video, I hope you enjoy it.

Greetings, NicoD.
 
 
P.S. : Pictures of anyone else their collection? Mine are not all on this pic, no room for them all. 

You waste our time not giving us the data we need to be able to help.
sudo armbianmonitor -u
What image? What kernel?

Mainline is still in development. Things are added, and other things break. That's just a fact of life.
We can't test every single thing.
Use Legacy if it fits your goal. Thank you for wasting my time too.
If you're not happy buy an x86 sbc and buy Windows for it. Then go complain to Microsoft like that. Please.

Since infrastructure upgrade from single server to group of servers we are running round robin re-director around servers. Since current capacity is overkill, we actually don't need to worry about that. We have statistics in some form - @lanefu can provide more data - I hope we have it  We have no info from downloads from torrents or direct download from mirrors.
 
Image build targets are manually adjusted in this file: https://github.com/armbian/build/blob/master/config/targets.conf 
 
Since images are built multi threaded and we have lots of CPU cores / enough memory to build 50-60 images at once, this is also not most critical problem. But building u-boot, kernel and BSP is only partially parallel ATM. Its planned to fix this problem and, probably next year, upgrade build infrastructure.
 
There are two levels of download infrastructure:
 
first - cca. 600 images)
- fast servers
- latest stable images shared around servers
- torrent network
 
second - several thousands)
- slow servers
- archived images
- test images
- beta repository
 
There is plan to move beta to faster connections.