balbes150

There is a mirror, where images are updated to the latest version (In a few hours there will be a new version).
https://users.armbian.com/balbes150/
 
I don't use archlinux. As far as I know (I may be mistaken) - this version is assembled from parts of Armbian with the addition of ready-made binary files and settings from other systems, i.e. it is essentially an analogue of twisteros (a prefabricated binary hodgepodge) based on archlinux.
 
u-boot radxa is useless junk with a bunch of errors and hidden problems for users (with any failure to start with NVMe, you will get a problem, you cannot start any system with SD\USB until you physically disable NVMe and other problems).
 
armbian-config is an order of magnitude better and more convenient, it also allows you to easily install\update u-boot in MTD\SPI and simultaneously install the system on NVMe or other media (eMMC\USB).
 
For a long time there have been versions of Armbian with support for different EFI\grub variants (EDK2-EFI and u-boot-efi), see details and links to such images in this topic. So far, OS selection management is available only via UART.
 
Using ARM-blob and additional system performance settings, I get almost 3800 on Rock 5b, on other rk3588s models I get more than 4400 and I have a suspicion that slower memory is used on models with 16GB of RAM, but no one wanted to share the results from rock5b with 8 GB of RAM, with with this system, to determine exactly how reliable it is.
 
Using extlinux.conf or efi\grub (with the correct parameters).

@NicoDVersion 20230219. No manual copying of dtb is needed anymore, all support is included in u-boot, i.e. after writing the image to USB\SD, you can use it immediately. The installation on eMMC has been checked.
 
ps All the necessary changes will automatically get into the official relise version, you can build your own version of the images  

I explained to you what the problem is and I absolutely don't care what you will use.
 
 

There is good news. I am currently testing a new loader u-boot. A version with support for direct start from USB media will be uploaded to the website tomorrow. That is,  can have a bootloader in SPI\MTD and only a USB media with the system and fully run the system from USB. Or have a system on NVMe and fully launch another system from USB media, simply by connecting a USB media (disconnected the USB media and the system starts with NVMe). 

@balbes150I already made the video. I did say in it the sollution for eMMC install is in this thread.
 
 

@balbes150Wifi works.
I'm starting to make the video about your Armbian image on Khadas Edge2. Good work. It's a great experience.

Yes. To use Name, start the system from the SD card and perform the installation using arm bin-config (use the SPI + NVMe\SATA installation option). Please note - my version does NOT support PD power supplies

Version 20230209 with kernel 5.10.110 with added HW support.
Test results.
 
[function] fragment-complexity=medium:fragment-steps=5: FPS: 4379 FrameTime: 0.228 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 4636 FrameTime: 0.216 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 4973 FrameTime: 0.201 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 4869 FrameTime: 0.205 ms ======================================================= glmark2 Score: 3851 ======================================================= user@rock-5b:~$ PAN_MESA_DEBUG=gofaster glmark2-es2-wayland arm_release_ver of this libmali is 'g6p0-01eac0', rk_so_ver is '6'. arm_release_ver of this libmali is 'g6p0-01eac0', rk_so_ver is '6'. ======================================================= glmark2 2021.02 ======================================================= OpenGL Information GL_VENDOR: ARM GL_RENDERER: Mali-LODX GL_VERSION: OpenGL ES 3.2 v1.g6p0-01eac0.ba52c908d926792b8f5fe28f383a2b03 ======================================================= [build] use-vbo=false: FPS: 4336 FrameTime: 0.231 ms [build] use-vbo=true: FPS: 4783 FrameTime: 0.209 ms [texture] texture-filter=nearest: FPS: 4729 FrameTime: 0.211 ms [texture] texture-filter=linear: FPS: 5175 FrameTime: 0.193 ms [texture] texture-filter=mipmap: FPS: 5091 FrameTime: 0.196 ms [shading] shading=gouraud: FPS: 4258 FrameTime: 0.235 ms [shading] shading=blinn-phong-inf: FPS: 4404 FrameTime: 0.227 ms [shading] shading=phong: FPS: 3972 FrameTime: 0.252 ms [shading] shading=cel: FPS: 4183 FrameTime: 0.239 ms [bump] bump-render=high-poly: FPS: 2528 FrameTime: 0.396 ms [bump] bump-render=normals: FPS: 5949 FrameTime: 0.168 ms [bump] bump-render=height: FPS: 6005 FrameTime: 0.167 ms [effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 4548 FrameTime: 0.220 ms [effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 3866 FrameTime: 0.259 ms [pulsar] light=false:quads=5:texture=false: FPS: 5457 FrameTime: 0.183 ms [desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 1829 FrameTime: 0.547 ms [desktop] effect=shadow:windows=4: FPS: 4512 FrameTime: 0.222 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 528 FrameTime: 1.894 ms [buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 495 FrameTime: 2.020 ms [buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 817 FrameTime: 1.224 ms [ideas] speed=duration: FPS: 2543 FrameTime: 0.393 ms [jellyfish] <default>: FPS: 3489 FrameTime: 0.287 ms [terrain] <default>: FPS: 299 FrameTime: 3.344 ms [shadow] <default>: FPS: 3963 FrameTime: 0.252 ms [refract] <default>: FPS: 633 FrameTime: 1.580 ms [conditionals] fragment-steps=0:vertex-steps=0: FPS: 4990 FrameTime: 0.200 ms [conditionals] fragment-steps=5:vertex-steps=0: FPS: 4897 FrameTime: 0.204 ms [conditionals] fragment-steps=0:vertex-steps=5: FPS: 4423 FrameTime: 0.226 ms [function] fragment-complexity=low:fragment-steps=5: FPS: 4529 FrameTime: 0.221 ms [function] fragment-complexity=medium:fragment-steps=5: FPS: 4752 FrameTime: 0.210 ms [loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 4532 FrameTime: 0.221 ms [loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 4175 FrameTime: 0.240 ms [loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 4724 FrameTime: 0.212 ms ======================================================= glmark2 Score: 3800 =======================================================  
 
For details of the new features, see this topic.
 
https://forum.armbian.com/topic/22986-firefly-station-m3-rk3588s/?do=findComment&comment=159554
 

@NicoDVersion 20230211 Armbian for khadas edge2 - added support for HW 3D . The result of gnome3+wayland+arm-blob gave about 3800 parrots. For details on how to install HW and testing, see this topic.
 
 

Alpha version of Armbian for Khades EDGE 2 (rk3588s).
Launch. Download, unpack, burn to USB media (you can use an SD card if there is an additional module with a card reader for an SD card). Connect to any USB port on EDGE 2 and turn on the power. The system starts automatically. It would be interesting to run tests on this version. I pay attention - there is no 3D acceleration yet, general performance tests for the Armbian image are interesting. Wi-Fi is not working yet,  need to use USB-LAN, this will be fixed in future versions.
 
https://disk.yandex.ru/d/QMgdvGqF3jpgJw

Read carefully - only LAN works on the EDGE version, HDMI does not work.
 
 

I am currently busy preparing the release, all checks will be after the release.
 
 

I am currently busy preparing the release, all checks will be after the release.
 
 

This command is enough to get information about the date of creation of the kernel and its version.
 

Specify the exact name of the image where there is support.

Specify the exact name of the image where there is support.

Now RPI strongly loses in all respects to s9xxx and rk33xx TV boxes. The only place where the use of RPI is justified, systems that use a variety of external sensors and actuators, of which a large number are produced and there are ready-made systems for their use.
 
 
 
 LE did not use patches, but a ready-made closed binary module (driver), which was taken from the finished Android firmware. This binary module was built exclusively for one version of the 3.14 kernel and cannot work with any other versions of the kernel. The manufacturer of the chip does not give anyone the source code from this driver, so no one will spend their time disassembling the binary code and studying it to write a new driver for the kernel 4\5. If you want, you can do the job yourself.

OK. I'll repeat it again with details. Armbian and Radxa images use essentially the same u-boot (in any case, this was the case at the time when I analyzed them). They are assembled from the same sources, so their behavior is the same. My u-boot is significantly different, it is a different source code and configuration, in which errors have been fixed and the configuration has been changed (UART is enabled, the startup order has been fixed, support for PD has been removed, etc.). Therefore, when using a power supply with PD, my version will not work. By the way, I recommend thinking about why radxa disabled the UART console in its u-boot. For the correct launch of my u-boot, you also need to completely erase the SPI, so that its "pieces" do not interfere with the correct launch of the new u-boot from the SD card. For reference, the primary loader (the first stage) is always launched in the strict order of SPI-eMMC-SD polling.

I think the power supply might deserve it's own topic.
 
Like balbes mentioned PD is meant for devices with internal battery. There it saves the battery during fast charging by preventing overcharging.
The Rock 5B is further 'borked' since the negotiation starts after the system starts. The advantage is it can be open source (more or less), but the big disadvantage it is so slow most PD chargers stop negotiating during system start in the meantime.
 
If you realise that the power supply in the Rock 5B (IP2315) is just a step-down converter with some logic and a PD car-adapter adds an step-up adapter to the equation you might realise it makes no sence to operate the power input at 20V. While the resistance in the cable might be minimized the power loss in the step-down and the step-up converters are maximized. Most power supplies can achieve 95% efficiency, but cheap step-up/step-down converters can only achieve that when V_in is almost equal to V_out. Normal PD-adapter should work more efficient than 12V car-adapters, but even then if they very efficiently produce 20V which the R5B very inefficiently transformes to 3.3-5V does that make sense?
 
A 20W PD car-adapter adds roughly 0.5W to the power consumption. With a 65W/20V PD car-adapter the adapter might add more, but the step-down converter in the R5B will definitely work more inefficient than at 9V.

These are the official versions, please contact the appropriate section with all questions. Modified versions are discussed in this topic, they differ from the official ones.

What do you want to update ?

This is for attaching the device itself to the wall or to the body of a large device (for example, a monitor, via a VESA mount)
 
I think the rubber bands are glued and they can be carefully peeled off (I peeled off such rubber bands and nothing happened to them). If there is not enough regular glue when re-gluing, you can lubricate them with another glue and glue them with an offset from the attachment points, so that you can then easily have access to the fastening screws.

That was very infomative.
Can't add much to the discussion. I agree that forum used to be a lot better and more important. Because of the use of Discord, irc, Jira... there is more fragmentation.

We used to use the forum also to chat between devs/users/mederators. Now that is done on discord, irc or github. So the fun is out of the forum.
Nothing of what is said on discord is of value in the future. While what is said on the forum keeps its value and is easy to find.

Github is good for bugreports and discussion on how to go ahead. But it is a developers tool and not for regular users.
Discord is good to chat. It added features we didn't have on the forum like being able to do voice chats or video chat. But it takes away the focus from the forum for many.

I don't check the forum as much as I used to. Only see if there is anything interesting in the notifications. But I miss a lot because I'm not present as much. And what happens on the forum isn't communicated much about on discord.

Maybe a discord/irc room where forum posts can be seen. Just the titles would be enough to sparkle curiosity.

For me there is too much to have to keep up with. I've got my YT channel, reddit, facebook groups, forum, discord, twitter, ...
Quality decreases when too much is going on. Nobody can keep up with it maybe except Igor. (he seems to see it al )

Watched at 1.25x.

Added alpha version of image build support for RISC-V.
So far, this is an early version and some of the functions do not work in it.
Currently, support has been added for the StarFive model.
 
https://rvspace.org/
 
Details can be seen in this topic.
 
https://forum.rvspace.org/t/armbian-for-starfive-build-system-ubuntu-debian/468
 
 
Added support for Nezha D1 and Lichee RV (Dock) with Allwinner D1 RISC-V chip. To start the system. Download the image, unpack it, burn it to the SD card.  Connect the SD card to the device and turn on the power. Further steps for initial setup are similar for all Armbian systems.
 
For the Nezha D1 model, HDMI, LAN, USB, analog audio via 3.5 jack works.
For Lichee RV Dock  works HDMI WiFi USB USB-LAN
 
Link to download images.
https://disk.yandex.ru/d/da8qJ8wyE1hhcQ
 
https://www.cnx-software.com/2021/12/30/sipeed-lichee-rv-risc-v-module-gets-5-carrier-board-with-hdmi-and-usb-ports-optional-wifi/

IMHO earlier, in all Armbian builds, autologin was enabled by default and all users are used to this behavior, so it is advisable to keep this in new versions (i.e. make autologin enabled by default and disable autologin yourself, through the armbian-config setting). For many users, this will preserve the usual behavior and at the same time allow you to disable autologin (if necessary).