gounthar

I can assure you ZFS from Arbmian repo works perfectly fine. We are using it on two production grade servers.
 
odroidhc4:~:# modinfo zfs filename: /lib/modules/6.0.12-meson64/updates/dkms/zfs.ko.xz version: 2.1.6-0york1~22.04  

Hi all, it is a pity to forget this topic forever.  As a newbie who own AM40 board, I still want to run armbian on it..
 
I accoccasionally got an this board,  it is quite able to serve as an android tvbox board, but can't do more due to the stock rom. 
 
I find maskrom pin on the back of the board. I think it is possible to run Armbian on it.   
 
Here are some of my research result:
 
if on stock android rom.  connect the board's upper usb port to computer with male to male usb cable,   flip the adb/nomal switch to adb mode,  press the white switch and power on the board, the board can enter loader mode. then I can use  rkdevtools to switch the board to maskrom mode.
 
if on other boot loader,   can shot maskrom tp for about 20 seconds and enter maskrom mode.

 
 
 
 
 

Thanks -- turns out the current limit is 16 as defined by https://github.com/jernejsk/FFmpeg/blob/v4l2-request-hwaccel-4.4/libavcodec/v4l2_request_hevc.c#L24. I increased that in my ffmpeg build to 32 and that made HEVC work with moonlight-qt! At I was able to stream for a few minutes; I didn't see much difference between HEVC and H.264 in moonlight streaming (and had no luck forcing HDR), so for now I went back to the better supported H.264 codec. I'll definitely give this another try once the kernel APIs + userspace code stabilizes.

I figured it out. I had it wired to MI instead of MO! I'll do a write up once I have everything working the way I want.

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

You don't have to justify yourself @NicoD, it was just in case this was possible for you. 🤷‍♂️
Maybe I'll bump into someone else involved in Armbian, you never know who one could meet when in FOSDEM. 😉
 

I'd like to go but finances ain't there. Have to save for a cycling trip in a few months, and investing in computer gear for kids.
Tho just going one afternoon is possible. But I've got to sit 2 hours on the train to get in Brussels, and then go from station to the expo, and 2 hours back. So would be a very boring day. And for just being there a few hours I don't feel it's worth it.
If I would go I'd rather stay the night in Brussels on Saturday and leave Sunday evening. And have my recording gear with me to make video's. Next year I can plan it if others promise to go. Enjoy your time in Brussels. I hope the weather will be good.

I am sure there will be! We even played with idea to present armbian-next build framework, but I guess next year or at another conference. I'll have to skip it this year. Somehow too busy.

Try a different program for your uart such as tio
 
Also try
 
export TERM=xterm && reset
 
Or
 
export TERM=linux && reset

Many of us are using Armbian not just on ARM single board computers but also on servers (bare metal & virtual). We use our builds since we trust it more then Debian, Ubuntu, not to mention other distributions that are recklessly updating and one ends up as an OS tester and not OS user. Personally I use Armbian Jammy on Ryzen 9 workstation with great success. My primary use case is development / productivity. For the road I used to have 13" Dell notebook which recently suddenly died. It was out of warranty so I had to get something new. After some testings of various devices I settled with 12th Gen Intel i5-1240P powered Lenovo. Then I tried many general purpose distros to see how well they work and all had some (minor) troubles ... 

We are having UEFI images (common image) since some time, but UEFI nor desktops were fine tuned nor ready for such performance daily driver desktop usage. We were close, but not close enough to just run it. Past two weeks we have been lifting general UEFI support, fixed many bugs and what came out is "Armbian ultimate developers desktop build".
 

 
- improved support in GRUB (armbian wallpaper) & HiDPI GRUB support
- all preinstalled applications are normal apt packages
- current 5.15.y kernel, Jammy userland (5.19.y has some strange issues)
- snapd is not installed (user can install it)
- HiDPI support (automated adjustments on big screen resolutions)
- NVIDIA graphics acceleration with proprietary driver (x86 only)
- Intel graphics acceleration also works out of the box
- preinstalled Google Chrome (x86 only)
- preinstalled Microsoft Visual Studio Code (x86 only)
- ZFS 2.1.5 ready (apt install zfsutils-linux zfs-dkms)
- face unlock works perfectly fine on this laptop
- installation to SSD drive to dual boot with Windows 10/11 is supported Armbian classical way by transferring actual live image to the prepared partition via nand-sata-install. All you need to do is prepare spare space on your drive, Windows 10/11 or Linux, UEFI support (most if not all hardware for past 10 years has it).
 
I have tweaked images (XFCE, Gnome, Cinnamon) a bit to my personal needs, but making changes is welcome.
 
Nice to have: disk encryption within nand-sata-install, small bug fixing, additional DEs. Currently we have CLI, XFCE, Gnome and Cinnamon. Others are too buggy.
 
https://www.armbian.com/uefi-x86/
https://www.armbian.com/uefi-arm64/
 
Please report where it works and how (well)!

> New ver 20220622 for D1 (Nezha Lichee RV Mango MQ pro etc) and StarFive V1 (u740)
This one, i've tested CLI only image - Armbian_22.08.0-trunk_Nezha_jammy_current_5.19.0.img.xz ( https://disk.yandex.ru/d/da8qJ8wyE1hhcQ/Nezha_D1/ArmbianTV/20220622/Armbian_22.08.0-trunk_Nezha_jammy_current_5.19.0.img.xz?pane=file-info )
Is there a way to determine which image that was from burned SD card content or booted Mango? (as i`m not sure that this is the only image that had RVV support). But i`m pretty sure it was june-july image, corresponding to your initial bring-up efforts for Mango PI.
Thanks!
 
P.S. I will check new images again with another sdcard to provide thorough report on which images boot and have "v" in "isa" and which do not
 
Image that has RVV outputs following when queried:
 
> msomeone@nezha:~$ uname -a
> Linux nezha 6.1.0-rc3-d1 #trunk Fri Jan 13 08:21:24 UTC 2023 riscv64 GNU/Linux
> msomeone@nezha:~$ cat /proc/cpuinfo
> processor       : 0
> hart                 : 0
> isa                   : rv64imafdcv
> mmu              : sv39
> uarch             : thead,c906
> mvendorid    : 0x5b7
> marchid         : 0x0
> mimpid          : 0x0
 

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.

@gounthar, notice the "v"  character missing in your output, so it means that that particular image does not detect vector extension.
isa : rv64imafdc For MangoPI MQ(PRO) - The thing is that there were several builds that successfully detected RVV extemsion ( RVV v0.7 ) present on c906 CPU, and there were builds that do not.  I`m wandering what has changed in those images, that prevents "v" appearing in "isa" line of /proc/cpuinfo? And how to enable it again?

Which of https://disk.yandex.ru/d/da8qJ8wyE1hhcQ/Nezha_D1/ArmbianTV images will support MangoPi MQ PRO and still have vector extension (RVV) present in /proc/cpuinfo ("rv64imafdcv") ?
Please advise,
thanks!
 

@gounthar It's working OK for me, both the FriendlyElec images and ones generated with pyavitz's debian image builder.
 
Which FriendlyElec image are you using? And which ethernet port? (Reason I ask is I think with FriendlyWRT SSH is firewalled off on the WAN interface)
 
If it's visible on your router it's presumably made a DHCP request so must be up and running.

Does it show a heartbeat on the front LEDs? If not,try flashing the SD,again. First I wrote the image as downloaded on SD card (raw mode). That didn't work nor did Etcher give me a negative feedback.Using the windows tool Mini Tool@Partition Wizard you can see if there are several volumes on the sd card.If not,you're doing it wrong. Never had any issues with Allwinner,Broadcom,Rockchip... Also I noticed I have to connect the WAN port and not LAN. Else you won't get proper access via DHCP.
 
 
Which image did you use? On the Nanopi R5C wiki there's a downloadlink to a gdrive.

My efforts into this are done. I was asked to make it boot and get it functioning, not to produce images for the masses. I think as that goes, I did as much. Sorry the kernel doesn't have everything "that everyone ever wanted" ticked on, but that wasn't a concern of mine at the time. With that said, I added support for it in the defconfig, if you or someone else wants to compile their own kernel for those images, you are more than welcome too.
 
Honestly, I would suggest people check the commit: https://github.com/armbian/build/pull/4247 and help provide proper Armbian support. 
 
Thanx

9bx154, its uploaded. #4

If you follow that way you could rip kernel package as well. That way the first working images for OPi Zero 2 were made. However Armbian does not want or like to do that since then you could basically directly use vendor provided images.https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one
 
At the bottom line it all depends on the development for the SoC or family which in this case is rk35xx. If that grows adding support for different boards that are built around that SoC is easy in comparison but that also depends on having a person that knows how to do that and want to donate their precious time doing so. Both aren't easy to find .
 

I have an R5S, how would I create a new board configuration? I noticed that there is currently no bootconfig in the upstream u-boot repository. Would that be an issue?
 
I read through some of the developer documentation, but I can't find a section that explains how to go about adding support for a new board.

I have some familiarity with compilers and the likes, but I have never built a kernel or OS images by myself. I would however love to contribute.

i have a brand new R5S here, let me know if i can help in anyway testing...
 
some technical insights into os buiding currently:
 
https://github.com/friendlyarm/sd-fuse_rk3568
 
Wiki: https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R5S
 
would love to have a proper armbian image 🚀

Once somebody starts dealing with this hardware. No ETA though
 

Nobody wants to wait but also very few of those are a willing to do something to decrease waiting time. One year was a rough estimation. Mainline development of arm platform is very slow in comparison to x86.
For example it took several years to bring RK3399 SoC to a well matured state and still not all functions are well supported yet. Now think about how long it might take for a mid-grade SoC like H616

You mean adjusting HW features? Because there are no overlays and nobody developed them. No, we have not plans nor budget for that.
 

We are also waiting and waiting that you realise that you need to support R&D in order to have some small rights to complain  
 
This graph below shows how many days is needed before reported issues is resolved. Terrible, right? https://docs.armbian.com/User-Guide_FAQ/#development-time Remember that if you don't contribute on the project, you can't add bugs / tasks to the system at all. With another words - we have no resources not even for write bugs into the system and if we would listen to your problems, situation for the project that helps you, but you don't help it, would only be much worse.

 
If all people that complain and report bugs to themselves would have Angel https://forum.armbian.com/subscriptions/ we would be able to perhaps hire full time person for you that would record bugs and solve them one by one. Since this is not the case and you expect the impossible, graph can only get steeper.