Werner

Sorry for the late reply. I was busy within these days.
 
I've seen you have merged it, I'll test the latest compiled kernel, if I found any issue, I'll reply to this topic.
 
Thank you

If you want integrated wifi, several sbc can be used and some others will require an usb wifi dongle. The key
For instance, the pineH64-B with 2 or 3GB of ram may do the job quite well and you can add an emmc module: https://www.pine64.org/pine-h64-ver-b/
A similar device is Orange Pi Lite 2.
If you want something closer to a tv box, station M1 is also a nice choice even if it is only community supported for now: https://www.firefly.store/goods.php?id=130
 
If you want a stronger cpu, any of the armbian supported sbc based on rk3399 will answer your needs (check for wifi in case it is not integrated on some boards, eg. rock pi 4A).

Ideas I'm great at ;] but I've wanted for a long time to learn to work with armbian-config.
Will reply on that thread.

Thank you I am littlebit close with this!
 
/ _ \| _ \(_) / _ \ _ __ ___ | | | | |_) | | | | | | '_ \ / _ \ | |_| | __/| | | |_| | | | | __/ \___/|_| |_| \___/|_| |_|\___| Welcome to Armbian 21.02.1 Focal with Linux 5.10.12-sunxi downloaded compiled via: sudo armbian-add-overlay tft35a-overlay.dts evtest touch screen works! I can see fb1 device root@orangepione:~# ls /dev/fb* /dev/fb0 /dev/fb1 but screen is still white  root@orangepione:~# cat /boot/armbianEnv.txt verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 rootdev=UUID=14ec09df-9864-4191-b047-c6bfafc28b7e rootfstype=ext4 overlays=spi-add-cs1 user_overlays=tft35a-overlay usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u /etc/X11/xorg.conf.d/99-fbturbo.conf Section "Device" Identifier "Allwinner A10/A13 FBDEV" Driver "fbturbo" Option "fbdev" "/dev/fb1" Option "SwapbuffersWait" "true" EndSection root@orangepione:~# dmesg | grep touch [ 7.180180] ads7846 spi0.1: touchscreen, irq 67 root@orangepione:~# dmesg | grep tft [ 7.220722] fbtft: module is from the staging directory, the quality is unknown, you have been warned. root@orangepione:~# dmesg | grep spi [ 7.116782] ads7846 spi0.1: supply vcc not found, using dummy regulator [ 7.179629] [drm] Initialized ili9486 1.0.0 20200118 for spi0.0 on minor 2 [ 7.180180] ads7846 spi0.1: touchscreen, irq 67 [ 7.180833] input: ADS7846 Touchscreen as /devices/platform/soc/1c68000.spi/spi_master/spi0/spi0.1/input/input1 [ 7.199053] ili9486 spi0.0: [drm] fb1: ili9486drmfb frame buffer device root@orangepione:~# startx X.Org X Server 1.20.9 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.15.0-130-generic armv7l Ubuntu Current Operating System: Linux orangepione 5.10.12-sunxi #21.02.1 SMP Wed Feb 3 20:39:30 CET 2021 armv7l Kernel command line: root=UUID=14ec09df-9864-4191-b047-c6bfafc28b7e rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 consoleblank=0 loglevel=1 ubootpart=54392a35-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 Build Date: 17 January 2021 09:13:31AM xorg-server 2:1.20.9-2ubuntu1.2~20.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.38.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 13 21:28:22 2021 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" MESA-LOADER: failed to open ili9486 (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri) failed to load driver: ili9486 (II) modeset(0): Initializing kms color map for depth 24, 8 bpc. (II) modeset(G0): Initializing kms color map for depth 16, 6 bpc. xinit: connection to X server lost waiting for X server to shut down (II) Server terminated successfully (0). Closing log file. ..
 
I think I am close but some detail still missing

What about the Nanopi R4S? Hexacore, dual GBe, 2nd interface connected via PCIe, NOT USB.
https://www.friendlyarm.com/index.php?route=product/product&product_id=284

I don't use android, after version 4 (after googl messed it up and turned it into shit).
 
I totally agree

Yes

These changes are long ago in the ArmbianTV images for Station P1\M1 

Hi,
 
Linux 5.10 has supported hardware PRNG, SHA, MD% for all sun8i-ce (H3/R40/A64/H5/H6) boards, and supported hardware TRNG on H6.
 
Please consider enable CONFIG_CRYPTO_DEV_SUN8I_CE_HASH, CONFIG_CRYPTO_DEV_SUN8I_CE_PRNG, CONFIG_CRYPTO_DEV_SUN8I_CE_TRNG for hardware offload support.
 
Thanks.
 
 
 

I would love to get involved with the redesign project! I don't have a ton of experience with CLI tools like this but really need to learn so this would be a good chance.

tl;dr. The 500€ subscription has been removed. No one took the generosity challenge
 
As a replacement we added a 20€ monthly subscription to attract people who would like to give more than 5€ but 50€ would be too much.
Existing Small business subscriptions have been "upgraded" to Angel color-wise.
 

I managed to get WiFi to work on P1 with the current kernel and configuration for rockchip64-legacy.

I would like to bring something to attention. Right now, Station P1 and M1 legacy are being added as new kernel packages. I think ideally, the changes should be merged into some of the existing RK3399/Rockchip64 legacy kernels. We were aiming to reduce the multiplicity of RK kernels, but now we are introducing two new kernel packages, station-m1 and station-p1, one of each for a single device.
 
Of course, I understand all the work involved on bringing up a new board, and how frustrating it is when new kernel configs or patches conflict with the existing one. But it is probably worth the effort to try and merge the changes for P1/M1 into Rockchip64, if that were possible.
 
 
@piter75 @martinayotte @balbes150 @TonyMac32 @Igor What do you think?

Hello, thanks for your response, how can i update these files? Also, if anyone knows how i can reply to more than 1 post in a day, i am blocked with the right to make only 1 post per day. 

Probably we should switch rather to https://vscodium.com/#install ?

IIRC I already agreed to changing the patch naming scheme for rockchip64 legacy kernels in the github discussion few weeks ago.
I would interpret the lack of response from others as indifference ;p
... or are we talking about other missing response?
 
BTW. I also received my mezzanine board which I reordered from AliExpress seller after previous order being cancelled resulted in a refund.
The order went smooth this time. 

With Armbian v20.11 one can write mainline u-boot image to board's SPI and enjoy booting nvme drives without any mmc devices.
Prerequisities: ROCK Pi 4(A/B/C) v1.4 or 1.3 with SPI soldered in (v1.3 comes without SPI flash from the factory).
 
If you already have Radxa's u-boot written to SPI you need to short pins 23 and 25 for Armbian to boot Boot fresh image of Armbian v20.11.x for ROCK Pi 4(A/B/C) Add the following lines to /boot/armbianEnv.txt overlays=spi-jedec-nor param_spinor_spi_bus=1 Reboot If you shorted 23-25 pins in 1.) then: disconnect them after the ROCK Pi 4 fully boot's  enable spi-nor by executing (as root):
echo spi1.0 > /sys/bus/spi/drivers/spi-nor/bind verify that the SPI mtd interface is enabled by running
ls /dev/mtdblock0 if the last command does not list any file then something went wrong between 3.) and 5.) Run nand-sata-install choose option: "Boot from SPI - system on SATA, USB or NVMe" choose NVMe partition, eg. /dev/nvme0n1p1 accept erasing of the choosen partition with "Yes" choose fs type (tested with ext4) wait a few minutes for rootfs transfer to chosen partition choose writing SPI bootloader with "Yes" confirm that you want to flash it with "Yes" wait ~60 seconds for writing choose Exit Reboot Enjoy Armbian booting with SPI / NVMe  
Why bother with mainline u-boot?
It is known to boot some NVMe drives that legacy u-boot from Radxa has issues with, eg. SAMSUNG 970 EVO Plus and SAMSUNG PM981.
This does not mean that all NVMe drives are supported, YMMV.
 
Which NVMe drives are known to be working?
Corsair MP510 240GB/480GB/960GB
Gigabyte SSD M.2 2280 PCIe x2 Model:GP-GSM2NE8128GNTD
HP SSD EX900 M.2 NVMe 120GB. Model: 2YY42AA#ABB
Intel SSD 660p Model:SSDPEKNW512GB
Kingston A1000 SSD 240GB (PHISON PS5008-E8-10)
Kingston A2000 M.2 2280 PCIe NVMe
PNY 250GB XLR8 CS3030 M.2 NVMe SSD PCIe Gen3 x4
Sabrent Rocket 256GB NVMe PCIe M.2 2280
Samsung 970 EVO Plus SSD 250GB M.2 2280, PCIe 3.0 x4, NVMe, 3500/2300 MB/s
Samsung PM981 256GB
XPG SX6000 Lite 128GB (ASX6000LNP-128GT-C)
 
Why not using Radxa's u-boot SPI image?
Ambian's u-boot configuration is incompatible with Radxa's SPI image
 
Why Armbian is using u-boot that is incompatible with Radxa's?
It uses mainline u-boot with Open Source TPL/SPL/proper and BL31 from Rockchip packaged into u-boot and we may switch to using open source ATF instead of the BL31 in the future.
 
Can I boot Radxa's images with Armbian's u-boot written to SPI?
Yes. Armbian's SPI u-boot is compatible with Radxa's images available here: https://github.com/radxa/rock-pi-images-released/releases
It may not be compatible with some older images (released before July 2020) because of the device tree filename change.

Hey Werner,
 
I went ahead and escalated this issue to Innoscale's NOC and they have been reviewing things this afternoon.  It looks like at this time the NOC has pushed out some new routes which looks to have helped to resolve the loss being seen there and causing latent loading of the forum / site.
 
Can you test a bit and let us know if things still continue to see issue via IPv6?
 
I will sub to this so that and updates come to my inbox and can be addressed.
 
Have a great day!
 
Regards,
TheBug

from scratch... I'm working out the exact process now to automate it.  When I have the scripting worked out, I'll format it into proper Armbian format and submit a PR. It was all pretty straight forward to accomplish manually.  Wipe the NVMe and setup several logical partitions to use as encryption stores, add them to fstab, etc. It's all working now.  My biggest gripe is which kernel is supported... so far this is only working on legacy 4.4 and I really want to use 5.7+

I have Wayland/sddm/Sway working as well and will be integrating that as my default managers.

My needs are a little different, I have a fairly tight device in the making.

Yes, I'm working on adding patches.

Are you mainly going to participate live, listen later to recordings or not at all? Any topics that are related, close to single board computer world to recommend?

I am still working on my "shopping list", but this is some initial draft from https://fosdem.org/2021/schedule/
 
QA
About the joy and tears of testing Embedded Devices
https://fosdem.org/2021/schedule/event/testing_embedded_devices/
Interactive debugging inside CI systems
https://fosdem.org/2021/schedule/event/debugging_inside_ci/
QAOps - The Latest Trend in QA & Software Delivery
https://fosdem.org/2021/schedule/event/qaops/

Software Composition devroom
Overview Software Bill of Materials (SBOM)
https://fosdem.org/2021/schedule/event/sca_overview/
 
Legal
Protecting against proprietary re-licensing with a community contract
https://fosdem.org/2021/schedule/event/qtproprietaryrelicensing/
 
CI
ARM your continuous integration system with fruits! by @gounthar
https://fosdem.org/2021/schedule/event/arm_your_continuous_integration_system_with_fruits/
 
Community
Mental health and free software
https://fosdem.org/2021/schedule/event/community_devroom_mental_health_free_software/
 
And one fine Belgian beer for each day of the conference also just arrived  
 
 

I have to say that, after I have done the setup, I am really impressed by the performance of this little beast .
 
Exited to see how it will do its job in the datacenter.
 

It's looking better now. I removed the wire for the antenna from the frame, plugged it back in. And attached the frame.
 
They should have designed the case a bit higher so the hat would fit. But I like it like this. I'll try hirsute now. Been a while since I tried it. 

It works  I upped it a bit more and used the Focal mainline image. 465.76GiB of Samsung EVO 970 goodness. 
That's nice.  Happy.

Now what image should I use for the video? I wanted to use the media script for buster on it to have a great desktop image. 
I could also make a gaming image on it, but I'm not sure many people are interested in that. Could you please share your link again with Armbian TV images? 
Also for N2+ if you've got one. I'd like to use it as headless armbian build server. Thanks.

Yes, meson uses stateful whereas Cedrus and rkvdec use stateless (request api).
Actually only one really worked on this driver but stopped working on most (all?) things due to real-life issues.
Vanilla Kodi will work for video decoding, but if you want HW deinterlacing, that will need Kodi patch and additional one for ffmpeg.