Jump to content

Search the Community

Showing results for tags 'bananapi'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. I still have a Banana Pi BPI-R1 on which I wanted to install PiHole. Can't find a suitable image? Is the Banana Pi BPI-R1 still supported?
  2. Hi form germany, i have problemes with my M1. The system hangs and only ping is working here the last timestamps: do, 14.04. 18:00 so, 01.05. 2:45 do, 05.05. 3:00 mo, 09.05. 15:22 i use Armbian 22.02.1 Focal with Linux 5.15.25-sunxi homeassistant + portainer (docker) mosquitto samba with sata 500gb ssd do we need some other logs? thanks to this nice work 🙂
  3. Dear Friends, this is Judy from Banana Pi team. We will have BPI-M2S and BPI-R2 PRO sample ready on May. If you have interesting and ability to develope the software for these two boards, please contact me, my mail: judyhuang@banana-pi.com Look forward to cooperate with you!
  4. My Banana Pi get a kernel panic if I try to shut it down as you can see in the picture. How can I fix this? I'm using Armbian 22.02.1 with Linux 5.15.25-sunxi http://ix.io/3VHA sudo i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --
  5. Hi, on my Bananapi M1 I have a 240GB SATA SSD connected for storage. Unfortunately I'm losing connection after a couple of days sometimes hours. Do you have an idea why? Apr 13 22:13:16 localhost rngd[854]: stats: Lowest ready-buffers level: 2 Apr 13 22:13:16 localhost rngd[854]: stats: Entropy starvations: 0 Apr 13 22:13:16 localhost rngd[854]: stats: Time spent starving for entropy: (min=0; avg=0.000; max=0)us Apr 13 22:13:18 localhost kernel: [ 3627.151866] ata1: COMRESET failed (errno=-16) Apr 13 22:13:18 localhost kernel: [ 3627.151914] ata1: hard resetting link Apr 13 22:13:23 localhost kernel: [ 3632.504265] ata1: link is slow to respond, please be patient (ready=0) Apr 13 22:13:28 localhost kernel: [ 3637.184617] ata1: COMRESET failed (errno=-16) Apr 13 22:13:28 localhost kernel: [ 3637.184662] ata1: hard resetting link Apr 13 22:13:33 localhost kernel: [ 3642.537021] ata1: link is slow to respond, please be patient (ready=0) Apr 13 22:14:03 localhost kernel: [ 3672.239231] ata1: COMRESET failed (errno=-16) Apr 13 22:14:03 localhost kernel: [ 3672.239279] ata1: limiting SATA link speed to 1.5 Gbps Apr 13 22:14:03 localhost kernel: [ 3672.239292] ata1: hard resetting link Apr 13 22:14:08 localhost kernel: [ 3677.291612] ata1: COMRESET failed (errno=-16) Apr 13 22:14:08 localhost kernel: [ 3677.291661] ata1: reset failed, giving up Apr 13 22:14:08 localhost kernel: [ 3677.291674] ata1.00: disabled Apr 13 22:14:08 localhost kernel: [ 3677.291801] sd 0:0:0:0: [sda] tag#23 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=60s Apr 13 22:14:08 localhost kernel: [ 3677.291820] sd 0:0:0:0: [sda] tag#23 Sense Key : 0x2 [current] Apr 13 22:14:08 localhost kernel: [ 3677.291832] sd 0:0:0:0: [sda] tag#23 ASC=0x4 ASCQ=0x21 Apr 13 22:14:08 localhost kernel: [ 3677.291849] sd 0:0:0:0: [sda] tag#23 CDB: opcode=0x28 28 00 08 99 ff 00 00 01 00 00 Apr 13 22:14:08 localhost kernel: [ 3677.291859] blk_update_request: I/O error, dev sda, sector 144310016 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 Apr 13 22:14:08 localhost kernel: [ 3677.291966] sd 0:0:0:0: [sda] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=60s Apr 13 22:14:08 localhost kernel: [ 3677.291983] sd 0:0:0:0: [sda] tag#24 Sense Key : 0x2 [current] Apr 13 22:14:08 localhost kernel: [ 3677.291996] sd 0:0:0:0: [sda] tag#24 ASC=0x4 ASCQ=0x21 Apr 13 22:14:08 localhost kernel: [ 3677.292010] sd 0:0:0:0: [sda] tag#24 CDB: opcode=0x28 28 00 08 9a 00 00 00 01 00 00 Apr 13 22:14:08 localhost kernel: [ 3677.292018] blk_update_request: I/O error, dev sda, sector 144310272 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0 Apr 13 22:14:08 localhost kernel: [ 3677.292062] ata1: EH complete Apr 13 22:14:08 localhost kernel: [ 3677.292156] sd 0:0:0:0: [sda] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:14:08 localhost kernel: [ 3677.292175] sd 0:0:0:0: [sda] tag#25 CDB: opcode=0x28 28 00 08 99 ff 00 00 00 08 00 Apr 13 22:14:08 localhost kernel: [ 3677.292184] blk_update_request: I/O error, dev sda, sector 144310016 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:14:08 localhost kernel: [ 3677.292334] sd 0:0:0:0: [sda] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:14:08 localhost kernel: [ 3677.292354] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 08 99 ff 00 00 00 08 00 Apr 13 22:14:08 localhost kernel: [ 3677.292364] blk_update_request: I/O error, dev sda, sector 144310016 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:14:08 localhost kernel: [ 3677.292644] sd 0:0:0:0: [sda] tag#26 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:14:08 localhost kernel: [ 3677.292667] sd 0:0:0:0: [sda] tag#26 CDB: opcode=0x28 28 00 08 99 ff 00 00 00 08 00 Apr 13 22:14:08 localhost kernel: [ 3677.292676] blk_update_request: I/O error, dev sda, sector 144310016 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:14:08 localhost kernel: [ 3677.292812] sd 0:0:0:0: [sda] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:14:08 localhost kernel: [ 3677.292832] sd 0:0:0:0: [sda] tag#2 CDB: opcode=0x28 28 00 08 99 ff 00 00 00 08 00 Apr 13 22:14:08 localhost kernel: [ 3677.292840] blk_update_request: I/O error, dev sda, sector 144310016 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:14:08 localhost kernel: [ 3677.293250] sd 0:0:0:0: [sda] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:14:08 localhost kernel: [ 3677.293276] sd 0:0:0:0: [sda] tag#27 CDB: opcode=0x28 28 00 08 99 ff 00 00 00 08 00 Apr 13 22:14:08 localhost kernel: [ 3677.293286] blk_update_request: I/O error, dev sda, sector 144310016 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:14:08 localhost kernel: [ 3677.293468] sd 0:0:0:0: [sda] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:14:08 localhost kernel: [ 3677.293490] sd 0:0:0:0: [sda] tag#3 CDB: opcode=0x28 28 00 08 99 ff 00 00 00 08 00 Apr 13 22:14:08 localhost kernel: [ 3677.293498] blk_update_request: I/O error, dev sda, sector 144310016 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:14:08 localhost kernel: [ 3677.294579] sd 0:0:0:0: [sda] tag#28 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:14:08 localhost kernel: [ 3677.294610] sd 0:0:0:0: [sda] tag#28 CDB: opcode=0x28 28 00 08 7e 88 00 00 00 08 00 Apr 13 22:14:08 localhost kernel: [ 3677.294620] blk_update_request: I/O error, dev sda, sector 142510080 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Apr 13 22:14:08 localhost kernel: [ 3677.294750] sd 0:0:0:0: [sda] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:14:08 localhost kernel: [ 3677.294770] sd 0:0:0:0: [sda] tag#4 CDB: opcode=0x28 28 00 08 7e 88 00 00 00 08 00 Apr 13 22:14:08 localhost kernel: [ 3677.294779] blk_update_request: I/O error, dev sda, sector 142510080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:14:31 localhost kernel: [ 3700.043662] scsi_io_completion_action: 12 callbacks suppressed Apr 13 22:14:31 localhost kernel: [ 3700.043713] sd 0:0:0:0: [sda] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:14:31 localhost kernel: [ 3700.043748] sd 0:0:0:0: [sda] tag#11 CDB: opcode=0x28 28 00 08 7e 88 00 00 00 08 00 Apr 13 22:14:31 localhost kernel: [ 3700.043758] print_req_error: 12 callbacks suppressed Apr 13 22:14:31 localhost kernel: [ 3700.043764] blk_update_request: I/O error, dev sda, sector 142510080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:14:31 localhost kernel: [ 3700.044327] sd 0:0:0:0: [sda] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:14:31 localhost kernel: [ 3700.044355] sd 0:0:0:0: [sda] tag#4 CDB: opcode=0x28 28 00 08 7e 88 00 00 00 08 00 Apr 13 22:14:31 localhost kernel: [ 3700.044364] blk_update_request: I/O error, dev sda, sector 142510080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:14:38 localhost systemd[1]: Created slice User Slice of UID 1000. Apr 13 22:14:38 localhost systemd[1]: Starting User Runtime Directory /run/user/1000... Apr 13 22:14:38 localhost systemd[1]: Started User Runtime Directory /run/user/1000. Apr 13 22:14:38 localhost systemd[1]: Starting User Manager for UID 1000... Apr 13 22:14:39 localhost systemd[2141]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Apr 13 22:14:39 localhost systemd[2141]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Apr 13 22:14:39 localhost systemd[2141]: Reached target Paths. Apr 13 22:14:39 localhost systemd[2141]: Listening on GnuPG cryptographic agent and passphrase cache. Apr 13 22:14:39 localhost systemd[2141]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Apr 13 22:14:39 localhost systemd[2141]: Listening on GnuPG network certificate management daemon. Apr 13 22:14:39 localhost systemd[2141]: Reached target Sockets. Apr 13 22:14:39 localhost systemd[2141]: Reached target Timers. Apr 13 22:14:39 localhost systemd[2141]: Reached target Basic System. Apr 13 22:14:39 localhost systemd[1]: Started User Manager for UID 1000. Apr 13 22:14:39 localhost systemd[2141]: Reached target Default. Apr 13 22:14:39 localhost systemd[2141]: Startup finished in 304ms. Apr 13 22:14:39 localhost systemd[1]: Started Session 17 of user markus. Apr 13 22:14:49 localhost kernel: [ 3718.399188] sd 0:0:0:0: [sda] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:14:49 localhost kernel: [ 3718.399248] sd 0:0:0:0: [sda] tag#12 CDB: opcode=0x2a 2a 00 0e c4 08 30 00 00 10 00 Apr 13 22:14:49 localhost kernel: [ 3718.399266] blk_update_request: I/O error, dev sda, sector 247728176 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 Apr 13 22:14:49 localhost kernel: [ 3718.399361] Aborting journal on device sda1-8. Apr 13 22:14:49 localhost kernel: [ 3718.399545] sd 0:0:0:0: [sda] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:14:49 localhost kernel: [ 3718.399577] sd 0:0:0:0: [sda] tag#5 CDB: opcode=0x2a 2a 00 0e c4 08 00 00 00 08 00 Apr 13 22:14:49 localhost kernel: [ 3718.399591] blk_update_request: I/O error, dev sda, sector 247728128 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Apr 13 22:14:49 localhost kernel: [ 3718.399623] blk_update_request: I/O error, dev sda, sector 247728128 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Apr 13 22:14:49 localhost kernel: [ 3718.399652] Buffer I/O error on dev sda1, logical block 30965760, lost sync page write Apr 13 22:14:49 localhost kernel: [ 3718.399708] JBD2: Error -5 detected when updating journal superblock for sda1-8. Apr 13 22:14:57 localhost kernel: [ 3726.375693] sd 0:0:0:0: [sda] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:14:57 localhost kernel: [ 3726.375737] sd 0:0:0:0: [sda] tag#6 CDB: opcode=0x28 28 00 08 7e 88 00 00 00 08 00 Apr 13 22:14:57 localhost kernel: [ 3726.375749] blk_update_request: I/O error, dev sda, sector 142510080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:14:57 localhost kernel: [ 3726.376315] sd 0:0:0:0: [sda] tag#13 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:14:57 localhost kernel: [ 3726.376344] sd 0:0:0:0: [sda] tag#13 CDB: opcode=0x28 28 00 08 7e 88 00 00 00 08 00 Apr 13 22:14:57 localhost kernel: [ 3726.376354] blk_update_request: I/O error, dev sda, sector 142510080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:15:00 localhost kernel: [ 3728.940667] sd 0:0:0:0: [sda] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:15:00 localhost kernel: [ 3728.940711] sd 0:0:0:0: [sda] tag#14 CDB: opcode=0x28 28 00 08 7e 88 00 00 00 08 00 Apr 13 22:15:00 localhost kernel: [ 3728.940722] blk_update_request: I/O error, dev sda, sector 142510080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:15:00 localhost kernel: [ 3728.941248] sd 0:0:0:0: [sda] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:15:00 localhost kernel: [ 3728.941277] sd 0:0:0:0: [sda] tag#7 CDB: opcode=0x28 28 00 08 7e 88 00 00 00 08 00 Apr 13 22:15:00 localhost kernel: [ 3728.941286] blk_update_request: I/O error, dev sda, sector 142510080 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:15:01 localhost CRON[2252]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Apr 13 22:15:01 localhost CRON[2254]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) Apr 13 22:15:16 localhost kernel: [ 3745.741588] sd 0:0:0:0: [sda] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:15:16 localhost kernel: [ 3745.741634] sd 0:0:0:0: [sda] tag#15 CDB: opcode=0x28 28 00 07 a3 08 00 00 01 00 00 Apr 13 22:15:16 localhost kernel: [ 3745.741645] blk_update_request: I/O error, dev sda, sector 128124928 op 0x0:(READ) flags 0x80700 phys_seg 31 prio class 0 Apr 13 22:15:16 localhost kernel: [ 3745.741805] sd 0:0:0:0: [sda] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:15:16 localhost kernel: [ 3745.741830] sd 0:0:0:0: [sda] tag#8 CDB: opcode=0x28 28 00 07 a3 08 00 00 00 08 00 Apr 13 22:15:16 localhost kernel: [ 3745.741838] blk_update_request: I/O error, dev sda, sector 128124928 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:15:16 localhost kernel: [ 3745.741895] EXT4-fs error (device sda1): ext4_journal_check_start:83: comm proftpd: Detected aborted journal Apr 13 22:15:16 localhost kernel: [ 3745.742109] sd 0:0:0:0: [sda] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:15:16 localhost kernel: [ 3745.742129] sd 0:0:0:0: [sda] tag#16 CDB: opcode=0x2a 2a 00 00 00 08 00 00 00 08 00 Apr 13 22:15:16 localhost kernel: [ 3745.742137] blk_update_request: I/O error, dev sda, sector 2048 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 0 Apr 13 22:15:16 localhost kernel: [ 3745.742158] blk_update_request: I/O error, dev sda, sector 2048 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 0 Apr 13 22:15:16 localhost kernel: [ 3745.742174] Buffer I/O error on dev sda1, logical block 0, lost sync page write Apr 13 22:15:16 localhost kernel: [ 3745.742213] EXT4-fs (sda1): I/O error while writing superblock Apr 13 22:15:16 localhost kernel: [ 3745.742225] EXT4-fs (sda1): Remounting filesystem read-only Apr 13 22:15:16 localhost kernel: [ 3745.742715] sd 0:0:0:0: [sda] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:15:16 localhost kernel: [ 3745.742740] sd 0:0:0:0: [sda] tag#9 CDB: opcode=0x28 28 00 07 a3 08 00 00 00 08 00 Apr 13 22:15:16 localhost kernel: [ 3745.742749] blk_update_request: I/O error, dev sda, sector 128124928 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:15:21 localhost kernel: [ 3750.198217] sd 0:0:0:0: [sda] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:15:21 localhost kernel: [ 3750.198261] sd 0:0:0:0: [sda] tag#17 CDB: opcode=0x28 28 00 07 a3 08 00 00 00 08 00 Apr 13 22:15:21 localhost kernel: [ 3750.198272] blk_update_request: I/O error, dev sda, sector 128124928 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:15:21 localhost kernel: [ 3750.198808] sd 0:0:0:0: [sda] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s Apr 13 22:15:21 localhost kernel: [ 3750.198837] sd 0:0:0:0: [sda] tag#10 CDB: opcode=0x28 28 00 07 a3 08 00 00 00 08 00 Apr 13 22:15:21 localhost kernel: [ 3750.198845] blk_update_request: I/O error, dev sda, sector 128124928 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 13 22:15:58 localhost chronyd[701]: Selected source 144.91.116.85 Apr 13 22:17:01 localhost CRON[2274]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
  6. Hello Community, I have a (hopefully) quick question about the SATA port on my Bananapi. I wanted to attach a msata card via adapter to my Bananapi, like I already do on my Cubietruck. However when I start look for the msata drive it does not show up. However when I double check the drive via a USB SATA adapter the drive does show up. Could someone please tell me what is going ? Thx, blub4747
  7. Hi forum members, when I try to install the kernel headers via: "sudo apt-get install kernel-headers-$(uname -r)" I gote these errors: Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package kernel-headers-4.19.62-sunxi E: Couldn't find any package by glob 'kernel-headers-4.19.62-sunxi' E: Couldn't find any package by regex 'kernel-headers-4.19.62-sunxi' In the /etc/apt/sources.list the lines with the deb-src links are comments. I've tried to uncomment these but got the same errors. So please can somwone point me right kernel-headers Armbian is using ? Many Thanks wollik
  8. Hello, Since a week I try moving the OS on the sdcard to an attached SSD. OS: Armbian 5.65 Ubuntu Xenial 3.4.113 desktop Because the BPIM1 has a genuime SATA interface it should work. I have found dozens of tutorials how to do this. Until now I did not find any tutorial that works. Of course I started with nand-install expecting this would work out of the box. But after the install and rebooting I got the notification that it couldn't find the ssd. I guess I have to change something in the bootloader on the sdcard? (I am not a Linux expert but an enthustiastic Linux user) Is there any working tutorial including the final steps? Kind regards, André Reinink From the Armbian docs: On Allwinner devices after switching to boot from NAND or eMMC clearing the boot loader signature on the SD card is recommended: dd if=/dev/zero of=/dev/mmcblkN bs=1024 seek=8 count=1 (replace /dev/mmcblkN with the correct device node – in case you run this directly after nand-sata-install without a reboot in between then it’s /dev/mmcblk0). 9FEB2019: I did add this extra step after the nand-install. After executing this and restarting, the BPIM2 doesn't boot anymore? What did I do wrong? 10FEB2019: After 7th attempts I changed the SSD (Intel 180GB) for an OCZ 120GB). Attempt number 8 with the OCZ was succesfull with nand-sata-install. No problems at all. I am happy:-)
  9. Hi, i'am desperate with my banana-p1 M1. It is (still) running nicely with an old 'Lemaker' Lubuntu version. But its an old linux version and the are 'iceweasel' issues in combination with https. So, it's a good time to use a (much) newer version of linux. I've tried several versions/downloads of Armbian: debian, ubuntu. I've tried different (tested with F3write/read) SD cards. Used several methods to 'write' the SD-card(s), like 'dd' or the etcher-tool.... ALL results have the same problem. (i've got an picture of the screen, but i can't upload it to this forum???) In sort, it say's: U-boot 2020.10-armbian ..... Allwinner Tech... CPU: Allwinner A20 (SUN7I) I2C: ready DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from FAT.... MMC: no card present HDMI connected: Setting up a 1920x1080...... IN: serial Out: vga Err: vga Net: eth0: ethernet@1c50000 MMC: no card present starting USB.... .... .... missing environment variable: bootfile There is a card present (tried serveral types/size/manufactories) and i removed the SD card > the screen stays 'black'. So the banana-pi is seeing the SD-card. The hardware is OK, b'cause i have tried the 'old' SD card with the 'lubuntu' version and that is working nicely... latest attempt was with image: Armbian_21.02.1_Bananapi_bionic_current_5.10.12.img.xy So what is going wrong? Can somebody give me some tricks? Thanks in advance
  10. I supose the armbianmonitor output doesn't help much. But here is an output from serial console: 3 times reseting before.... resetting ... U-Boot SPL 2021.04-armbian (May 06 2021 - 20:01:01 +0000) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2021.04-armbian (May 06 2021 - 20:01:01 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: LeMaker Banana Pi I2C: ready DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0) In: serial Out: vga Err: vga Net: eth0: ethernet@1c50000 230454 bytes read in 28 ms (7.8 MiB/s) starting USB... Bus usb@1c14000: USB EHCI 1.00 Bus usb@1c14400: USB OHCI 1.0 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 scanning bus usb@1c14000 for devices... 1 USB Device(s) found scanning bus usb@1c14400 for devices... 2 USB Device(s) found scanning bus usb@1c1c000 for devices... 1 USB Device(s) found scanning bus usb@1c1c400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3967 bytes read in 7 ms (552.7 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 203 bytes read in 6 ms (32.2 KiB/s) 11526673 bytes read in 1290 ms (8.5 MiB/s) 7975912 bytes read in 751 ms (10.1 MiB/s) Found mainline kernel configuration 43645 bytes read in 29 ms (1.4 MiB/s) 5532 bytes read in 27 ms (199.2 KiB/s) Applying kernel provided DT fixup script (sun7i-a20-fixup.scr) ## Executing script at 45000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11526609 Bytes = 11 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 data abort pc : [<7ef9673c>] lr : [<00000011>] reloc pc : [<4a01373c>] lr : [<cb07d011>] sp : 7af57c18 ip : 7efde6ec fp : 7efde6cc r10: 00000020 r9 : 7af62ec0 r8 : 7efeab8c r7 : 6c616972 r6 : 00000010 r5 : e75b616a r4 : 7af9f7f0 r3 : 7af9f7f8 r2 : 7af9f7e8 r1 : 7afa90b8 r0 : 00000019 Flags: nzCv IRQs off FIQs off Mode SVC_32 (T) Code: d005 f027 0501 441d (686d) 07ed Resetting CPU ... resetting ... U-Boot SPL 2021.04-armbian (May 06 2021 - 20:01:01 +0000) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2021.04-armbian (May 06 2021 - 20:01:01 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: LeMaker Banana Pi I2C: ready DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0) In: serial Out: vga Err: vga Net: eth0: ethernet@1c50000 230454 bytes read in 28 ms (7.8 MiB/s) starting USB... Bus usb@1c14000: USB EHCI 1.00 Bus usb@1c14400: USB OHCI 1.0 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 scanning bus usb@1c14000 for devices... 1 USB Device(s) found scanning bus usb@1c14400 for devices... 2 USB Device(s) found scanning bus usb@1c1c000 for devices... 1 USB Device(s) found scanning bus usb@1c1c400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) switch to partitions #0, OK mmc0 is current device ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) Scanning mmc 0:1... ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did not provide a handshake (OUT) (5) Found U-Boot script /boot/boot.scr 3967 bytes read in 7 ms (552.7 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 203 bytes read in 6 ms (32.2 KiB/s) 11526673 bytes read in 1189 ms (9.2 MiB/s) 7975912 bytes read in 703 ms (10.8 MiB/s) Found mainline kernel configuration 43645 bytes read in 29 ms (1.4 MiB/s) 5532 bytes read in 30 ms (179.7 KiB/s) Applying kernel provided DT fixup script (sun7i-a20-fixup.scr) ## Executing script at 45000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11526609 Bytes = 11 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 data abort pc : [<7ef961a8>] lr : [<7ef968b5>] reloc pc : [<4a0131a8>] lr : [<4a0138b5>] sp : 7af57c08 ip : 006c6168 fp : 7efde6cc r10: 00000020 r9 : 7af62ec0 r8 : 7efeab8c r7 : 72657370 r6 : 7b6644a8 r5 : 614e6e65 r4 : 7efde6cc r3 : 7af9e350 r2 : 00000000 r1 : 72d1d4c8 r0 : 6b6f545f Flags: Nzcv IRQs off FIQs off Mode SVC_32 (T) Code: e7d1 2201 e7cf 68f5 (60c5) 60a8 Resetting CPU ... resetting ... U-Boot SPL 2021.04-armbian (May 06 2021 - 20:01:01 +0000) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2021.04-armbian (May 06 2021 - 20:01:01 +0000) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: LeMaker Banana Pi I2C: ready DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0) In: serial Out: vga Err: vga Net: eth0: ethernet@1c50000 230454 bytes read in 28 ms (7.8 MiB/s) starting USB... Bus usb@1c14000: USB EHCI 1.00 Bus usb@1c14400: USB OHCI 1.0 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 scanning bus usb@1c14000 for devices... 1 USB Device(s) found scanning bus usb@1c14400 for devices... 1 USB Device(s) found scanning bus usb@1c1c000 for devices... 1 USB Device(s) found scanning bus usb@1c1c400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3967 bytes read in 7 ms (552.7 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 203 bytes read in 6 ms (32.2 KiB/s) 11526673 bytes read in 1188 ms (9.3 MiB/s) 7975912 bytes read in 705 ms (10.8 MiB/s) Found mainline kernel configuration 43645 bytes read in 29 ms (1.4 MiB/s) 5532 bytes read in 30 ms (179.7 KiB/s) Applying kernel provided DT fixup script (sun7i-a20-fixup.scr) ## Executing script at 45000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11526609 Bytes = 11 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 EHCI failed to shut down host controller. Loading Ramdisk to 49501000, end 49fff1d1 ... OK Loading Device Tree to 4948d000, end 49500fff ... OK Starting kernel ... [ 18.912230] phy id_det change to device during the second boot (here in the log) I unplugged the Unifying Reciever The next boot (without the reciever plugged in) brings the system up and running. After kernel started you may plug the reciever back in. lsusb-output: Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I did some investigation, and tried buster instead of focal. No difference. But I have another pi running: root@pipyload:~# uname -a Linux pipyload 5.4.20-sunxi #20.02.1 SMP Mon Feb 17 02:09:41 CET 2020 armv7l GNU/Linux root@pipyload:~# lsusb Bus 004 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub booting this pi is workling fine. Since years... So it seems to me, that the problem is somewhere in the newer kernel. Does someone has a glue what to do? Perhaps disabling usb during u-boot?
  11. Hi there! I just received three decommissioned BananaPI M1+ from a company and I'm trying to install the latest version of Armbian Buster available on them. Once I flash the image to the SD card (tested and working fine), however, the board goes into boot loop as per the video. The only error that seems to be displayed is "EHCI failed to shut down host controller". If it can be useful to find the cause, I point out that the problem occurs with both Armbian Buster and Armbian Focal regardless of the presence of the "fdtfile=sun7i-a20-bananapi-m1-plus.dtb" line in the /boot/armbianEnv.txt file. What do you think I could do to solve it? Thank you all in advance.
  12. Hello, for my BananaPi I recently downloaded "Armbian_21.05.1_Bananapi_buster_current_5.10.34.img" and did not get the on-board CAN controller working with this image. I found out that in sun7i-a20-bananapi.dtb (uses sun7i-a20.dtsi) the group name for the CAN pins PH20 and PH21 has changed from "can0_pins_a" to "can_ph_pins" but in the sun7i-a20-can overlay this change had not been done accordingly, and the DT merging failed. So changing "sun7i-a20-can.dts" to: /dts-v1/; /plugin/; / { compatible = "allwinner,sun7i-a20"; fragment@0 { target = <&can0>; __overlay__ { pinctrl-names = "default"; pinctrl-0 = <&can_ph_pins>; status = "okay"; }; }; }; solved the problem. Please consider this for further releases, regards Rainer
  13. Hi, A few weeks ago I downloaded the actual Debian Buster version without desktop. I installed the OS and moved the filesystem to the attached SATA disk. Finally I installed and configured Samba and tested it transferring files form my desktop. Everything worked fine except transferring relatively big files. The files (2 in total) giving problems were a about 3Gb. When transferring a big file the upload seems to stop. The ethernet connection with the BananaPi M1 is completely de-activated. There is only one solution to re-activate as far as I know: remove the power connector and resupply the board. After resupplying the board it starts normal and functions normal. 1) What is causing the problem when transferring big files? 2) Is there an easy way to monitor the board while transferring files, either in terminal mode or using a webinterface? Regards, André
  14. I found that it is not easy to use the Dallas one-wire temperature sensors and the composite TV-Out on the Banana Pi with the current Armbian version. I have searched for posts on these topics in the forum. The posts that I have found in this forum describe solutions for outdated Armbian versions or do not give enough detail. The following posts in this thread will describe how to solve these problems for the current Armbian version for the Banana Pi M1.
  15. Hello. From moment when i flashed armbian to SD card and boot it up on Banana Pi M1, random reboots started to show. Ya'll should know that i'm hosting Plex and Tautulli on that. It's pretty much handling these servers without big problems but i'm constantly getting these random reboots. Well, i looked into /var/log/syslog to see what is happening. It looks like before every booting session there's cron job couple of hours before reboot. Maybe that's the reason? I can post whole syslog here from jan 5 till feb 2.
  16. Hi Linux Admins, I have a wrong device in the /dev direcrory and can't delete it. Here is what I get when I do a: ls -la /dev/ttyUSB* pi@armbian_test: ls -la /dev/ttyUSB* crw-rw---- 1 root dialout 188, 0 Feb 15 20:47 /dev/ttyUSB0 -rw-r--r-- 1 root root 1 Feb 15 20:48 /dev/ttyUSB1 You see that the device ttyUSB1 is not character device and has no major device number assigned. Also the device belongs not to the dialout group. The causing USB_2_Serial Stick is disconnected and the device entry is still there. Trying to remove this devis is also not working. pi@armbian_test: sudo rm /dev/ttyUSB1 pi@armbian_test: ls -la /dev/ttyUSB* crw-rw---- 1 root dialout 188, 0 Feb 15 20:47 /dev/ttyUSB0 -rw-r--r-- 1 root root 1 Feb 15 20:48 /dev/ttyUSB1 pi@armbian_test: Pleas can somone help me to fix this wrong device ? Regards wollik
  17. Hi enthusiast, Last few year I used Armbian 5.25, which allow me to echo cpufreq into /sys/devices/system/cpu/cpu0/cpufreq/scaling_***_freq to choose the overclock freq. However, last week, I had to disconnect the power and the Banana Pi didn't boot again. So I decided to install a fresh updated version of Armbian, which is called Bionic. The /proc/version shows: Linux version 4.19.62-sunxi (root@armbian.com) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02)) #5.92 SMP Wed Jul 31 22:07:23 CEST 2019 But now, when I want to overclock by using the method above, it won't allow me to go beyond 960MHz. That's the maximum. I was able to have stable system at 1152MHz in older version of Armbian 5.25 (Debian_jessie_default_3.4.113). I found a post: http://forum.lemaker.org/thread-15543-1-1.html, but I don't know how to edit the file he mentioned in that post. Is it able to edit that file now? As I have set up everything now. So the question is, how to overclock my Banana Pi to 1152MHz in Armbian Bionic (Linux version 4.19.62-sunxi)? Thank you so much.
  18. Hello, I was looking for Kali on BPi and tried the "Kali Linux BananaPi offensive-securityDOTcom-2020.04"-image without success. Unfortunately the image does not boot and no support from there (Domain-contact nor forum[...][...]). Some message about "mount: mounting /dev/mmcblk0p1 on /root failed: No such device", even if kernel was started from this 'No such device"'-SD-card. So Igor wrote me about katoolin which I tested on BPi with Armbian 20.11.3 Busterarmbian. For anyone who is interested here is my way: install "Armbian 20.11.3 Buster \l" install "katoolin see https://github.com/LionSec/katoolin" sudo python2.7 katoolin/katoolin.py -> Add Kali repositories & Update by the menu katoolin.py adds "deb http://http.kali.org/kali kali-rolling main contrib non-free" to /etc/apt-sources apt-get install armitage to get msfconsole, first test with vsftpd_234_backdoor-exploit on testdevice was successfull, meterpreter not tested yet. apt-get install burpsuite did not work, I had to add "deb http://old.kali.org/kali sana main non-free contrib" manually. after this burpsuite could be started. For all who will look for this one day :-D
  19. I noticed that hop lost its cpu bars. I tried to add them but ger error: munmap_chunk(): invalid pointer Anyone else have this problem? Thanks
  20. Hello, I am trying to use BPI with legacy Armbian and Stella emulator with 16:10 monitor (using HDMI-DVI cable) I just dont know how to set proper 16:10 resolution. The resolution I set in armbian-config is 1680x1050, but it is different from resolution that Stella uses, when I launch it on the startup. It uses the resolution defined in FEX. So I checked https://linux-sunxi.org/Fex_Guide#disp_init_configuration and tried various resolutions, but dont know which of them is 16:10 and what is the exact resolution. For example 576p can mean anything. How can I find it out? Thank you very much.
  21. i have a project and i need to activate the vga output on my banapi m1. I searched the forum and found this link https://forum.armbian.com/topic/6292-banana-pi-enable-tv-outrca/ but I think it only applies to old kernel versions. The only reference I entered for these more recent versions was this https://docs.armbian.com/Hardware_Allwinner/#how-to-reconfigure-video-output but I don't know how to activate the video output Can someone help me? thank you
  22. Hi again. After 2 years i want to try configure CanBus on BananaPi and still nothing. I'm continuing my previous post What i do: 1) Paths dtb with this instruction : 2) Load kernel modules: # lsmod | grep can can_raw 20480 1 can_bcm 24576 0 can 20480 2 can_raw,can_bcm sun4i_can 16384 0 can_dev 20480 1 sun4i_can 3) Spawn can0 interface # ip link set can0 type can bitrate 500000 restart-ms 100 triple-sampling on loopback on # ip link set up can0 4) Play with candump / cansend On loopback my messages show in candump, but on arduino receiver still nothing My test env: Two arduino uno with mcp2515 + tja1050 - one as sender other as receiver BananaPi 4.19.62-sunxi and tja1051 transceiver Bitrate on all boards set to 500k Maybe this may be helpful: # ip -det link show can0 4: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP mode DEFAULT group default qlen 10 link/can promiscuity 0 minmtu 0 maxmtu 0 can <LOOPBACK,TRIPLE-SAMPLING> state ERROR-WARNING (berr-counter tx 0 rx 129) restart-ms 100 bitrate 500000 sample-point 0.875 tq 125 prop-seg 6 phase-seg1 7 phase-seg2 2 sjw 1 sun4i_can: tseg1 1..16 tseg2 1..8 sjw 1..4 brp 1..64 brp-inc 1 clock 24000000numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 # dmesg | grep can [ 8.090861] sun4i_can 1c2bc00.can: device registered (base=(ptrval), irq=53) [ 8.120057] can: controller area network core (rev 20170425 abi 9) [ 8.128499] can: broadcast manager protocol (rev 20170425 t) [ 8.132629] can: raw protocol (rev 20170425) [ 3502.151374] sun4i_can 1c2bc00.can can0: bus-off [ 3502.255288] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready [ 3507.633774] sun4i_can 1c2bc00.can can0: bus-off [ 3507.735553] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready [ 3509.316187] sun4i_can 1c2bc00.can can0: bus-off [ 3509.419665] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready [ 3510.275698] sun4i_can 1c2bc00.can can0: bus-off [ 3510.388158] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready [ 3518.457783] sun4i_can 1c2bc00.can can0: bus-off [ 3518.560252] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready [ 3520.323530] sun4i_can 1c2bc00.can can0: bus-off [ 3520.710972] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready [ 3522.219241] sun4i_can 1c2bc00.can can0: bus-off [ 3522.320498] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready [ 3523.602391] sun4i_can 1c2bc00.can can0: bus-off [ 3523.704584] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
  23. Symptoms: Board does not boot Armbian from inserted SD card, but may boot other distributions (based on old/legacy u-boot). Following or similar output can be grabbed from the serial console: U-Boot SPL 2017.01-armbian (Feb 02 2017 - 03:04:04) DRAM: 2048 MiB Trying to boot from MMC1MMC: no card present spl: mmc init failed with error: -123 SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### The key message here is "MMC: no card present" Most likely cause: Malfunctioning microSD slot card detect switch. It can be verified either visually (with a magnifying glass) or electronically (with a multimeter) - at least in the slots used on Orange Pi boards and on Pine64 the pin near the switch should be shorted to the ground (i.e. SD slot casing) when card is inserted. Illustration (example) of a working switch: Verification (with a multimeter): Probe 1 - slot pin near the switch (may be different for different slot types, but at least true for Oranges and Pine64) Probe 2 - microSD slot casing or other parts connected to GND (not shown on the photo) No card - circuit is open Card inserted - circuit is shorted Photos - card is not inseted on the left and is fully inserted on the right: Orange Pi Pine64 (switch is more visible) Can it be fixed? Yes if the switch is not broken completely, by carefully adjusting (bending) the stationary contact (left on the pictures and photos, it usually is a part of the SD slot casing) i.e using a needle so it touches the moving contact (mostly hidden inside the slot on the photos) when card is inserted and not touching it when it is not inserted.
  24. Hello Community, I'm trying to get Armbian running on my Banana PI M1 with the following image: https://dl.armbian.com/bananapi/archive/Armbian_20.05.2_Bananapi_buster_current_5.4.43_minimal.img.xz I flashed the image with Etcher on my SD Card which is a Sandisk Ultra 16GB SDHC Card. After flashing I have inserted the Card into my Banana PI but I only get a red light, I already tried different images like the bionic image but without positive result and tried different power supply cables. In my DHCP Server I see no request. I have also flashed for testing reasons current image of Bananian which was directly working but I don't want to use that because their project is not under active development anymore and they recommend to use Armbian. I would appreciate any ideas.
  25. Is it possible to include an older kernel in my build? Something along the 3.x era? I really need to get an OV5640 working, and it would seem that 5.x kernels don't work with it. The thread is for an orange Pi, but I have a banana pi. Either way, it's an allwinner A20 and I've struck out getting the camera to be detected.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines