Jump to content

Search the Community

Showing results for tags 'bananapipro'.

  • 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

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. For a long time, for more than three years, I did not use my BananapiPro board. And recently I decided to launch it again.I downloaded new Armbian image distribution. But the system when loading gives out an error. After the initialization of the devices, a message appears: Device 0: unknown device ethernet@1c50000 Waiting for PHY auto negotiation to complete......... done Speed: 100, full duplex BOOTP broadcast 1 DHCP client bound to address 192.168.2.200 (5ms) *** Warning: no boot file name: using 'COA802c8.img' Using ethernet@1c50000 device TFTP from server 192.168.2.1; our IP address is 192.169.2.200 Filename 'COA802C8.img'. Load address: 0x42000000 Loading: T T T T T T T Retry count exceeded; strarting again missing enviroment variable: pxeuuid Retrieving file: pxelinux.cfg/01-02-89-0b-41-bb-9e Speed 100, fulduplex .... which is postponed and the loading does not happen. I tried to record the image with different programs and dd from console. Also I use three different sd cards. I also tried the old images from the archive, but the situation is repeated. And the old images from 2019 have not been found. Does that mean that new images are not supported by my board? Did it be broken?
  2. Hi, I add a custom repository in customize-image.sh by echoing it in /etc/apt/sources.list.d/custom.list and then calling apt-get update when i build i get always the following error: [πŸ’²|πŸ”¨] Ign:1 http://apt.customrepo.com bookworm InRelease [πŸ’²|πŸ”¨] Ign:2 http://security.debian.org bookworm-security InRelease [πŸ’²|πŸ”¨] Ign:3 http://deb.debian.org/debian bookworm InRelease [πŸ’²|πŸ”¨] Ign:4 http://deb.debian.org/debian bookworm-updates InRelease [πŸ’²|πŸ”¨] Ign:5 http://deb.debian.org/debian bookworm-backports InRelease [πŸ’²|πŸ”¨] Ign:1 http://apt.customrepo.com bookworm InRelease [πŸ’²|πŸ”¨] Ign:2 http://security.debian.org bookworm-security InRelease [πŸ’²|πŸ”¨] Ign:3 http://deb.debian.org/debian bookworm InRelease [πŸ’²|πŸ”¨] Ign:4 http://deb.debian.org/debian bookworm-updates InRelease [πŸ’²|πŸ”¨] Ign:5 http://deb.debian.org/debian bookworm-backports InRelease [πŸ’²|πŸ”¨] Ign:1 http://apt.customrepo.com bookworm InRelease [πŸ’²|πŸ”¨] Ign:2 http://security.debian.org bookworm-security InRelease [πŸ’²|πŸ”¨] Ign:3 http://deb.debian.org/debian bookworm InRelease [πŸ’²|πŸ”¨] Ign:4 http://deb.debian.org/debian bookworm-updates InRelease [πŸ’²|πŸ”¨] Ign:5 http://deb.debian.org/debian bookworm-backports InRelease [πŸ’²|πŸ”¨] Err:2 http://security.debian.org bookworm-security InRelease [πŸ’²|πŸ”¨] System error resolving 'security.debian.org:http' - getaddrinfo (16: Device or resource busy) [πŸ’²|πŸ”¨] Err:1 http://apt.customrepo.com bookworm InRelease [πŸ’²|πŸ”¨] System error resolving 'apt.customrepo.com' - getaddrinfo (16: Device or resource busy) [πŸ’²|πŸ”¨] Err:3 http://deb.debian.org/debian bookworm InRelease [πŸ’²|πŸ”¨] System error resolving 'deb.debian.org:http' - getaddrinfo (16: Device or resource busy) [πŸ’²|πŸ”¨] Err:4 http://deb.debian.org/debian bookworm-updates InRelease [πŸ’²|πŸ”¨] System error resolving 'deb.debian.org:http' - getaddrinfo (16: Device or resource busy) [πŸ’²|πŸ”¨] Err:5 http://deb.debian.org/debian bookworm-backports InRelease [πŸ’²|πŸ”¨] System error resolving 'deb.debian.org:http' - getaddrinfo (16: Device or resource busy) [πŸ’²|πŸ”¨] Reading package lists... [πŸ’²|πŸ”¨] W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease System error resolving 'deb.debian.org:http' - getaddrinfo (16: Device or resource busy) [πŸ’²|πŸ”¨] W: Failed to fetch http://deb.debian.org/debian/dists/bookworm-updates/InRelease System error resolving 'deb.debian.org:http' - getaddrinfo (16: Device or resource busy) [πŸ’²|πŸ”¨] W: Failed to fetch http://deb.debian.org/debian/dists/bookworm-backports/InRelease System error resolving 'deb.debian.org:http' - getaddrinfo (16: Device or resource busy) [πŸ’²|πŸ”¨] W: Failed to fetch http://security.debian.org/dists/bookworm-security/InRelease System error resolving 'security.debian.org:http' - getaddrinfo (16: Device or resource busy) [πŸ’²|πŸ”¨] W: Failed to fetch http://apt.customrepo.com/dists/bookworm/InRelease System error resolving 'apt.customrepo.com' - getaddrinfo (16: Device or resource busy) [πŸ’²|πŸ”¨] W: Some index files failed to download. They have been ignored, or old ones used instead. Any idea? I have to add custom package with several dependencies
  3. Hi! I have banana pro, 5.15.93-sunxi #23.02.2 (bullseye), and use internal wifi adapter as a wifi client. The medium btw my client and ap is instable, there are frequent rate changes (6Mbps...54Mbps), so in order to get rid of it I need to set mandatory wifi rate no more than 6 Mbps. Give me the hint, please: 1. To set wifi rate strictly to 6 Mbps. I had tried iwconfig wlan0 rate 6M - I got "Error for wireless request "Set Bit Rate" (8B20) : SET failed on device wlan0 ; Operation not supported." . 2. To adjust 802.11n parameters (rate, number of spatial streams and so on). Thank you in advance, Aleksei
  4. Hello kind folk. Hoping someone can help. What's listed below is what gone wrong. Armbian monitor diagnostics dump: http://ix.io/3yOY All I've done is install Armbian, did the 'apt update && apt upgrade' and enabled options to see how will it will work. I'm not sure if I have done something wrong for several DT overlays not to load. I can see it states that (what is an ftd?) base ftds are missing a node and need recompiling. How do I do that? (The analog codec does load. It's the only one that does.) U-Boot SPL 2020.10-armbian (Aug 08 2021 - 14:48:33 +0200) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2020.10-armbian (Aug 08 2021 - 14:48:33 +0200) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: LeMaker Banana Pro I2C: ready DRAM: 1 GiB MMC: mmc@1c0f000: 0, mmc@1c12000: 1 Loading Environment from FAT... Unable to use mmc 0:1... Setting up a 720x576i composite-pal console (overscan 32x20) In: serial Out: vga Err: vga Net: eth0: ethernet@1c50000 230454 bytes read in 17 ms (12.9 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 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3964 bytes read in 4 ms (967.8 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 281 bytes read in 4 ms (68.4 KiB/s) 11582960 bytes read in 639 ms (17.3 MiB/s) 7995296 bytes read in 441 ms (17.3 MiB/s) Found mainline kernel configuration 40795 bytes read in 8 ms (4.9 MiB/s) 267 bytes read in 10 ms (25.4 KiB/s) Applying kernel provided DT overlay sun7i-a20-analog-codec.dtbo 386 bytes read in 10 ms (37.1 KiB/s) Applying kernel provided DT overlay sun7i-a20-can.dtbo failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND 500 bytes read in 9 ms (53.7 KiB/s) Applying kernel provided DT overlay sun7i-a20-i2c1.dtbo failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC base fdt does did not have a /__symbols__ node make sure you've compiled with -@ 500 bytes read in 10 ms (48.8 KiB/s) Applying kernel provided DT overlay sun7i-a20-i2c2.dtbo failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC base fdt does did not have a /__symbols__ node make sure you've compiled with -@ 500 bytes read in 9 ms (53.7 KiB/s) Applying kernel provided DT overlay sun7i-a20-i2c3.dtbo failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC base fdt does did not have a /__symbols__ node make sure you've compiled with -@ 766 bytes read in 10 ms (74.2 KiB/s) Applying kernel provided DT overlay sun7i-a20-i2c4.dtbo failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC base fdt does did not have a /__symbols__ node make sure you've compiled with -@ 778 bytes read in 10 ms (75.2 KiB/s) Applying kernel provided DT overlay sun7i-a20-pps-gpio.dtbo failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC base fdt does did not have a /__symbols__ node make sure you've compiled with -@ 443 bytes read in 10 ms (43 KiB/s) Applying kernel provided DT overlay sun7i-a20-pwm.dtbo failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC base fdt does did not have a /__symbols__ node make sure you've compiled with -@ 1069 bytes read in 11 ms (94.7 KiB/s) Applying kernel provided DT overlay sun7i-a20-spi-spidev.dtbo failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC base fdt does did not have a /__symbols__ node make sure you've compiled with -@ 777 bytes read in 11 ms (68.4 KiB/s) Applying kernel provided DT overlay sun7i-a20-w1-gpio.dtbo failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC base fdt does did not have a /__symbols__ node make sure you've compiled with -@ Error applying DT overlays, restoring original DT 40795 bytes read in 8 ms (4.9 MiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 11582896 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 494f4000, end 49fffdb0 ... OK Loading Device Tree to 494e7000, end 494f3f5a ... OK Starting kernel ... Armbian 21.08.2 Focal ttyS0 medusa login:
  5. How I solve this problem or is it an Ambrian bug? Maybe a better question is what is causing these repeated messages. I am at a loss to finding a solution. BOARD=bananapipro BOARD_NAME="Banana Pi Pro" BOARDFAMILY=sun7i
  6. Maybe there has been a glitch in the update release process? I performed a sudo apt update && sudo apt upgrade and this has pulled down an automated build. Should it had pulled down a supported build instead?
  7. Hello, despite using several threads (links below) and one whole week of work, either nothing or only backlight of my display work. Could anybody provide the forum with an image or .debs, please? Or step by step tutorial (adapting existing tutorials) didn't work for me. Thanks https://forum.armbian.com/topic/7233-bananapi-pro-7-touchlcd-with-debian-buster-and-mainline-kernel-5xxxx/ https://forum.armbian.com/topic/14560-sun4i-drm-and-lcd-panels/ or
  8. Recently, successfully, upgraded from Ubuntu Focal to Ubuntu Jammy. Does anyone know the correct procedure to sort out the apt-key deprecation issue? I've read apt-key(8), but I don't fully understand what I need to do. I think a Linux guru is needed here. πŸ™‚ ~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. myron@loki:~$ s apt-get update Hit:1 http://ports.ubuntu.com jammy InRelease Hit:2 http://ports.ubuntu.com jammy-security InRelease Hit:3 http://ports.ubuntu.com jammy-updates InRelease Hit:4 http://ports.ubuntu.com jammy-backports InRelease Hit:5 http://packages.azlux.fr/debian bullseye InRelease Hit:7 https://armbian.github.io/configurator stable InRelease Hit:6 http://armbian.hosthatch.com/apt jammy InRelease Reading package lists... Done W: http://apt.armbian.com/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
  9. Hi to all, I have been using banana pi pro and m1 for some years as mini PBX with asterisk, due the stop of bananian's development that works perfectly but now is obsolete and vulnerable, i'm testing armbian but registered prompt audio sounds choppy and i can't find reasons, I tried to move files in ram disk, use usb to lan interface, increase process priority, use performance ad cpu governor, also tried Armbian 5.83 Bananapi Debian stretch next, same problem. Any suggestion ? Thanks advance.
  10. Installed the Armbian distribution on 05.22 Jammy. In other distributions armbian, zombies are similar. Does not complete the shutdown -P. Instead of disconnecting - a kernel panic. In other distributions, the completion of work is correct. What to do? armbianmonitor -u : http://ix.io/43ZK Error: https://freeimage.host/i/wa9cWF
  11. I've got one of these boards. It is just Kernel development that has ceased as there are no maintainers? (Had I had the skills, I would have happily maintained it. ;-( ) Also, to get the latest Kernel later on, is it as simple as obtaining the official sources and then compiling (or cross-compiling to ARM) and then install the Kernel? On this one I'm a bit like a duck out of water and if anyone can point me along the right path, all help will be greatly appreciated.
  12. Hi forum, I ran an apt-get upgrade a few days back and here linux-image-current-sunxi:armhf was updated from 21.05.6 to 21.08.2 After reboot my SATA was gone. There was nothing in the logs which would have indicated that something is wrong. After I reverted back to 21.05.6 apt-get install linux-image-current-sunxi=21.05.6 apt-get install armbian-firmware=21.05.8 apt-get install linux-dtb-current-sunxi=21.05.6 everything worked again. Has anyone experienced something similar ? Regards Volker
  13. I'm not sure if this is a bug that needs to be reported and I don't know what issues it may be causing, if any. ----< CUT >---- Sep 16 08:55:56 loki kernel: [35972.411737] ieee80211 phy2: brcmf_fweh_event_worker: event handler failed (72) Sep 16 08:55:56 loki kernel: [35972.465736] ieee80211 phy2: brcmf_fweh_call_event_handler: no interface object Sep 16 08:55:56 loki kernel: [35972.465781] ieee80211 phy2: brcmf_fweh_event_worker: event handler failed (72) Sep 16 08:55:56 loki kernel: [35972.471791] ieee80211 phy2: brcmf_fweh_call_event_handler: no interface object Sep 16 08:55:56 loki kernel: [35972.471838] ieee80211 phy2: brcmf_fweh_event_worker: event handler failed (72) Sep 16 09:00:54 loki kernel: [36270.546084] ieee80211 phy2: brcmf_fweh_call_event_handler: no interface object Sep 16 09:00:54 loki kernel: [36270.546174] ieee80211 phy2: brcmf_fweh_event_worker: event handler failed (72) Sep 16 09:00:54 loki kernel: [36270.673121] ieee80211 phy2: brcmf_fweh_call_event_handler: no interface object Sep 16 09:00:54 loki kernel: [36270.673211] ieee80211 phy2: brcmf_fweh_event_worker: event handler failed (72) Sep 16 09:03:24 loki kernel: [36420.901890] sun7i-dwmac 1c50000.ethernet eth0: Link is Down Sep 16 09:03:25 loki kernel: [36421.344529] device wlan0 entered promiscuous mode Sep 16 09:03:26 loki kernel: [36422.743514] PM: suspend entry (s2idle) Sep 16 09:03:26 loki kernel: [36422.858919] Filesystems sync: 0.115 seconds Sep 16 15:54:45 loki kernel: [36422.893328] Freezing user space processes ... (elapsed 0.007 seconds) done. Sep 16 15:54:45 loki kernel: [36422.901044] OOM killer disabled. Sep 16 15:54:45 loki kernel: [36422.901053] Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done. Sep 16 15:54:45 loki kernel: [36422.903250] printk: Suspending console(s) (use no_console_suspend to debug) Sep 16 15:54:45 loki kernel: [61102.651236] usb usb1: root hub lost power or was reset Sep 16 15:54:45 loki kernel: [61102.651348] usb usb2: root hub lost power or was reset Sep 16 15:54:45 loki kernel: [61102.823144] usb usb3: root hub lost power or was reset Sep 16 15:54:45 loki kernel: [61102.887103] usb usb4: root hub lost power or was reset Sep 16 15:54:45 loki kernel: [61102.928819] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) Sep 16 15:54:45 loki kernel: [61102.930362] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Sep 16 15:54:45 loki kernel: [61102.931907] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Sep 16 15:54:45 loki kernel: [61102.934666] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) Sep 16 15:54:45 loki kernel: [61102.953149] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43362-sdio for chip BCM43362/1 Sep 16 15:54:45 loki kernel: [61102.953422] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43362-sdio.lemaker,bananapro.txt failed with error -2 Sep 16 15:54:45 loki kernel: [61102.953436] brcmfmac mmc1:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43362-sdio.lemaker,bananapro.txt Sep 16 15:54:45 loki kernel: [61102.953448] ------------[ cut here ]------------ Sep 16 15:54:45 loki kernel: [61102.953480] WARNING: CPU: 1 PID: 11708 at drivers/base/firmware_loader/fallback.c:569 firmware_fallback_sysfs+0x201/0x348 Sep 16 15:54:45 loki kernel: [61102.953486] Modules linked in: l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ppp_gene ric slhc nls_utf8 cifs libarc4 fscache evdev lima axp20x_adc gpu_sched sun4i_gpadc_iio industrialio sunxi_cir sun4i_ts brcmfmac brcmutil cfg80211 rfkill sunxi_cedrus(C) v4l2_mem2mem videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common nf_log_ipv6 uio_pdrv_genirq uio display_connector ip6t_REJECT nf_reject_ipv6 cpufreq_dt zram xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_recent xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 sch_fq_codel nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter ip_tables x_tables autofs4 pwrseq_simple sun4i_gpadc realtek Sep 16 15:54:45 loki kernel: [61102.953851] CPU: 1 PID: 11708 Comm: kworker/1:0 Tainted: G WC 5.10.60-sunxi#21.08.2 Sep 16 15:54:45 loki kernel: [61102.953858] Hardware name: Allwinner sun7i (A20) Family Sep 16 15:54:45 loki kernel: [61102.953878] Workqueue: events request_firmware_work_func Sep 16 15:54:45 loki kernel: [61102.953922] [<c010ca1d>] (unwind_backtrace) from [<c010952d>] (show_stack+0x11/0x14) Sep 16 15:54:45 loki kernel: [61102.953949] [<c010952d>] (show_stack) from [<c0978293>] (dump_stack+0x77/0x84) Sep 16 15:54:45 loki kernel: [61102.953976] [<c0978293>] (dump_stack) from [<c011ae71>] (__warn+0xad/0xc0) Sep 16 15:54:45 loki kernel: [61102.953999] [<c011ae71>] (__warn) from [<c09721a3>] (warn_slowpath_fmt+0x43/0x7c) Sep 16 15:54:45 loki kernel: [61102.954021] [<c09721a3>] (warn_slowpath_fmt) from [<c0667dcd (firmware_fallback_sysfs+0x201/0x348) Sep 16 15:54:45 loki kernel: [61102.954043] [<c0667dcd>] (firmware_fallback_sysfs) from [<c06671e1>] (_request_firmware+0x3a5/0x570) Sep 16 15:54:45 loki kernel: [61102.954061] [<c06671e1>] (_request_firmware) from [<c06673d9>] (request_firmware+0x2d/0x3c) Sep 16 15:54:45 loki kernel: [61102.954208] [<c06673d9>] (request_firmware) from [<bf9a7957>] (brcmf_fw_request_firmware+0xaf/0xe4 [brcmfmac]) Sep 16 15:54:45 loki kernel: [61102.954388] [<bf9a7957>] (brcmf_fw_request_firmware [brcmfmac]) from [<bf9a8063>] (brcmf_fw_request_done+0x23/0xa0 [brcmfmac]) Sep 16 15:54:45 loki kernel: [61102.954486] [<bf9a8063>] (brcmf_fw_request_done [brcmfmac]) from [<c066766b>] (request_firmware_work_func+0x37/0x60) Sep 16 15:54:45 loki kernel: [61102.954512] [<c066766b>] (request_firmware_work_func) from [<c012f701>] (process_one_work+0x179/0x3e0) Sep 16 15:54:45 loki kernel: [61102.954537] [<c012f701>] (process_one_work) from [<c012fa6b>] (worker_thread+0x103/0x408) Sep 16 15:54:45 loki kernel: [61102.954561] [<c012fa6b>] (worker_thread) from [<c01345bd>] (kthread+0x109/0x10c) Sep 16 15:54:45 loki kernel: [61102.954583] [<c01345bd>] (kthread) from [<c0100159>] (ret_from_fork+0x11/0x38) Sep 16 15:54:45 loki kernel: [61102.954592] Exception stack(0xde4f5fb0 to 0xde4f5ff8) Sep 16 15:54:45 loki kernel: [61102.954606] 5fa0: 00000000 00000000 00000000 00000000 Sep 16 15:54:45 loki kernel: [61102.954622] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Sep 16 15:54:45 loki kernel: [61102.954636] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 Sep 16 15:54:45 loki kernel: [61102.954648] ---[ end trace 0e7e15c499c4d644 ]--- ----< CUT >---- Might be related. Always happens on poweroff. reboot: Power down [ 351.051654] ------------[ cut here ]------------ [ 351.056307] WARNING: CPU: 0 PID: 1 at drivers/i2c/i2c-core.h:41 i2c_transfer+0x93/0xbc [ 351.064226] No atomic I2C transfer handler for 'i2c-1' [ 351.069364] Modules linked in: overlay l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ppp_generic slhc nls_utf8 cifs libarc4 fscache evdev axp20x_adc lima sun4i_gpadc_iio gpu_sched industrialio sun4i_ts sunxi_cir brcmfmac brcmutil cfg80211 rfkill sunxi_cedrus(C) v4l2_mem2mem videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common display_connector uio_pdrv_genirq uio cpufreq_dt nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 zram xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_recent xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 sch_fq_codel ip6table_filter ip6_tables iptable_filter ip_tables x_tables autofs4 pwrseq_simple sun4i_gpadc realtek [ 351.134401] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: G WC 5.10.60-sunxi #21.08.2 [ 351.143363] Hardware name: Allwinner sun7i (A20) Family [ 351.148615] [<c010ca1d>] (unwind_backtrace) from [<c010952d>] (show_stack+0x11/0x14) [ 351.156374] [<c010952d>] (show_stack) from [<c0978293>] (dump_stack+0x77/0x84) [ 351.163611] [<c0978293>] (dump_stack) from [<c011ae71>] (__warn+0xad/0xc0) [ 351.170496] [<c011ae71>] (__warn) from [<c09721bf>] (warn_slowpath_fmt+0x5f/0x7c) [ 351.177989] [<c09721bf>] (warn_slowpath_fmt) from [<c07616a7>] (i2c_transfer+0x93/0xbc) [ 351.186005] [<c07616a7>] (i2c_transfer) from [<c076170b>] (i2c_transfer_buffer_flags+0x3b/0x50) [ 351.194713] [<c076170b>] (i2c_transfer_buffer_flags) from [<c066e8ef>] (regmap_i2c_write+0x13/0x24) [ 351.203769] [<c066e8ef>] (regmap_i2c_write) from [<c066b257>] (_regmap_raw_write_impl+0x4af/0x580) [ 351.212736] [<c066b257>] (_regmap_raw_write_impl) from [<c066b369>] (_regmap_bus_raw_write+0x41/0x5c) [ 351.221963] [<c066b369>] (_regmap_bus_raw_write) from [<c066bb31>] (regmap_write+0x29/0x3c) [ 351.230325] [<c066bb31>] (regmap_write) from [<c0674f63>] (axp20x_power_off+0x23/0x30) [ 351.238254] [<c0674f63>] (axp20x_power_off) from [<c0136a39>] (__do_sys_reboot+0xf5/0x168) [ 351.246528] [<c0136a39>] (__do_sys_reboot) from [<c0100061>] (ret_fast_syscall+0x1/0x62) [ 351.254620] Exception stack(0xc1529fa8 to 0xc1529ff0) [ 351.259677] 9fa0: 4321fedc bebe1aa8 fee1dead 28121969 4321fedc 00000000 [ 351.267861] 9fc0: 4321fedc bebe1aa8 bebe1aa4 00000058 bebe1aa8 bebe1aa4 fffff000 bebe1aac [ 351.276042] 9fe0: 00000058 bebe1a1c b6e9e545 b6e1cbe6 [ 351.281096] ---[ end trace bd6c600f4ffe1d83 ]---
  14. It's possible I may have uncovered a bug. I'm having a problem getting a remote share to mount on boot. The mount is attempted before the network interface is ready and I've got `_netdev` on the required line in `/etc/fstab` . . . . //192.168.0.160/raspi /zeus/raspi cifs rw,auto,uid=1001,gid=1002,file_mode=0755,dir_mode=0755,_netdev,vers=3,credentials=/etc/.smbcredentials_raspi_01 0 0 Here is the part of `dmesg` that explains the issue better than I can: [ 41.572110] sun7i-dwmac 1c50000.ethernet eth0: PHY [stmmac-0:01] driver [RTL8211E Gigabit Ethernet] (irq=POLL) [ 41.574888] sun7i-dwmac 1c50000.ethernet eth0: No Safety Features support found [ 41.574913] sun7i-dwmac 1c50000.ethernet eth0: RX IPC Checksum Offload disabled [ 41.574928] sun7i-dwmac 1c50000.ethernet eth0: No MAC Management Counters available [ 41.574941] sun7i-dwmac 1c50000.ethernet eth0: PTP not supported by HW [ 41.611180] sun7i-dwmac 1c50000.ethernet eth0: configuring for phy/rgmii-id link mode [ 43.915166] ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout occurred [ 43.915201] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5 [ 44.368680] FS-Cache: Loaded [ 45.251206] FS-Cache: Netfs 'cifs' registered for caching [ 45.377166] Key type cifs.spnego registered [ 45.377203] Key type cifs.idmap registered [ 45.379138] CIFS: Attempting to mount //XXX.XXX.0.160/raspi [ 45.379624] CIFS: VFS: Error connecting to socket. Aborting operation. [ 45.379661] CIFS: VFS: cifs_mount failed w/return code = -101 [ 45.708719] sun7i-dwmac 1c50000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 45.708788] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 48.676700] PPP generic driver version 2.4.2 [ 48.732746] NET: Registered protocol family 24 [ 48.990513] l2tp_core: L2TP core driver, V2.0 [ 49.045525] l2tp_netlink: L2TP netlink interface [ 49.103512] l2tp_ppp: PPPoL2TP kernel driver, V2.0 [ 79.972498] device eth0 entered promiscuous mode [ 609.194770] CIFS: Attempting to mount //XXX.XXX.0.160/raspi At 863.282125 I manually issued the command `mount /zeus/raspi` which successfully created the remote fs mount. I've been trying to sort this one out for more than a month. Can anyone help me to get the OS to wait for the network physical link and IP protocol stack to be fully up before trying to connect to the remote share using the line in `/etc/fstab`?
  15. Hello, Im currently working on making lima run with an original 5"-LCD on BananaPro. My problem is to make it work with the sun4i-drm driver. At boot everything works fine and the display shows u-boot and kernel outputs but when the kernel starts the sun4i-drm driver the display freezes and turns white after some seconds. dmesg says: [ 11.178221] sun4i-drm display-engine: bound 1e00000.display-frontend (ops 0xc09986d4) [ 11.178361] sun4i-drm display-engine: bound 1e20000.display-frontend (ops 0xc09986d4) [ 11.178858] sun4i-drm display-engine: bound 1e60000.display-backend (ops sun4i_backend_ops [sun4i_backend]) [ 11.179226] sun4i-drm display-engine: bound 1e40000.display-backend (ops sun4i_backend_ops [sun4i_backend]) [ 11.179943] sun4i-drm display-engine: No panel or bridge found... RGB output disabled [ 11.179970] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops 0xc09973fc) [ 11.180653] sun4i-drm display-engine: No panel or bridge found... RGB output disabled [ 11.180675] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops 0xc09973fc) [ 11.195807] sun4i-codec 1c22c00.codec: Codec <-> 1c22c00.codec mapping ok [ 11.204374] sun4i-drm display-engine: bound 1c16000.hdmi (ops sun4i_hdmi_driver_exit [sun4i_drm_hdmi]) [ 11.204391] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 11.204395] [drm] No driver support for vblank timestamp query. [ 11.204411] checking generic (7fe89000 177000) vs hw (0 ffffffff) [ 11.204422] fb0: switching to sun4i-drm-fb from simple [ 11.205292] Console: switching to colour dummy device 80x30 [ 11.206140] [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on Lima was set up properly and works with HDMI output so far. What confuses me is the line where it says "No panel or bridge found... RGB output disabled". The 5"LCD is connected via RGB-Interface and has already been working less than a second before. So it seems the display has not been detected properly by the sun4i-drm module. Has anyone ever had a similar Problem? Any suggestions where to search for the problem's solution? regards
  16. Hello, First of all, I'm new on Armbian I got some a stack dump on the console and can see following messages on kernel.log : --- Oct 24 14:27:28 localhost kernel: [183195.142242] 8<--- cut here --- Oct 24 14:27:28 localhost kernel: [183195.152222] Unable to handle kernel paging request at virtual address 2f68f25c Oct 24 14:27:28 localhost kernel: [183195.167942] pgd = 36f6b267 Oct 24 14:27:28 localhost kernel: [183195.179169] [2f68f25c] *pgd=00000000 Oct 24 14:27:28 localhost kernel: [183195.191263] Internal error: Oops: 805 [#1] SMP THUMB2 Oct 24 14:27:29 localhost kernel: [183195.204864] Modules linked in: brcmfmac brcmutil axp20x_adc evdev lima sun4i_gpadc_iio gpu_sched industrialio cfg80211 sun4i_ts sunxi_cir rfkill sun4i_ss sunxi_cedrus(C) zram uio_pdrv_genirq uio cpufreq_dt ip_tables x_tables autofs4 pwrseq_simple sun4i_gpadc realtek Oct 24 14:27:29 localhost kernel: [183195.247439] CPU: 0 PID: 7113 Comm: kworker/0:3 Tainted: G C 5.8.16-sunxi #20.08.14 Oct 24 14:27:29 localhost kernel: [183195.266241] Hardware name: Allwinner sun7i (A20) Family Oct 24 14:27:29 localhost kernel: [183195.281439] Workqueue: events dbs_work_handler Oct 24 14:27:29 localhost kernel: [183195.295783] PC is at cpufreq_callback+0xfe/0x12c Oct 24 14:27:29 localhost kernel: [183195.310236] LR is at cpufreq_callback+0x109/0x12c Oct 24 14:27:29 localhost kernel: [183195.324760] pc : [<c010b86e>] lr : [<c010b879>] psr: 80000033 Oct 24 14:27:29 localhost kernel: [183195.340961] sp : ed8a5df0 ip : 00000000 fp : ed8a5ebc Oct 24 14:27:29 localhost kernel: [183195.356183] r10: c0f050d4 r9 : c0e8c228 r8 : 00000001 Oct 24 14:27:29 localhost kernel: [183195.371378] r7 : 00000000 r6 : 00e8c080 r5 : ed9c9e00 r4 : c0f0548c Oct 24 14:27:29 localhost kernel: [183195.387980] r3 : 00000000 r2 : 2f68f080 r1 : 00000008 r0 : 00000000 Oct 24 14:27:29 localhost kernel: [183195.404570] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA Thumb Segment none Oct 24 14:27:29 localhost kernel: [183195.421987] Control: 50c5387d Table: 6b97806a DAC: 00000051 Oct 24 14:27:29 localhost kernel: [183195.437887] Process kworker/0:3 (pid: 7113, stack limit = 0x2dcc7ac2) Oct 24 14:27:29 localhost kernel: [183195.454629] Stack: (0xed8a5df0 to 0xed8a6000) Oct 24 14:27:29 localhost kernel: [183195.469286] 5de0: 00000001 00000000 00000000 00000000 Oct 24 14:27:29 localhost kernel: [183195.488000] 5e00: c0fc11f4 ffffffff ed8a5ebc 00000001 00000000 ffffffff ef69a580 c0136947 Oct 24 14:27:29 localhost kernel: [183195.506830] 5e20: ffffffff 00000000 c0fc11f4 00000000 00000001 c0fc1208 ed8a5ebc c0136a8f Oct 24 14:27:29 localhost kernel: [183195.525689] 5e40: 00000000 ed9c8600 00000000 ed8a5ebc ed9c9e00 ed8a5ebc c0f050d4 ed8a4000 Oct 24 14:27:29 localhost kernel: [183195.544663] 5e60: 00000000 c0136ae3 00000000 c0136ae3 00000008 c078e231 ed9c9e00 ed9c9e00 Oct 24 14:27:29 localhost kernel: [183195.563711] 5e80: ef689e00 c08a5e4d 00000000 00000000 00000002 c104d804 00000000 c078e323 Oct 24 14:27:29 localhost kernel: [183195.582889] 5ea0: ed9c9e00 00000000 00080e80 c078e859 ed935280 00002710 a7107534 ed9c9e00 Oct 24 14:27:29 localhost kernel: [183195.602209] 5ec0: 000ea600 00080e80 000000a1 c0f04fc8 ed9c9e00 ed935280 ed935d00 0022dd00 Oct 24 14:27:29 localhost kernel: [183195.621615] 5ee0: edfcb900 ed935d00 00000000 c07915f7 c0791569 ed9352b8 00000000 ed935284 Oct 24 14:27:29 localhost kernel: [183195.641127] 5f00: ed9c9e00 c0fc15a4 00000000 c07923b1 ed9352b8 edf98280 ef69a580 ef69d700 Oct 24 14:27:29 localhost kernel: [183195.660729] 5f20: 00000000 c01309fb ed8a4000 ef69a580 ed8a5f48 edf98280 ef69a580 edf98294 Oct 24 14:27:29 localhost kernel: [183195.680265] 5f40: ef69a598 c0f03d00 00000008 ed8a4000 ef69a580 c0130d47 edf98294 c0fdb887 Oct 24 14:27:29 localhost kernel: [183195.699815] 5f60: edf98280 ed0b5280 ed0b5e40 00000000 ed8a4000 c0130c4d edf98280 ec11bebc Oct 24 14:27:29 localhost kernel: [183195.719431] 5f80: ed0b52a4 c0135b07 0000004f ed0b5e40 c0135a1d 00000000 00000000 00000000 Oct 24 14:27:29 localhost kernel: [183195.739128] 5fa0: 00000000 00000000 00000000 c0100159 00000000 00000000 00000000 00000000 Oct 24 14:27:29 localhost kernel: [183195.758788] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Oct 24 14:27:29 localhost kernel: [183195.778422] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000 Oct 24 14:27:29 localhost kernel: [183195.797908] [<c010b86e>] (cpufreq_callback) from [<c0136947>] (notifier_call_chain+0x43/0x5c) Oct 24 14:27:29 localhost kernel: [183195.817958] [<c0136947>] (notifier_call_chain) from [<c0136a8f>] (__srcu_notifier_call_chain+0x33/0x70) Oct 24 14:27:29 localhost kernel: [183195.839094] [<c0136a8f>] (__srcu_notifier_call_chain) from [<c0136ae3>] (srcu_notifier_call_chain+0x17/0x1c) Oct 24 14:27:29 localhost kernel: [183195.860797] [<c0136ae3>] (srcu_notifier_call_chain) from [<c078e231>] (cpufreq_notify_transition+0x7d/0x154) Oct 24 14:27:29 localhost kernel: [183195.882698] [<c078e231>] (cpufreq_notify_transition) from [<c078e323>] (cpufreq_freq_transition_end+0x1b/0x6c) Oct 24 14:27:29 localhost kernel: [183195.904941] [<c078e323>] (cpufreq_freq_transition_end) from [<c078e859>] (__cpufreq_driver_target+0x1fd/0x410) Oct 24 14:27:29 localhost kernel: [183195.927309] [<c078e859>] (__cpufreq_driver_target) from [<c07915f7>] (od_dbs_update+0x8f/0x108) Oct 24 14:27:29 localhost kernel: [183195.948495] [<c07915f7>] (od_dbs_update) from [<c07923b1>] (dbs_work_handler+0x29/0x4c) Oct 24 14:27:29 localhost kernel: [183195.969159] [<c07923b1>] (dbs_work_handler) from [<c01309fb>] (process_one_work+0x15f/0x3b0) Oct 24 14:27:29 localhost kernel: [183195.990458] [<c01309fb>] (process_one_work) from [<c0130d47>] (worker_thread+0xfb/0x3e0) Oct 24 14:27:29 localhost kernel: [183196.011469] [<c0130d47>] (worker_thread) from [<c0135b07>] (kthread+0xeb/0x10c) Oct 24 14:27:29 localhost kernel: [183196.031639] [<c0135b07>] (kthread) from [<c0100159>] (ret_from_fork+0x11/0x38) Oct 24 14:27:29 localhost kernel: [183196.051656] Exception stack(0xed8a5fb0 to 0xed8a5ff8) Oct 24 14:27:29 localhost kernel: [183196.069549] 5fa0: 00000000 00000000 00000000 00000000 Oct 24 14:27:29 localhost kernel: [183196.090862] 5fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 Oct 24 14:27:29 localhost kernel: [183196.111734] 5fe0: 00000000 00000000 00000000 00000000 00000013 00000000 Oct 24 14:27:29 localhost kernel: [183196.130431] Code: e004 f854 2020 4432 (f8c2) 71dc Oct 24 14:27:29 localhost kernel: [183196.147319] ---[ end trace 3a2dd626830effd8 ]--- Then CPU load goes to 2.00 but no process consumes power as per Top : it's happening on 2 days basis, randomly. Another issue : I tried to run armbianmonitor -u but it hangs after some messages (bellow) and the cpu load goes to 6.00 again without anything noticeable. ---- ---- Thanks Laurent
  17. Hello, I'm a complete beginner with Armbian and SOC board. I've a bananapi pro board from lemaker and I've installed 6 month ago Raspbian / Jessie and domoticz and all works well until a click unfortunately on update icons of domoticz...and the problems began...no back up...new version of domoticz required buster...image buster not avalaible under raspbian for bananapro.... So I decided to install Armbian/buster_minimal I've serial link on which I can see that board boot correctly. I've installed Armbian-config and the "Default install desktop with browser and extra". I want the board to show information on HDMI output...but no screen. I spent a lot of time on forums, my board is powered with USB from a PC. My monitor is a TV. My Sd card is working well (sandisk A1 16Gb) and the board worked and output data on HDMI with Raspbian/jessie so it seem that the problem doesn't come from hardware. I've also seen on posts that resolution could be the problem, I've change in /boot/armbianEnv.txt: console=display disp_mode=1920*1080p60 to 1280*1024p60 save it and reboot not working... Sorry for my question if it has already been solved or if it is a silly question Someone could help me ? Regards.
  18. This is a simple one, but the most annoying. The only Linux distribution I can not get to work in the Armbian on the Banana Pro. Sandisk 32Gb Class 10 MicroSD card. A USB power supply that does supply sufficient power and current. I write the image to the MicroSD card, insert it into the Banana Pro's card holder, power it up, the red LED lights up and ................. that's where it stops. No heartbeat on the green LED. The one thing I notice is that the image I download has only got one partition on it and that's the ext4 partition. It does not have the small FAT formatted partition and I think this is where it all goes wrong. The small FAT boot that is present on all the other SD card images is missing on the Armbian image. I think once I get Ambian to boot on the Banana Pro then I think everything should just work as it should. Can someone please help me with this? I'm using the image from here . . . . https://www.armbian.com/banana-pi-pro/
  19. Hello guys, I've been playing around with the build-in lima drivers but didn't get it to work on BananaPro using Armbian_20.02.1_Bananapipro_buster_current_5.4.20_desktop image. I installed drivers armsoc, modesetting, fbdev from debian buster repos but "Xorg -configure" fails. /var/log/Xorg.0.log says: and and generated xorg.conf: Any suggestions what I am doing wrong? regards
  20. After updating to 5.9.14 from 5.8.16, framebuffer is broken. No output after booting, hdmi monitor goes to sleep. [ 1.455763] ------------[ cut here ]------------ [ 1.455791] WARNING: CPU: 0 PID: 1 at arch/arm/mm/ioremap.c:287 __arm_ioremap_pfn_caller+0x13f/0x14c [ 1.455796] Modules linked in: [ 1.455810] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.9.14-sunxi #20.11.3 [ 1.455814] Hardware name: Allwinner sun7i (A20) Family [ 1.455846] [<c010cce9>] (unwind_backtrace) from [<c010945d>] (show_stack+0x11/0x14) [ 1.455862] [<c010945d>] (show_stack) from [<c093b0ab>] (dump_stack+0x77/0x84) [ 1.455878] [<c093b0ab>] (dump_stack) from [<c011ad8d>] (__warn+0xb1/0xb4) [ 1.455894] [<c011ad8d>] (__warn) from [<c093511b>] (warn_slowpath_fmt+0x43/0x7c) [ 1.455908] [<c093511b>] (warn_slowpath_fmt) from [<c01132d3>] (__arm_ioremap_pfn_caller+0x13f/0x14c) [ 1.455920] [<c01132d3>] (__arm_ioremap_pfn_caller) from [<c011330f>] (__arm_ioremap_caller+0x2f/0x38) [ 1.455935] [<c011330f>] (__arm_ioremap_caller) from [<c0599c73>] (simplefb_probe+0x19b/0x6b8) [ 1.455951] [<c0599c73>] (simplefb_probe) from [<c062ea3f>] (platform_drv_probe+0x33/0x68) [ 1.455967] [<c062ea3f>] (platform_drv_probe) from [<c062ce27>] (really_probe+0x13b/0x354) [ 1.455981] [<c062ce27>] (really_probe) from [<c062d205>] (driver_probe_device+0xa9/0x168) [ 1.455994] [<c062d205>] (driver_probe_device) from [<c062b89d>] (bus_for_each_drv+0x4d/0x78) [ 1.456007] [<c062b89d>] (bus_for_each_drv) from [<c062cc7f>] (__device_attach+0x8f/0xf0) [ 1.456019] [<c062cc7f>] (__device_attach) from [<c062c1ff>] (bus_probe_device+0x5b/0x60) [ 1.456033] [<c062c1ff>] (bus_probe_device) from [<c06299db>] (device_add+0x2e7/0x564) [ 1.456051] [<c06299db>] (device_add) from [<c07a396d>] (of_platform_device_create_pdata+0x65/0x88) [ 1.456067] [<c07a396d>] (of_platform_device_create_pdata) from [<c0e1d52f>] (simplefb_init+0x4f/0x60) [ 1.456081] [<c0e1d52f>] (simplefb_init) from [<c0101bf1>] (do_one_initcall+0x39/0x1a8) [ 1.456097] [<c0101bf1>] (do_one_initcall) from [<c0e00ee5>] (kernel_init_freeable+0x1bd/0x208) [ 1.456113] [<c0e00ee5>] (kernel_init_freeable) from [<c093fd9d>] (kernel_init+0xd/0xe0) [ 1.456125] [<c093fd9d>] (kernel_init) from [<c0100159>] (ret_from_fork+0x11/0x38) [ 1.456130] Exception stack(0xeed2bfb0 to 0xeed2bff8) [ 1.456138] bfa0: 00000000 00000000 00000000 00000000 [ 1.456147] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 [ 1.456155] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 [ 1.456170] ---[ end trace 396812099caf657e ]--- [ 1.456203] simple-framebuffer: probe of 7f817000.framebuffer failed with error -12
  21. System: armbian, BananaPi Pro, sd card, sata ssd, usb hdd I manually moved my existing armbian system from sd card to a sata ssd. Then I changed the rootdev in armbianEnv.txt to the ssdΒ΄s UUID. After reboot I thought everything was ok. Then after a system update I figured out that the kernel version differs from the installed kernel modules. I think the new kernel and the modules are installed in /boot at /dev/sda whereas the kernel still boots from /dev/mmcblk0p1. How can I fix this? Here some information: root@pi-nas:/mnt/boot# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 477G 0 disk β”œβ”€sda1 8:1 0 29,3G 0 part / β”œβ”€sda2 8:2 0 445,7G 0 part /home └─sda3 8:3 0 2G 0 part [SWAP] sdb 8:16 0 1,6T 0 disk └─sdb1 8:17 0 1,6T 0 part /share mmcblk0 179:0 0 7,3G 0 disk └─mmcblk0p1 179:1 0 1,3G 0 part root@pi-nas:~# mount /dev/mmcblk0p1 /mnt/ root@pi-nas:~# ls /mnt/boot/ armbianEnv.txt boot.scr overlay-user armbian_first_run.txt.template boot.scr.bak System.map-5.4.20-sunxi boot.bmp config-5.4.20-sunxi uInitrd boot.cmd dtb uInitrd-5.4.20-sunxi boot.cmd.bak dtb-5.4.20-sunxi vmlinuz-5.4.20-sunxi boot-desktop.png initrd.img-5.4.20-sunxi zImage root@pi-nas:~# cat /mnt/boot/armbianEnv.txt verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun7i-a20 rootdev=UUID=f631e37b-e2e5-431a-aab0-cbbcc544528f rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u root@pi-nas:~# blkid /dev/sda1 /dev/sda1: UUID="f631e37b-e2e5-431a-aab0-cbbcc544528f" TYPE="ext4" PARTUUID="000a6123-01" root@pi-nas:~# ls /boot boot.scr dtb-5.10.34-sunxi uInitrd zImage config-5.10.34-sunxi initrd.img-5.10.34-sunxi uInitrd-5.10.34-sunxi dtb System.map-5.10.34-sunxi vmlinuz-5.10.34-sunxi root@pi-nas:~# uname -a Linux pi-nas 5.4.20-sunxi #20.02.1 SMP Mon Feb 17 02:09:41 CET 2020 armv7l GNU/Linux root@pi-nas:~# ls /lib/modules/ 5.10.34-sunxi
  22. Greetings, after a long time I am playing with my old Banana Pi Pro again. This time with the intention to probably use it on IoT purposes. That implies I only need WIFI and the GPIO pins. Which gives some opportunity to save power by powering down every thing else which is not needed. My first approach here is to strip down everything from the device tree I donΒ΄t need. That means everything related to: framebuffer hdmi lcd sata display engine ethernet video codec usb ir gpu/mali That resulted in a drop in power consumption in idle from: ~0.990 - ~1.330W to: ~0.700 - ~1.000W Roughly 0.3W lower consumption. Furthermore I underclocked the CPU to the minimum of 144MHz with power save governor. Resulting in a idle power consumption of: ~0.670 - ~0.720W I also tried setting the default kernel tick rate from 250HZ to 100HZ but that gave no measurable gains. And just for curiosity I deactivated the WIFI from the device tree resulting in a consumption of: ~0.470 - ~0.520W Thats pretty much for one needed component and I am asking myself if there is some saving potential here. So I found out from iwconfig that power management is not enabled. Enabling it by changing /etc/NetworkManager/conf.d/20-override-wifi-powersave-disable.conf wifi.powersave from 2 to 3 changed what iwconfig shows. But it has no influence on power consumption at all. So my questions here are the following: Is there a possibility to save power on wifi? Are there other things I can do aside from these I have done?
  23. The info from "df" show /dev/sda but "lsblk" show a /dev/sdc unmounted unit. The unit is reachable at /media/sata and is added in fstab using the UUID. What's happening? Thanks in advance.
  24. Hi, trying to install a char driver without any driver framework. The only thing I can not install is getting the Interrupt through to the interrupt servce routine err = request_irq(irq, handler, // IRQF_TRIGGER_RISING, IRQF_TRIGGER_HIGH, "can4linux", &can_minors[minor]); irq is the Interrupt number of the CAN controller, it is fixed in the A20 to 58. I do get no error messages, but the isr is not called. What I am missing? Greetings Heinz By the way, it worked an Bananian 3.x
  25. Hi, trying to start my Banana Pi Pro Board with the latest Armbian buster image (Armbian_21.02.1_Bananapipro_buster_current_5.10.12.img.xz) without success. There is initial output on the screen until there is the message "Starting kernel ...", the after a few seconds the monitor loses its signal and nothing seems to happen any more see: https://c.1und1.de/@520257322610590089/1IBkHiwHQX6jYxLPdlkTZQ Reading through the forum I guessed it could have to do with an issue of automatic discovery of the correct DTB, so I edited the armbianEnv.txt file and added the following line to it: fdtfile=sun7i-a20-bananapro.dtb But still the same behavior. I then tested another image from the archive (Armbian_20.08.1_Bananapipro_bionic_current_5.8.5.img.xz). The board comes up fine. SD Card ist brand new SanDisk 32GB Class 10 A1 What should I be looking at next ? Thx. in advance
Γ—
Γ—
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines