balbes150

All questions after the holidays.

New image 20191025  DEV.

I checked on old USB 2.0 flash drives, reboot and shutdown work. I notice on different TV box models that rebooting and shutting down work better on slow devices than on fast ones.

Ok ! I will try in the next few days ...

Armbian (5.98_20191018) and Libreelec KODI-19 (kernel 4) 20191018 images update for rk3399 platform with USB startup support. Important change. When testing these images on Magicsee N6 Max (rk3399) and MVR (rk3328) I found an interesting nuance. If you install one of the versions of Armbian or Libreelec in eMMC of these models with support for launching from USB, you can write to a USB flash drive any version of the image for rk3399 or rk3328 and use it on both platforms (on TV boxes with rk3399 and rk3328 at the same time). I. e. the image from rk3399 can be run on rk3328 and Vice versa (you only need to correctly specify the desired DTB in the settings).
 
 
p.s. On Magicsee N6 Max running from USB works on both USB 2.0 ports (on the left side of the TV box).

New image 5.98 20191008
 
I sent a request to update the AML-g12 kernel (5.3.0) for AML images to a network repository.
Pay attention.
This kernel and the following aml-g12 images change the location of DTB files. They are now located at (/boot/dtb/amlogic).
The composition of "deb" packages with the kernel has also changed. I now use one "image" package for all files (the DTB package has been abolished and is no longer used).
For anyone who will update the kernel using the new kernel package, be SURE, after installing the package and BEFORE rebooting, to edit the files (uEnv.ini, extlinux.conf and boot.ini), add the "amlogic" subdirectory to the DTB setup line. The string must look like (/dtb/amlogic/filename.dtb). This information applies to all new images that will be released from now on.

N6 goes up to 1.70 .LITTLE and 2.02 big. with this
rk3399-rock-pi-4-2.dtb rk3399-rock-pi-4-2.dts

@balbes150 
I've tried with next bionic desktop and default bionic desktop. Both on an sd-card, but used a usb3 sd-card reader for one.  Changed the background to see the difference.
On the RockPi4. Both images work(hdmi works, no wifi in default). When having default in the RockPi4 it always boots the default, no matter where I put the sd-card reader with next.
With next in the rockpi4 and the sd-card reader in the bottom left usb3 port nothing seems to boot. The sd-reader turns on and flashes(doesn't do that in other ports). It doesn't seem to boot, display doesn't turn on. Flashing of sd-card reader stops after a few seconds, led stays on. 

With the NanoPi M4V2 there's no .dtb file for the NanoPi M4(also not in Buster) in default. I've copied the one from NEXT. It seems to boot, but without hdmi(as that other person said in the M4V2 thread). 
So I had the same behaviour as with the RockPi4. Only with next it seemed to boot from the sd-card reader. It even kept flashing as if it was booted. But since hdmi doesn't work on the default image I'm now not sure if it booted or just was stuck like the RockPi4.
I also tried with LE on the M4V2. That didn't boot into KODI. It did it reseize, rebooted. But stayed at the screen of just enough os for kodi without going further. 
That also didn't seem to boot from USB. And also with LE in the M4V2 it didn't boot Armbian from USB. 

I hope you're something with this information. It only made me more confused the longer I tried. 
Great job. Very cool to be able to run from USB. And also great to be able to use the same image on different boards. You make the compatibillity so much better with this. Cheers.

@NicoD
You can check on the rk3399 available to you the possibility of starting the system directly from USB media ? Unfortunately I only have EDGE, I checked on it, everything works. I'm wondering if other models will be able to run from USB.
 
 
 

I checked the latest DEV and NEXT images on N6. The system starts and works with dtb rock-pi-4. 
Only need to wait 4-5 minutes until the system starts (a picture will appear on the screen).
 
By the way, I just checked, on N6 starts LE with 5 core, but you need to wait more than 5 minutes until the setup wizard starts.
 

I tried both DEV and NEXT on the M4V2. Both boot after a while. Both don't have wifi working. No on-board, and none of my usb wifi dongles work. Also my 7" display doesn't work, so I can't connect it to ethernet.
USB ports do work. I tried an ssd and it mounted normally.  I've used the nanopi m4.dtb. I'll see if another dtb's gives more succes.

With the RockPi NEXT everything seems to work well. Wifi works. Even 5Ghz. Can't see anything wrong. 
On my own dev 5.3 RC4(also 5.4) it also takes that long to boot. But I can choose to clock to 1.5Ghz/2Ghz while yours only goes to 1.4Ghz/1.8Ghz. (with armbian-config cpu tool)
I'd like to see 1.5/2Ghz back as an option. It's stable, better performance, but leave 1.4Ghz/1.8Ghz as default so people can choose to clock higher. 

Now burning DEV for the rockPi. I guess it'll work well, I'll see if other dtb files can make usb wifi work for the m4v2. 
EDIT:
DEV indeed works as well on the RockPi4. 
I tried different dtb files on the m4v2. Only neo4 boots with display. T4 boots without display. rockpi didn't boot, khadas v didn't boot...
EDIT 2:
ZRam ain't working on rockpi4. I guess it'll be the same on the others? 

@NicoD  can you try running on M4v2 and on PockPi4 image for rk3399-tv ?
 
I'm primarily interested in running the DEV and NEXT variants (with kernel 5.x).
 
https://yadi.sk/d/HLVJ8FlLHEQpUQ

New image 5.98 for rk3399
"default" and "dev"

I'm not going to waste my time on all the shit that manufacturers shove in their crafts (just to write on them - WiFi available). Want to have WiFi, you have several options.
1. Use normal equipment where there is guaranteed WiFi support.
2. Use external USB WiFi with good support.
3. Themselves add the necessary support for your WiFi.
4. You seek from the seller\manufacturer of your equipment the necessary support.

I'm not going to waste my time on all the shit that manufacturers shove in their crafts (just to write on them - WiFi available). Want to have WiFi, you have several options.
1. Use normal equipment where there is guaranteed WiFi support.
2. Use external USB WiFi with good support.
3. Themselves add the necessary support for your WiFi.
4. You seek from the seller\manufacturer of your equipment the necessary support.

I totally agree with @balbes150.
In my opinion, what he's doing is absolutely great.
Maybe it's easy to forget @balbes150 is doing this for free, and maybe we don't know how many hours he's spending on doing this (I bet some of them, everyday).
 
Thank you, Mr. @balbes150: I think you should be paid by ATVs manufacturers, because, thanks to your work, and only in my case, they have sold 3 Amlogic ATVs (to me); and I had never bought them because of Android: It's your Armbian, the reason
 
To be sincere, I'm happier with my ATV boxes, running @balbes150 Armbian,  than I am with my Raspberrys, covered by tons of dust in this very moment.

I'm not going to waste my time on all the shit that manufacturers shove in their crafts (just to write on them - WiFi available). Want to have WiFi, you have several options.
1. Use normal equipment where there is guaranteed WiFi support.
2. Use external USB WiFi with good support.
3. Themselves add the necessary support for your WiFi.
4. You seek from the seller\manufacturer of your equipment the necessary support.

New image 5.98

New image 5.98

New version of SPIboot 20191003.
Added support for running official Armbian images (although more correctly, you need to change the logic of creating an image in official images).
Fixed a bug with the kernel and now there is a full image for the SD card to update SPIboot.

New image 5.96_20190920

The new version of the images for RK3399 5.96_20190920.
Added support for NanoPC T4.
Added items for priority use of big cores.

New image 5.96_20190918
 
fix wifi

It's been a while since I read this topic .... For reference u-boot-2019 and kernel 5.x have been working at N2 with Armbian (Including sound.).

It's been a while since I read this topic .... For reference u-boot-2019 and kernel 5.x have been working at N2 with Armbian (Including sound.).