Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Why armbian-release and uname -v don't match ??

Featured Replies

Hi

 

My Orange Pi PC shows 21.08.5 armbian version in /etc/os-release and /etc/armbian-release but 21.08.2 with uname -v

 

Why don't match the versions ?

 

Thanks

Have you rebooted yet?

 

Hypothesis:

The currently running kernel is 21.08.2, but the update has already changed the files.   
 

Run uname -a again after restarting.


These proc filesystem entries are another way to see what and how your currently running machine was booted:

cat /proc/cmdline

cat /proc/version

 

  • Author
1 hour ago, Werner said:

Not every update of bsp necessarily means kernel was updated too and vice versa.

 

Thanks, I thought so, so armbian updates are on one side and kernel upgrades are on the other and don't match if they don't come together so the reliable OS info is.... armbian version info and not uname

 

38 minutes ago, FossCoder said:

Have you rebooted yet?

 

Hypothesis:

The currently running kernel is 21.08.2, but the update has already changed the files.   
 

Run uname -a again after restarting.


These proc filesystem entries are another way to see what and how your currently running machine was booted:

cat /proc/cmdline

cat /proc/version

 

 

Here is the output of those commands (opi PC has been restarted several times since last update):

 

root@orangepipc:~# uname -a
Linux orangepipc 5.10.60-sunxi #21.08.2 SMP Tue Sep 14 16:28:44 UTC 2021 armv7l GNU/Linux

 

root@orangepipc:~# cat /proc/cmdline
root=/dev/mmcblk0p1 rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=5ae5405d-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

 

root@orangepipc:~# cat /proc/version
Linux version 5.10.60-sunxi (root@runner4) (arm-linux-gnueabihf-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #21.08.2 SMP Tue Sep 14 16:28:44 UTC 2021

 

Thanks

29 minutes ago, jmviper said:

reliable OS info

 

It's not just that.


Armbian has to deal with greater complexity than we are used in mainstream desktop Linux PC world. Where you have one hardware interface (kernel) and you don't deal with how hardware boots (you have bios). We cover loading Linux and we have / maintain up to tree kernels per each chip family. Then we have minimal and standard user land favours in 10 different variants (bionic, buster, focal, bullseye, ... ) and 10 different (xfce, gnome, ...) desktop types.

 

Imagine how much things would need to be updated, to unify "armbian" version. Also how much power - currently we rebuild things with only around 240 high end x86 cpu  cores which are barely enough to keep current situation under control.

 

https://docs.armbian.com/User-Guide_FAQ/

  • Author

Firstly, I've put this question in a wrong section of the forum....apologies... secondly, thank you for your explanation Igor, I really enjoy armbian and I applaud you all your huge effort maintaining and developing armbian.

Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.