Jump to content

Search the Community

Showing results for tags 'nanopim4'.

  • 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. Hi folks, I had an old install of armbian which worked. I wanted a new install to start fresh all over. My problem is that i don't het any HDMI signal form the board. What i've done so far: - Downloaded ISO from armbian (nanopim4 with DE) - flashed iso to sd 8GB SD card - ssh to the board and did the first install - with `armbian-install` installed to 32GB emmc - enabled RDP for remote access but i was not able to get this to work either -.-' System: _ _ ____ _ __ __ _ _ | \ | | _ \(_) | \/ | || | | \| | |_) | | | |\/| | || |_ | |\ | __/| | | | | |__ _| |_| \_|_| |_| |_| |_| |_| Welcome to Armbian 23.8.1 Bookworm with Linux 6.1.50-current-rockchip64 No end-user support: community creations System load: 2% Up time: 4 min Memory usage: 6% of 3.77G IP: 192.168.0.102 CPU temp: 33°C Usage of /: 28% of 29G RX today: 4.3 GiB Board starts with no issue, ssh works perfectly but i dont have any HDMI output. this is the `armbianmonitor - u` output: https://paste.armbian.com/akovewakud If you need log from the old installation i can provide the logs also. Thanks for your help!
  2. Myy

    Mainline VPU

    So, I tried to adapt @Kwiboo and @jernej patches on my 5.6 branch, but this made the kernel fail to boot for no visible reason. Since I were able to boot it without the VPU patches, I'm convinced that it's their readaptation that broke something. The patches applied are here : https://github.com/Miouyouyou/RockMyy64 If someone wants to play with them and determine which one break the boot process.
  3. Anyone cares, have some helpful tips or time & knowledge to fix this ? Problem: No audio on either sink (board or HDMI) with the latest built made available for download (Armbian 23.02 Jammy XFCE Kernel 5.15.y, Size: 1313Mb, Release date: Feb 27, 2023) Tried so far: Switching the default server to nanopmi4v2 and toggling the default sink; Hints: Both sinks work fine on a previous 'dirty nightly built' that I have used for a while. "armbianmonitor" on both built attached for anyone who can help. Thanks Older-Nightly-Dirty-Built.txt Lates-Official-Built.txt
  4. I downloaded the latest Armbian 22.08 image for the NanoPi M4V2 (https://armbian.chi.auroradev.org/dl/nanopim4v2/archive/Armbian_22.08.8_Nanopim4v2_jammy_current_5.15.75.img.xz), flashed it to an sd card and tried to boot my NanoPi M4 (non-V2 board). It crashes every time with the attached log. I have tried 4 different power supplies, so I don't think that's the issue. I tried the Bullseye CLI image and it fails in the same way. The Sid server image works fine. Any ideas? Thanks, Ben
  5. Hi, I own a nanopi m4 v1, I know there is no more armbian support neither maintainer for this board but I still enjoy "the other supported variants" which work very good for my needs. Until now, I only used armbian on sdcards for my system, but today I tried to install it of my emmc module. Maybe I did somethig stupid, I tried to install the bullseye current cli version from https://www.armbian.com/nanopi-m4/ on my emmc module via armbian-install. So all process of installation was ok (boot on sdcard then armbian-install => erase / format / install on emmc ...), I choose to boot from emmc too (maybe it was a mistake). => After the installation I put off the sdcard (to let only the emmc on the board), then plugin power to boot, but nothing happen (only red light on boot). From then my board cannot boot anymore, I have only the red light on, no more green light. I try to flash back sdcard again with a lot of differents images (armbian, legacy versions, friendly elec versions), without any success. I try with differents sdcards (who worked before), with or without the emmc module plug, nothing worked. I try too to boot on usb but same result. So I think the option I choose in armbian-install to boot on emmc maybe change the boot mode of my board ? Maybe is some eeprom on the board with some kind of boot order which was flash by armbian-install and explains the problem ? Have anyone have that kind of problem ? Some ideas to unbrick my board ? Thank you P.S. : My emmc module is ok too, I had friendlycore installed on it and I boot it more earlier today. I don't have emmc usb reader, so I cannot flash the emmc for now (I used the board for that).
  6. I simply can not figure out why UART4 at GPIO1 header with the pins 19 (TX) and 21 (RX) not working at all. I see that here (ttyS2) is running an agetty but there is no serial activity at any baudrate (9600, 115200). Please help me.
  7. Hi all, I have a nanopi m4 with following installation - Armbian_22.05.4_Nanopim4v2_jammy_current_5.15.48_xfce_desktop. I am looking for someone who has retroarch installed on armbian and fully working, and what the key steps are. Im asking because: 1) I tried installing by command line, which installs retroarch to a location with no cores. An issue with rk3399 cores is that there are none to download and must be built seperately (Is there a way to update a file so that cores can be downloaded through the application?) 2) In an attempt to build retroarch + cores, i downloaded and built libretro, which took probably 12+ hours. This resulted in a seperate installation, with cores not in the correct directory, and many cores uninstallable eg mame2010, ppsspp. I hope someone can assist - I want to find a use for my nanopi m4 but having difficulty with retro games - Rcade is buggy, lakka does not work well, batocera does not work well, TwisterOS does not boot after selecting correct .dtb etc. I have built linux and android on many boards but this one is troublesome. Thanks for reading
  8. mindee

    NanoPI M4

    NanoPi-M4 will be cheaper and same form factor as RPI 3.
  9. My nanopi m4b has been showing slowness problems that I believe to be caused by the ethernet, I access a site inside it that has a camera stream and sometimes it is slow, and now the connection via ethernet completely stopped working, I looked for something in the logs but I didn't find anything that could indicate the problem, I can access my site over wifi
  10. i found a running task on friendlyelec desktop called "pwm fan" But i found no more informations how to connect a pwm fan to the Nanopi M4 Which pins are needed to connect ? Can i use a normal 5V Fan or is a special Fan needed ? Anyone aware of this ?
  11. I originally installed Armbian witk Kernel 4.4 on my Nanopi.m4 and later upgraded it to 5.10 via armbian-config. Things work fine but whenever I got a new update via apt update, things get messed up a bit the /boot/Image got linked to vmlinux-4.4.213-rk3399 instead of vmlinuz-5.10.35-rockchip64 while others uInitrd -> uInitrd-5.10.35-rockchip64 dtb -> dtb-5.10.35-rockchip64 The result's the board couldn't boot-up, when I restarted it. And, I need to correct the Image -> vmlinuz-5.10.35-rockchip64 and doing mkimage -C none -A arm -T script -d boot.cmd boot.scr from another linux machine to the SDCard. It works fine afterward but I wondered if there is the right way to fix this issue for good. Thank you,
  12. Despite this being the supported image advertised for the board, it just does not boot on this board, whereas the "current" image does boot (but with limited hardware support). I'm booting with just the serial console connected, to limit interferences On serial console with default config I get: Found U-Boot script /boot/boot.scr 3185 bytes read in 4 ms (777.3 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 117 bytes read in 3 ms (38.1 KiB/s) 7861795 bytes read in 361 ms (20.8 MiB/s) 20770824 bytes read in 941 ms (21.1 MiB/s) 104363 bytes read in 11 ms (9 MiB/s) 2698 bytes read in 7 ms (376 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 7861731 Bytes = 7.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to 797b2000, end 79f315e3 ... OK ERROR: reserving fdt memory region failed (addr=0 size=0) Loading Device Tree to 0000000079730000, end 00000000797b1fff ... OK Starting kernel ... Could this "reserving fdt memory region failed" explain all the symptoms outlined below ? Tried with several versions, some details at "verbosity=7" follow: Armbian_21.05.1_Nanopim4_buster_legacy_4.4.213.img.xz boots but blocks (apparently systematically), following errors related to sdmmc: [ 26.536387] wifi_platform_set_power = 1 [ 26.537739] ======== PULL WL_REG_ON(-1) HIGH! ======== [ 26.539257] [WLAN_RFKILL]: rockchip_wifi_power: 1 [ 26.540704] [WLAN_RFKILL]: wifi turn on power. -1 [ 26.845813] sdio_reset_comm(): [ 26.877865] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 26.897284] mmc_host mmc2: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0) [ 26.975780] mmc2: queuing unknown CIS tuple 0x80 (2 bytes) [ 26.983328] mmc2: queuing unknown CIS tuple 0x80 (3 bytes) [ 26.990834] mmc2: queuing unknown CIS tuple 0x80 (3 bytes) [ 27.003171] mmc2: queuing unknown CIS tuple 0x80 (7 bytes) [ 27.217179] mmc_host mmc2: Bus speed (slot 0) = 150000000Hz (slot req 150000000Hz, actual 150000000HZ div = 0) [ 27.345857] dwmmc_rockchip fe320000.dwmmc: Unexpected command timeout, state 3 Armbian_21.02.3_Nanopim4_buster_legacy_4.4.213.img.xz can just block at various points (more around the sdio-connected wifi/bt chip ?): [ 16.801470] ======== PULL WL_REG_ON(-1) HIGH! ======== [ 16.803059] [WLAN_RFKILL]: rockchip_wifi_power: 1 [ 16.804576] [WLAN_RFKILL]: wifi turn on power. -1 [ 17.109606] sdio_reset_comm(): [ 17.141666] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 17.161095] mmc_host mmc2: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0) [ 17.219575] mmc2: queuing unknown CIS tuple 0x80 (2 bytes) [ 17.227230] mmc2: queuing unknown CIS tuple 0x80 (3 bytes) [ 17.234832] mmc2: queuing unknown CIS tuple 0x80 (3 bytes) [ 17.247507] mmc2: queuing unknown CIS tuple 0x80 (7 bytes) [ 17.466043] mmc_host mmc2: Bus speed (slot 0) = 150000000Hz (slot req 150000000Hz, actual 150000000HZ div = 0) [ 17.504236] Bluetooth: Core ver 2.21 [ 17.506949] NET: Registered protocol family 31 [ 17.508431] Bluetooth: HCI device and connection manager initialized [ 17.510762] Bluetooth: HCI socket layer initialized [ 17.512365] Bluetooth: L2CAP socket layer initialized [ 17.514572] Bluetooth: SCO socket layer initialized [ 17.536452] Bluetooth: HCI UART driver ver 2.3 [ 17.537979] Bluetooth: HCI UART protocol H4 registered [ 17.539482] Bluetooth: HCI UART protocol LL registered [ 17.540950] Bluetooth: HCI UART protocol ATH3K registered [ 17.542467] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 17.544983] Bluetooth: HCI UART protocol Intel registered [ 17.548795] Bluetooth: HCI UART protocol BCM registered [ 17.550324] Bluetooth: HCI UART protocol QCA registered [ 26.512941] ======== PULL WL_REG_ON(-1) HIGH! ======== [ 26.516635] [WLAN_RFKILL]: rockchip_wifi_power: 1 [ 26.520259] [WLAN_RFKILL]: wifi turn on power. -1 [ 26.825917] sdio_reset_comm(): [ 26.857990] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 26.881466] mmc_host mmc2: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0) [ 26.943715] mmc2: queuing unknown CIS tuple 0x80 (2 bytes) [ 26.953413] mmc2: queuing unknown CIS tuple 0x80 (3 bytes) [ 26.963010] mmc2: queuing unknown CIS tuple 0x80 (3 bytes) [ 26.977673] mmc2: queuing unknown CIS tuple 0x80 (7 bytes) [ 27.192254] mmc_host mmc2: Bus speed (slot 0) = 150000000Hz (slot req 150000000Hz, actual 150000000HZ div = 0) [ 27.321877] dwmmc_rockchip fe320000.dwmmc: Unexpected command timeout, state 3 [ 27.430050] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00 [ 27.431980] mmcblk0: error -110 transferring data, sector 2327936, nr 256, cmd response 0x900, card status 0xb00 [ 27.434110] rockchip-iodomain ff770000.syscon:io-domains: Setting to 3000000 done [ 27.436151] rockchip-iodomain ff770000.syscon:io-domains: Setting to 3000000 done [ 27.455898] rockchip-iodomain ff770000.syscon:io-domains: Setting to 3000000 done [ 27.457668] rockchip-iodomain ff770000.syscon:io-domains: Setting to 3000000 done [ 27.477983] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) ... or hit CPU lockup detection: [ 20.654689] systemd-journald[598]: Received request to flush runtime journal from PID 1 [ 21.520340] nr_pdflush_threads exported in /proc is scheduled for removal [ 21.542172] EXT4-fs (mmcblk0p1): resizing filesystem from 416768 to 7709728 blocks [ 36.125742] Watchdog detected hard LOCKUP on cpu 4 [ 36.126296] ------------[ cut here ]------------ [ 36.135788] WARNING: at kernel/watchdog.c:352 [ 36.140570] Modules linked in: zstd zstd_compress zlib lzo midgard_kbase zram uio_pdrv_genirq uio ip_tables x_tables [ 36.146211] [ 36.150803] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.4.213-rk3399 #2 [ 36.155895] Hardware name: FriendlyElec NanoPi M4 (DT) [ 36.155900] task: ffffffc07d6d2a00 task.stack: ffffffc07d6e0000 [ 36.155916] PC is at watchdog_timer_fn+0x180/0x2c8 [ 36.155920] LR is at watchdog_timer_fn+0x180/0x2c8 [ 36.155923] pc : [<ffffff800815b7c0>] lr : [<ffffff800815b7c0>] pstate: 600001c5 [ 36.155925] sp : ffffffc07ff24e60 [ 36.155930] x29: ffffffc07ff24e60 x28: 0000000000000004 [ 36.155934] x27: ffffff80092f88a0 x26: ffffffc07ff27250 [ 36.155938] x25: ffffffc07d6e3da0 x24: 0000000000000000 [ 36.155942] x23: ffffff80092f7000 x22: 000000000000001d [ 36.155946] x21: ffffff80092f7898 x20: ffffff80092ca2b0 [ 36.155950] x19: ffffff80092ca228 x18: 0000000000000000 [ 36.155954] x17: 0000000000000000 x16: 0000000000000000 [ 36.155958] x15: 000000000001eb2e x14: ffffffc07a652800 [ 36.155962] x13: ffffffc07a65a360 x12: 00000000ffffffff [ 36.155966] x11: 0000000000000008 x10: ffffff8008c4cc20 [ 36.155970] x9 : 0000000000aaaaaa x8 : ffffff8008451ee8 [ 36.155974] x7 : ffffff8009356c20 x6 : 0000000000000035 [ 36.155978] x5 : 0000000000000000 x4 : 0000000000000000 [ 36.155982] x3 : 0000000000000034 x2 : 0000004076c5d000 [ 36.155986] x1 : 0000000000000003 x0 : 0000000000000026 ... [ 36.157530] ---[ end trace 4f115b692efe9dce ]--- [ 36.157533] Call trace: [ 36.157539] Exception stack(0xffffffc07ff24c80 to 0xffffffc07ff24db0) [ 36.157545] 4c80: ffffff80092ca228 0000008000000000 ffffffc07ff24e60 ffffff800815b7c0 [ 36.157549] 4ca0: 00000000600001c5 0000000008111990 ffffff8000000000 0000000000000026 [ 36.157554] 4cc0: ffffffc07ff24d60 ffffff8008111adc ffffffc07ff24de0 ffffff8008e3c58d [ 36.157558] 4ce0: ffffff80092f7898 000000000000001d ffffff80092f7000 0000000000000000 [ 36.157563] 4d00: ffffffc07d6e3da0 ffffffc07ff27250 ffffff80092f88a0 0000000000000004 [ 36.157567] 4d20: 0000000000000000 00000000000001c0 0000000000000026 0000000000000003 [ 36.157571] 4d40: 0000004076c5d000 0000000000000034 0000000000000000 0000000000000000 [ 36.157576] 4d60: 0000000000000035 ffffff8009356c20 ffffff8008451ee8 0000000000aaaaaa [ 36.157580] 4d80: ffffff8008c4cc20 0000000000000008 00000000ffffffff ffffffc07a65a360 [ 36.157584] 4da0: ffffffc07a652800 000000000001eb2e [ 36.157590] [<ffffff800815b7c0>] watchdog_timer_fn+0x180/0x2c8 [ 36.157599] [<ffffff8008126544>] __hrtimer_run_queues+0x1bc/0x284 [ 36.157604] [<ffffff8008126b30>] hrtimer_interrupt+0xac/0x1bc [ 36.157611] [<ffffff80081327b0>] tick_receive_broadcast+0x30/0x4c [ 36.157618] [<ffffff800808c3f8>] handle_IPI+0x1f0/0x258 [ 36.157623] [<ffffff8008080f30>] gic_handle_irq+0x17c/0x180 [ 36.157626] Exception stack(0xffffffc07d6e3da0 to 0xffffffc07d6e3ed0) [ 36.157631] 3da0: 0000000000000000 0000000000000003 0000004076c5d000 0000000000000003 [ 36.157635] 3dc0: 0000000000000008 0000000000000000 0000000000001910 0000000000000003 [ 36.157639] 3de0: 00000032b5593519 ffffff8008081800 0000000000001000 0000000000000000 [ 36.157644] 3e00: 0000000034d5d91d 0000004076c5d000 ffffffc07d6d2a00 0000000000000000 [ 36.157648] 3e20: 0000000000000000 0000000000000000 0000000030d00800 0000000864e152a3 [ 36.157652] 3e40: ffffffc07a4a5800 0000000000000060 0000000000000002 ffffff800941b4f8 [ 36.157657] 3e60: 0000000000000001 0000000864a49116 ffffff80093d4660 0000000002bc8244 [ 36.157661] 3e80: 0000000000000000 ffffffc07d6e3ed0 ffffff8008958df0 ffffffc07d6e3ed0 [ 36.157666] 3ea0: ffffff8008958df4 0000000060000145 ffffffc07d6e3ed0 ffffff8008958df0 [ 36.157669] 3ec0: ffffffffffffffff ffffffc07a4a5800 [ 36.157674] [<ffffff80080827b4>] el1_irq+0xb4/0x140 [ 36.157681] [<ffffff8008958df4>] cpuidle_enter_state+0x1f8/0x25c [ 36.157685] [<ffffff8008958ecc>] cpuidle_enter+0x34/0x44 [ 36.157693] [<ffffff80080ff2a4>] call_cpuidle+0x70/0x78 [ 36.157699] [<ffffff80080ff554>] cpu_startup_entry+0x2a8/0x2b8 [ 36.157703] [<ffffff800808be58>] secondary_start_kernel+0x124/0x140 [ 36.157707] [<0000000002bc8188>] 0x2bc8188 Armbian_21.02.1_Nanopim4_buster_legacy_4.4.213.img.xz gets this panic: [ 8.348200] mali ff9a0000.gpu: Probed as mali0 [ 8.373865] zram0: detected capacity change from 0 to 1009078272 [ 8.407368] Adding 985424k swap on /dev/zram0. Priority:5 extents:1 across:985424k SS [ 8.428103] Unable to handle kernel paging request at virtual address f2228e88 [ 8.430338] pgd = ffffffc07aed5000 [ 8.432092] [f2228e88] *pgd=0000000000000000, *pud=0000000000000000 [ 8.434133] Internal error: Oops: 96000005 [#1] SMP [ 8.436003] Modules linked in: lzo midgard_kbase zram uio_pdrv_genirq uio ip_tables x_tables [ 8.438296] CPU: 5 PID: 461 Comm: cached_setup_fo Not tainted 4.4.213-rk3399 #14 [ 8.440396] Hardware name: FriendlyElec NanoPi M4 (DT) [ 8.442289] task: ffffffc07ab12a00 task.stack: ffffffc07b5a0000 [ 8.444258] PC is at kmem_cache_alloc+0x98/0x1ec [ 8.446091] LR is at kmem_cache_alloc+0x40/0x1ec [ 8.447900] pc : [<ffffff80081e3b90>] lr : [<ffffff80081e3b38>] pstate: 60000145 [ 8.449980] sp : ffffffc07b5a3cd0 [ 8.451694] x29: ffffffc07b5a3cd0 x28: ffffffc07b7bf160 [ 8.453634] x27: 0000000000100000 x26: ffffffc07b57bf20 [ 8.455559] x25: ffffffc000000001 x24: ffffff80094c7000 [ 8.457461] x23: ffffff80080b8f78 x22: 00000000024000c0 [ 8.459353] x21: ffffffc07b5a3e10 x20: 00000000024000c0 [ 8.461213] x19: ffffffc07b5a3e10 x18: 000000000000001f [ 8.463037] x17: 0000007f88f37670 x16: ffffff80080b9c78 [ 8.464844] x15: 0000000000000008 x14: ffffffc06bb9add0 [ 8.466646] x13: 000000000000015b x12: 0000000000000000 [ 8.468423] x11: ffffff80092d0eb8 x10: ffffff80092d0ec8 [ 8.470179] x9 : 0000004076c85000 x8 : 00000000fffffffa [ 8.471932] x7 : ffffffc07ff55ec8 x6 : 00000000000000fa [ 8.473675] x5 : fffffffffffffffb x4 : 000000000000002c [ 8.475404] x3 : ffffff80092f6300 x2 : 0000004076c85000 [ 8.477140] x1 : ffffffc07b5a3cd0 x0 : ffffffc07b5a3e88 [ 8.478866] [ 8.478866] PC: 0xffffff80081e3b10: ... [ 8.820000] Process cached_setup_fo (pid: 461, stack limit = 0xffffffc07b5a0000) [ 8.821631] Stack: (0xffffffc07b5a3cd0 to 0xffffffc07b5a4000) [ 8.823146] 3cc0: ffffffc07b5a3d20 ffffff80080b8f78 [ 8.824884] 3ce0: ffffffc065a29c00 0000000001200011 ffffffc065a2a200 0000000000000000 [ 8.826648] 3d00: ffffffc07b5a3cf0 ffffff8009358118 ffffffc000000001 0000000000000000 [ 8.828425] 3d20: ffffffc07b5a3e10 ffffff80080b98d8 0000000000000000 0000000000000000 [ 8.830178] 3d40: 0000000001200011 0000000000000000 0000000000000000 0000007f8902cc90 [ 8.831942] 3d60: 000000000000011d 00000000000000dc ffffff8008bd2000 ffffffc07ab12a00 [ 8.833690] 3d80: 0000000000000140 ffffffc07b7bf160 0000000000000000 ffffffc065a2a170 [ 8.835455] 3da0: ffffffc07b7bf170 ffffffc07b7bf188 ffffffc07b7bf180 0000000000000000 [ 8.837241] 3dc0: ffffffc06ba90800 ffffffc06ba91e80 ffffffc0663ea288 0000000000000000 [ 8.839039] 3de0: 0000000000000000 0000000000000000 ffffffc065a2a400 ffffffc0663ea260 [ 8.840859] 3e00: 0000000000000000 0000000000000000 ffffffc07b5a3e80 ffffff80080b9cc4 [ 8.842687] 3e20: 0000000001200011 0000000000000000 0000000000000000 0000007f8902cc90 [ 8.844532] 3e40: 0000000000000000 0000000000000015 0000000000000000 0000000000000000 [ 8.846385] 3e60: 0000007f8902cc90 0000007f8902cbc0 ffffffc07b5a3e90 ffffff8008086b14 [ 8.848261] 3e80: 0000000000000000 ffffff8008082f8c 0000000000000800 0000004076c85000 [ 8.850131] 3ea0: ffffffffffffffff 0000007f88f376cc 0000000060000000 0000007f88f376cc [ 8.852013] 3ec0: 0000000001200011 0000000000000000 0000000000000000 0000000000000000 [ 8.853879] 3ee0: 0000007f8902cc90 0000007f8902cbc0 00008088888b98d5 fefefefefeff736d [ 8.855741] 3f00: 00000000000000dc 0000000000000032 0101010101010101 0000000000000010 [ 8.857614] 3f20: 0101010101010101 0000000000000000 0000000000000000 0000000000000008 [ 8.859476] 3f40: 000000556de7daf0 0000007f88f37670 000000000000001f 0000000000000000 [ 8.861330] 3f60: 0000007f8902cac0 0000007f8902d2c0 0000000000000000 0000000000000000 [ 8.863168] 3f80: 00000055988b0440 000000556de7e8e8 000000556de7d590 000000556de68110 [ 8.865010] 3fa0: 0000000000000002 0000007fdd983730 0000007f88f376a4 0000007fdd983730 [ 8.866852] 3fc0: 0000007f88f376cc 0000000060000000 0000000001200011 00000000000000dc [ 8.868681] 3fe0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 8.870511] Call trace: [ 8.871843] Exception stack(0xffffffc07b5a3b00 to 0xffffffc07b5a3c30) [ 8.873543] 3b00: ffffffc07b5a3e10 0000008000000000 ffffffc07b5a3cd0 ffffff80081e3b90 [ 8.875387] 3b20: ffffffc07b7ed240 0000000000000000 ffffffc06ba91e00 ffffffc07b5dbff0 [ 8.877224] 3b40: ffffffc07b57b370 ffffffc07b791240 0000000000000000 000000000005c000 [ 8.879060] 3b60: ffffffc07b5a3b80 ffffff80081e3b38 ffffffbdc1edef80 ffffffc000400000 [ 8.880898] 3b80: ffffffc07b5a3bd0 ffffff80081c18d4 ffffffbdc1edef80 0000000000000000 [ 8.882728] 3ba0: ffffffc07b5a3e88 ffffffc07b5a3cd0 0000004076c85000 ffffff80092f6300 [ 8.884561] 3bc0: 000000000000002c fffffffffffffffb 00000000000000fa ffffffc07ff55ec8 [ 8.886384] 3be0: 00000000fffffffa 0000004076c85000 ffffff80092d0ec8 ffffff80092d0eb8 [ 8.888220] 3c00: 0000000000000000 000000000000015b ffffffc06bb9add0 0000000000000008 [ 8.890043] 3c20: ffffff80080b9c78 0000007f88f37670 [ 8.891594] [<ffffff80081e3b90>] kmem_cache_alloc+0x98/0x1ec [ 8.893226] [<ffffff80080b8f78>] copy_process.isra.5+0xaf0/0x1308 [ 8.894897] [<ffffff80080b98d8>] _do_fork+0x84/0x304 [ 8.896460] [<ffffff80080b9cc4>] SyS_clone+0x4c/0x60 [ 8.898017] [<ffffff8008082f8c>] __sys_trace_return+0x0/0x4 [ 8.899636] Code: f9400260 910003e1 d538d082 91002000 (f8626802) [ 8.901298] ---[ end trace ef8d2422557a597b ]--- Armbian_20.02.7_Nanopim4_buster_legacy_4.4.213.img: [ 7.528945] BUG: spinlock cpu recursion on CPU#4, systemd-udevd/361 [ 7.528953] lock: 0xffffff80093a5870, .magic: dead4ead, .owner: systemd-udevd/353, .owner_cpu: 4 [ 7.528958] CPU: 4 PID: 361 Comm: systemd-udevd Not tainted 4.4.213-rk3399 #23 [ 7.528960] Hardware name: FriendlyElec NanoPi M4 (DT) [ 7.528963] Call trace: [ 7.528978] [<ffffff800808803c>] dump_backtrace+0x0/0x21c [ 7.528982] [<ffffff800808827c>] show_stack+0x24/0x30 [ 7.528989] [<ffffff80084da768>] dump_stack+0xa4/0xcc [ 7.529005] [<ffffff800818d528>] spin_dump+0x84/0xa4 [ 7.529011] [<ffffff800810519c>] spin_bug+0x30/0x3c [ 7.529013] [<ffffff800810529c>] do_raw_spin_lock+0x90/0x164 [ 7.529019] [<ffffff8008ba53c0>] _raw_spin_lock_irqsave+0x28/0x38 [ 7.529024] [<ffffff8008977e18>] of_find_property+0x38/0x74 [ 7.529026] [<ffffff8008977ec8>] of_get_property+0x34/0x4c [ 7.529029] [<ffffff800897a324>] of_device_uevent+0xb0/0x19c [ 7.529035] [<ffffff800863b7e4>] dev_uevent+0x14c/0x288 [ 7.529037] [<ffffff8008639430>] uevent_show+0x90/0x118 [ 7.529039] [<ffffff8008639094>] dev_attr_show+0x3c/0x74 [ 7.529045] [<ffffff800826d2e0>] sysfs_kf_seq_show+0xa8/0x108 [ 7.529047] [<ffffff800826bb10>] kernfs_seq_show+0x44/0x50 [ 7.529052] [<ffffff8008215698>] seq_read+0x114/0x3a4 [ 7.529054] [<ffffff800826c4b0>] kernfs_fop_read+0x54/0x178 [ 7.529058] [<ffffff80081f2fc0>] __vfs_read+0x48/0xe8 [ 7.529061] [<ffffff80081f388c>] vfs_read+0x88/0x138 [ 7.529063] [<ffffff80081f4378>] SyS_read+0x5c/0xb0 [ 7.529067] [<ffffff8008082f8c>] __sys_trace_return+0x0/0x4 [ 7.536996] systemd[1]: Found device /dev/ttyFIQ0. and: [ 14.619236] mmcblk0: error -115 sending stop command, original cmd response 0x900, card status 0xb00 [ 14.621357] mmcblk0: error -110 transferring data, sector 538200, nr 144, cmd response 0x900, card status 0xb00 [ 14.623597] rockchip-iodomain ff770000.syscon:io-domains: Setting to 3000000 done [ 14.625751] rockchip-iodomain ff770000.syscon:io-domains: Setting to 3000000 done [ 14.645134] rockchip-iodomain ff770000.syscon:io-domains: Setting to 3000000 done [ 14.647081] rockchip-iodomain ff770000.syscon:io-domains: Setting to 3000000 done [ 14.663105] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 14.909334] rockchip-iodomain ff770000.syscon:io-domains: Setting to 3000000 done [ 14.911586] rockchip-iodomain ff770000.syscon:io-domains: Setting to 1800000 done [ 56.999390] mmc0: tried to reset card [ 57.000953] mmcblk0: retrying using single block read [ 99.111870] mmcblk0: error -110 transferring data, sector 538200, nr 144, cmd response 0x900, card status 0x0 [ 99.114032] blk_update_request: I/O error, dev mmcblk0, sector 538200 Armbian_5.98_Nanopim4_Debian_buster_default_4.4.192.img does not work any better, and u-boot even identifies the board as "NanoPC-T4" :/ Starting to wonder if this board ever worked ?
  13. I am trying to get a camera going on the Nanopi-m4 (I have tried another board as well with similar results). The sensor is setup in the device tree correctly and gets probed on boot. However there are some issues when loading rkisp1. [ 5.645127] rkisp1 ff920000.isp1: Adding to iommu group 5 [ 5.645695] rkisp1 ff920000.isp1: Failed to get clk 'clk_isp': -2 [ 5.645814] rkisp1: probe of ff920000.isp1 failed with error -2 My understanding with Failed to get is because it is either being used by another resource or was not defined correctly. Below are my entries in the device tree for the isp. I am using `isp1` in this case, I am assuming as well that `ispl` is locked to `csi1` where my camera is located. isp1: isp1@ff920000 { compatible = "rockchip,rk3399-cif-isp"; reg = <0x0 0xff920000 0x0 0x4000>; interrupts = <GIC_SPI 44 IRQ_TYPE_LEVEL_HIGH 0>; clocks = <&cru SCLK_ISP1>, <&cru ACLK_ISP1_WRAPPER>, <&cru HCLK_ISP1_WRAPPER>; clock-names = "isp", "aclk", "hclk"; iommus = <&isp1_mmu>; phys = <&mipi_dsi1>; phy-names = "dphy"; power-domains = <&power RK3399_PD_ISP1>; status = "okay"; ports { #address-cells = <1>; #size-cells = <0>; port@0 { reg = <0>; #address-cells = <1>; #size-cells = <0>; }; }; }; isp1_mmu: iommu@ff924000 { compatible = "rockchip,iommu"; reg = <0x0 0xff924000 0x0 0x100>, <0x0 0xff925000 0x0 0x100>; interrupts = <GIC_SPI 44 IRQ_TYPE_LEVEL_HIGH 0>; interrupt-names = "isp1_mmu"; clocks = <&cru ACLK_ISP1_WRAPPER>, <&cru HCLK_ISP1_WRAPPER>; clock-names = "aclk", "iface"; #iommu-cells = <0>; power-domains = <&power RK3399_PD_ISP1>; rockchip,disable-mmu-reset; }; &isp1_mmu { status = "okay"; }; &isp1 { status = "okay"; ports { port@0 { mipi_in_ucam1a: endpoint@0 { reg = <0>; remote-endpoint = <&ucam_out1a>; data-lanes = <1 2>; }; }; }; }; Currently I am disabling unused devices in order to make sure that this isn't related to some conflict. Any help or references would be great. I am still in the process of getting an understanding of rkisp.
  14. I'm getting burst "VOP vblank IRQ stuck for 10 ms" error messages in dmesg and wondering what it means and if anything to improve/fix. I'm using Nanopi m4 $ uname -a Linux nanopim4 5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux kern :err : [Sat Mar 13 22:20:13 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:04 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:04 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:06 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:06 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:09 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:11 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:12 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:12 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:18 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms kern :err : [Sat Mar 13 22:21:21 2021] rockchip-vop ff8f0000.vop: [drm:vop_crtc_atomic_flush [rockchipdrm]] *ERROR* VOP vblank IRQ stuck for 10 ms
  15. Hi all, This has confused me! I have an old copy Armbian_20.02.7_Nanopim4_buster_current_5.4.28_desktop.7z which works fine. Any SD cards I put it on using Balena Etcher works. Any of the latest versions simply won't boot. The only difference appears to be the XZ file format. I extracted one of the later ones using 7Zip and then Etcher to flash and as expected it mad no difference at all. Has something been done to the V1 firmware from the V2 that doesn't work or firmwares containing the wrong naming etc? Help!
  16. Hi, Just bought the SATA HAT and before I get started, I see in the OS Support that Lubuntu and Friendly Core is supported. Does this Exclude Armbian ? I'm not overwhelmed with FriendlyCore . Thank sin advance
  17. Board: Nanopi M4 with 4GB OS: Armbian_5.65_Nanopim4_Debian_stretch_default_4.4.162 Boot from SD, rootfs on an external HDD 8TB (WD MyBook). I attached another external HDD (Toshiba 2TB). I have been trying rsync -avh from the Toshiba one to the main MyBook one. It ran for under a minute before reporting files were vanished and exited with errors. It appeared the / is gone. nothing return from ls. Hard-reboot, fsck ran, everything's back to normal. I've been trying rsync with nice -n 20 as well as --bwlimit 10, 1MB. Nothing helped. stress test the board for 10 minutes, (stress -c 4 -m 4 -d 4 -i 4). All looks good. Any help's appreciated. Thanks, Jerry
  18. Hi, I was trying to load below Armbian images into NanoPi M4 (just M4, neither M4B nor M4V2). They are able to be loaded in the first place, but when I reboot the board by typing "reboot" command in the terminal, I can only see black screen showing on the monitor, no led flashing on the board even, and the board never boots up again. If I unplug the power cable and plug back again, it boots as expected. Is there any way I can reboot the board remotely? Armbian_20.08.1_Nanopim4_buster_current_5.8.6_desktop.img.xz Armbian_20.08.1_Nanopim4_buster_current_5.8.6.img.xz Armbian_20.08.1_Nanopim4_bionic_current_5.8.6.img.xz Armbian_20.08.1_Nanopim4_focal_current_5.8.6.img.xz As these are in the recommended image list for M4, do we have images with kernel version greater than 5 you guys would recommend? Thanks, Jason
  19. Hi, I noticed that on my board I didn't have notification with MOTD when updates were available and I think that I've found the culprit: In the file /usr/lib/armbian/armbian-apt-updates of the package linux-buster-root-legacy-nanopim4_20.08.17_arm64.deb, this line stop the script to go further : # give up if packages are broken [[ ! $(dpkg -l | grep ^..r) ]] && exit 0 If I remove the ! then it works (because the script, in fact, gives up if packages are not broken )
  20. I have a serious problem as I mentioned in a title Currently I'm using Armbian on my NanoPi M4 and very satisfied its functionality But when I try to use usb3 device (especially camera from ZWO campany, ZWO ASI 178) with it, it doesn't recognize it as USB3 device but USB2 by checking the data transfer speed with "lsusb -t" Then, once I unplug the cable and plug it to the pi again, that device is recognized as USB3 and the data transfer speed becomes much higher. I need to get USB3's fast data transfer as soon as the board gets booted, without unplugging cables since now it's not that easy to access to the board and cable. I tried usb reset command like echo -n "1-2.1" > /sys/bus/usb/drivers/usb/unbind but this doesn't change anything I suppose somehow I can simulate this unplugging processing with some commands and get USB3 connection. Hope anyone knows about this issue Thank you
  21. Hi, I'm using NanoPi M4 $ uname -a Linux nanopim4 4.4.213-rk3399 #3 SMP Mon Oct 5 15:53:54 CEST 2020 aarch64 aarch64 aarch64 GNU/Linux and wondering if I can upgrade the linux kernel to 5.8.x without reinstalling other things. I tried armbian-config -> System -> Other All available options are those 4.4.213-rk3399 with different Armbian versions 20.08.x. I'm currently on 20.08.9 Appreciated any step, pointer Thank you
  22. I am testing a Nano-Pi M4 with 4GB of RAM, with the heat sink and fans installed ARMBIAN 5.65 stable Ubuntu 18.04.1 LTS 4.4.162-rk3399, docker CE and BOINC / seti@home, installed. I am using 7 Raspberry-Pi 3B+ boards as nodes. I would like to implement and test boinc-client-docker, (https://github.com/BOINC/boinc-client-docker). I am new at this and running into overheating issues, (temps over 70C as reported by htop), when all 6 cores are maxed out at 100%. I can keep the board slightly below 70C if I add multiple fans pointed at the heat sink, however I would like a better solution. I was wondering if setting the max frequency of the cores to a slightly lower level would resolve this issue. 2x Cortex-A72 at up to 2.0GHz, 4x Cortex-A53 @ up to 1.5GHz cores 1 through 4 will run at 1.49x and cores 5 & 6 will run at 1.99x they all idle at 600 MHz with a resting temp of 32C Would setting thee max frequencies to 1.48 and 1.8 help resolve this issue? What would be the best method of testing this? The results of cat /etc/default/cpufrequtils # WARNING: this file will be replaced on board support package (linux-root-...) upgrade ENABLE=true MIN_SPEED=600000 MAX_SPEED=2016000 GOVERNOR=ondemand
  23. Hi, I would like to know if it is possible to switch from the current branch to the legacy one as I've read that the board will be much more stable with the older kernel ? I've installed my NanopiM4 last march, and I've experienced some random freezes of my board after some time (can take weeks). It seems that one of my solutions would be to use the legacy kernel as it is much more stable - information I got by reading the forums (something I haven't done before because I'm stupid and was in a hurry...). Is it possible to downgrade only the kernel at all ? Here are the packages that (I think) I have to replace : linux-buster-root-current-nanopim4/buster,now 20.08.3 arm64 [installed] linux-dtb-current-rockchip64/buster,now 20.08.3 arm64 [installed] linux-headers-current-rockchip64/buster,now 20.08.3 arm64 [installed] linux-image-current-rockchip64/buster,now 20.08.3 arm64 [installed] linux-u-boot-nanopim4-current/buster,now 20.08.1 arm64 [installed] With those packages, then : linux-buster-root-legacy-nanopim4 - armbian tweaks for buster on nanopim4 (legacy branch) linux-dtb-legacy-rockchip64 - linux dtb, version 4.4.213-rockchip64 linux-headers-legacy-rockchip64 - linux kernel headers for 4.4.213-rockchip64 on arm64 linux-image-legacy-rockchip64 - linux kernel, version 4.4.213-rockchip64 linux-u-boot-nanopim4-legacy - uboot loader 2020.07 Will that be enough or are more packages needed without screwing my install ? Should I use apt-get or do I have to use the armbian-config tool instead ? Is there an order to respect ?
  24. Have anyone tried to use USB connected monitor with NanoPi? I'm thinking about buying one but not sure it can work with it or, if some change has to be done to NanoPi , I would like to know about it.
  25. Hi, I'm currently working to enable SPI on NanoPi M4 but it is not working... I have edited main DT to the following one and now /dev/spidev0.0 appears. But when I checked spi with this tool:https://github.com/torvalds/linux/blob/master/tools/spi/spidev_test.c I only got the result below and no matrix appears... spi mode: 0x0 bits per word: 8 max speed: 500000 Hz (500 KHz) Here is what dmesg | grep spi returns I have checked the output from the proper GPIO with oscilloscope but found nothing. almost spent couple weeks on this Anyone had the same issue or knows what to do here?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines