| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Mobian image for the Pine...
Forum: Mobian on PinePhone
Last Post: Korfou
04-27-2026, 09:57 AM
» Replies: 2
» Views: 123
|
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
04-19-2026, 12:56 PM
» Replies: 13
» Views: 14,911
|
Pine Time dead
Forum: General Discussion on PineTime
Last Post: chris.burmajster
04-18-2026, 10:08 AM
» Replies: 0
» Views: 189
|
Booting Issues
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:17 PM
» Replies: 24
» Views: 19,453
|
App launcher shows tiny i...
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:12 PM
» Replies: 1
» Views: 1,123
|
my pinecil v2 is not work...
Forum: General Discussion on Pinecil
Last Post: jagrav
04-17-2026, 06:28 AM
» Replies: 0
» Views: 118
|
Freezes and kernel panics...
Forum: Linux on RockPro64
Last Post: prahal
04-15-2026, 06:48 PM
» Replies: 4
» Views: 1,441
|
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 309
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 9,260
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 431
|
|
|
| LTE Modem |
|
Posted by: niedoluk - 05-09-2018, 04:54 AM - Forum: Rock64 Hardware and Accessories
- Replies (1)
|
 |
Hello,
do you have any experience with any LTE accesory? I am going to start project for automatical upload of photos into cloud from an open-air places and wonder what is the best way accomplish that. Some USB solution would do but some solution connected directly to some bus would be the best.
Thank you and wish you a nice day.
Lukas
|
|
|
|
| how to set kernel parameter 'fsck.mode=force' |
|
Posted by: marcelser - 05-09-2018, 02:57 AM - Forum: Debian
- Replies (6)
|
 |
Hi,
I spent now several hours trying to find out by googling and search in this forum how to set the kernel parameter "fsck.mode=force" on the Pine A64. I tried to understand the boot process from the sunxi documentation but to be honest, the boot process of the pine a64 is like rocket science to me with all this parts like u-boot, initrd, kernel, etc.
I finally tried setting it in uEnv.txt but when I look at /proc/cmdline it's not applied. The system I'm running is debian with version "stretch/sid" and kernel image is "3.10.105-0-pine64-longsleep"
Can anyone in simple words explain me how to do this. I cannot be that hard, but it seems it's very hard to find instructions for this seemingly simple task.
Thanks to anyone who could she a light on this.
PS: Why is it so complicated on the PineA64 when on Raspberry I can just modify cmdline.txt and I'm done?
|
|
|
|
| 4.4.120-gac51b70a-dirty works, 4.4.126-g6dc34509-dirty seems broken |
|
Posted by: cooker - 05-07-2018, 08:54 AM - Forum: Linux on Rock64
- No Replies
|
 |
I dare not do apt update/upgrade on my rock64-NAS, my family is using it. So, I intend to build an update with AppArmor enabled on my spare rock64 and swap the sdcard after test.
Today, I follow exactly the same steps as what I had done successfully before. But failed.
Sorry I am not a developer, I don't even have an active git a/c, I am happy to follow if you have a comprehensive instruction know-how on how to report error. However, obviously, you don't have time to prepare that. I can only report it here.
Running the first make -j5 (after make menuconfig) looks fine. --edit-- sorry, it gets error too.
Then, there are lot of errors (missing files) during sudo make modules_install
Followings are copied from the end of sudo make install
I did it twice. It should easily be reproduced.
Code: make[3]: *** [drivers/gpu/arm/built-in.o] Error 1
scripts/Makefile.build:484: recipe for target 'drivers/gpu/arm' failed
make[2]: *** [drivers/gpu/arm] Error 2
scripts/Makefile.build:484: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
make[1]: *** Waiting for unfinished jobs....
CC drivers/hid/hid-debug.o
CC drivers/hid/hidraw.o
...
...
LD drivers/hid/usbhid/built-in.o
LD drivers/hid/built-in.o
Makefile:1028: recipe for target 'drivers' failed
make: *** [drivers] Error 2
Thank you for your attention.
edit --------------------
BTW, I always use
Code: $ git clone --depth 1 --single-branch -b release-4.4 https://github.com/ayufan-rock64/linux-kernel
to get the source code and assume it is the stable release. Is it?
edit 2 ---------------
Lucky me saved a copy of source code for 4.4.120
Just do the "make -j5" again, I timed it and it took real 80m.
I amended the first post that said the step of "make -j5" is fine because that took real 40m only. Something should be wrong for such a big time saving, right?
Good Night
|
|
|
|
| Issues with first start, what do the different LED states mean? |
|
Posted by: Botagar - 05-07-2018, 04:14 AM - Forum: Clusterboard
- Replies (4)
|
 |
Hi all!
I partook in the baseboard + 1 free SOPine offer a few months back but only just got around to having a play around with it.
I've attempted to get the module up and running with the xenial-minimal-sopine-bspkernel-0.7.19-118.img.xz image found here (https://github.com/ayufan-pine64/linux-build/releases). I loaded it up on a 64GB SD card through Etcher, but nothing gets registered on the network. I tried enabling emcc_compat=on after a fresh etch.
Basically debugging is rather hard because there is very little information about the default behavior of the baseboard. I've linked a gif of what the board is doing. The (power?) LED's just blink in near enough unison and the orange LEDS (Net Activity?) blink together semi frequently. Nothing lights up on the SOPine board itself.
I'm powering the system up through the barrel jack connector with the PSU sold on the official site. I've confirmed with a voltmeter that the voltage levels are correct.
![[Image: UdidCZU]](https://imgur.com/UdidCZU)
https://imgur.com/UdidCZU
Can anyone point out what might be happening? And what steps I could take to further debug what might be going on?
Cheers~!
|
|
|
|
| Android and SD Card |
|
Posted by: gigagames - 05-05-2018, 06:50 PM - Forum: Android on Rock64
- Replies (2)
|
 |
Hello,
i try to get Android running, with an SD card.
I Downloaded android-7.1-rock-64-rock64_atv-v0.3.13-r115-raw.img.gz
When im trying to Flash it with Etcher, its telling me "It looks like this is not a bootable image. The image does not appear to contain a partition table, and might not be recognized or bootable by your device"
When i Flash it to my sd card and insert the card into the Rock, my Window keeps being black.
When im using the Pine64 Installer, and select "Community Android TV 7.1. (ROCK64 microSD) (should be the same as i dowonloaded..) same behaviour -> Window keeps being black.
So how the heck can i get Android running with an SD card ?
Thanks for helping and sry for bad english
|
|
|
|
| Debian to eMMC? |
|
Posted by: Hoerli - 05-04-2018, 12:59 PM - Forum: General Discussion on ROCK64
- Replies (7)
|
 |
Hello!
I am the proud owner of a new ROCK64
I have already tried Android and would like to install a "normal" system on the ROCK.
Currently there is only Xenial Mate for the eMMC chip.
This is currently running, but not really stable / good.
It hangs when you update. So I had to reinstall the system 4 times.
Is there an easy way to get e.g. Debian on the eMMC chip?
So far I only found a manual with a console cable, but I don't own one.
Hope there will be a good possibility to install e.g. Linux Mint soon. To be honest, I also like the Cinnamon surface more than mate.
|
|
|
|
| Flashing rockchip 'update' images on Linux |
|
Posted by: Luke - 05-04-2018, 06:55 AM - Forum: Android on Rock64
- No Replies
|
 |
If you're using Linux on your PC then flashing Android images to the Rock64 (other than the RAW dd images) is a bit tricky.
I came across a utility for Linux that makes the process nice and easy, allowing you to flash 'update' images directly to eMMC.
The software is called upgrade_tool and can be downloaded from here
You can read about it and its different functions here
In short, after downloading and extracting the contents of the archive, navigate in terminal to the extracted utility and flash the update.img using the following command:
Code: sudo ./upgrade_tool uf /path/to/update.img
[edit] I forgot to add; you need to force the board into recovery mode first and it has to be connected to your Linux PC using an A-to-A USB cable.
|
|
|
|
|