Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates

  1. Yesterday
  2. Following my lack of knowledge of the subject I found out another GPIO implementation that seems to have mappings for the NanoPi M4 called OPi.GPIO. Rewired the LCD, I was unsure about the GPIO pin I picked for the DC pin: MOSI > GPIO1_A7 > SPI1_RXD > M4 Pin 21 > LCD DIN Pin (blue) SCK > GPIO1_B1 > SPI1_CLK > M4 Pin 23 > LCD CLK Pin (yellow) CS > GPIO1_B2 > SPI1_CSn0 > M4 Pin 24 > LCD CS Pin (orange) RST > GPIO1_A1(3V) > M4 Pin 11 > LCD RST Pin (white) DC > GPIO1_A3(3V) > M4 Pin 13 > LCD DC Pin (green) Installed and run the thing without much success: pip3 install --upgrade OPi.GPIO ls /dev/spi* /dev/spidev1.0 python3 luma.examples/examples/3d_box.py \ --display=ssd1351 \ --interface=spi \ --width=128 --height=128 \ --spi-bus-speed=16000000 \ --bgr \ --spi-device=1 --spi-port=0 \ --gpio-reset=35 \ --gpio-data-command=33 \ --gpio OPi.GPIO \ --gpio-mode nanopi.m4.BOARD Traceback (most recent call last): File "luma.examples/examples/3d_box.py", line 129, in <module> device = get_device() File "/root/luma.examples/examples/demo_opts.py", line 61, in get_device device = cmdline.create_device(args) File "/usr/local/lib/python3.7/dist-packages/luma/core/cmdline.py", line 246, in create_device device = Device(serial_interface=interface(), **params) File "/usr/local/lib/python3.7/dist-packages/luma/core/cmdline.py", line 161, in spi gpio=self.gpio or GPIO) File "/usr/local/lib/python3.7/dist-packages/luma/core/interface/serial.py", line 299, in __init__ bitbang.__init__(self, gpio, transfer_size, reset_hold_time, reset_release_time, DC=gpio_DC, RST=gpio_RST) File "/usr/local/lib/python3.7/dist-packages/luma/core/interface/serial.py", line 187, in __init__ self._DC = self._configure(kwargs.get("DC")) File "/usr/local/lib/python3.7/dist-packages/luma/core/interface/serial.py", line 200, in _configure self._gpio.setup(pin, self._gpio.OUT) File "/usr/local/lib/python3.7/dist-packages/OPi/GPIO.py", line 470, in setup pin = get_gpio_pin(_mode, channel) File "/usr/local/lib/python3.7/dist-packages/OPi/pin_mappings.py", line 80, in get_gpio_pin return _pin_map[mode][channel] KeyError: 33 From what I understand of https://github.com/rm-hull/OPi.GPIO/blob/master/nanopi/m4.py my physical pin 11 maps to GPIO 33 and physical pin 13 to GPIO 35. Is this even correct? Either way it still fails.
  3. I found this on lore.kernel.org: https://lore.kernel.org/linux-rockchip/YS0v9UbzoHkiU9om@sashalap/T/#t Apparently they're looking into a proper fix, but nothing has come of it yet.
  4. Nope, not yet, I'm a bit busy with rk3288 at the moment, but here you go: ddrbin_v1.16.bin
  5. Maybe a stupid question but why would the regular serial (the one I connect to using USB) of the helios64 not work?
  6. More news, I think this could be a u-boot issue. I have seen some u-boot related changes in the Armbian changelog at https://docs.armbian.com/Release_Changelog/ Thank you for moving to Jira and keeping such good track of completed tasks -- this gives me much more insight into what has changed and when. Here's how I believe it's a u-boot issue: 1. I started with an older Armbian image I have: Armbian_5.91_Rock64_Debian_buster_default_4.4.184_desktop.img 2. I copied several Linux kernels onto this SD card and updated the /boot/Image and /boot/uInitrd and /boot/dtb symlinks to load different kernels. All kernels I tried did not produce any black bars on the HDMI output. The kernels tested were - 4.4.184 from Armbian_5.91_Rock64_Debian_buster_default_4.4.184_desktop.img - 4.4.213 from Armbian_21.08.1_Rock64_buster_legacy_4.4.213_xfce_desktop.img - 5.10.60 from Armbian_21.08.1_Rock64_bullseye_current_5.10.60.img - 5.13.12 from Armbian_21.08.1_Rock64_hirsute_edge_5.13.12.img Next I will load the Armbian 21.08.1 images without any changes to SD card to verify that they are all affected before inspecting u-boot.
  7. Hi, I was making my own battery for the kobol64. To do this, you can use a ready-made balancing board, like this https://aliexpress.ru/item/32884781878.html?item_id=32884781878&sku_id=12000024864748835 any 10k thermistor, for example such https://aliexpress.ru/item/32819250168.html 6 pin connector https://aliexpress.ru/item/1005001490801246.html?item_id=1005001490801246&sku_id=12000016325255609
  8. Thanks for this. Confirmed the same bug can also be found on Bulleseye image for Allwinner H6 TX box: [ Armbian_21.11.0-trunk_Aw-h6-tv_bullseye_current_5.10.62.img.xz ] by balbes150 ZRAM log was getting full again after device reboot & also due to Bulleseye image "ignore the setting SystemMaxUse=20M in /etc/systemd/journald.conf" For now I'll fallback to Buster image previously downloaded for the device.
  9. Hi, forums main language is English only. Use translator tool if necessary.
  10. I tried but "Install/Update the bootloader on SD/eMMC" this option is showing
  11. Both sharing the same very same kernel package so firmware is identical. I would go for bullseye since this is the most recent stable Debian release.
  12. Thank you for sharing the schedule. But no hurry, my daily use cases are already working anyway. I'm only doing this for my own education and as a preview of maybe landing features in Mainline. For me, it's the other way around. hwdec=drm yield high CPU utilisation for bbb_sunflower_2160p_30fps_normal.mp4 and hwdec=drm-copy yield low CPU utilisation. As the values are fluctuating heavyly it is difficult to provide absolut numbers. But anyway here are some rough values: bbb_sunflower_1080p_30fps_normal.mp4: gst-play-1.0 ~35% mpv --hwdec=none --hwdec-codecs=all ~40% mpv --hwdec=drm --hwdec-codecs=all ~38% mpv --hwdec=drm-copy --hwdec-codecs=all ~28% bbb_sunflower_2160p_30fps_normal.mp4: gst-play-1.0 ~35% mpv --hwdec=none --hwdec-codecs=all ~98% playing slow, sound out of sync mpv --hwdec=drm --hwdec-codecs=all ~98% playing jerky, sound out of sync mpv --hwdec=drm-copy --hwdec-codecs=all ~34% playing slow, sound out of sync This is on plasma desktop with wayland backend. Desktop CPU usage fluctuates around 8 to 15% without playing a video, so it's uncertain which CPU cycles are really associated with video playback. The utilization is always distributed almost evenly over all cores. Frequency scaling is not considered here. For reference here the values for lxqt desktop with native xorg backend: bbb_sunflower_1080p_30fps_normal.mp4: gst-play-1.0 ~25% mpv --hwdec=none --hwdec-codecs=all ~30% mpv --hwdec=drm --hwdec-codecs=all ~28% mpv --hwdec=drm-copy --hwdec-codecs=all ~18% bbb_sunflower_2160p_30fps_normal.mp4: gst-play-1.0 ~18% paying as diashow mpv --hwdec=none --hwdec-codecs=all ~98% playing slow, sound out of sync mpv --hwdec=drm --hwdec-codecs=all ~98% playing jerky, sound out of sync mpv --hwdec=drm-copy --hwdec-codecs=all ~22% playing slow, sound out of sync Conlusion: The VPU decoder is not the bottleneck, but setting up an efifcient video pipeline with proper interaction of the several involved hardware acellerators. For Xwindow with the modeset driver this seems not realy possible.
  13. I was hoping to use the tv box as a cheap PC, because I have a bluetooth connection thanks to the CSR 4.0 adapter and a wifi connection thanks to the TL-WN722N v1.0 adapter Version: Armbian 20.10 Focal with Linux 5.9.0-arm-64, using dtb for TX3 mini (I had previously used a rom for this device on my TV Box, so I tried my luck and it did not cause me any problems) Model: X96 mini [CPU: S905w, RAM: 2GB, EMMC: 16GB, WiFi: SV6051P (they say there is a driver that maybe works, but nobody wanted to rewrite it)] Micro SD: SanDisk Ultra 32GB Class 10 A1 There are several things that I do not know because I am a newbie to this topic and I would like to get the full potential of the TvBox so I will do my best with the information from the forum. [Translated from Spanish with Google translator].
  14. Hey, here I am again! This time around I'm trying to use "leocad", but I have this weird bug going on where I cannot see the bricks, nor the tile... Has anyone experienced something similar, maybe with another CAD program...? I will be asking this on their forum as well! On the other picture you can see my terminal info about the package and its dependencies! Thanks and best!
  15. Last week
  16. I've been using the following table with the M4v2: ------+-----+----------+------+ Model NanoPi-M4 +------+----------+-----+------+ | GPIO | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | GPIO | +------+-----+----------+------+---+----++----+---+------+----------+-----+------+ | | | 3.3V | | | 1 || 2 | | | 5V | | | | | | I2C2_SDA | | | 3 || 4 | | | 5V | | | | | | I2C2_SCL | | | 5 || 6 | | | GND(0V) | | | | 32 | 7 | GPIO1_A0 | OUT | 0 | 7 || 8 | | ALT | GPIO4_C1 | 15 | 145 | | | | GND(0V) | | | 9 || 10 | | ALT | GPIO4_C0 | 16 | 144 | | 33 | 0 | GPIO1_A1 | IN | 0 | 11 || 12 | 1 | IN | GPIO1_C2 | 1 | 50 | | 35 | 2 | GPIO1_A3 | IN | 0 | 13 || 14 | | | GND(0V) | | | | 36 | 3 | GPIO1_A4 | IN | 0 | 15 || 16 | 0 | IN | GPIO1_C6 | 4 | 54 | | | | 3.3V | | | 17 || 18 | 0 | IN | GPIO1_C7 | 5 | 55 | | | | UART4_TX | | | 19 || 20 | | | GND(0V) | | | | | | UART4_RX | | | 21 || 22 | 0 | IN | GPIO1_D0 | 6 | 56 | | | | SPI1_CLK | | | 23 || 24 | | | SPI1_CSn | | | | | | GND(0V) | | | 25 || 26 | | ALT | GPIO4_C5 | 11 | 149 | | | | I2C2_SDA | | | 27 || 28 | | | I2C2_SCL | | | | | | I2S0_LRX | | | 29 || 30 | | | GND(0V) | | | | | | I2S0_LTX | | | 31 || 32 | | | I2S_CLK | | | | | | I2S0_SCL | | | 33 || 34 | | | GND(0V) | | | | | | I2S0SDI0 | | | 35 || 36 | | | I2S0SDO0 | | | | | | I2S0I1O3 | | | 37 || 38 | | | I2S0I2O2 | | | | | | GND(0V) | | | 39 || 40 | | | I2S0I3O1 | | | +------+-----+----------+------+---+----++----+---+------+----------+-----+------+ Let's try GPIO1_A4: echo 36 > /sys/class/gpio/export echo "out" >/sys/class/gpio/gpio36/direction echo "1" > /sys/class/gpio/gpio36/value And then I can measure 3v with a multimeter hooked to the physical pin 15.
  17. Now unfortunately luma-oled seems to be yet another problem. I wired up my LCD as: MOSI > GPIO1_A7 > SPI1_RXD > M4 Pin 21 > LCD DIN Pin (blue) SCK > GPIO1_B1 > SPI1_CLK > M4 Pin 23 > LCD CLK Pin (yellow) CS > GPIO1_B2 > SPI1_CSn0 > M4 Pin 24 > LCD CS Pin (orange) DC > GPIO1_A0(3V) > M4 Pin 7 > LCD DC Pin (green) RST > GPIO1_A1(3V) > M4 Pin 11 > LCD RST Pin (white) From my understanding I had to get GPIO1_A0 and GPIO1_A1 in the system so the lib could use them. According to this https://hev.cc/2927.html GPIO mapping I tried: ls -la /dev/spi* crw------- 1 root root 153, 0 Sep 16 18:51 /dev/spidev1.0 echo 32 > /sys/class/gpio/export echo 33 > /sys/class/gpio/export ls -la /sys/class/gpio/ total 0 drwxr-xr-x 2 root root 0 Jan 18 2013 . drwxr-xr-x 76 root root 0 Jan 18 2013 .. --w--w---- 1 root dialout 4096 Sep 16 20:51 export lrwxrwxrwx 1 root root 0 Sep 16 20:50 gpio32 -> ../../devices/platform/pinctrl/gpiochip1/gpio/gpio32 lrwxrwxrwx 1 root root 0 Sep 16 20:50 gpio33 -> ../../devices/platform/pinctrl/gpiochip1/gpio/gpio33 lrwxrwxrwx 1 root root 0 Jan 18 2013 gpiochip0 -> ../../devices/platform/pinctrl/gpio/gpiochip0 lrwxrwxrwx 1 root root 0 Jan 18 2013 gpiochip128 -> ../../devices/platform/pinctrl/gpio/gpiochip128 lrwxrwxrwx 1 root root 0 Jan 18 2013 gpiochip32 -> ../../devices/platform/pinctrl/gpio/gpiochip32 lrwxrwxrwx 1 root root 0 Jan 18 2013 gpiochip64 -> ../../devices/platform/pinctrl/gpio/gpiochip64 lrwxrwxrwx 1 root root 0 Jan 18 2013 gpiochip96 -> ../../devices/platform/pinctrl/gpio/gpiochip96 --w--w---- 1 root dialout 4096 Sep 16 19:19 unexport Now I tried the luma-oled examples (running as root): python3 3d_box.py --display ssd1351 --interface spi --spi-port 0 --spi-device 1 --gpio-reset 33 --gpio-data-command 32 --width 128 --height 128 usage: 3d_box.py >(....) 3d_box.py: error: GPIO access not available I'm not even sure if this part "--gpio-reset 33 --gpio-data-command 32" is correct. I've tried both the virtual pin number and the hardware number without luck. Also tried to install https://github.com/friendlyarm/RPi.GPIO_NP without much luck: apt-get update apt-get install python-dev git clone https://github.com/friendlyarm/RPi.GPIO_NP cd RPi.GPIO_NP python3 setup.py install python3 setup.py install python3 luma.examples/examples/3d_box.py --display=ssd1351 --interface=spi --width=128 --height=128 --spi-bus-speed=16000000 --bgr --spi-device=1 --spi-port=0 --gpio-reset=33 --gpio-data-command=32 --gpio RPi.GPIO Traceback (most recent call last): (...) RuntimeError: It is not NanoPi based board.
  18. Hi. Have you been able to get the wifi to work with 2.4 and 5 GHz on your H96 Pro in Bullseye?
  19. There are 1000+ people that also wants to kill me with a "favour", which is nothing else but covering your interest. Don't you agree? I have give you those links that you will follow and perhaps understand. More then that it is not possible to do. We are supporting you with best effort and our effort is already at a very extreme range. If you find a bug, but you would like to fix it, hire someone to fix it for you and send a patch: https://docs.armbian.com/Process_Contribute/ You don't need to give me money. Give it to someone else. This is your support contract: https://github.com/armbian/build#support @Süleyman Poyraz Topic was split and moved to respective "board bring up forum" ...
  20. I could set up the `armbian/build` repository to compile the kernel for my board. I would like to compile an out-of-tree kernel module on the host machine and copy it to the target machine. I understand that my target machine (Nano Pi Neo Air) has enough resource to compile the module but I just want to try this out. I built the kernel with the following command: ./compile.sh BOARD=nanopiair BRANCH=current KERNEL_CONFIGURE=prebuilt KERNEL_ONLY=yes CLEAN_LEVEL="" KERNEL_CONFIGURE=no CLEAN_LEVEL= KERNEL_KEEP_CONFIG=yes BUILD_MINIMAL=yes BUILD_DESKTOP=no EXTERNAL=no The problem I encountered was that the kernel source (~/build/cache/sources/linux-mainline/orange-pi-5.10) will clear after build, so if I build my kernel module with this source, it prompted that files like `./scripts/basic/fixdep` are missing. I tried to fixed it by running `make ARCH=arm CROSS_COMPILE=.....` . The compilation succeeded. But the kernel module compiled with this source is not compatible with my kernel, because the vermagic (modinfo) is `5.10.60+ SMP mod_unload ARMv7 thumb2 p2v8` rather than `5.10.60-sunxi SMP mod_unload ARMv7 thumb2 p2v8`. I wonder how could I retain the kernel build after running `./complile.sh` so that I can reuse it for kernel module cross compilation purpose? Thank you!
  21. Hello all, This seems to be an issue related to the python script to start the program, any help will be appreciated for those with python programming understanding: $ sudo systemctl status sys-oled.service * sys-oled.service - System Starting on OLED Display Loaded: loaded (/etc/systemd/system/sys-oled.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2021-09-17 02:22:42 JST; 10s ago Process: 4425 ExecStart=/usr/bin/python3 /usr/local/bin/sys-oled --display ${display_model} (code=exited, status=1/FAILURE) Main PID: 4425 (code=exited, status=1/FAILURE) Sep 17 02:22:42 nas python3[4425]: main() Sep 17 02:22:42 nas python3[4425]: File "/usr/local/bin/sys-oled", line 132, in main Sep 17 02:22:42 nas python3[4425]: display_info(device) Sep 17 02:22:42 nas python3[4425]: File "/usr/local/bin/sys-oled", line 105, in display_info Sep 17 02:22:42 nas python3[4425]: draw.text((0, 0), cpu_usage(), font=font, fill="white") Sep 17 02:22:42 nas python3[4425]: File "/usr/local/bin/sys-oled", line 78, in cpu_usage Sep 17 02:22:42 nas python3[4425]: temp = psutil.sensors_temperatures()['f10e4078.thermal'] Sep 17 02:22:42 nas python3[4425]: KeyError: 'f10e4078.thermal' Sep 17 02:22:42 nas systemd[1]: sys-oled.service: Main process exited, code=exited, status=1/FAILURE Sep 17 02:22:42 nas systemd[1]: sys-oled.service: Failed with result 'exit-code'. Thank you in advance for any hints or recommendations about how to solve this. Sincerely,
  22. 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 ]---
  23. Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs). With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported. Your report is invalid for one or more of the following reasons (non-exhaustive list): it is for an unsupported board or image (CSC/EOS/WIP/edge) it is for software that is not supported (such as userspace modules installed on top of the core operating system) it has been logged in the wrong forum (for example requests for help that are not actual bug reports) it lacks requested data (armbianmonitor output) it could have been easily solved by a quick search and/or reading documentation Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)
  1. Load more activity