Hey guys, Linux newbie here. I got my Rock64 running with the new ubuntu image (xenial-mate-rock64-0.5.5-93-arm64.img.xz) and I'm trying to compile the Wifi+BT driver for my combo USB dongle. I cloned the git repo (Git) and tried compile it with "sudo make", but I keep getting an error. Anybody here can help me out?
Code:
rock64@rock64:~/.git/rtl8723bu$ sudo make
[sudo] password for rock64:
make ARCH=aarch64 CROSS_COMPILE= -C /lib/modules/4.4.77-rockchip-ayufan-93/build M=/home/rock64/.git/rtl8723bu modules
make[1]: Entering directory '/usr/src/linux-headers-4.4.77-rockchip-ayufan-93'
Makefile:634: arch/aarch64/Makefile: No such file or directory
make[1]: *** No rule to make target 'arch/aarch64/Makefile'. Stop.
make[1]: Leaving directory '/usr/src/linux-headers-4.4.77-rockchip-ayufan-93'
Makefile:321: recipe for target 'modules' failed
make: *** [modules] Error 2
I already tried installing the linux-headers from ayufans repo with dpkg, didn't help. The same command works on my normal ubuntu PC.
hi. i have a yuntab B102(tulip-p1) tablet with an allwinner chipset that is stuck on the initial boot screen. i can enter recovery, but nothing in it resolves anything...
1. rebooting to bootloader freezes at the initial boot screen
2. factory reset works, but doesn't help
3. mounting system the 1st time actually caused this problem for some reason. no modifying.
i have tried the (HDMI version) marshmallow firmware(that's what it came with) rooted and no root. all i get is a blank screen when trying to boot. i don't know what else to do.
My pinebook arrived today and I am very happy with its look and am happily running android 7.1 now. Still one thing that's bother me a lot is that the spacebar must be pushed exactly the center (around 1.5~2 cm) in order to have pinebook to register a keystroke. I used to place my thumb on the 1/3 of the left (and right) of the spacebar when I am typing, this is killing me that now every single spacebar I hit it's not taken by the pinebook.
Am I getting a defective pinebook or this is the usual case?
I don't know why I can only boot once. If I just unplug the power, I cannot boot the second time when I power it on.
I use a Linux image which is called stretch-minimal-rock64-0.4.16-83-arm64.
(08-28-2017, 04:29 PM)fbms Wrote: I don't know why I can only boot once. If I just unplug the power, I cannot boot the second time when I power it on.
I use a Linux image which is called stretch-minimal-rock64-0.4.16-83-arm64.
Actually, when I boot the board on the second time I have to unplug the HDIM wire and replug it into the board. I don't know it's a problem of my TV ( I use a TV) or it's a problem of the Linux image. Anyway if you meet the same problem just try what I said.
I also use ‘USB image tool’ to write the image. It works great.
What does work?
- eMMC and SD,
- GbE ethernet, 100M ethernet,
- PXE and USB booting via U-boot,
- SPI accessible from U-boot and Kernel,
- Power/standby leds,
- Power key,
- Persistent eth0 and eth1 address,
What does not?
- Everything else probably, like HDMI, Mali, cpu scaling.
Usage?
This is suitable for testing and headless use.
^^ This will only work when running on one of my images. It will not work with Official images.
^^ In above you may want to look at https://github.com/ayufan-rock64/linux-build/releases and get the latest archive.
Hello, I am trying to find or how to build a volumio image for the Rock64 4g with the added DAC addon board. I am currently using RPi 3 with HiFiBerry DAC running Volumio in my car for Very high end music competitions. I want to upgrade to the ROCK64 because of the speed and USB3 for faster read times on the attached 2TB SSD. Any help would be greatly appreciated.
I've installed the Android SDK using Android Studio (version 23.0.3 of the build-tools, since I use Android 6.0.1). When I use 'adb devices' to list the devices, it is not listed. But when I go to System Information to check if it's even detected, under Hardware > USB, nothing appears. So it seems that is not that 'adb' doesn't recognize the device, but the USB connection doesn't appear to be there; the computer doesn't detect it.
USB debugging is on, I've tried changing the USB mode between MTP and PTP, I've tried different USB ports from my laptop (if I connect my phone, Android too, it works in both), I've tried different USB cables, I've tried the different USB ports in the board (using Linux the USB ports work well, so I assume is something with Android, and not the board).
Could anyone help me? Should I use Android 5.1.1? Do I need to change some configuration, or install some app?
![[Image: 4jZ8VKT.png]](http://i.imgur.com/4jZ8VKT.png)
