NicoD

@NicoD
I'm using Armbian_5.99.191102_Rockpi-4b_Debian_buster_dev_5.3.0-rc4_minimal.7z as suggested in a previous post by @martinayotte
 
On top of it, I'm remotely running the mate desktop by means of tightvncserver.  I'm quite impressed by the responsiveness of the desktop, considered that I'm still using the sd card, and accessing the mate desktop over the (wired) network. Things at the moment seem to work quite well, apart from the browsers, both chromium and firefox. Browsing is very slow and after few minutes the whole desktop gets stuck, forcing me to kill the vncserver.
 
I hope I'll be able to do further tests this evening.

As mentioned in this thread and in another one, use RockPi image, it should boot ...
Then, after initial setup, root password and user creation, add this line "fdtfile=rockchip/rk3399-nanopi-m4.dtb" in /boot/armbianEnv.txt to get proper hardware setting.

I have successfully compiled and run http://wiki.friendlyarm.com/wiki/index.php/Buildroot_for_RK3399 on a nanopi m4 v2.  I can confirm that uboot's makefile from these sources reports "version=2014".
My question is: how do I use the  working compiled uboot 2014 version with an armbian image? Is it possible to simply substitute some (compiled) file of the armbian image to do a first very raw try and see if the nanopi m4 v2 board boots and works?
 
Thank you and sorry for my very noob question
 
 

Hi Nico, I fitted the NVME hat to my original M4 today and used armbian-config to install to NVME and all is working fine
 

Have you tried with autodetect on? If that doesn't work disable it by changing "true" to "false". 
Then set the correct resolution :
setenv hdmimode "1680x1050"
And set dvi. 
setenv voutmode "dvi"

Should be this simple. 

Hi,
First of all i'm NOT a software developer and i have NO one skill on this kind of board's hardware...
I've a good soldering skill, so just for fun i've bought a new RAM module for my OrangePi Zero Board...

I've bought a K4B4G1646E-BYMA RAM module and then i've replace the onboard module...
All of the work gone fine, the OrangePi Zero still boot and work perfectly, but i was hoping to upgrade the RAM on the board...
After the boot, in the welcome screen the, the RAM amount is now 512MB (494MB) and before was 256MB...
The RAM amount is now increased, but not like expected...

I've choose the K4B4G1646E RAM module because, theoretically, it was a 4GB RAM module...

What's was wrong? I cannot upgrade the memory in this way? Have i to edit something in the FEX file?


Thanks in advance,
Luca

Ps. my OrangePi Zero come without an inductor, that's why you see an horrible inductor in my board

All questions after the holidays.

lima & panfrost driver (mesa) has been pushed to beta.armbian.com, if you already use beta image or use beta armbian software repo, please just update.
if not please add armbian beta software repo, and update.
 
newer version (19.3-develop) mesa will be installed.
 
you need to follow https://gitlab.freedesktop.org/lima/web#xorgconf
to configure your Xserver.
 
then enjor your mali GPU.

Hi guys,
 
I guess some might have heard that we (Kobol Team) were spinning a new project to succeed to Helios4. Here it is... Helios64
 

 
 
We didn't have to look too far for the board name since in essence the goal was to redesign from scratch Helios4 with a 64-bit SoC and try to improve every key features that made Helios4 a very targeted board for NAS setup.
 
Right now we are at the prototyping test phase, hopefully in a 2 month time will have dozen of Eval boards to send around for evaluation and review... and if all goes well first batch should be available for order in Feb / March 2020.
 
Happy to answer any question :-)
 

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

The NVMe hat 12v fan socket doesn't work at all for armbian, most likely missing a drive or something. I got it to around 50c and the fan didn't even kick in. I have directly connected the fan to the 5v gpio port for the time being works fine not loud at all but downside to this is that you have to fully disconnect the device to power the fan down. Their was some information regarding controlling the port pwn0 link did try it but it completely bricked the account i exported to so. Have not tried friendlyelec desktop as i prefer armbian's clean image.
 
As for cooling i have no problems even with fan off in the metal case as i have used copper shims and thermal paste sits at 30c idle and 40c something under load. I will say its a pain to say the least to do that in the metal case without the copper shim going misaligned. I did try their thermal pad but tbh temps were going up to 50c once the metal case was warmed up. The metal case is alot more effective though then the normal heat-sink they supplied.

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

Just found this thread after googling around to see if PiVPN works with Armbian on an Orange Pi Zero 512MB.
 
Can confirm that it workes perfectly fine on Armbian 5.91 using and Orange Pi Zero H2+ 512 MB Board.
 
Allows me to shut down my open ports on my router :-) Yeah.
 
This is my 3rd Board using Armbian now. 
 
1) Orange Pi One as Pi-hole and Webcam
2) Orange Pi Lite as Webcam
3) Orange Pi Zero as PiVPN
 
Just had to donate to Armbian. This stuff is working very good.

@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 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

not Igor but I can help here..
 
https://github.com/armbian/build/blob/259a0bf5fe3bc9a20709597e43f18421aa3ae4ed/config/sources/rockchip64.conf#L8-L9
 
The Rockpi uses ayufans u-boot which is not upstream (it's based on rockchips u-boot). The former nanopis are supported by upstream u-boot (DDR3 or normal DDR4 should be supported for RK3399 iirc). There were a few attempts so that upstream u-boot can handle lpddr4 but the last I heard is that it's not stable yet (someone from the forum was involved but I don't remember the name.. ).
 
Patch in the defconfig and the DT into ayufans u-boot should be an easy task (I'm confident that friendlyarms is based on the same one.. so not much to patch around).
 
unfortunate I would happily dive in (if there's still a spare one)..

Yes, I know. Waiting for hardware to arrive ... it seems it was sent to a wrong destination  

Looks good! Only thing missing for my linux noobs is a simple tar overview for extracting and creating archives and a simple grep overview
 
Can I win the hat this time please?

No idea. I'll see if I can recreate this with Buster 5.95.
I don't think it's a problem in the meaning of "problem". Just a small bug in either htop or Buster.
I rarely use htop. So others will know more about that.

Agree with you. I'll see the htop source code. Thanks!
 
 
You're right. my htoprc file is same as yours. when I delete and recreate the file it works properly. It might be bug in Armbian customized htop.

Have the same issue with my XU4.
 
I have a workaround for this. Remove all files in /home/[username]/.config/htop and replace it with the files from /root/.config/htop. 
Then all cores are labeled with "big." and ".LITTLE" as usual. But as soon as you change the configuration (for example toggle "Tree" with F5), everything is broken again.
 

A deeper inspection shows, that it has something to do with the file /home/[username]/.config/htop/htoprc.
The config parameter "right_meters" is set incorrectly.
 
For my XU4 the proper params are:
right_meters=Hostname Tasks LoadAverage Uptime CpuFreq(1) CpuFreq(2) CpuFreq(3) CpuFreq(4) CpuFreq(5) CpuFreq(6) CpuFreq(7) CpuFreq(8)
 
HTOP shows the wrong labels when the params are:
right_meters=Hostname Tasks LoadAverage Uptime CpuFreq CpuFreq CpuFreq CpuFreq CpuFreq CpuFreq CpuFreq CpuFreq

Hi all. For a new video I've made a list with my most used/useful terminal commands.
Please let me know what I've missed, or which commands you use most.
 
Useful Linux commands for Ubuntu/Debian --------------------------------------- Update/Install -------------- sudo apt update Update repolists sudo apt upgrade Upgrade system/programs sudo apt autoremove Remove obsolete programs sudo apt install programName Install program sudo apt remove programName Remove program sudo aptitude install When having issue's with apt, aptitude can help to solve this sudo apt update && sudo apt upgrade Update and upgrade together/You can run multiple commands with && sudo dpkg -i packageName.deb Install .deb file Root user --------- sudo passwd Change root password su Super User/Enter root user Debug/Monitor ------------- dmesg Shows debug messages uname -a Shows basic system information env Shows the environment information htop Hardware monitor Switch terminal --------------- ctrl + ALT + F4 (F1 - F6) Open new terminal 4 ctrl + ALT + F1 Go back to terminal 1 ctrl + ALT + F7 Go back to desktop Reboot/Shutdown --------------- sudo reboot Reboot sudo shutdown now Shutdown CPU Tools --------- cpufreq-set -g performance Set governor to performance cpufreq-set -u 2Ghz Set max frequency for all cores cpufreq-set -c 0-1 -u 1.8Ghz Set max frequency for specific cores lscpu | grep MHz Show cpu frequency taskset -c 3 programName Use a specific core for an application Files/Directories ----------------- nano /home/fileToRemove.txt Create a txt file with Nano. You could use any other texteditor. touch filename Create an empty file, no matter what kind cat /home/fileToRemove.txt Shows the content of a file cp /home/fileToRemove.txt /home/copy.txt Copy file find /home/ -iname "*.txt" Search files that end with .txt comm /home/fileToRemove.txt /home/copy.txt Compare files rm /home/fileToRemove.txt Remove file mv /home/copy.txt ~/Documents/ Move file mkdir /home/directoryToGoTo/ Create directory cd /home/directoryToGoTo/ Go to directory ls List directory ls -l Gives more information about every file/directory ls -l filename.txt Gives file information pwd Show current working directory cd .. Go to the above directory rmdir /home/directoryToGoTo/ Remove directory wget http://www.website.com/file.txt Download file Zip/Tar/GunZip -------------- zip myzip file1 file2 file3 Create zip file unzip myzip.zip Unzip file tar xvf filename.tar gunzip filename_tar.gz Mount drives/USB Devices ------------ lsusb List USB devices lsblb List attached drives mount /mount/mountedDisk /dev/sda2 Mount drive sudo chmod -R 777 /mount/mountedDisk Give user read/write permissions df -a List all filesystems Swap file/ZRam -------------- sudo apt install zram-config Install zram script sudo fallocate -l 8G /swapfile Allocate 8GB for swapfile sudo chmod 600 /swapfile Give the correct rights for the swapfile sudo mkswap /swapfile Make it a swapfile sudo swapon /swapfile Turn on the swapfile sudo nano /etc/fstab Open fstab and add the line ... |_ /swapfile swap swap defaults 0 0 Wifi ---- sudo nano /etc/network/interfaces and write: auto wlan0 iface wlan0 inet dhcp wpa-ssid {ssid} wpa-psk {password} OR nmcli device wifi rescan Scan for available wifi networks nmcli device wifi list Show available wifi networks nmcli device wifi connect SSID-Name password wireless-password Connect wifi ip a Show ip ifconfig iwconfig Change Keyboard Layout ---------------------- sudo dpkg-reconfigure keyboard-configuration Set keyboard layout Add display resolution ---------------------- cvt 2560 1440 60 Select the display resolution you want # 2560x1440 59.96 Hz (CVT 3.69M9) hsync: 89.52 kHz; pclk: 312.25 MHz Modeline "2560x1440_60.00" 312.25 2560 2752 3024 3488 1440 1443 1448 1493 -hsync +vsync xrandr --newmode "2560x1440_60.00" 312.25 2560 2752 3024 3488 1440 1443 1448 1493 -hsync +vsync Add resolution, everything after Modeline from cvt is copied after newmode xrandr --addmode HDMI-1 2560x1440_60.00 Add the new resolution to your display xrandr --newmode "2560x1440_60.00" 312.25 2560 2752 3024 3488 1440 1443 1448 1493 -hsync +vsync && xrandr --addmode HDMI-1 2560x1440_60.00 Others ------ reset Clear terminal shift + page up Scroll up shift + page down Scroll down tab Autocomplete ctrl + c Quit for many programs date Show date/time cal Show calender Funny commands -------------- sl First need to install "sudo apt install sl", then try it out. It's great :) sl -alF cmatrix fortune/fortune-mod cowsay figlet toilet ponysay inxi cat /dev/urandom :(){ :|:& };: Endless loop (useful to test CPU maximized temperatures) Armbian ------- sudo armbianmonitor -m sudo armbian-config change cpu settings sudo nano /etc/default/cpufrequtils Made by NicoD  

Pimp your bash. To be fair I copied some from the link at the bottom:
 
A few commands are needed quite often and to reduce typing a little bit, voila: To create the file nano ~/.bash_aliases ############################ # my personal Aliases list # ############################ # to create the file nano ~/.bash_aliases # **** DIRECTORY LISTING in human-readable units **** alias ll="ls -lhAF" alias ..="cd .." alias ...="cd ../../../" alias back="cd $OLDPWD" alias lsmount="mount |column -t" # * Disk Space Usage in human-readable units, including filesystem type * alias dfh="df -Tha --total" alias df="df -h --exclude=squashfs" # * ALL files in a directory listed, according their size * alias du="du -ach | sort -h" # * listing process table in detail * alias psa="ps auxf" alias dmesg="dmesg --human" # * How to really CLEAR the terminal * alias clr='printf "\033c"' alias h="history" # reload bash config alias reload="source ~/.bashrc" Now execute . ~/.bashrc in your terminal (there should be a space between the . and ~/.bashrc )  
https://pastebin.com/kzPjE8y4    |   http://smlr.us/