All Activity

Looks like you have the vendor kernel package installed. If you want mainline kernel, then you need to install the current kernel package. Run armbian-config and see what it tells you are the available kernels for you. Now realize that going from vendor to mainline kernel you might loose some functionality (there is an FAQ item on this), but you can always switch back to vendor kernel if it is important.

Thank you for clarifying. I tested some image from Armbian, but it had several limitations for me. For example kernel v.6 had some problem with internal sound card in my test, while kernel v.5 works with it.

CM4 and 3b have the same SOC.

Hi all, First post here. I have been running Armbian on my original Bananapi Pro for a long while now, and thought that it's time to upgrade from Bullseye to Bookworm finally. There were some complications with UsrMerge that I had to resolve manually (I think some boot files from the original Buster installation were both in /lib and /usr/lib), but apart from that the upgrade appears to have worked: All userspace stuff is on Bookworm. # lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Armbian 24.5.0-trunk.530 bookworm Release: 12 Codename: bookworm However, the kernel seems to be stuck on 5.15: # uname -a Linux bananapi 5.15.43-sunxi #22.05.1 SMP Sat May 28 08:17:47 UTC 2022 armv7l GNU/Linux This version number appears to be inconsistent with the contents of armbian-image-release: # cat /etc/armbian-image-release # PLEASE DO NOT EDIT THIS FILE BOARD=bananapipro BOARD_NAME="Banana Pi Pro" BOARDFAMILY=sun7i BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=85080ff3 VERSION=5.99.191113 LINUXFAMILY=sunxi BRANCH=dev ARCH=arm IMAGE_TYPE=nightly BOARD_TYPE=eos INITRD_ARCH=arm KERNEL_IMAGE_TYPE=zImage IMAGE_UUID=1b7fd79e-803f-4438-8b4c-5e9287a7b86c I saw on the download page that a current download of Armbian Bookwork for the Bananapi Pro would include Kernel 6.6.29, so there should be a newer kernel available. Can you help me troubleshooting what is holding my system back from upgrading to a newer kernel? Various posts on the forum suggest anything from "apt-get upgrade will update your kernel" to "use armbian-config". Using the latter, I tried switch between nightly and stable, which didn't offer any updated kernel to apt. The "Switch to other kernels" option retrieves some files, then shows the "Yes, I understand" screen but then immediately goes back to the main "System settings" screen, which makes me think that something is broken here. How can I find out what exactly is broken?

Thank you! I've checked it and it doesn't contain release for Orange Pi CM4. I went with image supplied in orangepi.org site and it answers my needs (in most cases). BTW, their image has something common with Armbian (or based on).

Hi! I installed for orange 3b from here. I installed "Armbian_community_24.5.0-trunk.522_Orangepi3b_jammy_edge_6.8.8_gnome_desktop.img.xz" Regards

@amazingfate I have one problem with the netflix addon though. It displays a green overlay "fog". Everything else works, I have the Amazon VOD addon working, the Disney+ addon works, I can play H264 as well as 4K HEVC videos with hardware acceleration. Does anyone expierence the same with Netflix? Another thing is, that I have only one working rock 5b image. I have created it myself from armbian with the legacy kernel 5.10.160 as I need custom gpio overlays for using an IR receiver where the driver needs to be activated in the kernel. After that I installed everything based on the howtos for the Rock 5b. I built MPP, RGA, FFMPEG and Kodi and got real nice hardware accelleration. I could, however, never reproduce it to create a current how to. I tried using an edge kernel where the UARTs are supposed to be working and other features should be enabled, but when I start Kodi in a Wayland session I get this: with the following errors in syslog: May 3 12:03:02 rock-5b kernel: [ 185.881239] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0 May 3 12:03:02 rock-5b kernel: [ 185.881258] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0 May 3 12:03:02 rock-5b kernel: [ 185.881265] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0 May 3 12:03:02 rock-5b kernel: [ 185.881271] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0 May 3 12:03:02 rock-5b kernel: [ 185.881278] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0 May 3 12:03:02 rock-5b kernel: [ 185.881284] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0 May 3 12:03:02 rock-5b kernel: [ 185.881299] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0 May 3 12:03:02 rock-5b kernel: [ 185.881306] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0 May 3 12:03:02 rock-5b kernel: [ 185.881312] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0 May 3 12:03:02 rock-5b kernel: [ 185.881319] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0 May 3 12:03:07 rock-5b kernel: [ 190.882731] vop2_isr: 198389 callbacks suppressed I don't know what the difference is. I also get that behaviour using the same base image that is working in a new install. Up to now I did not find anything usefull with google or here in the forums. Maybe someone has seen it and can point me somewhere. Thanks Peter

Hi @Kein, I made good expierience in building kodi and the inputstream.adaptive - addon from the sources on github and not using the repository versions.

Description As per the title. Allows using emmc for boot partition and nvme or usb for root partition when installing via armbian-install. How Has This Been Tested? [X] Created and booted image on VIM1S with emmc+USB combo Checklist: Please delete options that are not relevant. [X] My code follows the style guidelines of this project [X] I have performed a self-review of my own code [X] I have commented my code, particularly in hard-to-understand areas [X] My changes generate no new warnings [X] Any dependent changes have been merged and published in downstream modules View the full article

@VanGeldon Seems like an old image, try one from here: https://imola.armbian.com/dl/orangepi5/archive/ When you choose an image with amazingfated and Wayland like Gnome or KDE you probably only need to install Kodi. By the way when I search the package with apt search, this is the result: libgjs0g/jammy-updates 1.72.2-0ubuntu2 arm64 So or it's corrected or you've got other sources in /etc/apt/sources.list deb http://ports.ubuntu.com/ jammy main restricted universe multiverse # deb-src http://ports.ubuntu.com/ jammy main restricted universe multiverse deb http://ports.ubuntu.com/ jammy-security main restricted universe multiverse # deb-src http://ports.ubuntu.com/ jammy-security main restricted universe multiverse deb http://ports.ubuntu.com/ jammy-updates main restricted universe multiverse # deb-src http://ports.ubuntu.com/ jammy-updates main restricted universe multiverse deb http://ports.ubuntu.com/ jammy-backports main restricted universe multiverse # deb-src http://ports.ubuntu.com/ jammy-backports main restricted universe multiverse

Try this https://launchpad.net/~savoury1

Hi Thomas, thanks for your report - I was thinking about a cronjob too o something that monitors dmesg nevertheless, as a mitigation to avoid a reboot when wifi stops I can suggest: sudo rmmod sprdwl_ng && sudo modprobe sprdwl_ng Definitely not elegant, but gets wifi back from the dead until the next band hop Hope it helps Ale

@kuber gld This might be the answer

Following initial steps with Armbian_23.8.1_Orangepi5_jammy_legacy_5.10.160_xfce_desktop at sudo apt install ubuntu-desktop kodi receiving The following packages have unmet dependencies: gjs : Depends: libgjs0g (= 1.72.2-0ubuntu2) but 1.72.4-0ubuntu0.22.04.1 is to be installed E: Unable to correct problems, you have held broken packages.

Yes, the cpu temperature is about 40 °C.

lsusb should display USB devices.

Are you using proper cooling?

Plug in another usb-serial device, see what happens in that case

I tried another version: armbian_23.02.0-runk_Onecloud_jammy_edge_6.1.9_minimal.burn.img It shutdown about every 10 minutes. log uploaded here: https://paste.armbian.com/reseqowita armbian-hardware-monitor.log dmesg.0 kern.log 23.02.0-shutdown-every-10-minutes.txt

@martivo are you using beta or stable?

Description Use radxa's next-dev-v2024.03 branch for armsom's boards. Note that I have to remove CONFIG_OPTEE_ALWAYS_USE_SECURITY_PARTITION=y from defconfig to boot the board. So boards affected by https://github.com/armbian/build/pull/6534 like nanopi6 and nanopc-t6 should also check this. @efectn @Tonymac32 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] ./compile.sh BOARD=armsom-sige7 BRANCH=vendor BUILD_DESKTOP=no BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=bookworm KERNEL_GIT=shallow Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article