NicoD

In this video I show how to use armbian-gaming.
 

Hi all.
I'm working on a script that can install different Linux gaming tools like Box86, Box64, PPSSPP, ...
For now it can only install box86 and box64. There is also an issue installing wine, so this doesn't work either.
 
https://github.com/NicoD-SBC/armbian-gaming
 
Download and unzip and run script : sudo /bin/bash ./armbian-gaming.sh When ready I'll make a video about it and give more info.
 
I've tested it on the PineBookPro with Hirsute.
With the Odroid N2+ you need to activate panfrost, install dependecies for N2+, and then install box86. Tho it didn't work as it should.
If "install box86" gives a build error, try the dependencies for N2+ and try "install box86" again.
 
Please let me know your experiences on other systems.
 

Hi all.

Werner has made a video where he presents himself and talks about how he got into using Linux, SBCs and Armbian.
A very interesting video.
 

This is a serie of video's. Igor and Lanefu also have made a video like that.
You can find the other video's here.
https://www.armbian.com/authors/

If you're willing to make a video like this. I am willing to edit and help out.
Greetings, NicoD

Hi all.

Werner has made a video where he presents himself and talks about how he got into using Linux, SBCs and Armbian.
A very interesting video.
 

This is a serie of video's. Igor and Lanefu also have made a video like that.
You can find the other video's here.
https://www.armbian.com/authors/

If you're willing to make a video like this. I am willing to edit and help out.
Greetings, NicoD

Hi all.

Werner has made a video where he presents himself and talks about how he got into using Linux, SBCs and Armbian.
A very interesting video.
 

This is a serie of video's. Igor and Lanefu also have made a video like that.
You can find the other video's here.
https://www.armbian.com/authors/

If you're willing to make a video like this. I am willing to edit and help out.
Greetings, NicoD

FriendlyELEC’s family of NanoPi router SBCs and gateways will soon be extended with the NanoPi R5S board equipped with a Rockchip RK3568 quad-core Cortex-A55 processor, and providing three Ethernet ports (2x 2.5Gbps, 1x 1 Gbps), plus support for M.2 NVMe SSD storage. The company has not published any information publicly, but a post on Weibo social network reveals additional details with the single board computer being equipped with 2GB LPDDR4X, 8GB eMMC flash, two USB 3.0 ports, HDMI video output, and more. NanoPi R5S preliminary specifications: SoC – Rockchip RK3568B2 quad-core Cortex-A55 processor @ up to 2.0 GHz with Arm Mali-G52 MP2 GPU, 0.8 TOPS AI accelerator (RK3568B2 comes in a “plastic package” instead of the “metal-can type package” found on RK3568, but the features are the same) System Memory – 2GB LPDDR4 Storage 8GB eMMC flash for OS Key M socket for M.2 2280 NVMe SSD support Optional SPI [...]
The post NanoPi R5S router SBC/gateway with 2x 2.5GbE, 1x Gigabit Ethernet, M.2 NVMe storage coming soon appeared first on CNX Software - Embedded Systems News.
View the full article

Release is not just freezing the code and generating images. Its a time when we pull together stronger, agree and deal with common goals and ideas. Things we are dealing with are complicated. Linux is complex, our framework is getting there too and only together we can deal with all this.
 
I started on freezing the kernel version. There is also some breakage, some related to our patches, some not. But since we have to freeze it sooner or later, perhaps now its the right time.
 
This brings a few good things at once:
temporally release people that are working close with maintaining kernel code @going@jock@balbes150@amazingfate myself ... this can bring more resources on trying to match with / merge armbian-next. @rpardiniworked for moths on this. Lets review the code and help sorting out bugs. Again. IMHO it is possible to merge, but if code remain unstable by the code freeze date (2022-05-14), we are merging after new images are generated. asking @Contributor/Maintainer board maintainers to engage in images building and testing (currently still from master branch) and bug reporting as earlier as possible (once PR 3736 gets merged) reproducible build framework in release branch. Which is most important long term consequence. Additionally, we would like to finish u-boot upgrade on Rockchip and release major forum refactoring @TonyMac32 @piter75 @balbes150
 
Happy Workers' Day!

Here my review video of the Tanix TX6 TV-Box. I show Android and how to install Armbian onto it.
Greetings,
NicoD

Hi all.
I made a new video where I explain all the basics of working with Armbian xfce4.
This for the absolute beginners that come from Windows. But a more advanced user can maybe also learn a few things from it.
Here is the video.
Greetings,
NicoD

I wasn't sure where to put this...but this thread seemed closest. Armbian wallpaper / artwork rendered in Blender 3.1 with procedural text and materials.
 

Hi all.
I made a new video where I explain all the basics of working with Armbian xfce4.
This for the absolute beginners that come from Windows. But a more advanced user can maybe also learn a few things from it.
Here is the video.
Greetings,
NicoD

Samples arrived ♥️ HW looks fascinating, Armbian is yet to be ported so can't comment how good this is in realworld. Its shipped with stock Khadas Ubuntu, kernel 5.4.y, which is good to boot something ...
 
Technical specs at CNX.

Hi great question.  Def can be confusing.  We're working to be more clear.
 
GitHub issues (NOT PRs) are meant to be specific to the Armbian build engine and not specific to devices.
 
Raise device issues on forum for conversation and hopefully find the attention of a maintainer.  (Part of reason we do it on forum is it creates too much noise on GitHub for such a small team of devs)
 
If it's an issue a maintainer or armbian developer thinks it needs to be prioritized, they will add to our Jira
 
For those that don't like posting on forum anybody can open a draft PR with a proposed solution and explanation of what's being solved in GitHub 

For some people it is wanted/needed to change things. And for the devs it is a must.
It's just expected of people who do change things, that they know what they are doing.

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

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
 
 

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!