TonyMac32

Just built/tested desktop Bionic for this board, flashed to eMMC and from USB, added topic in "Bring-up" to move it to "Supported".

I liquid cool my XU4 if I had the HCx it would probably be better off, but nowhere near as cool. ;-)

The N2 has some patches to fix the USB3 to my understanding. I haven't tried them just yet, or perhaps Igor has integrated it already...

The Renegade Elite has an add-on board for nvme and a wifi, and a nice case with giant heatsink that should dissipate far better than the M4 (but is generally larger).

All that said, the XU4 and relatives are still king for all-around performance and software support. I have the big heatsink one set up for retro gaming, if(once) the RK3399 or s922 are finally properly supported (looking at you Rockchip, shame on you for your RAM bullshit, and Amlogic, one word, "blobs").

Sent from my Pixel using Tapatalk

That would be pretty interesting to debug, I've always been horrified at the "division of labor" between the two, sometimes U-boot configures some hardware and the kernel just assumes it's there, sometimes not, no standard... 
 
Drive levels are a possibility, perhaps the 4.4 kernel is assuming U-boot configured the I/O levels, or maybe a regulator is being set up in FriendlyElec's u-boot that isn't in mainline.
 
All I know for sure is I want anything with RK3399 in it to behave logically and consistently, which seems too much to ask most of the time...

Yes, NEW Linux rockpi 4.4.198-rockchip64 boot fine SPI without SDcard
(Kingston A2000 NVME), also Gigabyte SSD M.2 2280 PCIe x2

Release details

https://docs.armbian.com/Release_Changelog/
 
Upgrading your Armbian to v19.11.y
 
This upgrade is changing kernel branch names and first upgrade is not done via regular apt-upgrade process, but you have to login as root or get super user privileges with sudo su. Than do the following:
apt update apt upgrade armbian-config -> system -> Other -> select either legacy or current with v19.11.3
 
 
Choose latest version of 19.11.x and select upgrade according to this scheme:
Odroid XU4 default, next or dev -> legacy (stock 4.14.y) Allwinner default, next, dev -> legacy (4.19.y), current (5.3.y) Odroid C2 and other meson64 boards -> current (5.3.y) Odroid N2 -> legacy (4.4.y), current (5.3.y) Tinkerboard and other rockchip boards -> legacy (4.4.y), current (5.3.y) Cubox and Udoo -> imx6 current (5.3.y) Helios 4 and Clearfog -> mvebu legacy (4.14.y), current (4.19.y) Espressobin -> mvebu64 legacy (4.14.y), current (4.19.y) Those upgrades were tested manually:
 

Note: upgrade will replace your boot script. In case you made changes, you can find a backup in /usr/share/armbian
Main build system changes
Due to changes in branch names and removal of all legacy kernels < 4 your predefined automatic scripts might need updating. Temporally quick fix is to add
LIB_TAG="v19.08" to your build config file which by default is:
userpatches/config-default.conf Then run your script as you did before.
 
Thanks to all who are contributing their time to Armbian in various forms and especially developers who contributed to this release. Also thanks to the greater kernel developers community which are playing great role in this.

In case you want to participate, you are more then welcome. Step up and start making changes! In case you run into the troubles or find a bug, forum is the place for talking about while fixes you are welcome to prepare and send here.

Note: some images will be missing today and tomorrow from the download section. Missing one are being created and uploaded but this takes time ... Most of the images were manually tested for booting, upgrades as stated above, but we can't afford to make stability, functional or just boot auto tests on industrial scale. Not with our ultra tiny resources. Perhaps in the future if "you" will support that.
 
Enjoy! 

Quick update on DingleBerry Pi...
 
Schematics - done - It's essentially a respin of the QC/Atheros reference design into a Pi board form factor.
Layout/Gerbers - done - 4 layer board, single sided - nice to have a friend with an Orcad license from Cadence.
 
Specifics
MIPS24kc @ 650Mhz - big endian 802.11n - ATH9K driver - 2*2:2 for 300Mbps at 2.4GHz (wide channels) - PCB trace antennas Two 100Base-2 Ethernet - WAN dedicated port, LAN on switched port One USB-A for peripherals MicroUSB for Power/Console 32MB SPI-NOR flash - uboot and OS 128MB SPI-NAND flash - extending FS for application and user space 64MB DDR2 RAM SW - OpenWRT Master on the ATH79 target Bootloader - uboot with Pepe2K mods (web server fail-safe)  
The 4351 does have PCIe, but I've decided not to implement
 
Performance Targets:
Reference board is good for 100Mbps WiFi and NAT LAN/WAN performance so fairly balanced there. Power - 5V5DC, 1000ma for PS - right now with everything active on reference design, we're around 850ma at max load.  
BOM is reasonable, COGS says we're around $50USD to cover the NRE and breakeven with 1K boards with kits (box, cables, boards, ac adapter)
 
I will not build/ship at a loss... So the next step before doing the engineering sample boards it to gauge the potential market interest.

It works GREAT!

I've been following that project - good work there...

Here's something crazy - found this in my goodie/junk box... mad dog linux something or other - from back in 2006 timeframe - well before kickstarter.
 
PowerPC device implemented on an FPGA - the shiny item is a fingerprint sensor that would log a person in...
 
Mounted as a mass-storage device, with a lightweight desktop environment that one would run in Windows 98...
 
The SD Card (or maybe MMC) was for storage for the linux space, booted off the internal flash...
 

Sigh...  My guess (entirely guessing, I have not looked yet), is that we or Mainline fixed the Rev 3, which broke the Rev 2.  I am not entirely pleased at the significant hardware changes made by Pine in this case, it is causing problems...

Sigh...  My guess (entirely guessing, I have not looked yet), is that we or Mainline fixed the Rev 3, which broke the Rev 2.  I am not entirely pleased at the significant hardware changes made by Pine in this case, it is causing problems...

https://github.com/buildo/react-components/pull/1367
 
Conclusion: we definitively need a nemobot as well here...

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.).

I will double check this, but my "Le Potato" board seems to have no trouble with 4K screens (I don't often test this feature, it's my main monitor, I don't have a second test monitor so the test is a little disruptive of my work flow)
 
[edit[ It took it a long time to bring up the desktop on this 5.3 RC kernel, but Le Potato:
 

Added (untested) nightly images:
https://dl.armbian.com/kvim1/

Added nightly minimal images (root ≈ 500 Mb in size) for La Frite.
https://dl.armbian.com/lafrite/

Thanks goes to @Neil Armstrong and BayLibre, they've been handling mainlining Amlogic.  I simply curate any additional patches and keep things playing nice with the build system.

Thanks goes to @Neil Armstrong and BayLibre, they've been handling mainlining Amlogic.  I simply curate any additional patches and keep things playing nice with the build system.

A very thank you to TonyMac32 and the great Armbian comunity!
 
I've compiled the desktop image with no special options (just select the target) and everything is running very nice.
The CPU clock is set to max 1.5 GHz, slightly overclocked but it runs without headsink around 50-60 °C on high loads the temperatur rise up to around 65-68 °C in my case.
OpenGL (glxgears) and Gles2 (es2gears) runs fine, even the WebGL in Chromium is supported.
Video is not HW accelerated in included mpv and Chromium, I think there are any patches needed, but its ok at the moment.
 
I have only one problem, there is no audio. Only the DummyOutput is present. aplay -l says no soundcards found...
dmesg has no message related to "sound" or "audio". USB soundcard works pretty well but is not that great experiene
 
Can someone give me a hint to get sound working? load missing modules etc.?
 
For easy testing, the image i compiled can be downloaded here (7zip file): https://drive.google.com/open?id=1Xl-4_R1aolxJMZFqlZdb0voNxOxbJ4PC
 
regards

OK, so, if you are the sort to build it yourself, you can.  It's under WIP/CSC, and is currently kernel 5.2.y.  You can do a couple things, one is to flash the image (using etcher) to a USB keyfob, the other is to update your firmware, then use a USB A to A cable from the closest USB port to the IR sensor.  Power up, hitting escape to interrupt the boot process, then type in
 
ums 0 mmc 0 to get the device to show up on the host computer.  The use etcher to flash the image right to the eMMC on the La Frite.

_ _____ _ _ | | __ _ | ___| __(_) |_ ___ | | / _` | | |_ | '__| | __/ _ \ | |__| (_| | | _|| | | | || __/ |_____\__,_| |_| |_| |_|\__\___| Welcome to Ubuntu Bionic with Armbian Linux 5.2.8-meson64 System load: 1.23 0.45 0.17 Up time: 5 min Memory usage: 11 % of 967MB IP: CPU temp: 55°C Usage of /: 4% of 56G Well then.  Give me a few to get it committed.

_ _____ _ _ | | __ _ | ___| __(_) |_ ___ | | / _` | | |_ | '__| | __/ _ \ | |__| (_| | | _|| | | | || __/ |_____\__,_| |_| |_| |_|\__\___| Welcome to Ubuntu Bionic with Armbian Linux 5.2.8-meson64 System load: 1.23 0.45 0.17 Up time: 5 min Memory usage: 11 % of 967MB IP: CPU temp: 55°C Usage of /: 4% of 56G Well then.  Give me a few to get it committed.

Omg it's happening!!!!!!

Added a wip target to the build system, it is dev kernel only, and builds just fine, however booting is another issue I've not spent a lot of time with yet:
 
Found U-Boot script /boot/boot.scr 3048 bytes read in 11 ms (270.5 KiB/s) ## Executing script at 08000000 154 bytes read in 5 ms (29.3 KiB/s) ## Error: Can't overwrite "ethaddr" himport_r: can't insert "ethaddr=00:50:43:84:fb:2f" into hash table 8101414 bytes read in 217 ms (35.6 MiB/s) 16093192 bytes read in 416 ms (36.9 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 232 bytes read in 26 ms (7.8 KiB/s) Applying kernel provided DT fixup script (meson-fixup.scr) ## Executing script at 34000000 ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Created: 2019-08-12 5:04:59 UTC Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 8101350 Bytes = 7.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree The device tree is there in the /boot/fdt/amlogic folder, and the script is the same for Le Potato/ Khadas Vim/Nanopi K2 and works.
 
[some minutes elapse]
 
I think I found it, the printenv (had to figure out the UART, not an easy task) shows me
 
fdtfile=libre-computer/aml-s805x-ac/platform.dtb
 
...which is completely wrong in a normal context, where it should match the linux device tree:  meson-gxl-s805x-libretech-ac.dtb
 
I'll try to figure that out later.
 
 

Added a wip target to the build system, it is dev kernel only, and builds just fine, however booting is another issue I've not spent a lot of time with yet:
 
Found U-Boot script /boot/boot.scr 3048 bytes read in 11 ms (270.5 KiB/s) ## Executing script at 08000000 154 bytes read in 5 ms (29.3 KiB/s) ## Error: Can't overwrite "ethaddr" himport_r: can't insert "ethaddr=00:50:43:84:fb:2f" into hash table 8101414 bytes read in 217 ms (35.6 MiB/s) 16093192 bytes read in 416 ms (36.9 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! 232 bytes read in 26 ms (7.8 KiB/s) Applying kernel provided DT fixup script (meson-fixup.scr) ## Executing script at 34000000 ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Created: 2019-08-12 5:04:59 UTC Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 8101350 Bytes = 7.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree The device tree is there in the /boot/fdt/amlogic folder, and the script is the same for Le Potato/ Khadas Vim/Nanopi K2 and works.
 
[some minutes elapse]
 
I think I found it, the printenv (had to figure out the UART, not an easy task) shows me
 
fdtfile=libre-computer/aml-s805x-ac/platform.dtb
 
...which is completely wrong in a normal context, where it should match the linux device tree:  meson-gxl-s805x-libretech-ac.dtb
 
I'll try to figure that out later.