Jump to content

Search the Community

Showing results for tags 'rockpi-4cplus'.

  • 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

Found 10 results

  1. The mainline 5.11 patch "phy: rockchip: set pulldown for strobe line in dts" https://github.com/torvalds/linux/commit/8b5c2b45b8f0a11c9072da0f7baf9ee986d3151e (not backported to 5.10.y) seems to have broken most if not all rockchip board EMMC HS400 enhanced strobe support. This probably affects supported rockchip boards (at least rk3399 ones, but probably most). That is boards exhibit: [ 18.985162] mmc1: running CQE recovery [ 18.988056] ------------[ cut here ]------------ [ 18.988500] mmc1: cqhci: spurious TCN for tag 12 and the filesystem ends up corrupted on write attempt. Note that another bug about regulator core DEFERRED support (which might have produced the same issue hardware wise) was introduced in 5.10.43 (I had bisected it to https://github.com/torvalds/linux/commit/98e48cd9283dbac0e1445ee780889f10b3d1db6a "regulator: core: resolve supply for boot-on/always-on regulators"). But I was confident that it to be fixed in at least 6.1 by https://github.com/torvalds/linux/commit/8a866d527ac0441c0eb14a991fa11358b476b11d "regulator: core: Resolve supply name earlier to prevent double-init" (introduced in 6.1), still EMMC was still failing on me. Thanks to @RussianNeuroMancer telling me that not all rk339 boards had EMMC HS400es broken, I found that nanopc-t4 had https://github.com/torvalds/linux/commit/463be3cb357dab7d7e4d8dcc7c15c642e10c5bef arm64: dts: rockchip: add enable-strobe-pulldown to emmc phy on nanopi4 So the current way, from this nanopc-t4 commit, to fix EMMC HS400 on most rockchip is to add "rockchip,enable-strobe-pulldown;" to the "emmc_phy" node (at least this node alias for rk3399). &emmc_phy { + rockchip,enable-strobe-pulldown; status = "okay"; }; With this patch I can renable hs400es for rk3399 emmc on helios64 (it is already set for nanopc-t4 in mainline). Details in: I believe the https://github.com/torvalds/linux/commit/8b5c2b45b8f0a11c9072da0f7baf9ee986d3151e mainline commit was wrong in that it probably should have done the opposite (that is enable the pulldown) as most boards were hardwired so. As was done for rk3588 boards: "arm64: dts: rockchip: Fix eMMC Data Strobe PD on rk3588" https://github.com/torvalds/linux/commit/37f3d6108730713c411827ab4af764909f4dfc78 " JEDEC standard JESD84-B51 defines the eMMC Data Strobe line, which is currently used only in HS400 mode, as a device->host clock signal that "is used only in read operation. The Data Strobe is always High-Z (not driven by the device and pulled down by RDS) or Driven Low in write operation, except during CRC status response." RDS is a pull-down resistor specified in the 10K-100K ohm range. Thus per the standard, the Data Strobe is always pulled to ground (by the eMMC and/or RDS) during write operations. Evidently, the eMMC host controller in the RK3588 considers an active voltage on the eMMC-DS line during a write to be an error. The default (i.e. hardware reset, and Rockchip BSP) behavior for the RK3588 is to activate the eMMC-DS pin's builtin pull-down. As a result, many RK3588 board designers do not bother adding a dedicated RDS resistor, instead relying on the RK3588's internal bias. The current devicetree, however, disables this bias (`pcfg_pull_none`), breaking HS400-mode writes for boards without a dedicated RDS, but with an eMMC chip that chooses to High-Z (instead of drive-low) the eMMC-DS line. (The Turing RK1 is one such board.) Fix this by changing the bias in the (common) emmc_data_strobe case to reflect the expected hardware/BSP behavior. This is unlikely to cause regressions elsewhere: the pull-down is only relevant for High-Z eMMCs, and if this is redundant with a (dedicated) RDS resistor, the effective result is only a lower resistance to ground -- where the range of tolerance is quite high. If it does, it's better fixed in the specific devicetrees. Maybe one can confirm this is the case not only for rk5588 but for other rockchip boards? (about the default for hardware reset and rockchip BSP with regards to active that eMMC-DS pin's builtin pulldown if any, and board designers for other boards than rk5588 also not bothering to add a dedicated RDS resistor, instead relying on the rockchip internal bias, also if any on non rk5588) At least two other boards disabled hs400es in mainline probbaly due to this patch disabling the internal pulldown by default "phy: rockchip: set pulldown for strobe line in dts" https://github.com/torvalds/linux/commit/8b5c2b45b8f0a11c9072da0f7baf9ee986d3151e in 2023 in vanilla Linux: Rock 4C+ https://github.com/torvalds/linux/commit/2bd1d2dd808c60532283e9cf05110bf1bf2f9079 Rock Pi 4 https://github.com/torvalds/linux/commit/cee572756aa2cb46e959e9797ad4b730b78a050b
  2. Hello everyone, I seem to have a problem with not knowing how to change the top usb3 port of my Rock pi 4+ to host mode from otg mode, I just got it and installed armbian on it and open media vault, only to notice that I couldn't connect anything to the top usb 3 port and have it show up in open media vault, the other ports work fine and looking at the internet seems to have found that the answer is that the port is in OTG mode and on the official website they do have a way to change it to host mode, but not in armbian and I'm not skilled enough in linux to find where the file I need to change is. I'm running this build "Armbian_v22.05.2_Rockpi-4cplus_bullseye_current_6.1.33.img.xz" downloaded from the armbian website. Thanks in advance for the help :)
  3. Hello, I tried to use the power button on my Rock 4 C+ running Armbian 23.02.2 Bullseye with Linux 5.15.93-rockchip64. It is able to power off. But I can't boot up the controller. When I use the debian based radxa image the button works like expected. I found this at the rk3399-rock-4c-plus.dts of the radxa kernel. &rockchip_suspend { status = "okay"; rockchip,sleep-debug-en = <1>; rockchip,sleep-mode-config = < (0 | RKPM_SLP_ARMPD | RKPM_SLP_PERILPPD | RKPM_SLP_DDR_RET | RKPM_SLP_PLLPD | RKPM_SLP_CENTER_PD ) >; rockchip,wakeup-config = < (0 | RKPM_GPIO_WKUP_EN | RKPM_PWM_WKUP_EN | RKPM_USB_WKUP_EN | RKPM_USB_LINESTATE_WKUP_EN ) >; rockchip,pwm-regulator-config = < (0 | PWM2_REGULATOR_EN ) >; rockchip,power-ctrl = <&gpio1 17 GPIO_ACTIVE_HIGH>, <&gpio1 14 GPIO_ACTIVE_HIGH>, <&gpio0 3 GPIO_ACTIVE_HIGH>; }; I would test the overlay with current armbian build, but I doesn't know where to place it. Maybe someone can help me here?
  4. Hi, I want to use a mcp2515 can controller over spi1 or 2. I read about internal flash is blocking the spi1. Can I use another Chipselect pin to use the spi1 with GPIO? Can you please give some advice where to start my research about overlays? What else do I need to activate? (core moduls, driver…)
  5. I'm using the newest Ubuntu image for my RockPi4C+, and from time to time, I try to login, but it wont allow it. If I reboot, I can login just fine. I tried from 2 devices, both devices could not ssh into the pi. running a cat on /var/log/auth.log doesnt show any attempts at all. After a reboot, I cat the log and can see my login attempts present after the reboot. Its like the sshd service is dying. Mar 17 00:15:01 rockpi-4cplus CRON[1869]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Mar 17 00:15:01 rockpi-4cplus CRON[1868]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Mar 17 00:15:01 rockpi-4cplus CRON[1869]: pam_unix(cron:session): session closed for user root Mar 17 00:15:01 rockpi-4cplus CRON[1868]: pam_unix(cron:session): session closed for user root Mar 17 00:17:01 rockpi-4cplus CRON[1883]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Mar 17 00:17:01 rockpi-4cplus CRON[1883]: pam_unix(cron:session): session closed for user root Mar 17 00:22:48 rockpi-4cplus sudo: ben : TTY=pts/0 ; PWD=/home/ben ; USER=root ; COMMAND=/usr/sbin/service ssh restart Mar 17 00:22:48 rockpi-4cplus sudo: pam_unix(sudo:session): session opened for user root(uid=0) by ben(uid=1000) Mar 17 00:22:48 rockpi-4cplus sshd[965]: Received signal 15; terminating. Mar 17 00:22:48 rockpi-4cplus sshd[1903]: Server listening on 0.0.0.0 port 22. Mar 17 00:22:48 rockpi-4cplus sshd[1903]: Server listening on :: port 22. Mar 17 00:22:48 rockpi-4cplus sudo: pam_unix(sudo:session): session closed for user root Mar 17 00:22:52 rockpi-4cplus sudo: ben : TTY=pts/0 ; PWD=/home/ben ; USER=root ; COMMAND=/usr/sbin/service ssh status Mar 17 00:22:52 rockpi-4cplus sudo: pam_unix(sudo:session): session opened for user root(uid=0) by ben(uid=1000) Mar 17 00:22:52 rockpi-4cplus sudo: pam_unix(sudo:session): session closed for user root Mar 17 00:25:01 rockpi-4cplus CRON[1911]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Mar 17 00:25:01 rockpi-4cplus CRON[1911]: pam_unix(cron:session): session closed for user root Mar 17 00:27:21 rockpi-4cplus sudo: ben : TTY=pts/0 ; PWD=/home/ben ; USER=root ; COMMAND=/usr/bin/cat /var/log/auth.log Mar 17 00:27:21 rockpi-4cplus sudo: pam_unix(sudo:session): session opened for user root(uid=0) by ben(uid=1000) Can someone help? I dont know what else to look at. I checked the Journal but nothing. ben@rockpi-4cplus:~$ journalctl | grep sshd Mar 16 23:17:10 rockpi-4cplus sshd[965]: Server listening on 0.0.0.0 port 22. Mar 16 23:17:10 rockpi-4cplus sshd[965]: Server listening on :: port 22. Mar 17 00:11:24 rockpi-4cplus sshd[1664]: Accepted password for ben from 10.0.0.245 port 56146 ssh2 Mar 17 00:11:24 rockpi-4cplus sshd[1664]: pam_unix(sshd:session): session opened for user ben(uid=1000) by (uid=0) Mar 17 00:22:48 rockpi-4cplus sshd[965]: Received signal 15; terminating. Mar 17 00:22:48 rockpi-4cplus sshd[1903]: Server listening on 0.0.0.0 port 22. Mar 17 00:22:48 rockpi-4cplus sshd[1903]: Server listening on :: port 22.
  6. Need some help, docker is broken. I used the official docker site to install docker, that was a PITA as the apt hash was mismatching, but I got past that, but NOW hello-world will not run at all. I need someone with more experience to help me look at the logs below: Hello-World: sudo docker run hello-world docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: unable to apply apparmor profile: apparmor failed to apply profile: write /proc/self/attr/apparmor/exec: no such file or directory: unknown. ERRO[0001] error waiting for container: ben@rockpi-4cplus:~$ journalctl | grep docker Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.103935029Z" level=info msg="Starting up" Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.121140305Z" level=warning msg="AppArmor enabled on system but \"apparmor_parser\" binary is missing, so profile can't be loaded" Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.124122295Z" level=info msg="[core] [Channel #1] Channel created" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.124335211Z" level=info msg="[core] [Channel #1] original dial target is: \"unix:///run/containerd/containerd.sock\"" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.124536752Z" level=info msg="[core] [Channel #1] parsed dial target is: {Scheme:unix Authority: Endpoint:run/containerd/containerd.sock URL:{Scheme:unix Opaque: User: Host: Path:/run/containerd/containerd.sock RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.124626585Z" level=info msg="[core] [Channel #1] Channel authority set to \"localhost\"" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.125290124Z" level=info msg="[core] [Channel #1] Resolver state updated: {\n \"Addresses\": [\n {\n \"Addr\": \"/run/containerd/containerd.sock\",\n \"ServerName\": \"\",\n \"Attributes\": {},\n \"BalancerAttributes\": null,\n \"Type\": 0,\n \"Metadata\": null\n }\n ],\n \"ServiceConfig\": null,\n \"Attributes\": null\n} (resolver returned new addresses)" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.126441620Z" level=info msg="[core] [Channel #1] Channel switches to new LB policy \"pick_first\"" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.126900119Z" level=info msg="[core] [Channel #1 SubChannel #2] Subchannel created" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.127208993Z" level=info msg="[core] [Channel #1 SubChannel #2] Subchannel Connectivity change to CONNECTING" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.127437659Z" level=info msg="[core] [Channel #1 SubChannel #2] Subchannel picks a new address \"/run/containerd/containerd.sock\" to connect" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.127661950Z" level=info msg="[core] [Channel #1] Channel Connectivity change to CONNECTING" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.129733151Z" level=info msg="[core] [Channel #1 SubChannel #2] Subchannel Connectivity change to READY" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.129933525Z" level=info msg="[core] [Channel #1] Channel Connectivity change to READY" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.136601795Z" level=info msg="[core] [Channel #4] Channel created" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.136792252Z" level=info msg="[core] [Channel #4] original dial target is: \"unix:///run/containerd/containerd.sock\"" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.136976585Z" level=info msg="[core] [Channel #4] parsed dial target is: {Scheme:unix Authority: Endpoint:run/containerd/containerd.sock URL:{Scheme:unix Opaque: User: Host: Path:/run/containerd/containerd.sock RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.137071960Z" level=info msg="[core] [Channel #4] Channel authority set to \"localhost\"" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.137358375Z" level=info msg="[core] [Channel #4] Resolver state updated: {\n \"Addresses\": [\n {\n \"Addr\": \"/run/containerd/containerd.sock\",\n \"ServerName\": \"\",\n \"Attributes\": {},\n \"BalancerAttributes\": null,\n \"Type\": 0,\n \"Metadata\": null\n }\n ],\n \"ServiceConfig\": null,\n \"Attributes\": null\n} (resolver returned new addresses)" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.137624666Z" level=info msg="[core] [Channel #4] Channel switches to new LB policy \"pick_first\"" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.137869082Z" level=info msg="[core] [Channel #4 SubChannel #5] Subchannel created" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.138125748Z" level=info msg="[core] [Channel #4 SubChannel #5] Subchannel Connectivity change to CONNECTING" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.138310372Z" level=info msg="[core] [Channel #4 SubChannel #5] Subchannel picks a new address \"/run/containerd/containerd.sock\" to connect" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.138439288Z" level=info msg="[core] [Channel #4] Channel Connectivity change to CONNECTING" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.141760194Z" level=info msg="[core] [Channel #4 SubChannel #5] Subchannel Connectivity change to READY" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.142022401Z" level=info msg="[core] [Channel #4] Channel Connectivity change to READY" module=grpc Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.169234518Z" level=info msg="[graphdriver] using prior storage driver: overlay2" Mar 17 00:38:16 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:16.187258000Z" level=info msg="Loading containers: start." Mar 17 00:38:16 rockpi-4cplus NetworkManager[856]: <info> [1679013496.7062] manager: (docker0): new Bridge device (/org/freedesktop/NetworkManager/Devices/5) Mar 17 00:38:16 rockpi-4cplus NetworkManager[856]: <info> [1679013496.9197] device (docker0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Mar 17 00:38:16 rockpi-4cplus NetworkManager[856]: <info> [1679013496.9222] device (docker0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external') Mar 17 00:38:16 rockpi-4cplus NetworkManager[856]: <info> [1679013496.9261] device (docker0): Activation: starting connection 'docker0' (cec9bf20-e7eb-4668-8a94-73c7877780d9) Mar 17 00:38:16 rockpi-4cplus NetworkManager[856]: <info> [1679013496.9267] device (docker0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Mar 17 00:38:16 rockpi-4cplus NetworkManager[856]: <info> [1679013496.9279] device (docker0): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Mar 17 00:38:16 rockpi-4cplus NetworkManager[856]: <info> [1679013496.9292] device (docker0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Mar 17 00:38:16 rockpi-4cplus NetworkManager[856]: <info> [1679013496.9306] device (docker0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Mar 17 00:38:16 rockpi-4cplus NetworkManager[856]: <info> [1679013496.9377] device (docker0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Mar 17 00:38:16 rockpi-4cplus NetworkManager[856]: <info> [1679013496.9388] device (docker0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Mar 17 00:38:16 rockpi-4cplus NetworkManager[856]: <info> [1679013496.9424] device (docker0): Activation: successful, device activated. Mar 17 00:38:17 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:17.256107456Z" level=info msg="Removing stale sandbox 72c1d4470e5e427325cdee8d88a5bbccc1e935b72204517df77a486c05a528ec (82cfaa715918eb31665ef270299e1769cc8fd061c6f1b19a77bc3c88edf93ba3)" Mar 17 00:38:17 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:17.259002905Z" level=info msg="Removing stale endpoint suspicious_dijkstra (a2ce9673b63b1c359bb0e5e97efa5dd046159d2e91006724d69a4009aa673c47)" Mar 17 00:38:17 rockpi-4cplus systemd[1]: run-docker-netns-72c1d4470e5e.mount: Deactivated successfully. Mar 17 00:38:17 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:17.485150188Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address" Mar 17 00:38:17 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:17.666442080Z" level=info msg="Loading containers: done." Mar 17 00:38:17 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:17.732452650Z" level=info msg="Docker daemon" commit=bc3805a graphdriver=overlay2 version=23.0.1 Mar 17 00:38:17 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:17.733325022Z" level=info msg="Daemon has completed initialization" Mar 17 00:38:17 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:17.805429447Z" level=info msg="[core] [Server #7] Server created" module=grpc Mar 17 00:38:17 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:38:17.842482948Z" level=info msg="API listen on /run/docker.sock" Mar 17 00:40:49 rockpi-4cplus sudo[2194]: ben : TTY=pts/0 ; PWD=/home/ben ; USER=root ; COMMAND=/usr/bin/docker run hello-world Mar 17 00:40:50 rockpi-4cplus systemd[1]: var-lib-docker-overlay2-a83857f63d6a6d2e0bbe432738a01ebd8220aee2ff55323e371492843efd51e9\x2dinit-merged.mount: Deactivated successfully. Mar 17 00:40:50 rockpi-4cplus kernel: docker0: port 1(vethea138c1) entered blocking state Mar 17 00:40:50 rockpi-4cplus kernel: docker0: port 1(vethea138c1) entered disabled state Mar 17 00:40:51 rockpi-4cplus kernel: docker0: port 1(vethea138c1) entered blocking state Mar 17 00:40:51 rockpi-4cplus kernel: docker0: port 1(vethea138c1) entered forwarding state Mar 17 00:40:51 rockpi-4cplus kernel: IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready Mar 17 00:40:51 rockpi-4cplus NetworkManager[856]: <info> [1679013651.0217] device (docker0): carrier: link connected Mar 17 00:40:51 rockpi-4cplus audit[2291]: AVC apparmor="DENIED" operation="change_onexec" info="label not found" error=-2 profile="unconfined" name="docker-default" pid=2291 comm="runc:[2:INIT]" Mar 17 00:40:51 rockpi-4cplus kernel: audit: type=1400 audit(1679013651.026:2): apparmor="DENIED" operation="change_onexec" info="label not found" error=-2 profile="unconfined" name="docker-default" pid=2291 comm="runc:[2:INIT]" Mar 17 00:40:51 rockpi-4cplus systemd[1]: docker-a53710e47a6652bae5005e6fba5fedf14a033cfaee91d0b4b3d16f145b2be7db.scope: Deactivated successfully. Mar 17 00:40:51 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:40:51.086424464Z" level=error msg="stream copy error: reading from a closed fifo" Mar 17 00:40:51 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:40:51.086425923Z" level=error msg="stream copy error: reading from a closed fifo" Mar 17 00:40:51 rockpi-4cplus kernel: docker0: port 1(vethea138c1) entered disabled state Mar 17 00:40:51 rockpi-4cplus kernel: docker0: port 1(vethea138c1) entered disabled state Mar 17 00:40:51 rockpi-4cplus kernel: docker0: port 1(vethea138c1) entered disabled state Mar 17 00:40:51 rockpi-4cplus NetworkManager[856]: <info> [1679013651.1803] device (vethea138c1): released from master device docker0 Mar 17 00:40:51 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:40:51.203132669Z" level=error msg="a53710e47a6652bae5005e6fba5fedf14a033cfaee91d0b4b3d16f145b2be7db cleanup: failed to delete container from containerd: no such container" Mar 17 00:40:51 rockpi-4cplus systemd[1]: var-lib-docker-overlay2-a83857f63d6a6d2e0bbe432738a01ebd8220aee2ff55323e371492843efd51e9-merged.mount: Deactivated successfully. Mar 17 00:41:30 rockpi-4cplus sudo[2354]: ben : TTY=pts/0 ; PWD=/home/ben ; USER=root ; COMMAND=/usr/bin/docker pull hello-world Mar 17 00:41:36 rockpi-4cplus sudo[2380]: ben : TTY=pts/0 ; PWD=/home/ben ; USER=root ; COMMAND=/usr/bin/docker run hello-world Mar 17 00:41:37 rockpi-4cplus systemd[1]: var-lib-docker-overlay2-d71c98f987921c05e25a087a01c6e4fe04ba790e6b9a71cd61b6a965dd91c51f\x2dinit-merged.mount: Deactivated successfully. Mar 17 00:41:37 rockpi-4cplus kernel: docker0: port 1(veth3975e07) entered blocking state Mar 17 00:41:37 rockpi-4cplus kernel: docker0: port 1(veth3975e07) entered disabled state Mar 17 00:41:37 rockpi-4cplus kernel: docker0: port 1(veth3975e07) entered blocking state Mar 17 00:41:37 rockpi-4cplus kernel: docker0: port 1(veth3975e07) entered forwarding state Mar 17 00:41:37 rockpi-4cplus NetworkManager[856]: <info> [1679013697.5857] device (docker0): carrier: link connected Mar 17 00:41:37 rockpi-4cplus audit[2476]: AVC apparmor="DENIED" operation="change_onexec" info="label not found" error=-2 profile="unconfined" name="docker-default" pid=2476 comm="runc:[2:INIT]" Mar 17 00:41:37 rockpi-4cplus kernel: audit: type=1400 audit(1679013697.602:3): apparmor="DENIED" operation="change_onexec" info="label not found" error=-2 profile="unconfined" name="docker-default" pid=2476 comm="runc:[2:INIT]" Mar 17 00:41:37 rockpi-4cplus systemd[1]: docker-08a2fde8e2ac5043751612449b1950d7ec7a0391b22b252b05edc1de8628ec84.scope: Deactivated successfully. Mar 17 00:41:37 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:41:37.666672897Z" level=error msg="stream copy error: reading from a closed fifo" Mar 17 00:41:37 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:41:37.666675397Z" level=error msg="stream copy error: reading from a closed fifo" Mar 17 00:41:37 rockpi-4cplus kernel: docker0: port 1(veth3975e07) entered disabled state Mar 17 00:41:37 rockpi-4cplus kernel: docker0: port 1(veth3975e07) entered disabled state Mar 17 00:41:37 rockpi-4cplus kernel: docker0: port 1(veth3975e07) entered disabled state Mar 17 00:41:37 rockpi-4cplus NetworkManager[856]: <info> [1679013697.8091] device (veth3975e07): released from master device docker0 Mar 17 00:41:37 rockpi-4cplus dockerd[1181]: time="2023-03-17T00:41:37.846552627Z" level=error msg="08a2fde8e2ac5043751612449b1950d7ec7a0391b22b252b05edc1de8628ec84 cleanup: failed to delete container from containerd: no such container" Mar 17 00:41:38 rockpi-4cplus systemd[1]: var-lib-docker-overlay2-d71c98f987921c05e25a087a01c6e4fe04ba790e6b9a71cd61b6a965dd91c51f-merged.mount: Deactivated successfully.
  7. I am using the Rockpi 4c plus for the first time. I am also trying out Armbian (for the first time) and downloaded the latest stable version for my board (Linux rockpi-4cplus 5.15.93-rockchip64 #23.02.2 SMP PREEMPT Fri Feb 17 23:48:36 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux) Using armbian-config I selected in hardware configuration "spi-spidev". when my board rebooted, I checked the following: dmesg | grep uart This returns: [ 6.120938] dw-apb-uart ff1a0000.serial: forbid DMA for kernel console I then tried dmesg | grep i2c and this returns [ 1.511705] i2c_dev: i2c /dev entries driver [ 1.564824] input: rk805 pwrkey as /devices/platform/ff3c0000.i2c/i2c-0/0-0020/rk805-pwrkey/input/input0 And finally, I tried dmesg | grep spi And this returns blank. So I was a little confused. (PS. I forgot to mention that lsmod | grep uart or i2c or spi provides some more useful info too). Doing some reading in the Armbian website documentation section I found a section on Device Tree Overlays, but this is just a generic help guide: https://docs.armbian.com/User-Guide_Allwinner_overlays/ This document does help, to a point. Step 1 notes a readme. I found this in the "boot/dtb/rockchip/overlay" folder. However, this readme text was still not very clear to me (see points below): ### spi-spidev Activates SPIdev device node (/dev/spidevX.Y) for userspace SPI access, where X is the bus number and Y is the CS number SPI 0 pins (MOSI, MISO, SCK, CS): GPIO3_A5, GPIO3_A4, GPIO3_A6, GPIO3_A7 SPI 1 pins (MOSI, MISO, SCK, CS): GPIO1_A7, GPIO1_B0, GPIO1_B1, GPIO1_B2 SPI 2 pins (MOSI, MISO, SCK, CS): GPIO1_C0, GPIO1_B7, GPIO1_C1, GPIO1_C2 SPI 3 pins (MOSI, MISO, SCK, CS): GPIO2_B2, GPIO2_B1, GPIO2_B3, GPIO2_B4 Parameters: param_spidev_spi_bus (int) SPI bus to activate SPIdev support on Required Supported values: 0, 1 param_spidev_spi_cs (int) SPI chip select number Optional Default: 0 Supported values: 0, 1 Using chip select 1 requires using "spi-add-cs1" overlay param_spidev_max_freq (int) Maximum SPIdev frequency Optional Default: 1000000 Range: 3000 - 100000000 The overlays guide then instructs "2. Add names of overlays you want to activate to overlays= line in /boot/armbianEnv.txt, separated with spaces". Checking this file, confirmed that the "armbian-config" tool worked as it had added the spi-spidev parameter: But the above pin description was confusing as it not match the pinout diagram I had found as a reference: https://wiki.radxa.com/Rockpi4/hardware/gpio Basically for SPI I wanted to use Pin#: 19, 21, 23 & 24 which from the above gpio pinout at least matches the readme (e.g. GPIO1_A7, GPIO1_B0, GPIO1_B1, GPIO1_B2). But what confused me is that the GPIO pinmap has 1 spi bus marked as default and yet nothing is set in Armbian. Reading online and the forums, I see most use the following: param_spidev_spi_bus=0. But I am guessing if this is the spi bus then should I be using "1" instead. Then what is not shown is what to do if you want to have two SPI buses. What is the format. Then a somewhat related aside question. I wanted to use UART2 Pin#: 8 & 10. I read that in the Radxa debian release they have this on as default (for debugging purposes). It was not clear to me if this is the same here - from what I see it could be inferred but thought to ask. Using "grep uart" indicates that something is available for UART. It was also not clear to me, from the gpio pin mapping what UART4 is as not shown. Any help gladly appreciated
  8. Looks like my Rock Pi 4C+ does not recognize builtin sound card: root@rockpi-4cplus:~# aplay -l **** List of PLAYBACK Hardware Devices **** root@rockpi-4cplus:~# armbianmonitor link: https://paste.armbian.com/xucibilaza It seems to me that there are some clues here: What is the issue? How can I fix it?
  9. Hey there, I just joined the ARM universe & to be honest I lost all my skills with Linux. First I tried some official images Armbian_22.11.1_Rockpi-4cplus_jammy_current_5.15.80_xfce_desktop.img & with all of them I got a Blackscreen after the Logo. (all settings were made) Then I a tried a pre-release so I could finally get into armbian. Wifi : I couldn't connect via. wifi, "wifi network could not be found" But it was listed with a good signal strength. BT: no adapter was found. ( I used armconfig to enable BT) USB: just 3 of 4 usb ports were working. ( I guess it was 1x usb 3.0 & 2x usb 2.0) The Rock Pi ist connected via usbc and I tried different Power sources, Monitor (supercharging enabled), PC & and a seperate power supply with 3,5 A. Then I tried librelec,(LibreELEC-RK3399.arm-10.0.4-rock-pi-4) there wasnt even a Wifi or a BT adapter listed. And only 1 usb port were working. And then I tried Debian and I finally got all USB ports working. Also my BT adapter showed up the first time. But I still wasnt able to connect to my wifi network, my network was listed but I got again: "wifi network could not be found" With BT was nearly the same..., it listed my BT device but it couldn't connect. I guess I'll give armbian another chance & also use another sd card (because the were some situations were it told me....path not found) But the Issues with wifi & BT is everywhere present..., any tipps how to solve this ? Any version recommendation ?
  10. The link to nightly builds for the Rockpi 4C+ WIP on https://www.armbian.com/rockpi4/ is broken. (Perhaps it should link directly to https://github.com/armbian/community ?)
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines