Werner

They are not available via apt yet
 
https://www.armbian.com/newsflash/armbian-leaflet-8/

https://docs.armbian.com/User-Guide_Getting-Started/#how-to-upgrade-distribution-like-focal-to-jammy-or-bullseye-to-bookworm

https://www.armbian.com/newsflash/armbian-leaflet-8/

@Contributor/Maintainer 

- added missing Rockpi 4C plus
- enabled Mekotronic boards https://www.armbian.com/download/?device_support=Supported&tx_maker=mekotronics
- added Orangepi 5 Plus
 
In case there is another missing or broken images, please report, here or to Jira directly https://armbian.atlassian.net/browse/AR-1765 

Yep. Totally missed that. Didn't come to my mind it's new and needs to be partition first. It works now, as intended.

https://www.armbian.com/newsflash/armbian-leaflet-8/

@Minh do you know what does `omxh264enc` mean? I recommend you to google it first.

moved

Interesting. Gonna look into that.
 
Edit: From what I can see you are allowed to like up to 10 posts per day.
Edit2: Ah you were just promoted from validating to member a few minutes ago. Therefor the limit mentioned above now counts.
 

Having used YOCTO for a couple of years at work I assumed that creating my own Armbian image was going to be difficult. However to my suprise I was able to create a Bullseye image for the Orange Pi R1+ LTS in less than 1 hour. And, .... it actually runs correctly on the target board. That is pretty good.

Depends. If you are impatient yes, you have to download new img and use this.
If you can wait a bit until our apt repositories are up to date then a common apt upgrade will do.

Armbian does not provide updates for userspace packages. Firmware (u-boot, kernel) however may (or may not) receive further updates until something breaks (and nobody volunteers to fix).

I have also noticed this issue on nanopi duo2. I tried to find out the cause of it and I think its caused by this upstream commit. I added a revert patch in userpatches/kernel/archive/sunxi-6.1 and compiled an image. Image was able to boot successfully. I am going to investigate a bit more about why its impacting 32bit allwinner boards, and will raise a merge request with the fix once I have it ready

I think the one you have will be fine. Just don't connect the red wire, even on boards which have 4 pins.

No idea. I don't use windows for such things. Too much annoyance.

Another try: 'Armbian_23.5.0-trunk.275_Nanopineo_bookworm_edge_6.2.16_minimal.img' works!
So filesystem resize, account creation, reboot, power cycle. U-Boot reports: 2022.04-armbian (May 25 2023 - 19:26:34 +0000) Allwinner Technology
 

GPU drivers have nothing to do with Armbian. Armbian can only show how to use them. We are not driver developers.
It is expected that the blob Rockchip driver runs way better than the open-source panfrost/panfork drivers. Panfrost might improve in time. N2/N2+/VIM3 at first also performed worse than RK3399 but after time it now outperforms RK3399 by a lot.
Both drivers are very useful to me.
You can use the blob by running in x11 and run your program with "malirun programname"
Not everything will work, but for example PS2 emulation works perfect like that.

Video playback has nothing to do with GPU drivers but VPU drivers. For that there is the multimedia ppa from AmazingFate. 

split from origin topic since hw is different

Are you sure about that? IIRC it was SPI, eMMC and microSD last.
See page 30 at https://www.t-firefly.com/download/Firefly-RK3399/docs/TRM/Rockchip RK3399TRM V1.3 Part1.pdf
I know this is for RK3399 but I assume Rockchip did not reconsider their boot order in the mean time?

Not necessarily. It depends on what is on the eMMC. The order you described would work only if there is a boot loader on eMMC that checks for microSD presence and points there if found.
 
If however the boot loader on eMMC is dumb and doesn't care about other bootable devices it just runs through, which can be a big issue if the eMMC module cannot disabled or removed from the board.
 
I faced a similar issue long time ago when I had a pinebook pro in my collection.
The fixed boot order of rk3399 is SPI, eMMC, SD. RK3588 might be similar. This default behavior cannot be altered, only worked around by telling the boot loader, that is going to be flashed to SPI or eMMC, to look for microSD first.

With free samples nobody can pay for their living.
https://www.armbian.com/partner-contact-form/
https://forum.armbian.com/subscriptions/

thank you very much, found the image burn part in the code.

amazing job you guys did with this framework.

Share full log.

code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } apt install linux-headers-current-sunxi

Hm did you run apt update beforehand?
Download works for me
 
apt-get download linux-headers-current-sunxi Get:1 http://fi.mirror.armbian.de/apt buster/main armhf linux-headers-current-sunxi armhf 23.02.2 [12.0 MB] Fetched 12.0 MB in 4s (3,045 kB/s)