Jerry Jyrer
-
Posts
51 -
Joined
-
Last visited
Posts posted by Jerry Jyrer
-
-
The work around [trusted=yes] no longer works. As Igor said, Bionic one is not signed.
If you must,
$ sudo apt update -o Acquire::AllowInsecureRepositories=true -o Acquire::AllowDowngradeToInsecureRepositories=true
for the time being while it's being solved (hopefully, it is).
-
1 hour ago, IgorS said:
Ok, than I need just wait. No problem, this is not such a big issue.
here's what I did to get around the issue in the meantime:
$ cat /etc/apt/sources.list.d/armbian.list deb [trusted=yes] http://apt.armbian.com bionic main bionic-utils bionic-desktop -
Errors shown when doing
$ sudo apt update ... Ign:1 https://armbian.tnahosting.net/apt bionic InRelease Get:8 https://armbian.tnahosting.net/apt bionic Release [17.5 kB] Get:9 http://ports.ubuntu.com bionic-updates InRelease [88.7 kB] Ign:10 https://armbian.tnahosting.net/apt bionic Release.gpg .... E: The repository 'http://apt.armbian.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. -
3 hours ago, Werner said:
Maybe there is an issue with switching to a different board family which is usually not the case
35 ii linux-dtb-current-rockchip64 21.05.1 arm64 Linux DTB, version 5.10.35-rockchip64 36 ii linux-dtb-legacy-rk3399 21.05.1 arm64 Linux DTB, version 4.4.213-rk3399From armbian-config -> System -> Other, here are the options I'm seeing
linux-image-current-rockchip64=21.02. 5.10.21-rockchip64
…
linux-image-dev-rockchip64=21.02.2 … 5.10.16-rockchip64
…
linux-image-legacy-rk3399=21.05.1 … 4.4.213-rk3399
I don't see an option of rk3399 with 5.x kernel.
Do you know which dtb it's for those with 5.x kernel from the Download page:
-
6 minutes ago, Werner said:
So you used the switch kernel feature, correct?
Yes, that is correct.
-
Armbianmonitor:
I originally installed Armbian witk Kernel 4.4 on my Nanopi.m4 and later upgraded it to 5.10 via armbian-config. Things work fine but whenever I got a new update via apt update, things get messed up a bit
the /boot/Image got linked to vmlinux-4.4.213-rk3399 instead of vmlinuz-5.10.35-rockchip64
while others
uInitrd -> uInitrd-5.10.35-rockchip64
dtb -> dtb-5.10.35-rockchip64
The result's the board couldn't boot-up, when I restarted it. And, I need to correct the Image -> vmlinuz-5.10.35-rockchip64 and doing mkimage -C none -A arm -T script -d boot.cmd boot.scr from another linux machine to the SDCard.
It works fine afterward but I wondered if there is the right way to fix this issue for good.
Thank you,
-
I'm getting burst "VOP vblank IRQ stuck for 10 ms" error messages in dmesg and wondering what it means and if anything to improve/fix. I'm using Nanopi m4
$ uname -a Linux nanopim4 5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 aarch64 aarch64 GNU/Linuxkern :err : [Sat Mar 13 22:20:13 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:04 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:04 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:06 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:06 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:09 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:11 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:12 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:12 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:18 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:21 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms -
On 2/15/2021 at 2:07 PM, Igor said:
armbian-config -> system -> alternative kernel -> rockchip64-current v21.02.2 ...
but I can't give you warranty that it will succeed. If it breaks down, we can't afford to guide you, so you will anyway need to start from scratch or try to fix this way. You will also lose certain functions that are present in 4.4.y but not yet in modern one.
I didn't know it is available now. I was so excited to try out. As you warned, I did the upgrade and bricked it. I couldn't get it boot up and ended up with restored from my backup back to 4.4 ;-(
Anyone success upgrading from 4.4 to 5.1 without reinstalling things?
My setup is the boot on SD with root on usb HDD, if that matters.
-
57 minutes ago, Jim MacKenzie said:
Looks like you're using the Ubuntu Armbian, not the Debian - do you mind telling me what kernel you're using?
(A pity I only saw this now.)
Right, between the original post and now, I had been switching and trying different Armbian Ubuntu, Debian with Buster, and other variations. None of them worked at the time. I stopped at some point and the workaround was to connect a usb 2.0 hub as a middle man. Recently, I found myself need to do a full local rsync between hard drives again and it works. I'm currently with
Armbian 21.02.1 Bionic with Linux 4.4.213-rk3399
-
On 7/5/2020 at 8:16 AM, Jim MacKenzie said:
Not solvable, then?
Somehow as of today, I tried again and it seems the problem is no longer seen. At least so far, rsync between two hard drives about 30 hrs is working fine.
```
$ cat /etc/armbian-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=nanopim4
BOARD_NAME="NanoPi M4"
BOARDFAMILY=rk3399
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=b0760915-dirty
DISTRIBUTION_CODENAME=bionic
DISTRIBUTION_STATUS=supported
VERSION=20.11
LINUXFAMILY=rk3399
BRANCH=legacy
ARCH=arm64
IMAGE_TYPE=stable
BOARD_TYPE=conf
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
``` -
I ran apt-cache below and it showed that it has only the legacy 4.4.213-rk339. Is it the same for everyone else or somehow I am missing something?
$ apt-cache show linux-image*rk3399 | grep -E "Package:|Version:|version:" Package: linux-image-legacy-rk3399 Version: 20.08.8 files, version: 4.4.213-rk3399. Package: linux-image-legacy-rk3399 Version: 20.08.6 files, version: 4.4.213-rk3399. Package: linux-image-legacy-rk3399 Version: 20.08.4 files, version: 4.4.213-rk3399. Package: linux-image-legacy-rk3399 Version: 20.08.3 files, version: 4.4.213-rk3399. Package: linux-image-legacy-rk3399 Version: 20.08.2 files, version: 4.4.213-rk3399. Package: linux-image-legacy-rk3399 Version: 20.08.1 files, version: 4.4.213-rk3399. Package: linux-image-legacy-rk3399 Version: 20.08 files, version: 4.4.213-rk3399. -
18 hours ago, Werner said:
Usually it is done via armbian-confg. No idea though why current branch is not shown there.
As stated this needs to be verified and depending on investigated.
Oh let me know if this happens to only for me or in general. If it is the former, I wondered what caused and how to solve it.
Thanks
-
-
Hi,
I'm using NanoPi M4
$ uname -a Linux nanopim4 4.4.213-rk3399 #3 SMP Mon Oct 5 15:53:54 CEST 2020 aarch64 aarch64 aarch64 GNU/Linuxand wondering if I can upgrade the linux kernel to 5.8.x without reinstalling other things. I tried armbian-config -> System -> Other
All available options are those 4.4.213-rk3399 with different Armbian versions 20.08.x. I'm currently on 20.08.9
Appreciated any step, pointer
Thank you
-
Hi all,
I'd just like to share a problem I experienced and what solved after a bit of Googling. Basically, I have Nextcloud installed on my Nanopi M4 (v1) with Armbian:
$ uname -a Linux nanopim4 4.4.192-rk3399When I sync files from my Android phone via local wifi, often the transfers were just failed. Not always but usually, it's when a directory contains lot of large files. After a bit of Googling and came across this: https://unix.stackexchange.com/questions/494290/nanopi-m4-rk3399-apache2-ssl-large-download-hangs/495378#495378
It works. The problem's solved after:
ethtool -K eth0 rx off tx offand put the command in /etc/network/if-up.d/ethtool
Just wondering if anyone knows the root cause and have better solution than disabling things.
Thanks,
-
1 hour ago, Igor said:
I already told you exactly what you have to do, but can't guide in case of troubles. Also you have to remain on stock/legacy kernel. With development kernels (5.1.y) you are on your own. This recipe might work or not.
Thank you Igor. I finally got it work. Basically, follow your guidance:
$vi /lib/systemd/system/
[Unit]
Description=Bluetooth nanopi
After=bluetooth.target
[Service]
Type=forking
ExecStartPre=/bin/echo 1 > /sys/class/rfkill/rfkill0/state
ExecStart=/usr/bin/hciattach /dev/ttyS0 bcm43xx 115200 > /dev/null
TimeoutSec=0
RemainAfterExit=yes
SysVStartPriority=99
[Install]
WantedBy=multi-user.target
$ sudo systemctl --no-reload enable nanopi-bluetooth.service
$ sudo systemctl start nanopi-bluetooth.service
BT is working now. : )
Trying to get my generic gamepad to work is another story : (
But at least, it's connected.
-
I got the bluetooth working with a fresh install from the download section to a new microSDCard. I have rootfs installed in my external hdd. So, I did similar procedures in what nand-sata-install is doing except formatting the external hdd (rootfs). Basically,
- setting the correct UUID and others in /boot/armbianEnv.txt
$ mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
- setting the correct UUID and mount locations in /etc/fstab
The system boots fine. Other things seem to be working okay. BUT the bluetooth is not working : (
Here is $ sudo armbianmonitor -u
Helps are appreciated.
-
34 minutes ago, Igor said:
Use image from the download section and stay away from nightly / beta sections if you want that things works.
sir, yes sir. : ) I'll definitely try to flash the image from the download section to a new SDCard to just check if BT comes back to work and report here when I get a chance.
By the way, do you have any suggestion for me to just update the core parts in my existing system with the image from the download section? I have things setup already and its kind of painful to re-config things from a fresh install.
-
10 hours ago, Igor said:
Simply implement this https://github.com/armbian/build/commit/1541de32b85fa81c82bb549b67a91746ae33230c#diff-fd85d58c8bb1c2923d75fd40b35d907f or start with a clean build if that will give you too much trouble.
Thanks Igor. Pretty newbie here. I changed to nightly firmware and upgrade there to
$ uname -a
Linux nanopim4 5.1.0-rk3399 #5.91.190708 SMP Tue Jul 9 07:58:42 CEST 2019 aarch64 GNU/Linux
Things are still not working. Here is $ sudo armbianmonitor -u (it works now :))
Thanks for your helps.
-
48 minutes ago, Igor said:
I used (Bionic) image from the download section and I could navigate KODI via Bluetooth enabled mouse ... Which image did you used? Have you mage some upgrade from Stretch to Buster? Where is your armbianmonitor -u (which can perhaps tell more).
I think I saw Buster available on the Download page but what I did was simply change /etc/apt/sources.list and apt update & upgrade. Something similar to:
https://linuxconfig.org/how-to-upgrade-debian-9-stretch-to-debian-10-buster
somehow armbianmonitor -u returned empty string for me.
I did something similar here:
Thanks for your help.
-
One more, in case it might help:
$ sudo dmesg | grep blue
[ 3.016666] of_get_named_gpiod_flags: parsed 'uart_rts_gpios' property of node '/wireless-bluetooth[0]' - status (0)
[ 3.016670] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 83.
[ 3.016675] of_get_named_gpiod_flags: can't parse 'BT,power_gpio' property of node '/wireless-bluetooth[0]'
[ 3.016686] of_get_named_gpiod_flags: parsed 'BT,reset_gpio' property of node '/wireless-bluetooth[0]' - status (0)
[ 3.016689] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,reset_gpio = 9.
[ 3.016700] of_get_named_gpiod_flags: parsed 'BT,wake_gpio' property of node '/wireless-bluetooth[0]' - status (0)
[ 3.016703] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 90.
[ 3.016713] of_get_named_gpiod_flags: parsed 'BT,wake_host_irq' property of node '/wireless-bluetooth[0]' - status (0)
[ 3.016716] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 4.
-
Anyone gets Nanopo M4 on-board bluetooth working. Any pointer would be appreciated.
Here are what I did:
- install Bluetooth component from armbian-config
$ sudo service bluetooth status
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2019-07-31 15:59:27 PDT; 9s ago
Docs: man:bluetoothd(8)
Main PID: 14661 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4558)
Memory: 2.1M
CGroup: /system.slice/bluetooth.service
└─14661 /usr/lib/bluetooth/bluetoothd
Jul 31 15:59:27 nanopim4 systemd[1]: Starting Bluetooth service...
Jul 31 15:59:27 nanopim4 bluetoothd[14661]: Bluetooth daemon 5.50
Jul 31 15:59:27 nanopim4 systemd[1]: Started Bluetooth service.
Jul 31 15:59:27 nanopim4 bluetoothd[14661]: Starting SDP server
Jul 31 15:59:27 nanopim4 bluetoothd[14661]: kernel lacks bnep-protocol support
Jul 31 15:59:27 nanopim4 bluetoothd[14661]: System does not support network plugin
Jul 31 15:59:27 nanopim4 bluetoothd[14661]: Bluetooth management interface 1.10 initialized
$ sudo hcitool dev
Devices:
$ sudo rfkill list
0: bt_default: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: brcmfmac-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
$ uname -a
Linux nanopim4 4.4.179-rk3399 #1 SMP Thu Jun 27 23:31:19 CEST 2019 aarch64 GNU/Linux
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
-
Thanks Igor. Got a workaround solution with fail2ban with geoiplookup for what I need. Another day to do as what you suggested. ;-)
-
Basically, I'm trying to get iptables to block per country:
https://daenney.github.io/2017/01/07/geoip-filtering-iptables.html
I got most of things work until getting problem on installing xtables-addons-dmks
# apt-get install --reinstall xtables-addons-dkms
------------------------------
Deleting module version: 2.12
completely from the DKMS tree.
------------------------------
Done.
Unpacking xtables-addons-dkms (2.12-0.1) over (2.12-0.1) ...
Setting up xtables-addons-dkms (2.12-0.1) ...
Loading new xtables-addons-2.12 DKMS files...
Building for 4.4.174-rk3399
Building initial module for 4.4.174-rk3399
Error! Build of xt_ACCOUNT.ko failed for: 4.4.174-rk3399 (aarch64)
Consult the make.log in the build directory
/var/lib/dkms/xtables-addons/2.12/build/ for more information.
# cat /var/lib/dkms/xtables-addons/2.12/build/make.log
DKMS make.log for xtables-addons-2.12 for kernel 4.4.174-rk3399 (aarch64)
Mon Mar 25 18:58:27 PDT 2019
make: Entering directory '/usr/src/linux-headers-4.4.174-rk3399'
Makefile:667: arch//Makefile: No such file or directory
make: *** No rule to make target 'arch//Makefile'. Stop.
make: Leaving directory '/usr/src/linux-headers-4.4.174-rk3399'
I have both kernel headers and source installed from armbian-config.Any pointer to get correct commands to solve this problem would be appreciated.
Thanks,
The repository 'http://apt.armbian.com bionic Release' is not signed.
in Common issues / peer to peer technical support
Posted
It's working for me now. Thanks Igor.