| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,679
» Latest member: Gett1272
» Forum threads: 16,253
» Forum posts: 117,171
Full Statistics
|
| Latest Threads |
Are you interested in a n...
Forum: General Discussion on Pinebook Pro
Last Post: WEF
Yesterday, 02:33 PM
» Replies: 2
» Views: 2,970
|
Recycling pinephone as ho...
Forum: PinePhone Hardware
Last Post: biketool
Yesterday, 11:18 AM
» Replies: 3
» Views: 288
|
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
Yesterday, 07:29 AM
» Replies: 0
» Views: 64
|
black cursos background
Forum: General Discussion on PineTab
Last Post: polrus
11-11-2025, 04:07 PM
» Replies: 0
» Views: 56
|
slight bumps causing phon...
Forum: PinePhone Pro Hardware
Last Post: JadenSki
11-11-2025, 02:05 PM
» Replies: 2
» Views: 96
|
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
11-11-2025, 02:01 PM
» Replies: 10
» Views: 12,482
|
Switching cameras on PPpr...
Forum: Mobian on PinePhone
Last Post: biketool
11-11-2025, 10:44 AM
» Replies: 0
» Views: 49
|
Battery connector dead
Forum: PinePhone Hardware
Last Post: mdk
11-11-2025, 10:05 AM
» Replies: 3
» Views: 2,372
|
No touch KB after update(...
Forum: Mobian on PinePhone
Last Post: biketool
11-11-2025, 09:45 AM
» Replies: 3
» Views: 184
|
compass pdf link expired:...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-10-2025, 12:39 PM
» Replies: 4
» Views: 307
|
|
|
| [PINE A64 2GB Kickstarter]How to boot android from external SSD |
|
Posted by: v1n1c1uS - 01-10-2018, 06:50 PM - Forum: Android on Pine A64(+)
- Replies (1)
|
 |
Hi, guys.
I have an Pine a64 2GB that i'm using as media center (android 6.0 ayufan with kodi app), I have a 16gb micro sd and it is working. But I want to use an 128GB SSD in a usb enclosure with separated power to boot the OS and have extra storage.
I know that I have to maintain the sd connected for boot. All tutorials that I found are for linux installations and android does not have the same commands;
So, the question is: How do I use android 6.0 and boot the OS from external SSD?
Thanks in advance.
|
|
|
|
VPN not working at all - Hardware issue |
|
Posted by: milkaca - 01-10-2018, 06:03 PM - Forum: Pinebook Hardware and Accessories
- Replies (9)
|
|
I just tested VPN on Armbian image on my Pinebook. It looks like Pinebook is having some hardware issues, I am quite sure because I tested VPN on all images and always the same thing. On every single device that I have things are working fine, so it must be some issue with Pinebook itself.
Can you please bring some light to this topic, there are already couple of topics about VPN not working and no response so far??? It would be at least fair to tell us that VPN is not possible on Pinebook at all.
Thank you.
|
|
|
|
| Zwave module on LTS |
|
Posted by: saileshrajk - 01-10-2018, 04:56 PM - Forum: P64-LTS / SOPINE Hardware, Accessories and POT
- Replies (2)
|
|
Hi,
Any idea if the Z-Wave module for both Pine64+ and LTS are the same? i.e. will the one bought for pine64+ work on LTS?
I currently have xenial-minimal from ayufan-pine64 repositories, ubuntu-mate installed.
I have also installed Openhabian from here (manual steps)
https://docs.openhab.org/installation/op...nual-setup.
+
Its all up and running.
When I install the z-wave binding and try to get the z-wave serial controller, it says port /dev/ttyS1 or S0 does not exist.
Any idea as to how to get this work?
The same z-wave module was working fine on another Pine64+ board
Thanks
Sailesh
|
|
|
|
| u-boot doesn't receive packets over ethernet |
|
Posted by: hibernick - 01-10-2018, 02:53 PM - Forum: General Discussion on ROCK64
- Replies (3)
|
|
Hi,
I try to boot my rock64 board over network but unsuccessfully:
Code: => tftpboot boot.img
Speed: 100, full duplex
Using ethernet@ff540000 device
TFTP from server 192.168.15.151; our IP address is 192.168.15.20
Filename 'boot.img'.
Load address: 0x800800
Loading: *
ARP Retry count exceeded; starting again
this is what I see with tcpdump on another board
Code: mik@odroidc1:~$ sudo tcpdump src 192.168.15.20
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
21:12:37.998173 ARP, Request who-has odroidc1 tell 192.168.15.20, length 46
21:12:42.998551 ARP, Request who-has odroidc1 tell 192.168.15.20, length 46
21:12:47.999351 ARP, Request who-has odroidc1 tell 192.168.15.20, length 46
21:12:53.000215 ARP, Request who-has odroidc1 tell 192.168.15.20, length 46
Code: mik@odroidc1:~$ sudo tcpdump -i eth0 ether host 86e0c0eafaa9
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
21:29:57.672793 ARP, Request who-has odroidc1 tell 192.168.15.20, length 46
21:29:57.672902 ARP, Reply odroidc1 is-at 00:1e:06:10:01:65 (oui Unknown), length 28
21:30:02.673599 ARP, Request who-has odroidc1 tell 192.168.15.20, length 46
21:30:02.673730 ARP, Reply odroidc1 is-at 00:1e:06:10:01:65 (oui Unknown), length 28
21:30:07.674456 ARP, Request who-has odroidc1 tell 192.168.15.20, length 46
21:30:07.674581 ARP, Reply odroidc1 is-at 00:1e:06:10:01:65 (oui Unknown), length 28
21:30:12.675321 ARP, Request who-has odroidc1 tell 192.168.15.20, length 46
21:30:12.675452 ARP, Reply odroidc1 is-at 00:1e:06:10:01:65 (oui Unknown), length 28
This is u-boot environment
Code: => printenv
arch=arm
baudrate=115200
board=rock64_rk3328
board_name=rock64_rk3328
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}
boot_efi_binary=load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootaa64.efi; if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addi
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}extlinux/extlinux.conf
boot_net_usb_start=usb start
boot_prefixes=/ /boot/
boot_script_dhcp=boot.scr.uimg
boot_scripts=boot.scr.uimg boot.scr
boot_targets=mmc0 mmc1 usb0 pxe dhcp
bootcmd=run distro_bootcmd
bootcmd_dhcp=run boot_net_usb_start; if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi;setenv efi_fdtfile ${fdtfile}; setenv efi_o;
bootcmd_mmc0=setenv devnum 0; run mmc_boot
bootcmd_mmc1=setenv devnum 1; run mmc_boot
bootcmd_pxe=run boot_net_usb_start; dhcp; if pxe get; then pxe boot; fi
bootcmd_usb0=setenv devnum 0; run usb_boot
bootdelay=2
cpu=armv8
cpuid#=00000000000000000000000000000000
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
efi_dtb_prefixes=/ /dtb/ /dtb/current/
eth1addr=86:e0:c0:ea:fa:c9
ethact=ethernet@ff540000
ethaddr=86:e0:c0:ea:fa:a9
fdt_addr_r=0x01f00000
fdtcontroladdr=7df0fba8
fdtfile=rockchip/rk3328-rock64.dtb
ipaddr=192.168.15.20
kernel_addr_r=0x02000000
load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefix}${efi_fdtfile}
mmc_boot=if mmc dev ${devnum}; then setenv devtype mmc; run scan_dev_for_boot_part; fi
partitions=uuid_disk=${uuid_gpt_disk};name=loader1,start=32K,size=4000K,uuid=${uuid_gpt_loader1};name=loader2,start=8MB,size=4MB,uuid=${uuid_gpt_loader2};
pxefile_addr_r=0x00600000
ramdisk_addr_r=0x04000000
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_fo;
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; de
scan_dev_for_efi=setenv efi_fdtfile ${fdtfile}; for prefix in ${efi_dtb_prefixes}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${efi_fe
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}extlinux/extlinux.conf; then echo Found ${prefix}extlinux/extlinux.confi
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot scrie
scriptaddr=0x00500000
serial#=0
serverip=192.168.15.151
soc=rockchip
stderr=serial@ff130000
stdin=serial@ff130000
stdout=serial@ff130000
usb_boot=usb start; if usb dev ${devnum}; then setenv devtype usb; run scan_dev_for_boot_part; fi
vendor=rockchip
Environment size: 4094/32764 bytes
If I don't interrupt booting and boot to linux then I have network.
Has anybody else this problem?
|
|
|
|
| Pine64 installer way slow flashing |
|
Posted by: Paraplegic Racehorse - 01-10-2018, 10:57 AM - Forum: Getting Started
- Replies (2)
|
|
I just did a speed test. The pine64-Installer, while very convenient, is also super slow.
Flashing the same Debian image to same brand SD card (supplied by Pine at purchase of my boards) using same adapter on same computer running Ubuntu 17.10 Budgie
| _flash_tool_ | _time_to_flash_ |
| Pine64-installer | 32 mins |
| linux dd | 4 mins |
Both cards work fine.
Didn't test basic Etcher.
***
What gives?
Has anyone else noticed this?
|
|
|
|
| USB 3.0 Portable HDD - Suggestions |
|
Posted by: thewonderer - 01-09-2018, 08:38 PM - Forum: Linux on Rock64
- Replies (8)
|
|
Hi,
I'm looking at buying a large portable HDD. There is a WD 3TB USB elements portable that looks ideal. I've been reading about USB 3 performance on the rock64 and how there is a JM chipset that gives best performance.
I wanted to ask other users what suggestions / experiences they have with USB 3 drives and throughput / reliability before buying a drive.
My rock64 will be an always on box and a NAS.
Thanks in advance.
|
|
|
|
| Booting from eMMC |
|
Posted by: saileshrajk - 01-08-2018, 01:09 PM - Forum: General Discussion on PINE A64-LTS / SOPINE
- Replies (12)
|
|
Hi,
I just received my Pine64-LTS version with 64GB eMMC. I am having major issues trying to boot from the emmc.
I have tried the following
Downloaded the images from
https://github.com/ayufan-pine64/linux-build/releases
mainly
jessie-minimal-pine64-0.7.19-118.img.xz and xenial-minimal-pine64-bspkernel-0.7.19-118.img.xz
1. I then wrote the image to SD card and booted the Pine, which is fine.
2. Followed the instruction to
sudo ./pine64_update_kernel.sh 0.7.19
sudo ./pine64_update_uboot.sh 0.7.19
sudo ./pine64_update_package.sh 0.7.19
3. executed sudo ./pine64_install........to_emmc.sh xenial-minimal 0.7.19
4. Tried setting the following
emmc_compat=on
emmc_compat=150mhz
emmc_compat=200mhz
5. removed the SD
6 booted with eMMC
I get nothing.
Does the boot take very long as compared to SD (i have left it for few hours)? I get nothing.
I have also tried to burn the above image directly to the emmc without any luck.
Is there something I am missing?
Thanks
Sailesh
|
|
|
|
| flash image directly to eMMC? |
|
Posted by: gmruiz - 01-07-2018, 06:55 PM - Forum: General Discussion on ROCK64
- Replies (4)
|
|
Hello,
It´s the first time that I use a eMMC module, and I have one question. I have bought the USB adapter for eMMC module (https://www.pine64.org/?product=usb-adap...mmc-module), and I have tested that is possible to flash images to the USB with the eMMC module. My question is if it's possible to flash an image direcly to the USB and the connect the eMMC module to the ROCK64 to boot, or if it's necesary to do the process with the sdcard and the jumper. if not, what is the reason?
Thank you in advance,
Gregorio Martinez.
|
|
|
|
|
