Jump to content

Search the Community

Showing results for tags 'rockpi-4a'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

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. Hello everyone, I was going to purchase Rock Pi 4 model B+ (with WiFi/BT and eMMC chip). I see that Rock Pi 4 family is supported by Armbian (https://www.armbian.com/rockpi4/), however, there is no mention of models A+ and B+. There are just A, B and C+. Could you please confirm/refute that Rock Pi 4 B+ is supported by Armbian and point me to the image for that model?
  2. I tried to install Armbian_22.11.0-trunk_Rockpi-4b_bullseye_current_5.15.76_minimal.img.xz from https://github.com/radxa-build/rock-pi-4b/releases/tag/20221101-0235 After first reboot main partition goes readonly. Checking disk show free cluster records mismatch. It is not SD-card issue, because Ubuntu Server on same SD-card working perfectly.
  3. Hello all, I am trying to interface with the MCP2515 on SPI2 of the RockPi4B on Armbian 22.08.6 Bullseye with Linux 5.15.74-rockchip64 and encountering some issues. The rockpi4B pins that I am using to connect to the MCP2515 INT - GPIO2_A7 MOSI - GPIO2_B2 MISO - GPIO2_B1 CLK - GPIO2_B3 CS - GPIO2_B4 When using the overlay file that I have shown below, the output for "dmesg | grep mcp": [ 6.662536] rockchip-pinctrl pinctrl: unable to find group for node mcp2515_int_pin I have been able to get the MCP2515 to initialize successfully, but only if I comment out the pinctrl-0 reference to the mcp2515_int_pin in the overlay. Doing this I can bring up the device but I am only able to send/receive a few messages before candump shows it's not transmitting any messages until I bring down and up the can0 device where it will do the same thing. The interesting thing is, when the device doesn't communicate I can still see that the can0 device is still in the "Error-Active" mode, so theoretically I should still be able to interface with it. So, I am led to believe the issue I am encountering is due to that comment line to pinctrl-0 in the overlay. Just not sure of the solution to this. I have looked about just about every forum that makes reference to the MCP2515 and have not found any promising solutions. I have tried changing the target on fragment@0 to <&gpio>, <&gpio2>, etc. Here is a look at the DTS overlay I am using for the MCP2515: //This devicetree overlay is used for RS485 CAN HAT. /dts-v1/; /plugin/; / { compatible = "rockchip,rockpi","rockchip,rk3399", "rockchip,rk3399-pinctrl"; fragment@0 { target = <&pinctrl>; __overlay__ { mcp2515_int_pin: mcp2515_int_pin { rockchip,pins = <2 7 0 &pcfg_pull_none>; }; }; }; fragment@1 { target-path = "/"; __overlay__ { can_mcp2515_osc: can-mcp2515-osc { compatible = "fixed-clock"; clock-frequency = <16000000>; #clock-cells = <0>; }; }; }; fragment@2 { target = <&spi2>; __overlay__ { status = "okay"; max-freq = <10000000>; #address-cells = <1>; #size-cells = <0>; can_mcp2515: can-mcp2515@0 { status = "okay"; compatible = "microchip,mcp2515"; reg = <0>; interrupt-parent = <&gpio2>; interrupts = <7 2 8>; spi-max-frequency = <10000000>; clocks = <&can_mcp2515_osc>; vdd-supply = <&vcc3v3_sys>; xceiver-supply = <&vcc3v3_sys>; pinctrl-names = "default"; pinctrl-0 = <&mcp2515_int_pin>; }; }; }; }; And my armbianEnv.txt: verbosity=1 bootlogo=false overlay_prefix=rockchip fdtfile=rockchip/rk3399-rock-pi-4b.dtb rootdev=UUID=fa2cbc7c-56d1-448b-9ab3-fe864e21fbc5 rootfstype=ext4 overlays=spi-spidev param_spidev_spi_bus=1 user_overlays=spi1-mcp2515-can0-overlay usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Here's a link to my armbianmonitor -u: https://paste.armbian.com/azameworos I would like to mention I not very skilled with Linux based devices so please bear with me. Any help would be greatly appreciated! Best, Austin
  4. I can use echo 0 >/sys/class/leds/status/brightness to turn off the status led (blinking blue one, but I was to turn off the bright ass green one. I assume this is mmc1::, but I cannot turn it off.
  5. Is there a method to boot with BSP kernel (the 4.4 kernel supplied by Rockchip/Radxa) on an existing install (jammy) to compare power usage to mainline kernel (5.15.y current or even 5.19.y rolling)? I tried using the switch kernel support in armbian-config, but the linux-image-legacy-rockchip64 4.4.213-rockchip64 just hung during early boot and had to recover to linux-image-current-rockchip64 5.15.69 . P.S. This is related to my question on the Radxa forums about reducing Rock Pi 4 B+ power usage.
  6. Hello. I am trying to have the 1-wire working on Rockpi4B+ on pin GPIO4_D6 (= number 158). I have this /boot/armbianEnv.txt: verbosity=1 bootlogo=true overlay_prefix=rockchip fdtfile=rockchip/rk3399-rock-pi-4b.dtb rootdev=UUID=aa1f4e9a-bad9-4760-87c5-511247ef7227 rootfstype=ext4 overlays=w1-gpio param_w1_pin=GPIO4_D6 param_w1_pin_int_pullup=1 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u but when I check on my board: sudo cat /sys/kernel/debug/gpio GPIOs 0-31, platform/pinctrl, gpio0: gpio-4 ( |bt_default_wake_host) in lo gpio-9 ( |bt_default_reset ) out hi gpio-10 ( |reset ) out hi GPIOs 32-63, platform/pinctrl, gpio1: gpio-35 ( |vcc5v0_otg ) out hi gpio-36 ( |w1 ) in lo gpio-46 ( |vsel ) out lo gpio-49 ( |vsel ) out lo GPIOs 64-95, platform/pinctrl, gpio2: gpio-83 ( |bt_default_rts ) out hi gpio-90 ( |vcc3v3_pcie ) out hi gpio-91 ( |bt_default_wake ) out hi GPIOs 96-127, platform/pinctrl, gpio3: gpio-124 ( |? ) out lo gpio-125 ( |? ) out lo GPIOs 128-159, platform/pinctrl, gpio4: gpio-153 ( |vcc5v0_host ) out hi and if I check the dtb file: It appears than the w1-gpio is connected to GPIO1_A5 (= number 36) I guess something went wrong in the configuration of 1-wire pin, but what ?
  7. Hello, I have been using Armbian OS on Rock Pi 4B. Full system is on NVME, not using SD card, and there is no eMMC chip on the board. During usage, I needed to shut it down improperly: by removing power cable, not through sudo shutdown now In the end I have following message during boot: Also, here is contents of dev folder: I was wondering if it is possible to fix this error. If not, I will reinstall with new image. Just spent much time on setting the environment, don't want to redo this all I would appreciate any help.
  8. System logs: http://ix.io/4bd2 I have been using Armbian OS with Rock Pi 4B. The problem with Rock Pi 4B is that it doesn't have a power-on/off button. So, for closed systems with no keyboard/UI, there is no way to shutdown/start the system properly. Only option is to disconnect the power cable, which has corrupted my OS few times(by the way didn't happen on Debian). I implemented shutdown function through MRAA library and by attaching a button to 40-pin GPIO header. But with this approach, system can go to sleep, but cannot wake-up through button because my software is not running. As I have understood, the best approach to have a proper button functionality is to put Linux into sleep instead of shutdown, and to modify the device tree so that a GPIO would have a wake-up functionality. Unfortunately, I don't have expertise in device trees. On RockPro64, another device that uses RK3399, the device has a power button. So, I tried to copy its dts implementation into rock pi 4b dts, but unfortunately it didn't work. Here is the link showing the modifications of rock-pi-4b dts: https://github.com/RafigRzayev/RockPi4B_wake_button_dts/commit/046c5b81c39756e8cd0e8b69a243539e01429c39 I also opened an issue on Radxa forum, but no success there yet. Could someone help with this topic?
  9. Hi, i'm trying to compile an u-boot for my Rock-PI 4B. I wanted to apply a userpatch, that disables the uart debug console in u-boot. I seem to have an issue when using the Rock-PI together with a weather-sensor via RS485-Hat. Here is my patch: diff --git a/configs/rock-pi-4-rk3399_defconfig b/configs/rock-pi-4-rk3399_defconfig index be07b16bae..63d04ced6e 100644 --- a/configs/rock-pi-4-rk3399_defconfig +++ b/configs/rock-pi-4-rk3399_defconfig @@ -13,7 +13,7 @@ CONFIG_DEBUG_UART_CLOCK=24000000 CONFIG_SPL_SPI_FLASH_SUPPORT=y CONFIG_SPL_SPI=y -CONFIG_DEBUG_UART=y +CONFIG_DEBUG_UART=n CONFIG_SYS_LOAD_ADDR=0x800800 # CONFIG_ANDROID_BOOT_IMAGE is not set CONFIG_DEFAULT_FDT_FILE="rockchip/rk3399-rock-pi-4b.dtb" When i run the compile script, the patch is applied successfully, but something goes wrong and i cannot find a hint what could be the issue. This is my config-default.conf # Read build script documentation https://docs.armbian.com/Developer-Guide_Build-Options/ # for detailed explanation of these options and for additional options not listed here KERNEL_ONLY="yes" # leave empty to select each time, set to "yes" or "no" to skip dialog prompt KERNEL_CONFIGURE="no" # leave empty to select each time, set to "yes" or "no" to skip dialog prompt CLEAN_LEVEL="make,debs,oldcache,cache" # comma-separated list of clean targets: "make" = make clean for selected ke> # "debs" = delete packages in "./output/debs" for current branch and family, # "alldebs" = delete all packages in "./output/debs", "images" = delete "./o> # "cache" = delete "./output/cache", "sources" = delete "./sources" # "oldcache" = remove old cached rootfs except for the newest 8 files REPOSITORY_INSTALL="" # comma-separated list of core modules which will be installed from reposito> # "u-boot", "kernel", "bsp", "armbian-config", "armbian-firmware" # leave empty to build from sources or use local cache DEST_LANG="en_US.UTF-8" # sl_SI.UTF-8, en_US.UTF-8 # advanced EXTERNAL_NEW="prebuilt" # compile and install or install prebuilt additional packages INSTALL_HEADERS="" # install kernel headers package LIB_TAG="master" # change to "branchname" to use any branch currently available. USE_TORRENT="no" # use torrent network for faster toolchain and cache download DOWNLOAD_MIRROR="" # set to "china" to use mirrors.tuna.tsinghua.edu.cn CARD_DEVICE="" # device name /dev/sdx of your SD card to burn directly to the card when done # additions to compile for the rock-pi4 CREATE_PATCHES="yes" BOARD="rockpi-4b" BRANCH="current" RELEASE="bullseye" PROGRESS_LOG_TO_FILE="yes" OFFLINE_WORK="no" USE_MAINLINE_GOOGLE_MIRROR="yes" USE_GITHUB_UBOOT_MIRROR="yes" LIB_TAG="v22.05.3" userpatch log [ o.k. ] Started patching process for [ u-boot rockchip64-rockpi-4b-current ] [ o.k. ] Looking for user patches in [ userpatches/u-boot/u-boot-rockchip64 ] [ o.k. ] * [l][c] add-board-clockworkpi-a06.patch ... [ o.k. ] * [l][c] u-boot-rk-rk3399-usb-start-nanopc-t4.patch [ o.k. ] * [l][c] u-boot-rk-rk3399-usb-start.patch [ o.k. ] * [u][c] u-boot-rk_rk3399-disable-uart-debug.patch [ warn ] Make your changes in this directory: [ /home/michael/ws/build/cache/sources/u-boot/v2022.04 ] [ warn ] Press <Enter> after you are done [ waiting ] compilation aborts with AR spl/drivers/built-in.o LD spl/u-boot-spl OBJCOPY spl/u-boot-spl-nodtb.bin SYM spl/u-boot-spl.sym CAT spl/u-boot-spl-dtb.bin COPY spl/u-boot-spl.bin [ error ] ERROR in function compile_uboot [ main.sh:588 -> main.sh:481 -> compilation.sh:240 -> general.sh:0 ] [ error ] U-boot compilation failed [ o.k. ] Process terminated i found this in the compilation.log /home/michael/ws/build/cache/sources/u-boot/v2022.04/drivers/ram/rockchip/sdram_common.c:232: undefined reference to> /home/michael/ws/build/cache/toolchain/gcc-arm-9.2-2019.12-x86_64-aarch64-none-linux-gnu/bin/aarch64-none-linux-gnu-> /home/michael/ws/build/cache/sources/u-boot/v2022.04/drivers/ram/rockchip/sdram_common.c:349: undefined reference to> CC spl/drivers/mmc/sdhci.o CC spl/drivers/core/syscon-uclass.o make[1]: *** [scripts/Makefile.spl:509: tpl/u-boot-tpl] Error 1 make: *** [Makefile:2112: tpl/u-boot-tpl.bin] Error 2 make: *** Waiting for unfinished jobs.... CC spl/drivers/mmc/rockchip_sdhci.o CC spl/drivers/core/of_extra.o CC spl/drivers/core/ofnode.o But i cannot makeup, what could be the issue?
  10. I will show you how I successfully enabled pcie gen2 on my Rock Pi 4b and now my nvme is running at 1.1 GB/s. The solution which you can find on the web to activate pcie gen2 on an Armbian did NOT work for me: sudo nano /boot/armbianEnv.txt and insert: dtoverlay=pcie-gen2 The following solution activated pcie gen2: 0. check your current nvme speed to compare it afterwards with: sudo dd if=/dev/nvme0n1 of=/dev/null bs=1M count=2048 iflag=direct status=progress --> 618 MB/s 1. find out which rk3399-rock-pi-xxx.dtb your Rock Pi 4 is using. cat /boot/armbianEnv.txt | grep fdtfile --> fdtfile=rockchip/rk3399-rock-pi-4b.dtb --> In my example I will use rk3399-rock-pi-4b.dtb 2. make a backup of your *.dtb file sudo cp /boot/dtb/rockchip/rk3399-rock-pi-4b.dtb /boot/dtb/rockchip/rk3399-rock-pi-4b.dtb.bak 3. copy *.dtb to /tmp sudo cp /boot/dtb/rockchip/rk3399-rock-pi-4b.dtb /tmp/rk3399-rock-pi-4b.dtb 4. we need to make *.dtb into *.dts to edit it sudo dtc -I dtb -O dts -o /tmp/rk3399-rock-pi-4b.dts /tmp/rk3399-rock-pi-4b.dtb (4b). If you don't have dtc on rockpi than install it with: sudo apt-get install device-tree-compiler 5. edit *.dts sudo nano /tmp/rk3399-rock-pi-4b.dts search with [Ctrl + w] for the string: max-link-speed you will find something like this replace it with: save your file 6. turn *.dts into *.dtb sudo dtc -I dts -O dtb /tmp/rk3399-rock-pi-4b.dts -o /tmp/rk3399-rock-pi-4b.dtb 7. copy new *.dtb to /boot/dtb/rockchip sudo cp /tmp/rk3399-rock-pi-4b.dtb /boot/dtb/rockchip/rk3399-rock-pi-4b.dtb 8. give the file the same rights as before sudo chmod 0755 /boot/dtb/rockchip/rk3399-rock-pi-4b.dtb REBOOT Now check your vnme speed again and if everything worked you should see 1.0 GB/s [ ] sudo dd if=/dev/nvme0n1 of=/dev/null bs=1M count=2048 iflag=direct status=progress --> 2134900736 bytes (2.1 GB, 2.0 GiB) copied, 2 s, 1.1 GB/s """THERE WE HAVE THE SALAD""" """B0F1B0"""
  11. This feels really awkward, since I already asked about this problem in another part of the forum, but the bug reporting system says that bugs should be reported by posting in this section of the forum. Feel free to merge the other thread into this one if you want. (Link at bottom.) Linux kernel 5.15.x appears to have a serious regression that prevents GPIO from working correctly on the Rock Pi 4B+ (board version 1.73). Summary: All GPIO4A pins are nonfunctional: Pin 12 stuck off Pin 35 stuck off Pin 36 stuck off Pin 38 stuck off Pin 40 stuck off GPIO1B is nonfunctional. Pin 19 stuck off Pin 23 are stuck off. Pin 24 is stuck on GPIO4C is partially working. Pin 8 is stuck on (serial overlay?) Pin 10 is stuck off (serial overlay?) Other 4C pins work as expected. All other pins work. No overlays are explicitly enabled, and the documentation says that all overlays are supposed to default to off. What I've tried: Using my own code (first discovered) linked against mraa C library. Using mraa-gpio. Using echo commands in /sys/class/gpio/. Switching kernels with arbian-configure: 4.4.213-rockchip64 - works as expected 5.10.16-rockchip64 - works as expected 5.10.63-rockchip64 - works as expected 5.15.25-rockchip64 - GPIO malfunction as described above. 5.15.63-rockchip64 - GPIO malfunction as described above. 5.19.5-rockchip64 - GPIO malfunction as described above. So it looks like GPIO broke rather badly in the 5.15 branch and after, but is working in the 5.10 branch. Either that or some overlays are getting turned on by default somehow (but Armbian doesn't seem to have a syntax to turn them off as far as I can tell, so the net effect is the same). In a related bug, the exact same set of problem pins work only when running as root in 5.10.x and 4.4.x, whereas all other GPIO pins work correctly as a non-root user when the sysfs nodes have the correct ownership and permissions applied. This suggests that there is some chunk of code that reconfigures the SoC to set those pins to be GPIO output pins that either A. is incorrectly being guarded by a root UID check in 5.10.xx or B. is on some other /dev or /sys node that I failed to chown/chmod, and is either missing entirely or not properly exposed in devfs or sysfs in the 5.15.x kernel. Not sure if that will help narrow the search for the bug, but it seemed relevant. 🙂 And before you read the log linked below and ask me about it, yes, I know that the image I installed was apparently for the Rock Pi 4c. I changed the overlay already and swapped out the two 4c-specific packages with their 4b equivalents, and it made no difference. And then, just to make sure it wasn't something that I missed, I loaded the 4b image onto a flash card, and it failed in the same way with the 5.15.x kernels. Armbianmonitor log: https://www.gatwood.net/bugs/armbian_info.txt For more info, see the original discussion thread:
  12. Hi, I built a second nas from rockpi4 and as I used the 12V plug to power the tower, I thought, I could use an old pc power supply to drive both. But when I start both nas from the same power supply, both will crash. Any idea, how I could avoid that crash and stil use only one power supply? Maybe add some electronic components?
  13. Hi, i'm currently trying to disable the serial console on port 2 on my Rockchip based Rockpi 4B (based on rk3399). I already found the following forum thread, that describes in brief, that i basically have to recompile my own armbian image. But still I'm missing some information. I have read the docs in docs.armbian.com and watched the YouTube video on how to build an armbian image. So far, i was able to setup a VM for building an image on my workstation. I also had a successful compile run yesterday, that created some output in my output folder. Now, I'd like to apply a patch, that changes the serial debugging console during boot from port 2 to port 4. I have created a patchfile using the source code files from the mainline linux repository with the following command: ``` diff -Naur rk3399-rock-pi-4.dtsi rk3399-rock-pi-4.dtsi.1 > rk3399-rock-pi-4.dtsi.patch ``` My patch file looks like this now: --- rk3399-rock-pi-4.dtsi 2022-08-29 12:33:21.534325708 +0000 +++ rk3399-rock-pi-4.dtsi.1 2022-08-29 12:36:59.535513608 +0000 @@ -17,7 +17,7 @@ }; chosen { - stdout-path = "serial2:1500000n8"; + stdout-path = "serial4:1500000n8"; }; clkin_gmac: external-gmac-clock { The original file is from here. My question(s) would be: - is this the correct way to create the patch file? - Where do i put the patch file (and how do i name it)? I have the following folder structure in my userpatches/u-boot directory: drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-clearfog/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-helios4/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-imx6/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-imx7d-current/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-imx7d-legacy/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-media/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-meson/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-meson64/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-mt7623/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-mvebu64/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-mvebu-edge/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-odroid/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-odroidxu4/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-rk322x/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-rk35xx/ drwxrwsr-x 2 root sudo 4096 Aug 30 08:08 u-boot-rockchip/ // <---- i would place the patch file here. Is that correct? drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-rockchip64/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-rockchip-rk3588/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-rockpis/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-s5p6818/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-sun50iw9/ drwxrwsr-x 2 root sudo 4096 Aug 29 12:45 u-boot-sunxi/ I'd appreciate any help and input! Thanks in advance, Michael
  14. Hi, I installed a fresh Armbian_22.05.4_Rockpi-4a_sid_edge_5.18.0 first on SD-card, then I used nand-sata-install to copy system to emmc. After that I rebooted and set up the nas (rockpi-4a with 4 ssd-drives). I already used ssh remote shell to perform apt dist-upgrade and copying of about 6TB ... When all setup was finished, I shutdown the system, closed the tower and restarted again. On that restart, the network came up without inet-address. ifconfig showed eth0 and l0, but eth0 had a mac-address (not the one, I configured in armbianEnv.txt) but no ip-address. Here are some lines from syslog: Aug 28 15:57:01 mynas NetworkManager[1659]: <info> [1661695021.5656] device (eth0): state change: disconnected -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed') Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.7361] device (eth0): carrier: link connected Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.7370] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') Aug 28 15:57:02 mynas kernel: [ 327.420987] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx Aug 28 15:57:02 mynas kernel: [ 327.421037] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.7393] policy: auto-activating connection 'Armbian ethernet' (9362e2eb-3533-439f-acd4-3804f33c01a5) Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.7409] device (eth0): Activation: starting connection 'Armbian ethernet' (9362e2eb-3533-439f-acd4-3804f33c01a5) Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.7413] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.7425] manager: NetworkManager state is now CONNECTING Aug 28 15:57:02 mynas NetworkManager[1659]: <warn> [1661695022.7434] platform-linux: do-change-link[2]: failure changing link: failure 16 (Device or resource busy) Aug 28 15:57:02 mynas kernel: [ 327.429651] rk_gmac-dwmac fe300000.ethernet eth0: Link is Down Aug 28 15:57:02 mynas NetworkManager[1659]: <warn> [1661695022.7460] platform-linux: do-change-link[2]: failure changing link: failure 99 (Cannot assign requested address) Aug 28 15:57:02 mynas NetworkManager[1659]: <warn> [1661695022.7461] device (eth0): set-hw-addr: failed to set-cloned MAC address to AB:CD:47:11:FE:D0 (AB:CD:47:11:FE:D0) (NME_UNSPEC) Aug 28 15:57:02 mynas kernel: [ 327.433545] rk_gmac-dwmac fe300000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211E Gigabit Ethernet] (irq=POLL) Aug 28 15:57:02 mynas kernel: [ 327.484253] rk_gmac-dwmac fe300000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 Aug 28 15:57:02 mynas kernel: [ 327.495328] rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found Aug 28 15:57:02 mynas kernel: [ 327.495354] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW Aug 28 15:57:02 mynas kernel: [ 327.495370] rk_gmac-dwmac fe300000.ethernet eth0: configuring for phy/rgmii link mode Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.8109] device (eth0): state change: prepare -> failed (reason 'config-failed', sys-iface-state: 'managed') Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.8121] manager: NetworkManager state is now DISCONNECTED Aug 28 15:57:02 mynas NetworkManager[1659]: <warn> [1661695022.8128] device (eth0): Activation: failed for connection 'Armbian ethernet' Aug 28 15:57:02 mynas NetworkManager[1659]: <info> [1661695022.8139] device (eth0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Aug 28 15:57:08 mynas NetworkManager[1659]: <info> [1661695028.8165] device (eth0): state change: disconnected -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed') I see the error, but I have no idea, what to do.
  15. I am a Linux-Newbee myself but in the DOS/Windows-world I was programmer and admin. But my friend is a total user-only (he is physiotherapist an GOOD in that) so I ended up being his computerman. We both have the rockPi 4 A (no WLAN) with Armbian XFCE. He also has some pad with Android. Everything was good for about a year. He is using Telegram a lot. On the pad he had several messages about a Telegram update, one click, done. On the RockPi with Armbian instead he had messages about using an outdated version of Telegram which soon will cease functioning. No Updates offered. He installed Telegram new which worked, but after a restart he had the old version back. Tragedy is developing: In some forum they advised him to upgrade Armbian which would update Telegram as well. They told him the magic words (sudo apt update/upgrade). They did not tell him to make a backup on an external drive. After the update Armbian is running but the desktop is not coming up any more, he is stuck with command prompt. He can log in though. I never had this before so I don't know what to do. Ok, a complete new install, but no backup and lots of music and movies. Is there a way to "repair" it with commands? Thank you for reading and for (hopefully) advice!
  16. Hello, I installed Armbian 22.05.3 Jammy on a Rock Pi 4A+. Unfortunately 3 out of 4 USB ports do not work; only the USB 3.0 OTG port works. I tried using the Debian Buster download from Radxa, and all four ports work. Any suggestion on how to fix this with Armbian?
  17. (only rockpi-4a tag available..) After enabled `rpi-7inch-lcd` overlay, rockpi-4-b-plus doesnt boot, no display, no ip. Before reboot: root@rockpi-4c:/home/qnet# cat /boot/armbianEnv.txt verbosity=1 bootlogo=true overlay_prefix=rockchip fdtfile=rockchip/rk3399-rock-pi-4b.dtb rootdev=UUID=072c27ac-4335-4062-9b8d-a9d0a71d6c3a rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u overlays=rpi-7inch-lcd root@rockpi-4c:/home/qnet# sudo reboot root@rockpi-4c:/home/qnet# Thank you!
  18. dolphs

    rockpi4a @2GHz

    Hi, Just noticed image " Linux rockpi-4a 5.9.14-rockchip64 #20.11.4 SMP PREEMPT Tue Dec 15 08:52:20 CET 2020 aarch64 GNU/Linux " my rockpi4a runs at 2Ghz. To radxa overclocking is possible so that 2GHz is not a real surprise ... Though checked " armbianEnv.txt " but did not find any "overlays" option present overlocking this board, neither any other files in /boot ( or /boot/dtb/rockchip/overlay ). However building a custom image ( kernel 5.10 ) it is running at 1,8GHz again, how can I set this to 2GHz ? ( as a side note - tehre is no need to enable panfrost BTW as I run this as a headless server ) Thanks
  19. RockPi4a. Installed busster current 5.8.6 armbian onto eMMC. Works fine. Now i figure out i need swap space (app needs more than the 1G mem i have). So i boot another image from SD an use gparted to shrink the first partition from the end to create 4GByte and create a swap partition in there. Now the board won't boot anymore (see attached file). Erased SPI, no difference. Partition table shows GPT and "MBR protective" (before and after resizing). so, whats the magic to create a bootable armbian disk if one needs different partitioning than just the "full disk one partition" layout ? Is this "uboot" hidden behind the only partition, there was a bunch of space unused after the partition that i used for the swap partition. Sorry if this was discussed before but uncle google and dr armbian search couldn't find anything for me ;-( armbian-failure.txt
  20. Hi. I've just bought a Rock Pi 4a board, I plan to use it as home server, running stuff like Owncloud, Postfix/Dovecot, Apache, pihole, OpenHab, Emby server etc. I'm thinking of running Armbian on it, but I have absolutely no experience of this dist (I've been managing Debian/Ubuntu servers for many years though). It's going to run headless. I'm wondering what would be the best way to set up disks from an Armbian point of view. My main reason for buying Rock Pi is for the M.2 port, I'm going to put my data on a M.2 disk. Booting from M.2 seems to be tricky though so I'm thinking about booting from micro SD card. I don't want to put any important data or any data that is written a lot on the card though, so my question is what the best way to do this would be? 1: I just keep / on the sd card and mount /var and maybe /home from the M.2 disk. 2: I just boot from the sd card and keep /boot there and keep the entire / on the M.2 disk. (not sure how to set this up though, any good guides?) 3: Any better suggestion? /Daniel
  21. Hi guys! I would like to know why this is happening. I guess the script doesnt identify my sd card as the sd card and it erase it just like it does with emmc before clonning the sd card to the emmc. I use latest armbian focal.
  22. Hi, I owe a rockpi4a which I like to reflash with a custom build dev image: ./compile.sh BRANCH=dev RELEASE=buster BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no BOARD=rockpi4a Can I flash this image directly to emmc, so it boots from it ?
  23. I use Armbian_20.05.3_Rockpi-4a_buster_legacy_4.4.213 The armbian kernel version uses 4.4-213 Follow the radxa official installation script: curl -sL https://rock.sh/get-rockpi-penta | sudo -E bash - The output is as follows: I don’t know where the problem is after execution, I still can’t drive it.... It feels like a failure caused by the kernel, it seems that it only supports linux-image-4.4.154-110-rockchip-gcef30e88a9f5 I executed the command to install the kernel: sudo apt-get install linux-4.4-latest Something went wrong. I just started contacting SBC System and hope I can get help here!!!!!!!!!!!!!!!!!
  24. Hey guys, bunch of thanks for your great work. Was wondering what's up with the latest buster images (20.05.2-5.4.43) for the 1Gig A versions. Worked great up to 20.02.11-5.4.32. The boot gets up to changing the freq, then nothing : > change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=14 CS=1 Die Bus-Width=16 Size=512MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=14 CS=1 Die Bus-Width=16 Size=512MB 256B stride channel 0 CS = 0 MR0=0x19 MR4=0x3 MR5=0x6 MR8=0x0 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0xFF channel 1 CS = 0 MR0=0x19 MR4=0x3 MR5=0x6 MR8=0x0 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0xFF channel 0 training pass! channel 0 training pass! channel 1 training pass! channel 0, cs 0, advanced training done
  25. WIthout SD card, it boots normally, but if SD card is inserted, it won’t boot. On serial port, it is visible that there’s a crash right after the message that says something like “booting from eMMC”. The message includes the values of the registers IIRC. Then, something like “resetting CPU”, and it starts over: tries to boot from eMMC, crashes, etc. Sorry, I didn’t record the exact message, but there’s a chance I’ll re-flash the board in the next couple weeks and then I can provide the exact messages. I’ve tested it with Bionic minimal with 5.4 kernel and buster server with 5.4 kernel. If I insert the SD card later, it’s fine. Also, the official ubuntu bionic server image from radxa works fine.
×
×
  • Create New...