balbes150

I tested the latest versions from this link, booting from USB media works and all items work with DTB by default (except NVMe). By default, DTB does not support NVMe, if you need NVMe, you need to replace DTB with a second link.
 
https://yadi.sk/d/TnDjwCsvG9-nuA?w=1
 
DTB for NVMe
https://yadi.sk/d/UgUTCAw8mxijYw?w=1

What model do you want to run on ?
 
You can take these files (need two files\libraries) from your x86 host system, or from any of my images (ArmbianTV\Armbian for M1\P1). Or from my GIT (these libraries are included in all my builds, so that users can easily run the build themselves on any ARM device). by the way, the site has versions of images with these libraries for n2 and t4. 
 
https://users.armbian.com/balbes150/

I found the marking of the sound chip - this is es8388

I don't have a good camera. I did take some pictures of the top, not from the bottom. I did film the replacing of the thermal pad, but it isn't sharp enough to see anything. I'd need to disassemble the whole thing to be able to see the bottom. 

There are some pictures of it here. https://download.t-firefly.com/产品规格文档/开源主板/ROC-RK3399-PC Plus - Specification.pdf?


I'm using a normal 1080p pc display. No tv. I'll try again. I also tried the focal mainline from your folder and it also didn't boot. Also stuck at those stripes. I didn't know USB boot worked. I'll try that too. 

@NicoD  I uploaded new Legacy images 20210204 to the site with support for WiFi NVMe and analog audio for the P1.

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

You don't need to change anything. I found a solution-changed the patches so that can now use a common core for p1. 

I am already in the upload process ... need to push out this release faster to merge desktop branch sooner. An update release just for those boards can be done whenever ready, next week perhaps. Don't worry.

Yes, I'm working on adding patches.

The DTS patch is sufficient to enable NVMe. For the rest of the elements-I'm just now preparing patches for the current Legacy kernel (rockchip64), which is used to build the version for P1 in the official GIT.
 
 

@NicoD try this image, it's with a new kernel and DTB.
 
https://yadi.sk/d/1vS1NGwoYnQWVQ?w=1

@NicoD Can you try with the current version of Buster-legacy this DTB ? With it, you should have NVMe. There will also be a device for analog sound, but without patches in the core itself, the sound does not work (in the new image with patches, the sound and remote control work).
 
https://yadi.sk/d/VnNZwpT0Sfbf8Q

I meant the release of a new model P1 (if the manufacturer releases one), in which the M2 connector will be built into the main board (for example, as it is done on the Firefly rk3399 or on the NanoPC T4).
 
As for the photos, this is @NicoD, we have a specialist, I hope he can make them.
 
 
The good news is, I'm currently testing a new "old " kernel (legacy) that runs NVMe, analog audio, and remote control on the P1. I hope to upload a new Buster-legacy image with this core to the site soon. By the way, do I need to build more versions of Focal \ Bullseye, etc. with this kernel ?
 
https://yadi.sk/i/jICyz61XLYsoGw

Awesome. This performs better than my M4V2. M4V2 does 750MB/s max. This does 850MB/s.
@balbes150There seems to be an issue with Hirsute mainline. Some apps don't work right. Like gparted. It doesn't open when you click it in the applications menu. 
You can start it with 'sudo gparted'. 
For gnome-disks it doesn't as for a password to do a task, so it fails it. When you load it with 'sudo gnome-disks' it does work as expected.
Also when doing reboot it goes into AndroidTV instead of rebooting to hirsute. 
NVMe does work.
I'll try sid now. 

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. 

If @JMCC adds a script for the main kernel, then any version can be used. 
Personally, I like the latest Hirsute. I am testing the latest versions (Hirsute and Sid) and see a significant improvement regarding Focal and Bullsey. As far as I know (when building LE with the main core), the main core now has all the components for HW.
I am quite satisfied with the main core, even without HW, it is enough for full-screen video in 1080p mode (this is the main mode I use, 4k is too small for the desktop).
 
I regularly update all the latest images on the site 
http://bbs.t-firefly.com/forum.php?mod=redirect&goto=findpost&ptid=2781&pid=13344&fromuid=636914
 
I don't have N2+. I try not to release versions for hardware that I don't have (this creates a lot of problems for me, users ask questions and describe problems, but I can't test and fix them, so I avoid creating such variants).

The old LEGACY kernel does not see NVMe. Need to understand the configuration and DTS. But there's no time for that yet.

I checked it again now. NVMe works with all ArmbianTV and Armbian images with the main core. I didn't check the legacy kernel. Here is a screenshot. Please note, the hat is very sensitive to the contact fit, if you put it on too tightly, NVMe does not work. You need to slightly raise the hat over the main board, so that there is no contact with other elements.
 
https://yadi.sk/i/cWmayDV-hH0D5Q
 
Disk /dev/mtdblock0: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mmcblk2: 29.12 GiB, 31268536320 bytes, 61071360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x72dd71e9
Device         Boot   Start      End  Sectors  Size Id Type
/dev/mmcblk2p1        30720  1038335  1007616  492M  c W95 FAT32 (LBA)
/dev/mmcblk2p2      1040384 61071359 60030976 28.6G 83 Linux

Disk /dev/nvme0n1: 232.91 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 970 EVO 250GB               
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x95cda040
Device         Boot Start       End   Sectors   Size Id Type
/dev/nvme0n1p1       2048 488396799 488394752 232.9G 83 Linux

Disk /dev/sda: 14.73 GiB, 15795748864 bytes, 30851072 sectors
Disk model: Transcend 16GB  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd59e383c
Device     Boot   Start      End  Sectors  Size Id Type
/dev/sda1         32768  1081343  1048576  512M  e W95 FAT16 (LBA)
/dev/sda2       1081344 30542559 29461216   14G 83 Linux
 
 
armbianmonitor
https://yadi.sk/d/iw5-pIbZWEucmQ
 
 

No and armbian-config needs to be written from scratch. We have talked about to:

- discuss how to do this @tparys
- make a plan
- divide work into several parts. 

It's a lot of work so we should plan it carefully. I would propose to finish desktop integration first - which is also a very big change, then we go for this. But we can already start talking about - "how to to do this?".

We had some troubles with torrents which is why all those caches were deleted - I planned to make new ones, then this bug was found. I am already building caches on ARM server now.
 
In 900s, those were made. A few more ... signing, uploading. ... some food in between, ... soon.
 
 

Checked the minimal version of DE XFCE - gives an error. This means that among the packages that are included in the lists of additional groups, there is something that allows quemu to work correctly. Now I will look for this "something".

A test version of the image Armbian for TV boxes on the basis of RK3328. Tested on MVR9
http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/653167-bqeel-mvr9-rk3328-quad-core-64bit-cortex-a53-android-7-2-16gb-2-4ghz-wifi-bt4
 
All basic functions work. For running. Download. Unpack. To record on the SD card. Connect the SD card to TV box, connect a keyboard and mouse. To turn the power on the TV box. The system should start within 2-3 minutes. You must perform the initial configuration of Armbian.

https://yadi.sk/d/DSO6euzB3ahemo
 
https://mega.nz/#F!zoZywCTQ!9sNfXIAB3m_DyLl5I8P94w
 
The system of choosing the correct dtb has changed.
Please note, now it should be done on a different principle (files do not need to be copied).
To select the desired dtb, you need to change the line in the text file "/extlinux/extlinux.conf". In the line "FDT" you need to change the name of the file that the system will use at startup. The list of available files (names to specify in the configuration) can be found in the "dtb"directory. If you do not know exactly what file you need , you can enter all available names in turn and check the operation of the system. In accordance with this, the system installation script in eMMC has been changed. The steps to install the system on the eMMC remain the same.
 
Added a utility to full backup and restore the entire eMMC "ddbr". Checked mode the backup MVR9. Now if you try to check the recovery mode.
 
The order of installation in eMMC.
 
1. Download, unzip and burn the image to SD card.
2. Start Armbian on the TV box and perform the initial setup of the system.
3. If the system works correctly and you are satisfied, run the utility "ddbr" and create a full backup of eMMC (this is a prerequisite).
4. Rename the file "/boot/mvr9-uboot.img" in "/boot/uboot.img".
5. Run as user "root" script "/boot/create-mbr-linux.sh"
6. To run the script "/root/install.sh"
 
Pay attention to the correct operation of the installation procedure need to comply strictly with the order of the steps.

Armbian have historically been much more geared towards "server/headless" usage, for many different reasons.  It has taken a much longer time not only for upstream development of underlying graphical libraries / drivers to mature, but also for us (the Armbian project itself) to come up with a sensible implementation that would fit nicely into our existing build framework.
 
However, this work has been going on in the background for quite some time already. 
 
Announcement
 
Finally, the time is right to announce we are publishing our initial implementation of these "desktop" features!
 
Warning!

We are only announcing this here on our own forums for the time being, as this is still early days.  In fact, at this point we are still mainly looking for testers. You should consider this an alpha quality release at this time!
 
What works so far?

Features we plan to develop works, we are already hunting bugs for months, but they are certainly still present. Remember, we are not looking for bugs that are tied to specific hardware feature, but bugs that are linked to the build process, userland and basic desktop functionality. 
 
Report bugs in Armbian build framework section: https://forum.armbian.com/forum/12-armbian-build-framework/
 
Currently, the following Desktop Environments (DEs) are considered to have early "support":
 

 

 
In addition, there are more DEs which should be considered very much WIP, in other words, not really fully working (yet), but we designed a system that can have unlimited variants.
 
Help Wanted!
 
These changes are wide ranging and touch many parts of the code.  Therefore even if you don't plan on using any "desktop" features, your testing can help to find bugs, even in "server" versions (as eventually this code will be merged with master in matter of weeks).
 
If you have been looking for some opportunity to help the project by getting involved a bit more, this could be your chance!

When you notice a problem make a pull request: https://github.com/armbian/build/pulls ( currently sits on a branch "desktop" )
 
Going forward we will be looking for additional desktop maintainers.  Currently the plan is for the Armbian core team to maintain the framework and perhaps settle on 2-3 DE options.  Any which are to be considered in addition to that, will need to come with some commitment to ongoing maintenance by whoever is interested in those additional desktops.
 
Join #armbian-devel IRC channel for development level chat and strengthen the desktop team. Welcome!
 
Getting Started
 
If this is your very first time using the build scripts, start with general instructions. If you are already familiar with the basics of building, some additional detailed instructions pertaining to desktop features can be found here.  You will also need to add:
 
./compile.sh LIB_TAG=desktop EXPERT=yes  
If you don't have option or desire to build from sources, you can also check if your board has nightly images - we are compiling them from this new development branch for a few weeks now - for the desktop you want to try / see:


 
Documentation
 
For end users, if you just want to build image interactively and by choosing supported OS variants, things hasn't changed much and should just work while advanced documentation has changed significantly. Its pretty much WIP and is scattered around in those files:
 
https://github.com/armbian/build/blob/desktop/config/desktop/README.md
https://github.com/armbian/documentation/pull/125
https://github.com/armbian/documentation/pull/98
 
Additional
 
During this change we also added most recent userland(s):
 

I just enabled the 1.5Ghz OPP for legacy. The board is clearly the fastest RK3328 I've used so far, most probably due to good emmc and memory, plus great thermal management.
 
Due to the good thermals , I dared to dial down just a few uV from our standard 1.5Ghz OPP patch (1425000 instead of 1450000). I tested it extensively and found it stable. Reducing it to 1400000 caused some occasional instabilities.

I tried with an application Pi SDCard image writer, or something like that, but it does not allow to download images, and proposes only images for the Raspberry.
I then found another application that would burn whatever image you give it, but... it needs a rooted device.
I tried lots of one-click root application (bad idea), but none of them worked.
I then switched to recovery mode, and tried to install TWRP (specific to RK3399 TV boxes), but it fails with an error 21.
Even the opengapps fails the same way.
I tried it with adb sideload, but it fails the same way.
Would someone have a link to a working TWRP for this box, or to a way to root it properly?
As @balbes150 asked, the goal would be to write a tutorial for people wanting to switch from Android to Armbian in the case they have just this computer available, and nothing else.
Thanks.