Jump to content

Search the Community

Showing results for tags 'rock64'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • 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. Gentlemen, I have a rock64 board, and I would like to use an external RTC module with DS1307 chip. Unfortunately the armbian kernel does not provide DS1307 driver by default: root@rock64:~# cat /boot/config-4.4.162-rockchip64 | grep DS1307 # CONFIG_RTC_DRV_DS1307 is not set I don't have the programming skills for sending a pull request to enable this module. Could you please enable this module for ROCK64? I believe other ROCK64 owners may also benefit from this driver, as the board does not expose a working RTC, and DS1307 is a very common RTC chip. Thanks in advance.
  2. I have a Rock64 powered by Armbian version 5.60 kernel 4.4.162-rockchip64 Ubuntu Bionic How can I activate i2c0 and i2s0 ports for connecting a 16x2 characters LCD display like 1602LCD and a PCM5102 DAC ? I'm trying armbian-config and I'm reading https://docs.armbian.com/User-Guide_Allwinner_overlays/ but I'm getting no help. Thanks for advance.
  3. So now I am playing with Rock64 4GB. I installed the Armbian_5.65 server edition OS and then installed xorg, lxde, and lxdm., then rebooted into a working system. Final stage of setting up was to test rhythmbox_3.4.2 and there was no sound. pavucontrol > playback shows the app is running and the worm is leaping about, but absolutely no sound. Same playing a .wav file with mpv, or indeed any player. Is there something unusual about the audio socket, or some other limitation. armbianmonitor -u = http://ix.io/ltt0
  4. Hi, the rockchip64 missing the gre modules for ipv4 and ipv6. they had been existing in 4.4.156-rockchip64 /lib/modules/4.4.156-rockchip64/kernel/net/ipv4/gre.ko /lib/modules/4.4.156-rockchip64/kernel/net/ipv4/netfilter/nf_nat_proto_gre.ko /lib/modules/4.4.156-rockchip64/kernel/net/ipv4/ip_gre.ko /lib/modules/4.4.156-rockchip64/kernel/net/netfilter/nf_conntrack_proto_gre.ko /lib/modules/4.4.156-rockchip64/kernel/net/ipv6/ip6_gre.ko is it possible to add these? thx in advance meno
  5. Can someone please help me understand how Armbian for Rock64 is developed? In the past, there was an image for the Rock64 that was a server image, not a desktop image. Now, I see Ubuntu and a Debian Stretch desktop images, no server image. Is there a plan to build a server image going forward? Also, will a newer kernel be built at some point? Not trying to stir the pot or cause trouble, just trying to understand where the Rock64 support is going in the future. Thank you for all the spectacular work the Armbian team does.
  6. Hello. I bought a Rock64 and I have a lot of errors. Im using a eMMC 32GB Storage with Armbian 5.65 stretch 4.4.162 Desktop, Ethernet connection with TP-Link switch, a Wireless Keyboard with touch pad and the original 5V 3A Power Supply. HDMI is connect to a HDMI Splitter/Switch. The Rock64 is placed in the Aluminum casing. Full-Log: http://ix.io/1rce The system is reboot very often before i see the Desktop. Sometimes only after several resets. Can someone help me?
  7. Hello! I've recently installed NextCloudPi, which ships Linux 4.4 by default (linux-image-rockchip64 - Linux kernel, version 4.4.159-rockchip64). Is it OK to update to linux-image-arm64? As far as I understood, mainline Linux supports RK3328 chip since version 4.14. Thanks a lot!
  8. Armbian version: Armbian_5.65_Rock64_Ubuntu_bionic_default_4.4.162 the stuck prompt message: rock64 login: [OK] Started Update UTMP about System Runlevel changes. I MUST press enter key to continue the startup progress, please help me to fix the bug. Thanks very much
  9. Working on the rockchip64 family dev images, since 4.19 is an LTS and the RK3328 support is somewhat workable. With a reminder of something I failed to read by @JMCC, I got this today: ____ _ | _ \ ___ _ __ ___ __ _ __ _ __| | ___ | |_) / _ \ '_ \ / _ \/ _` |/ _` |/ _` |/ _ \ | _ < __/ | | | __/ (_| | (_| | (_| | __/ |_| \_\___|_| |_|\___|\__, |\__,_|\__,_|\___| |___/ Welcome to ARMBIAN 5.65 user-built Debian GNU/Linux 9 (stretch) 4.19.0-rockchip6 4 System load: 0.99 0.55 0.22 Up time: 2 min Memory usage: 3 % of 2000MB IP: CPU temp: 40°C Usage of /: 2% of 117G [ General system configuration (beta): armbian-config ] New to Armbian? Check the documentation first: https://docs.armbian.com Thank you for choosing Armbian! Support: www.armbian.com Building a Rock64 test image as I write this, then checking out the RK3399 boards in my possession. HDMI works after a plug cycle, may need to utilize some of @botfap's script-fu on boot to wake up the interface. Known Issues: Renegade bottom USB2 port is non-functional HDMI needs a friendly reminder to talk to the display Rock64 Same HDMI hickup Top USB2 port is non-functional Boot up your build machines (or launch you virtual ones, whatever) and get hacking!
  10. Your build Armbian 5.65 kernel 4.4 and my build 5.65 the same kernel - system has sound only via HDMI monitor. Is it possible to enabled audio via 3.5 jack or external USB sound card?
  11. Hi! I'm trying to create a vpn access point with a Rock64. I'm receving a low speeds with openvpn but the openssl tests show that there is crypto acceleration. I'm new to all of this. I assume the vpn speeds would be much higher since crypto extensions are enabled in armbian, that's why I choose the Rock64 and Armbian. This is the openssl test: openssl speed -evp aes-256-cbc Doing aes-256-cbc for 3s on 16 size blocks: 14416568 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 64 size blocks: 10625804 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 256 size blocks: 4907054 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 1024 size blocks: 1594735 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 8192 size blocks: 218375 aes-256-cbc's in 3.00s Doing aes-256-cbc for 3s on 16384 size blocks: 109757 aes-256-cbc's in 3.00s OpenSSL 1.1.0f 25 May 2017 built on: reproducible build, date unspecified options:bn(64,64) rc4(char) des(int) aes(partial) blowfish(ptr) compiler: gcc -DDSO_DLFCN -DHAVE_DLFCN_H -DNDEBUG -DOPENSSL_THREADS -DOPENSSL_NO_STATIC_ENGINE -DOPENSSL_PIC -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/lib/ssl\"" -DENGINESDIR="\"/usr/lib/aarch64-linux-gnu/engines-1.1\"" The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes aes-256-cbc 76888.36k 226683.82k 418735.27k 544336.21k 596309.33k 599419.56k My internet speed is around 76 MB download and 19 MB upload. The rock64 without a vpn connection is capable of reaching those speeds but with the openvpn connected and using the same cipher aes-256-cbc these are the results: speedtest-cli Retrieving speedtest.net configuration... Testing from Zare (185.44.76.118)... Retrieving speedtest.net server list... Selecting best server based on ping... Hosted by fdcservers.net (London) [0.96 km]: 38.804 ms Testing download speed................................................................................ Download: 20.42 Mbit/s Testing upload speed.................................................................................................... Upload: 17.88 Mbit/s I've been reading posts from other people talking about speeds of 60 or 80 MB/s through openvpn connections. Is 20MB the maximum speed I will achieve with the Rock64? If not, what should I do? As I said, I'm new to this and I don't know how to proceed, my ideas are that perhaps openvpn is not compiled to use the crypto engine but maybe I'm just talking nonsense. I'm using Armbian Stretch with desktop legacy kernel 4.4.y Thank you very much for your help
  12. Vin

    Rock64 Not booting

    Hello everybody, bought a Rock64 4 GB recently and I´m not able to boot it with any provided armbian Debian/Ubuntu image. With the Ubuntu Image ethernet doesnt seem to be initialized and with Debian there is activity on the eth port, but no connection, neither of the images show any output on the screen. Also i tried various SD-Cards and different image burning programs. Openmediavault works flawlessly, so I can exclude Hardware issues.
  13. I'm considering buying a Rock64 4GB to use a Docker server running media apps (plex,sonarr,radarr,jackett,smb,etc). I already have a 64GB SD card available for this system, probably overkill, but I have it. I noticed another post saying the SD card performance is not what it could be. I'd like to hear from other have a similar setup to what I'm thinking about. Does it perform well enough for what you're using it for? What are you using it for? What kind of samba through put do you get on the USB2 and USB3 (perhaps with the USB3->SATA adapter) Thanks.
  14. Hi there, I'm trying to made a dts file to handle a pican2 hat on ROCK64 armbian, but now I'm stuck. I'm a noob in writing dts files, I've tried to take as exemple dts from RPI and Thinker. edit: I've rebuild the kernel, and build the mcp251x.ko module, it load like a charm. But I assume I've to write a correct .dts file to link it to my devices tree. here is my loaded modules list: Module Size Used by can_bcm 24576 0 can_raw 20480 0 can 53248 2 can_bcm,can_raw mali 262144 0 rt2800usb 28672 0 rt2800lib 81920 1 rt2800usb rt2x00usb 20480 1 rt2800usb rt2x00lib 49152 3 rt2x00usb,rt2800lib,rt2800usb zram 32768 5 lz4_compress 16384 1 zram mcp251x 20480 0 dw_hdmi_i2s_audio 16384 0 can_dev 20480 1 mcp251x binfmt_misc 20480 1 ip_tables 24576 0 x_tables 32768 1 ip_tables autofs4 40960 2 uas 20480 0 usb_storage 61440 1 uas Cannot find device "can0" eth0 lo wlx00c141390c5a And as you can see, there is no can0 devices in /sys/class/net. here is my dts file: /dts-v1/; /plugin/; / { compatible = "rockchip,rk3328", "pine64,rock64"; fragment@0 { target-path = "/spi@ff190000"; //target = <&spi0>; __overlay__ { status="okay"; spidev@0{ status = "disabled"; }; spidev@1{ status = "disabled"; }; }; }; /* the interrupt pin of the can-controller */ fragment@1 { target-path = "/pinctrl/gpio3@ff240000"; //target = <&gpio3>; __overlay__ { can0_pins: can0_pins { rockchip,pins = <0 7 0 &pcfg_pull_none>; //phandle = <1>; }; }; }; /* the clock/oscillator of the can-controller */ fragment@2 { target-path = "/"; __overlay__ { /* external oscillator of mcp2515 on SPI0.0 */ can0_osc: can0_osc { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <16000000>; }; }; }; /* the spi config of the can-controller itself binding everything together */ fragment@3 { target-path = "/spi@ff190000"; //target = <&spi0>; __overlay__ { /* needed to avoid dtc warning */ #address-cells = <1>; #size-cells = <0>; can0: can0@0 { //phandle = <1>; reg = <0>; compatible = "microchip,mcp2515"; pinctrl-names = "default"; pinctrl-0 = <&can0_pins>; //pinctrl-0 = "/pinctrl/gpio3@ff240000/can0_pins/"; spi-max-frequency = <10000000>; interrupt-parent = <&gpio3>; //interrupt-parent = "/pinctrl/gpio3@ff240000"; interrupts = <7 0x2>; // 7 2 //clocks = "/can0_osc"; clocks = <&can0_osc>; }; }; }; }; here is what I can read from dmesg: pi@rock64:/boot/overlay-user$ dmesg | fgrep -i spi [ 0.199580] bus: 'spi': registered [ 0.199591] device class 'spi_master': registering [ 0.215439] device: 'ff190000.spi': device_add [ 0.215471] bus: 'platform': add device ff190000.spi [ 0.215560] PM: Adding info for platform:ff190000.spi [ 2.069101] bus: 'spi': add driver cros-ec-spi [ 2.069297] device class 'spi_transport': registering [ 2.069329] device class 'spi_host': registering [ 2.070797] bus: 'spi': add driver m25p80 [ 2.070861] device class 'spidev': registering [ 2.070890] bus: 'spi': add driver spidev [ 2.070956] bus: 'platform': add driver rockchip-spi [ 2.071145] bus: 'platform': driver_probe_device: matched device ff190000.spi with driver rockchip-spi [ 2.071162] bus: 'platform': really_probe: probing driver rockchip-spi with device ff190000.spi [ 2.071495] rockchip-spi ff190000.spi: no init pinctrl state [ 2.071552] rockchip-spi ff190000.spi: no sleep pinctrl state [ 2.071566] rockchip-spi ff190000.spi: no idle pinctrl state [ 2.071795] rockchip-spi ff190000.spi: no high_speed pinctrl state [ 2.071820] device: 'spi32766': device_add [ 2.072075] PM: Adding info for No Bus:spi32766 [ 2.072326] device: 'spi32766.0': device_add [ 2.072362] bus: 'spi': add device spi32766.0 [ 2.072582] PM: Adding info for spi:spi32766.0 [ 2.072661] rockchip-spi ff190000.spi: chipselect 0 already in use [ 2.072675] spi_master spi32766: spi_device register error /spi@ff190000/flash@0 [ 2.072692] spi_master spi32766: Failed to create SPI device for /spi@ff190000/flash@0 [ 2.072709] driver: 'rockchip-spi': driver_bound: bound to device 'ff190000.spi' [ 2.072758] bus: 'platform': really_probe: bound device ff190000.spi to driver rockchip-spi [ 8.643523] bus: 'spi': add driver mcp251x [ 8.643560] bus: 'spi': driver_probe_device: matched device spi32766.0 with driver mcp251x [ 8.643570] bus: 'spi': really_probe: probing driver mcp251x with device spi32766.0 [ 8.643678] mcp251x spi32766.0: no pinctrl handle [ 8.646051] mcp251x spi32766.0: Looking up vdd-supply from device tree [ 8.646071] mcp251x spi32766.0: Looking up vdd-supply property in node /spi@ff190000/can0@0 failed [ 8.648100] mcp251x spi32766.0: Looking up xceiver-supply from device tree [ 8.648120] mcp251x spi32766.0: Looking up xceiver-supply property in node /spi@ff190000/can0@0 failed [ 8.661924] mcp251x: probe of spi32766.0 rejects match -19 pi@rock64:/boot/overlay-user$ help me plz.
  15. /proc/sys/crypto doesn't exist, so anything checking the status of /proc/sys/crypto/fips_enabled fails terribly. (Specifically trying to bring up a FreeIPA server which includes tomcat-based Dogtag CA, it checks for FIPS during setup, dies). I see there is an rk_crypto kernel module available, so I don't know why /proc/sys/crypto itself is missing. I tried 'modprobe rk_crypto' and it loaded (appears in output of 'lsmod'), but /proc/sys/crypto still doesn't exist.
  16. Dear all, i have been using Armbian bionic currently running kernel 4.4.156-rockchip64, for sharing files over the internet, i am currently using sshfs. Openssl benchmark ls as followed OpenSSL 1.1.0g 2 Nov 2017 built on: reproducible build, date unspecified options:bn(64,64) rc4(char) des(int) aes(partial) blowfish(ptr) compiler: gcc -DDSO_DLFCN -DHAVE_DLFCN_H -DNDEBUG -DOPENSSL_THREADS -DOPENSSL_NO_STATIC_ENGINE -DOPENSSL_PIC -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/lib/ssl\"" -DENGINESDIR="\"/usr/lib/aarch64-linux-gnu/engines-1.1\"" The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes 16384 bytes aes-256-cbc 89554.02k 252995.50k 458589.18k 588922.54k 641851.39k 637659.82k However, when it comes to sshfs speeds, i can only reach around 20-25MBytes per second > fallocate -l 1G /tmp/largefile > pv /tmp/largefile > /srv/tmp/test_largefile 1.00GiB 0:00:46 [22.0MiB/s] [==============================================================================================================================================>] 100% Do i need AF_ALG to actually speedup sshfs speed? or is this board not fast enough to achieve higher sshfs speeds? Note : the cpu loading is not that high on sshfs copying Thanks a lot for your help
  17. Luks encrypted devices need this cipher: aes-xts-plain64 I get these error messages: > Check that kernel supports aes-xts-plain64 cipher > device-mapper: table: 254:0: crypt: Error allocating crypto tfm It seems that at least the following modules are needed: xts, aes-x86_64 They are misising in all armbian debian kernals for rockchip. Could you please add them?
  18. The wireless interfaces are not coming up [ 16.959456] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 16.969238] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 16.971635] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 16.971650] cfg80211: failed to load regulatory.db [ 41.751941] rk_gmac-dwmac ff540000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off [ 41.751976] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  19. Hi, I received my new rock64 today and I downloaded this image https://dl.armbian.com/rock64/Debian_stretch_default_desktop.7z I used Etcher as recommended to create the SD card and booted off of it with just power and network connected as I assumed it would boot, assign a dhcp address and bring up sshd so I could remote onto it. I scanned my network to see if any new devices had been added with dhcp, but couldn't see anything new so I connected the rock64 up to a TV and then booted it up, connected up a keyboard and noticed it ran through an install process on first local login. I followed all the directions and a desktop appeared on screen. However, there was no network connectivity so I had a look at /etc/network/interfaces and could see that nothing at all had been set for eth0. Only the loopback interface was defined. I manually edited /etc/network/interfaces and added my eth0 static IP config in there and rebooted and the eth0 network came up as expected. source /etc/network/interfaces.d/* # Network is managed by Network manager auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet static address 10.0.0.42/24 gateway 10.0.0.2 dns-nameservers 10.0.0.2 Is this expected behaviour for the rock64 Debian image? In that, you have to manually configure eth0 after running through the install process or is this a bug? Thanks very much for your help and for maintaining a distribution for the rock64.
  20. Trying to choose between an eMMC module or a USB Flash drive for the boot volume on a Rock64. I have a few Rock64's that I'm building as various services (Nextcloud, Pi-Hole, VPN, OMV, and/or Netatalk Backup). None of these devices will need large boot volumes as the data will be in secondary (Hard or SSD) Drives or will require VERY little data storage. On the RPi's that the Rock64's are replacing, I've been using USB Flash drives for booting. I get the feeling that an eMMC module is a better choice, but do have any real knowledge. Are the eMMC modules more reliable and less prone to corruption that USB Flash Drives? I do have some 32GB and 64GB eMMC models from Pine64 and am going to try them out shortly. Any thoughts and advice? Thank you all in advance. Armbian ROCKS!
  21. As discussed on multiple threads, the aim of this thread is to bring all RockChip devices under one BSP (4.4) Kernel. This discussion can be found (partly): and a bit background here: https://github.com/rockchip-linux/kernel/issues/98 Cause I'm not willing to cut out all this stuff from the related threads (this would end in a complete disaster) I try to summarize it here (if something is missing, let me know I'll add it): RockChips BSP kernel is not longer an option. Cause it breaks faster that our current resources allow to fix it. Having all SoCs under one kernelsource would make it more predictable and decrease the efforts needed to keep them 'reliable working'. Ayufans (https://github.com/ayufan-rock64/linux-kernel/tree/release-4.4) tends to be the preferred Kernel at the moment. First attempts to bring up rk3288 boards are made notify some of the involved people just to make sure they don't miss it (I probably miss some, don't be upset ): @TonyMac32, @JMCC, @tkaiser, @Igor, @zador.blood.stained, @hjc & @ayufan Some questions which are open for me: How can we ensure that the 4.4 kernel we currently use for the RK3288 get at least 'security updates' as long as the switch needs? Is someone in touch with ayufan so that he recognizes our idea? (or @ayufan do you read the stuff here ) Can we 'channel our efforts' to ensure that we don't waste our and others time (e.g. open a transitions branch and make it clear that PRs against the old kernels don't make sense) I hope this thread doesn't get floated with garbage but on the other side I hope that people write about their plans and 'results' so that we don't do the work twice. EDIT: BTW, I'm not sure if this thread fits better in development or here, but I think it's more recognized by the rk-users when we have it here..
  22. I'm building a portable battery powered NAS because syncing and having everything multiple times on all my Android devices sucks. I took my old Banana Pi connected a SSD to the SATA port and made it a access point (no Samba yet installed). Booting from the 16GB SanDisk Ultra A1 is 27 seconds. Moving everything to the SSD in armbian config is also 27 seconds (no difference?) I know the Banana has not the fastest SATA and NIC and that USB 3 on the Rock64 is faster. But i don't copy tons of gigabyte to the device everyday and for streaming over the WiFi stick it's fast enough. I'm interested on the boot time of the Rock64 (eMMC or USB/SSD). If its not much faster then i see no reason to by a Rock64 for that. Also the Banana has the advantage that you can solder a battery to it.
  23. Hello, Each time I'm booting the Rock64, it starts on Jan, 21 of 2016 but the filesystem has a superblock on Jan,28 of 2018, so in the future. It's inconsistant and the filesystem is checking each time and I'm waiting a few seconds. How can I avoid this trouble ? Here is the screen shot of logs through the tty/usb console. I'm booting from the spi flash and a sd-card with Ubuntu 18.04.1.
  24. Hello I recently set up NextCloudPlus/NextCloudPi on a Rock64. I used the image that can be downloaded from the ownyourbits website, cat /etc/*-release resulted in the following output: BOARD=rock64 BOARD_NAME="ROCK64" BOARDFAMILY=rk3328 VERSION=5.44 LINUXFAMILY=rk3328 BRANCH=default ARCH=arm64 IMAGE_TYPE=user-built BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image 03af3b07-6131-4b1c-8cc2-7f716caf75e1 # PLEASE DO NOT EDIT THIS FILE BOARD=rock64 BOARD_NAME="ROCK64" BOARDFAMILY=rk3328 VERSION=5.44 LINUXFAMILY=rk3328 BRANCH=default ARCH=arm64 IMAGE_TYPE=user-built BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image PRETTY_NAME="Debian GNU/Linux 9 (stretch)" NAME="Debian GNU/Linux" VERSION_ID="9" VERSION="9 (stretch)" ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" Now, I wanted to use rtcwake to automatically shut down or suspend my server during night. I tested the states off, suspend-to-disk and suspend-to-ram. The first two did not work at all (-m disk was not recognized and when completly switching off, it did not wake). Probably they are not supported by the device. Suspend-to-Ram (-m mem) did work, however, after my Rock64 woke, I was unable to communicate with it. Both the NextCloudPi web interface and ssh are unreachable, then until i manually restart the device using the power connection. This is a link to a section out of my system log that I think is important (I think it is when rtcwake was launched, the command was sudo rtcwake -m mem -s 300, if I remember the time correctly). I already posted this question in the NextCloud forum and they told me that I may have better chances here. Does anybody know how to solve this issue? Thanks in advance for any help.
  25. I'm trying to switch the upper USB port to peripheral mode so I can use the ethernet gadget on it. Has anyone done anything like that before? I've got an issue here https://github.com/ayufan-rock64/linux-build/issues/117 with some of the things I've tried already.
×
×
  • Create New...