Jerry Jyrer

Members
  • Content Count

    35
  • Joined

  • Last visited

About Jerry Jyrer

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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 http://ix.io/1Qkq Helps are appreciated.
  3. 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.
  4. 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 :)) http://ix.io/1Qi6 Thanks for your helps.
  5. 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: http://sprunge.us/yK0GdC Thanks for your help.
  6. 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.
  7. 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/"
  8. Thanks Igor. Got a workaround solution with fail2ban with geoiplookup for what I need. Another day to do as what you suggested. ;-)
  9. 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,
  10. Quick scan, it looks like the same. Solution / root cause?
  11. Totally agreed. I posted here and similar topics for the same issue but so far no real solutions. Many suggestions were around under voltage being supplied. I personally doubt if that is the root cause. Armbian software/driver itself? Not too sure I tried the stock one from FriendlyElec, the result is the same. Is it the upstream Linux? Possible but no verification. I have just tried after recent apt update and upgrade. The same problem is still reproducible.
  12. Yes, exactly what I finally solved my problem. Same to you Jim, I initially thought and be advised by many that it was the power problem but at the end what solved was to connect one with an USB 2.0 port.
  13. Half correct sir. I fixed the power things. The problem wasn't. What really did the trick was to connect one hard drive with an usb extension (usb 2.0). The extension has no external power supply whatsoever. If any of my cabel is bad, adding additional one result worse. But in fact, it did the trick. I successfully rsync 1.7TB as expected. Now, I'm going to just connect my original usb-c adapter --- the one that all of us said it's the problem -- instead of the DC power adapter 5V 8A powering via GPIO pin 4 (+) and 6(GDN). I'm about 80% sure it wouldn't have any problem. What would it be really a problem to connect 2 USB 3.0 gen 1 external hard drives to Nanopi M4 and doing their full capacity reading/writing. Driver, board, or kernel issues? Thought?
  14. It looks like I might find the problems. I connected my Toshiba external hard drive (2TB) with another usb 2.0 extension cable. Basically, instead of contect it as usb 3.0, I made it as usb 2.0. My WD Mybook 8TB is connecting to the board directly as usb 3.0 Copying now going >1GB of data and still continue on going. dmesg shows some errors and warnning about resetting the speed though but the rsync is still good and continue: kern :info : [Dec12 19:26] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd kern :warn : [ +0.138467] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +0.000055] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +6.776374] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :info : [ +31.102096] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd kern :warn : [ +0.133845] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +0.000056] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [Dec12 19:27] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :warn : [ +4.933371] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :warn : [ +35.645125] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :info : [Dec12 19:28] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd kern :warn : [ +0.138459] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +0.000057] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +17.781779] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :warn : [ +4.944248] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :info : [Dec12 19:29] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd kern :warn : [ +0.134115] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +0.000055] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes kern :info : [ +36.858678] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd kern :warn : [ +0.133971] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +0.000056] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [Dec12 19:30] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :warn : [ +9.477617] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :warn : [ +6.977276] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :warn : [Dec12 19:31] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued? kern :info : [ +37.592164] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd kern :warn : [ +0.134474] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes kern :warn : [ +0.000068] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes
  15. A normal cp creates the same problem also: $ sudo cp -Rf /mnt/Photos-Videos/* /media/WDMyBook/Photos-Videos/ $dmesg -xH shows