| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Satellite antenna
Forum: Community and Events
Last Post: biketool
Yesterday, 02:46 PM
» Replies: 2
» Views: 356
|
Irradium (based on crux l...
Forum: Linux on Pinebook
Last Post: mara
10-25-2026, 04:11 AM
» Replies: 5
» Views: 14,847
|
Booting Issues
Forum: PineNote Software
Last Post: vlagged
10-23-2026, 12:14 PM
» Replies: 25
» Views: 26,010
|
Alpha One - no connectivi...
Forum: Getting Started
Last Post: Dabdarklighter
10-22-2026, 03:51 PM
» Replies: 1
» Views: 1,143
|
Article: The Advantages o...
Forum: General
Last Post: zetabeta
10-20-2026, 02:38 PM
» Replies: 2
» Views: 313
|
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
10-19-2026, 12:27 PM
» Replies: 22
» Views: 21,452
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
10-19-2026, 10:01 AM
» Replies: 25
» Views: 16,212
|
Article: Will Linux phone...
Forum: General
Last Post: amosbatto
10-19-2026, 09:52 AM
» Replies: 11
» Views: 1,435
|
Login issues
Forum: PineTab Hardware
Last Post: Corkonian
10-17-2026, 02:34 AM
» Replies: 2
» Views: 439
|
Rii mini 4 keyboard and t...
Forum: PinePhone Accessories
Last Post: Flymoon
10-15-2026, 08:04 AM
» Replies: 3
» Views: 5,946
|
|
|
Rock64 Android TV - Android Studio - adb.exe device is not found. |
|
Posted by: eaeamending@gmail.com - 11-11-2018, 05:52 PM - Forum: Android on Rock64
- Replies (2)
|
 |
I have a standard Rock64 (not pro64) loaded with latest Android TV firmware. I am looking to get the device connected to adb.exe. I tinkered with it a little bit but after the installation of various USB drivers to get the Android TV device to be recognized by adb.exe via an USB A to A cable I was not able to get the device to be recognized by my PC running Windows 10.
If in the future instructions for connecting Rock64 directly to Android Studio via adb.exe? Such that "adb.exe devices" command will detect the device?
I did put Rock64 Android TV into developer mode but that did not seem to help either.
Thank You!
|
|
|
|
| Android for 1080p Pinebook? |
|
Posted by: Tomash - 11-11-2018, 04:51 PM - Forum: Android on Pinebook
- Replies (7)
|
|
I was pleasantly surprised to receive my pinebook a few days ago in upgraded 1080p version. However the official Android for 768p Pinebook does not boot (yes, I waited over 5 minutes, just black screen).
Therefore, does anyone know when any Android for 1080p Pinebook will be released? When will the official one appear?
It's a wonderful low-cost linux laptop, but for consuming multimedia content (streaming services) Android would be much better.
|
|
|
|
| How to finish installation of KDE ? |
|
Posted by: Surehand53 - 11-11-2018, 03:58 PM - Forum: General Discussion on Pinebook
- Replies (3)
|
|
Hi.
I have the Pinebook a few days now and all in all it works great.
However I noticed that the original shipped OS (KDE) seems to be not a completely installed version.
I have this `First time run this installer` icon in the top ft of my desktop which is usually found on installer images.
Also the current installation uses only about 6 GB of the eMMC (16GB).
So what would be the next step to complete this installation ?
|
|
|
|
| Pinebook 1080: US keymap for \ | (backslash pipe) key near left shift? |
|
Posted by: acruhl - 11-11-2018, 07:40 AM - Forum: General Discussion on Pinebook
- Replies (10)
|
|
I have a Pinebook 1080 11.6", and there is a key which doesn't map correctly.
I searched and found no answer, hopefully this has already been answered though.
Near my left shift key, I have a key with \ on the bottom and | on top, which are backslash and pipe.
However, when I use it to type, I get this:
<
> (with shift)
I don't know much about keymaps because I'm in the US and it always "just worked".
|
|
|
|
| Pinebook screenshots |
|
Posted by: e-minguez - 11-11-2018, 01:26 AM - Forum: General Discussion on Pinebook
- Replies (1)
|
 |
Do you have a fancy desktop with cool tweaks? Do you want to share that awesome config you have? Your latest OS customization? Then, share your screenshots!
Adding details on your os, setup, dotfiles, tweaks, etc for (imaginary) bonus points!
Enviado desde mi ONEPLUS A5010 mediante Tapatalk
|
|
|
|
| Printer install |
|
Posted by: icemeister - 11-10-2018, 08:54 PM - Forum: General Discussion on Pinebook
- Replies (4)
|
|
Hi all, I have run into a snafu in trying to set up a printer on my pinebook. All goes well until i get ask for a username and password. I tried the pine64/pine64 with no luck. I think that i read some where about a root password but am unable to find a source. Do i need a different password to install a printer? This is just a test as i am having problems on a linux mint printer install and needed to know the process.
Thanks for any help
IceMeister
18.04 Mate
|
|
|
|
| BUilding everything from scratch (buildroot) |
|
Posted by: lm- - 11-10-2018, 05:22 PM - Forum: General Discussion on ROCK64
- Replies (9)
|
|
Hi,
I bought rock64 and now I am trying to prepare very minimal script that will build all steps from scratch. Intend is to publish it to buildroot repository later. But I have problem booting kernel. Some information what have I already done and where I am stuck.
1. tpl, spl and uboot are build from ayufan repository, branch "2017.09-rockchip-ayufan-1035-gd646df03ac", and "rock64-rk3328_defconfig", no changes have been made to the files. To create tpl/spl image I use these commands (this is flashed to 0x40). Note, no rockchip binary blobs anywhere!
Code: $MKIMAGE -n rk3328 -T rksd -d $BINARIES_DIR/u-boot-tpl.bin $BINARIES_DIR/u-boot-tpl.img
cat $BINARIES_DIR/u-boot-tpl.img $BINARIES_DIR/u-boot-spl.bin > $BINARIES_DIR/u-boot-tpl-spl.img
2. then ATF is built, also from ayufan repository and "rk3328" as a platform. Generated BL31 is used to generate u-boot.itb (with make u-boot.itb from ayufan repo). That u-boot.itb is flashed to 0x200 on sdcard.
3. Kernel, no surprise here, it's from ayufan repo, "rockchip_linux_defconfig" used and "rockchip/rk3328-rock64" dts from in-tree, again no changes have been made.
4. Now sdcard image is generated with this config:
Code: image sdcard.img {
hdimage {
}
partition uboot-spl {
in-partition-table = "no"
image = "u-boot-tpl-spl.img"
offset = 32768 # 512 * 0x40 from start of sd card
}
partition uboot {
in-partition-table = "no"
image = "u-boot.itb"
offset = 262144 # 512 * 0x200 from start of sd card
}
partition rootfs {
partition-type = 0x83
image = "rootfs.ext4"
size = 500M
}
}
It's in mbr dos format (so no gpt). On rootfs there is extlinux, Image and dtb in /boot directory.
5. Toolchain is gcc 7.x and binutils 2.29.x.
Now logs,
Code: <debug_uart> U-Boot TPL board init
configuring DDR parameters
LPDDR3
DRAM frequency: 800MHz
configuring DDR parameters
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2017.09 (Nov 11 2018 - 00:07:11)
setup_ddr_param 1
booted from SD
Trying to boot from MMC2
U-Boot 2017.09 (Nov 11 2018 - 00:07:11 +0100)
Model: Pine64 Rock64
DRAM: 4 GiB
MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1
SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: Pine64 Rock64
misc_init_r
cpuid=00000000000000000000000000000000
serial=0
Net: eth0: ethernet@ff540000
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
mmc_init: -95, time 10
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
205 bytes read in 36 ms (4.9 KiB/s)
1: rock64 linux-next
Retrieving file: /boot/Image
20054024 bytes read in 17452 ms (1.1 MiB/s)
append: earlyprintk earlycon=uart8250,mmio32,0xff130000 console=ttyS2,1500000n8 console=tty0 root=/dev/mmcblk0p1 rootwait
Retrieving file: /boot/rk3328-rock64.dtb
70953 bytes read in 29 ms (2.3 MiB/s)
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Device Tree to 00000000fceed000, end 00000000fcf01528 ... OK
Starting kernel ...
And that's it. No more output and I am completaly out of ideas how to proceed.
u-boot properly boots, it finds my kernel and dtb, it loads it but it fails to boot it. Kernel and dtb are good, I downloaded slackware image for rock64 and replaced Image and dtb, and it started - I could see todays date and my build host in kernel message, so it's enough of a proof linux and dtb are generated properly.
Anybody got any idea what am I missing? I was thinking that it might be mbr instead of gpt or missing initrd, but slackware image doesn't use them as well. I would appreciate any advice or ideas how to proceed with that.
|
|
|
|
|
