Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 30,105
» Latest member: kiwigoldfish
» Forum threads: 16,361
» Forum posts: 117,529

Full Statistics

Latest Threads
Pinephone software
Forum: General Discussion on PinePhone
Last Post: Csanderson0313
8 hours ago
» Replies: 0
» Views: 37
PineNote v1.2 - Charges N...
Forum: General Discussion on Pinebook Pro
Last Post: ttsp
07-02-2026, 02:52 AM
» Replies: 0
» Views: 106
How to change the PineNot...
Forum: General Discussion on PineNote
Last Post: cameronharring
07-01-2026, 12:22 PM
» Replies: 0
» Views: 67
PinePhone Pro disable Vol...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
07-01-2026, 10:53 AM
» Replies: 1
» Views: 1,542
Star64/Starpro64 kernel b...
Forum: General
Last Post: tgbgreen
06-30-2026, 12:17 PM
» Replies: 1
» Views: 2,167
Manjaro affected by Arch ...
Forum: General
Last Post: tantamount
06-28-2026, 10:45 AM
» Replies: 0
» Views: 234
Fix Bricked SPI Flash, Pi...
Forum: PinePhone Pro Hardware
Last Post: FR_IV
06-27-2026, 05:00 PM
» Replies: 0
» Views: 156
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
06-27-2026, 04:09 PM
» Replies: 12
» Views: 19,634
irradium (based on crux l...
Forum: Linux on Rock64
Last Post: mara
06-27-2026, 02:43 PM
» Replies: 13
» Views: 18,830
Android Gaming Image
Forum: Game Station Emulation
Last Post: Jacobgilbert
06-26-2026, 07:06 AM
» Replies: 52
» Views: 111,245

 
Exclamation WiFi/BT module - Any images with support?
Posted by: duckkcud - 08-31-2018, 06:22 PM - Forum: Linux on RockPro64 - Replies (1)

Reading the release:

  • 0.7.8: Disable sdio (no wifi/bt) to fix pcie/nvme support on 4.4 for RockPro64,
This is the first mention that I saw. Shouldn't prior releases be unaffected?

I tried 7.7 and it was disabled.


  Creating bootable Debian backup image
Posted by: Drago - 08-31-2018, 03:01 PM - Forum: Getting Started - Replies (3)

Hi all,

I'd like to periodically create backup images of Debian (stretch-minimal-rockpro64-0.7.9-1067) because I end up breaking my system a lot (I am a brand new to Linux). How would I go about doing this? Could I take an image of my microSD while it's connected to my macbook pro, or do I have to do this from the Debian command line?

-D


Sad Noob connecting to internet
Posted by: splash131 - 08-31-2018, 01:00 PM - Forum: General Discussion on ROCKPRO64 - Replies (3)

I am just starting with my rockpro64 and I have an lxde ubuntu on an emmc 64G
My unit is the 4gB version. I bought the wif bt mimo module but have had no success setting it up on my home network
Please offer some direction. The wlan is not showing up in ip a, after initial boot.


  Android 8.1 Released
Posted by: Luke - 08-31-2018, 09:00 AM - Forum: Android on RockPro64 - Replies (15)

An Android 8.1 release is now available for the RockPro64.
Two image versions are available - on for dd and one for rkflashtools


  Reboot problem
Posted by: Drago - 08-30-2018, 09:05 AM - Forum: Linux on RockPro64 - Replies (1)

Hi all,

I'm very new to using Linux so please bear with me. I have stretch-minimal-rockpro64-0.7.9-1067 installed on my rockpro64. Sometimes when I uninstall packages (for example, pivpn) I am asked to reboot my system. But when I reboot and try to ssh back in, I am unable to ("Operation timed out"). I assume the system has not rebooted and I have to manually press the reset switch. However, this would be inconvenient if I wanted to access my rockpro64 from another location and did not have physical access to the box. Could anyone recommend a solution?

Thanks,

-D


  Rock64 - can not connect via store's USB-to-serial nor see (if) booting.
Posted by: jovval - 08-30-2018, 06:50 AM - Forum: Linux on Rock64 - Replies (5)

My attempts (five steps) and my question follow.


1.    With the store's USB adapter, I have flashed eMMC 16GB using Etcher on a Windows 7 laptop with the image in the second link that follows.
https://etcher.io/
https://github.com/ayufan-rock64/linux-b...m64.img.xz

2.    I have put the eMMC in my Rock64.

3.    I have wired and connected the store's USB-to-serial adapter and my Rock64.
    On USB-to-serial adapter (pins at right):
Jumper is south (facing me) and set on east pair of pins, S1 and 3V3.
GND: black (goes to GND on Rock64's PI-2 bus)
RTX: brown (goes to TXD on Rock64's PI-2 bus)
TXD: white (goes to RTX on Rock64's PI-2 bus)
3V3: red (most northward cable) - NOT CONNECTED to Rock64
    On Rock64, PI-2 bus (long set of pins) is most northward; HDMI is south; GigE/USB is east.
    Bottom (southern) pins are numbered odd starting at 1 (going to 39); top (northern) pins are numbered even starting at 2 (going to 40). See,
    bottom (southern) pin (this is the leftmost one):
1  3.3V PWR - DO NOT use. See Serial Console for the Rock64 - https://forum.pine64.org/showthread.php?tid=4928 - NO EXPLANATION given for why!
    top (northern) pins:
6  GND: black (goes to GND on USB adapter)
8  TXD: brown (goes to RTX on USB adapter)
10 RTX: white (goes to TXD on USB adapter)
    Executive Summary:
USB    Rock64
GND <---> GND
Rx <---> Tx
Tx <---> Rx

4.    I have tried putty on Windows 7 (to no avail), and then minicom on Debian, and now Raspian.
    Upon plugging in USB-to-serial adapter on Debian, I saw/see a red led (and iirc, a light blue led next to it, at  least on Debian)
# dmesg | tail -n 10
    gave
# usb 6-1: ch341-uart converter now attached to ttyUSB0
    I issued
# minicom -s -D /dev/ttyUSB0 -b 1500000
    which returned (for both Debian and now Raspian)
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on May  7 2017, 05:18:49.
Port /dev/ttyUSB0, 14:19:34

Press CTRL-A Z for help on special keys

5. I plugged in power which lit an additional led on the Rock64. I see no change at my console (minicom).

ADDENUM: blue led is lit @RPi too; HDMI connected but monitor shows nothing.

QUESTION: What did I omit/do wrong, or what should I be doing next (or should have done before)?


  Customize Android 6.0
Posted by: Tanveer - 08-29-2018, 11:54 AM - Forum: Android on Pine A64(+) - Replies (1)

Dear Manager,

I am new to Android Source code.

I have to customize Android 6.0: remove all the apks/apps and Add my own apk/app.

Please guide me the steps, how can I do it. where to make changes in source code or make files.

Regards,

Tanveer


  ARM CPU Stress Test
Posted by: jzhang18 - 08-29-2018, 10:32 AM - Forum: Linux on RockPro64 - Replies (14)

I saw this thread:
https://core-electronics.com.au/tutorial...ry-pi.html

sudo apt-get install stress
wget https://raw.githubusercontent.com/ssvb/c...burn-a53.S
gcc -o cpuburn-a53 cpuburn-a53.S

For Raspberry PI 3,  there are 4 A53 cores only.  for RockPro64.   How to test the other A72 cores? 

Can I use cpuburn-a53 to test A72 cores?


  USB OTG?
Posted by: stuartiannaylor - 08-28-2018, 10:38 PM - Forum: General Discussion on ROCKPRO64 - Replies (1)

Which port is the OTG port?

Many thanks


  Issues with both Deb and Ubuntu
Posted by: germanshep - 08-28-2018, 05:47 PM - Forum: Linux on Pine A64(+) - No Replies

On my first board here and been trying to do some creative googling and getting no where.....After first install on both the Deb image and Ubuntu images(64 bit) I get several mmcblk1 errors as follows....card should be fine, works perfectly in Pi2b/3b

Code:
rock64@rock64:~$ cat /var/log/syslog | grep err
Jul 21 21:08:22 rock64 kernel: [    0.000000] CPU features: enabling workaround for ARM erratum 845719
Jul 21 21:08:22 rock64 kernel: [    0.546183] vcc_sys: could not add device link regulator.4 err -2
Jul 21 21:08:22 rock64 kernel: [    1.180019] kvm [1]: interrupt-controller@ff814000 IRQ44
Jul 21 21:08:22 rock64 kernel: [    2.406223] vcc_sys: could not add device link regulator.5 err -2
Jul 21 21:08:22 rock64 kernel: [    2.409981] vcc_sys: could not add device link regulator.6 err -2
Jul 21 21:08:22 rock64 kernel: [    2.413227] vcc_sys: could not add device link regulator.7 err -2
Jul 21 21:08:22 rock64 kernel: [    2.415598] vcc_sys: could not add device link regulator.8 err -2
Jul 21 21:08:22 rock64 kernel: [    2.418477] vcc_io: could not add device link regulator.9 err -2
Jul 21 21:08:22 rock64 kernel: [    2.422335] vcc_io: could not add device link regulator.10 err -2
Jul 21 21:08:22 rock64 kernel: [    2.426337] vcc_sys: could not add device link regulator.11 err -2
Jul 21 21:08:22 rock64 kernel: [    3.326989] sdhci: Copyright(c) Pierre Ossman
Jul 21 21:08:22 rock64 kernel: [    5.155562] ttyS2 - failed to request DMA, use interrupt mode
Jul 21 21:08:22 rock64 kernel: [    5.697333] vdd_logic: could not add device link ff300000.gpu err -17
Jul 21 21:08:22 rock64 kernel: [    7.343826] mmcblk1: error -5 transferring data, sector 265264, nr 216, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [    7.465794] mmcblk1: error -5 transferring data, sector 265264, nr 216, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [    7.613125] mmcblk1: error -5 transferring data, sector 3211296, nr 224, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [    7.826677] mmcblk1: error -5 transferring data, sector 3211296, nr 224, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [    7.968141] mmcblk1: error -5 transferring data, sector 275232, nr 232, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [    8.265202] mmcblk1: error -5 transferring data, sector 1020424, nr 136, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [    8.507798] mmcblk1: error -5 transferring data, sector 268304, nr 96, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [    8.714527] mmcblk1: error -5 transferring data, sector 1007792, nr 136, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [    8.877894] mmcblk1: error -5 transferring data, sector 1007792, nr 136, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [    9.101895] mmcblk1: error -84 transferring data, sector 3252656, nr 112, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [    9.381547] mmcblk1: error -5 transferring data, sector 991264, nr 200, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [    9.607938] mmcblk1: error -5 transferring data, sector 991264, nr 200, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [    9.758450] mmcblk1: error -5 transferring data, sector 3213520, nr 256, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [    9.990317] mmcblk1: error -5 transferring data, sector 3213520, nr 256, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   10.142110] mmcblk1: error -5 transferring data, sector 3211520, nr 256, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [   10.340877] mmcblk1: error -5 transferring data, sector 3213776, nr 192, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   10.481192] mmcblk1: error -5 transferring data, sector 3213776, nr 192, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   11.089348] mmcblk1: error -5 transferring data, sector 269088, nr 232, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [   11.282167] mmcblk1: error -5 transferring data, sector 3699456, nr 32, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   11.402387] mmcblk1: error -5 transferring data, sector 3699456, nr 32, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   11.455316] mmcblk1: error -5 transferring data, sector 3360968, nr 104, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [   11.605523] mmcblk1: error -84 transferring data, sector 1400216, nr 136, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   11.753621] mmcblk1: error -5 transferring data, sector 1397640, nr 256, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   12.079896] mmcblk1: error -5 transferring data, sector 290056, nr 256, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   15.067747] mmcblk1: error -5 transferring data, sector 3181240, nr 240, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [   15.523452] mmcblk1: error -5 transferring data, sector 267784, nr 8, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   16.177910] dwmmc_rockchip ff500000.dwmmc: Unexpected interrupt latency
Jul 21 21:08:22 rock64 kernel: [   16.204864] mmcblk1: error -5 transferring data, sector 1471592, nr 56, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   16.430114] mmcblk1: error -5 transferring data, sector 1025912, nr 248, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   16.485075] mmcblk1: error -5 transferring data, sector 1025128, nr 32, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   16.724921] dwmmc_rockchip ff500000.dwmmc: Unexpected interrupt latency
Jul 21 21:08:22 rock64 kernel: [   16.909081] mmcblk1: error -5 transferring data, sector 3181856, nr 64, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   17.008933] dwmmc_rockchip ff500000.dwmmc: Unexpected interrupt latency
Jul 21 21:08:22 rock64 kernel: [   17.026930] dwmmc_rockchip ff500000.dwmmc: Unexpected interrupt latency
Jul 21 21:08:22 rock64 kernel: [   17.044915] dwmmc_rockchip ff500000.dwmmc: Unexpected interrupt latency
Jul 21 21:08:22 rock64 kernel: [   17.320930] dwmmc_rockchip ff500000.dwmmc: Unexpected interrupt latency
Jul 21 21:08:22 rock64 kernel: [   17.516330] mmcblk1: error -84 transferring data, sector 1031840, nr 136, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   19.194723] mmcblk1: error -5 transferring data, sector 1001592, nr 120, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   19.341256] mmcblk1: error -5 transferring data, sector 1029632, nr 32, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [   19.465169] mmcblk1: error -5 transferring data, sector 3768320, nr 256, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   19.538940] mmcblk1: error -5 transferring data, sector 3768320, nr 256, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   19.679183] mmcblk1: error -84 transferring data, sector 269360, nr 208, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [   19.748753] mmcblk1: error -84 transferring data, sector 269360, nr 208, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   20.063339] mmcblk1: error -84 transferring data, sector 3215392, nr 56, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [   20.320405] mmcblk1: error -5 transferring data, sector 3772624, nr 256, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   20.389313] mmcblk1: error -84 transferring data, sector 3772624, nr 256, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   20.569071] mmcblk1: error -5 transferring data, sector 3766336, nr 256, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [   26.236996] mmcblk1: error -5 transferring data, sector 1027864, nr 224, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [   26.418093] mmcblk1: error -5 transferring data, sector 3214368, nr 224, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   26.581754] mmcblk1: error -5 transferring data, sector 1566784, nr 32, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   26.674998] mmcblk1: error -5 transferring data, sector 1454576, nr 32, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   26.872129] mmcblk1: error -84 transferring data, sector 1419208, nr 144, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   27.015751] mmcblk1: error -5 transferring data, sector 1417248, nr 256, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   27.115733] mmcblk1: error -5 transferring data, sector 1417248, nr 256, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   27.198200] mmcblk1: error -84 transferring data, sector 1417319, nr 185, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   27.433301] mmcblk1: error -5 transferring data, sector 1523560, nr 200, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [   28.984400] mmcblk1: error -5 transferring data, sector 1435816, nr 136, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [   29.839149] mmcblk1: error -5 transferring data, sector 1983024, nr 224, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   29.928741] mmcblk1: error -5 transferring data, sector 3185696, nr 224, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   30.004381] mmcblk1: error -5 transferring data, sector 3185696, nr 224, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   30.171146] mmcblk1: error -5 transferring data, sector 3243712, nr 144, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [   30.259272] mmcblk1: error -5 transferring data, sector 3243712, nr 144, cmd response 0x900, card status 0x0
Jul 21 21:08:22 rock64 kernel: [   30.384478] mmcblk1: error -84 transferring data, sector 1002832, nr 16, cmd response 0x900, card status 0xb00
Jul 21 21:08:22 rock64 kernel: [   30.476076] mmcblk1: error -84 transferring data, sector 3240480, nr 512, cmd response 0x900, card status 0x0
Jul 21 21:08:23 rock64 kernel: [   30.690737] mmcblk1: error -5 transferring data, sector 1271200, nr 224, cmd response 0x900, card status 0x0
Jul 21 21:08:23 rock64 kernel: [   30.886311] mmcblk1: error -84 transferring data, sector 1397328, nr 136, cmd response 0x900, card status 0x0
Jul 21 21:08:24 rock64 kernel: [   32.483706] mmcblk1: error -5 transferring data, sector 1395968, nr 224, cmd response 0x900, card status 0xb00
Jul 21 21:08:25 rock64 kernel: [   32.558287] mmcblk1: error -5 transferring data, sector 1395968, nr 224, cmd response 0x900, card status 0x0
Jul 21 21:08:27 rock64 kernel: [   34.762659] mmcblk1: error -5 transferring data, sector 1436184, nr 256, cmd response 0x900, card status 0xb00
Jul 21 21:08:27 rock64 kernel: [   34.877391] mmcblk1: error -84 transferring data, sector 1447712, nr 200, cmd response 0x900, card status 0xb00
Jul 21 21:08:27 rock64 kernel: [   35.500603] mmcblk1: error -5 transferring data, sector 1335808, nr 224, cmd response 0x900, card status 0x0
Jul 21 21:08:28 rock64 kernel: [   36.196391] mmcblk1: error -5 transferring data, sector 1044176, nr 224, cmd response 0x900, card status 0x0
Jul 21 21:08:28 rock64 kernel: [   36.260766] mmcblk1: error -5 transferring data, sector 1044176, nr 224, cmd response 0x900, card status 0x0
Jul 21 21:08:29 rock64 kernel: [   37.188665] mmcblk1: error -5 transferring data, sector 2031648, nr 224, cmd response 0x900, card status 0xb00
Aug 28 23:10:19 rock64 kernel: [   69.238218] mmcblk1: error -84 transferring data, sector 1456488, nr 32, cmd response 0x900, card status 0xb00
Aug 28 23:10:19 rock64 kernel: [   69.331273] mmcblk1: error -5 transferring data, sector 1003504, nr 24, cmd response 0x900, card status 0x0
Aug 28 23:10:26 rock64 kernel: [   75.489166] mmcblk1: error -115 sending stop command, original cmd response 0x900, card status 0x400900
Aug 28 23:10:26 rock64 kernel: [   75.489179] mmcblk1: error -84 transferring data, sector 279296, nr 8, cmd response 0x900, card status 0x0
Aug 28 23:10:26 rock64 kernel: [   75.557069] mmcblk1: error -5 transferring data, sector 277264, nr 48, cmd response 0x900, card status 0x0
Aug 28 23:10:26 rock64 kernel: [   75.643106] mmcblk1: error -5 transferring data, sector 279064, nr 232, cmd response 0x900, card status 0x0
Aug 28 23:10:26 rock64 kernel: [   76.358160] mmcblk1: error -5 transferring data, sector 1104448, nr 144, cmd response 0x900, card status 0x0
Aug 28 23:10:28 rock64 kernel: [   77.530206] mmcblk1: error -5 transferring data, sector 2391608, nr 144, cmd response 0x900, card status 0x0
Aug 28 23:10:28 rock64 kernel: [   77.580228] mmcblk1: error -5 transferring data, sector 2391608, nr 144, cmd response 0x900, card status 0x0
Aug 28 23:10:28 rock64 kernel: [   77.663996] mmcblk1: error -5 transferring data, sector 2390272, nr 256, cmd response 0x900, card status 0xb00
Aug 28 23:10:28 rock64 kernel: [   77.716422] mmcblk1: error -5 transferring data, sector 2390272, nr 256, cmd response 0x900, card status 0x0
Aug 28 23:11:23 rock64 kernel: [  132.781444] mmcblk1: error -5 transferring data, sector 1515104, nr 144, cmd response 0x900, card status 0x0
Aug 28 23:11:38 rock64 kernel: [  147.686941] mmcblk1: error -5 transferring data, sector 3226808, nr 136, cmd response 0x900, card status 0x0
Aug 28 23:11:38 rock64 kernel: [  147.765620] mmcblk1: error -5 transferring data, sector 3224056, nr 256, cmd response 0x900, card status 0x0
Aug 28 23:11:38 rock64 kernel: [  147.814748] mmcblk1: error -5 transferring data, sector 3224056, nr 256, cmd response 0x900, card status 0x0
Aug 28 23:11:39 rock64 systemd-resolved[370]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Aug 28 23:11:41 rock64 kernel: [  150.674709] mmcblk1: error -5 transferring data, sector 3270984, nr 32, cmd response 0x900, card status 0x0
Aug 28 23:18:20 rock64 systemd-resolved[370]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Aug 28 23:23:11 rock64 apt-helper[3163]: E: Sub-process nm-online returned an error code (1)
Aug 28 23:23:58 rock64 kernel: [  888.049388] mmcblk1: error -84 transferring data, sector 3377544, nr 120, cmd response 0x900, card status 0xb00
Aug 28 23:25:16 rock64 kernel: [  966.197638] mmcblk1: error -5 transferring data, sector 1612752, nr 136, cmd response 0x900, card status 0x0
Aug 28 23:25:16 rock64 kernel: [  966.284395] mmcblk1: error -5 transferring data, sector 1329824, nr 256, cmd response 0x900, card status 0x0
Aug 28 23:25:16 rock64 kernel: [  966.350188] mmcblk1: error -5 transferring data, sector 1330080, nr 256, cmd response 0x900, card status 0x0
Aug 28 23:25:44 rock64 kernel: [  993.626073] mmcblk1: error -5 transferring data, sector 1526040, nr 32, cmd response 0x900, card status 0x0
Aug 28 23:28:19 rock64 kernel: [    0.000000] CPU features: enabling workaround for ARM erratum 845719
Aug 28 23:28:19 rock64 kernel: [    0.546217] vcc_sys: could not add device link regulator.4 err -2
Aug 28 23:28:19 rock64 kernel: [    1.179789] kvm [1]: interrupt-controller@ff814000 IRQ44
Aug 28 23:28:19 rock64 kernel: [    2.406169] vcc_sys: could not add device link regulator.5 err -2
Aug 28 23:28:19 rock64 kernel: [    2.409285] vcc_sys: could not add device link regulator.6 err -2
Aug 28 23:28:19 rock64 kernel: [    2.411846] vcc_sys: could not add device link regulator.7 err -2
Aug 28 23:28:19 rock64 kernel: [    2.414217] vcc_sys: could not add device link regulator.8 err -2
Aug 28 23:28:19 rock64 kernel: [    2.416723] vcc_io: could not add device link regulator.9 err -2
Aug 28 23:28:19 rock64 kernel: [    2.420538] vcc_io: could not add device link regulator.10 err -2
Aug 28 23:28:19 rock64 kernel: [    2.424535] vcc_sys: could not add device link regulator.11 err -2
Aug 28 23:28:19 rock64 kernel: [    3.324544] sdhci: Copyright(c) Pierre Ossman
Aug 28 23:28:19 rock64 kernel: [    5.146434] ttyS2 - failed to request DMA, use interrupt mode
Aug 28 23:28:19 rock64 kernel: [    5.860813] vdd_logic: could not add device link ff300000.gpu err -17
Aug 28 23:28:19 rock64 kernel: [    8.248957] dwmmc_rockchip ff500000.dwmmc: Unexpected interrupt latency
Aug 28 23:28:19 rock64 kernel: [    9.887153] mmcblk1: error -5 transferring data, sector 2490400, nr 256, cmd response 0x900, card status 0x0
Aug 28 23:28:19 rock64 kernel: [   11.007181] mmcblk1: error -5 transferring data, sector 2416728, nr 256, cmd response 0x900, card status 0x0
Aug 28 23:28:23 rock64 kernel: [   18.042011] mmcblk1: error -5 transferring data, sector 1416136, nr 32, cmd response 0x900, card status 0xb00
Aug 28 23:33:09 rock64 kernel: [  308.868068] mmcblk1: error -5 transferring data, sector 2116128, nr 136, cmd response 0x900, card status 0xb00
Would love to know if Im doing something wrong!(Know I probably am)