| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,775
» Latest member: SuiYuan
» Forum threads: 16,285
» Forum posts: 117,305
Full Statistics
|
| Latest Threads |
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: PinePhoneProUser
11 hours ago
» Replies: 12
» Views: 6,306
|
Booting Issues
Forum: PineNote Software
Last Post: d2minik
12-26-2025, 12:44 PM
» Replies: 22
» Views: 16,170
|
Window Maker Live for Pin...
Forum: Linux on Pinebook Pro
Last Post: vajak
12-24-2025, 06:00 AM
» Replies: 2
» Views: 406
|
Rrkisp issue with CSI cam...
Forum: Linux on Quartz64
Last Post: lystar
12-24-2025, 02:34 AM
» Replies: 1
» Views: 3,787
|
bookworm vs trixie discus...
Forum: Mobian on PinePhone
Last Post: Kevin Kofler
12-24-2025, 12:11 AM
» Replies: 80
» Views: 45,734
|
Fedora + Phosh for PinePh...
Forum: PinePhone Software
Last Post: shanehill@mail.com
12-23-2025, 09:12 PM
» Replies: 75
» Views: 201,057
|
Trixie - bring up the On ...
Forum: Mobian on PinePhone
Last Post: grump_fiddle_reinstall
12-23-2025, 04:34 AM
» Replies: 0
» Views: 100
|
On-Screen Keyboard Arrow ...
Forum: Mobian on PinePhone
Last Post: grump_fiddle_reinstall
12-23-2025, 04:25 AM
» Replies: 11
» Views: 6,107
|
Armbian has been released...
Forum: News
Last Post: ArmbianForSBCs
12-23-2025, 01:36 AM
» Replies: 21
» Views: 32,366
|
Alarm clock doesn’t work
Forum: Mobian on PinePhone
Last Post: biketool
12-23-2025, 12:12 AM
» Replies: 14
» Views: 24,476
|
|
|
Mate Kiosk Problem on Rock64 |
|
Posted by: RocknKiosks - 01-10-2018, 08:11 PM - Forum: Linux on Rock64
- Replies (1)
|
 |
Hi gang. I have the strangest problem and figured I'd see if any of you have experienced it. I'm using the latest xenial mate image on a high quality sd card with plenty of power.
For those of you who don't know this, chromium browser can be run with a -kiosk flag that fullscreens it and takes away the location bar. You can still close it with altf4, but otherwise you'd never know it's a browser.
On this Rock64 image, right "out of the box", when you put it into kiosk mode and autolaunch, when it boots, it's hidden, and there is a tab of it down in the tray. It's there, technically. You can grab it sometimes and move it, without being able to see it, and the computer is locked until you hit altf4 and close chromium.
And get this, on two occasions, it didn't happen and it booted into chromium fine.
It's like it can't render it, and this is the 4g model of the rock64.
Debian mate doesn't do it.
|
|
|
|
| USB 3.0 Host Controller crashes when accessing several devices simultaneously |
|
Posted by: h31 - 01-10-2018, 06:52 PM - Forum: Linux on Rock64
- Replies (10)
|
 |
Hello!
I'm trying to connect three 2.5" HDDs to the ROCK64 computer. To do this, I use an externally-powered USB 3.0 hub. The problem is that I'm receiving errors when trying to access two drives simultaneously.
I've used fio and dd utilities to access hard drives. The example command is "dd if=/dev/sda of=/dev/null bs=128k". When I'm reading from one drives, everything works well. When I'm reading from two drives in parallel, dd and fio utilities hang and ROCK64 disconnects hard drives.
Here are some samples of the errors occured. Each time I'm trying, the new error I receive
Code: [ 1563.840645] xhci-hcd xhci-hcd.8.auto: WARN Successful completion on short TX
[ 1563.845139] xhci-hcd xhci-hcd.8.auto: WARN Event TRB for slot 4 ep 2 with no TDs queued?
[ 1563.849678] xhci-hcd xhci-hcd.8.auto: WARN Event TRB for slot 4 ep 2 with no TDs queued?
Code: [ 1498.598339] usb 5-1-port2: Cannot enable. Maybe the USB cable is bad?
Code: [ 500.701392] usb 5-1.2: reset SuperSpeed USB device number 4 using xhci-hcd
[ 501.702379] usb 5-1.3: reset SuperSpeed USB device number 5 using xhci-hcd
[ 503.633374] usb 5-1.3: reset SuperSpeed USB device number 5 using xhci-hcd
[ 503.707382] usb 5-1.2: reset SuperSpeed USB device number 4 using xhci-hcd
[ 505.797483] usb 5-1.3: reset SuperSpeed USB device number 5 using xhci-hcd
[ 542.889165] xhci-hcd xhci-hcd.8.auto: xHCI host not responding to stop endpoint command.
[ 542.890041] xhci-hcd xhci-hcd.8.auto: Assuming host is dying, halting host.
[ 542.890883] xhci-hcd xhci-hcd.8.auto: HC died; cleaning up
[ 542.890970] hub 5-1:1.0: hub_port_status failed (err = -22)
[ 542.890979] usb 5-1-port2: cannot reset (err = -22)
[ 542.890983] usb 5-1-port2: cannot reset (err = -22)
[ 542.890987] usb 5-1-port2: cannot reset (err = -22)
[ 542.890992] usb 5-1-port2: cannot reset (err = -22)
[ 542.890995] usb 5-1-port2: cannot reset (err = -22)
[ 542.890998] usb 5-1-port2: Cannot enable. Maybe the USB cable is bad?
[ 542.891004] usb 5-1-port2: cannot disable (err = -22)
[ 542.891011] hub 5-1:1.0: hub_port_status failed (err = -22)
[ 542.891016] usb 5-1-port2: cannot reset (err = -22)
[ 542.891020] usb 5-1-port2: cannot reset (err = -22)
[ 542.891024] usb 5-1-port2: cannot reset (err = -22)
[ 542.891028] usb 5-1-port2: cannot reset (err = -22)
[ 542.891031] usb 5-1-port2: cannot reset (err = -22)
[ 542.891033] usb 5-1-port2: Cannot enable. Maybe the USB cable is bad?
[ 542.891037] usb 5-1-port2: cannot disable (err = -22)
[ 542.891044] hub 5-1:1.0: hub_port_status failed (err = -22)
[ 542.891048] usb 5-1-port2: cannot reset (err = -22)
[ 542.891052] usb 5-1-port2: cannot reset (err = -22)
[ 542.891056] usb 5-1-port2: cannot reset (err = -22)
[ 542.891059] usb 5-1-port2: cannot reset (err = -22)
[ 542.891063] usb 5-1-port2: cannot reset (err = -22)
[ 542.891065] usb 5-1-port2: Cannot enable. Maybe the USB cable is bad?
[ 542.891069] usb 5-1-port2: cannot disable (err = -22)
[ 542.891075] hub 5-1:1.0: hub_port_status failed (err = -22)
[ 542.891079] usb 5-1-port2: cannot reset (err = -22)
[ 542.891083] usb 5-1-port2: cannot reset (err = -22)
[ 542.891087] usb 5-1-port2: cannot reset (err = -22)
[ 542.891091] usb 5-1-port2: cannot reset (err = -22)
[ 542.891095] usb 5-1-port2: cannot reset (err = -22)
[ 542.891096] usb 5-1-port2: Cannot enable. Maybe the USB cable is bad?
[ 542.891100] usb 5-1-port2: cannot disable (err = -22)
[ 542.891105] usb 5-1-port2: cannot disable (err = -22)
[ 542.891235] hub 5-1:1.0: hub_port_status failed (err = -22)
[ 542.942185] xhci-hcd xhci-hcd.8.auto: xHCI host not responding to stop endpoint command.
[ 542.945100] xhci-hcd xhci-hcd.8.auto: Assuming host is dying, halting host.
[ 542.947869] xhci-hcd xhci-hcd.8.auto: HC died; cleaning up
[ 542.951904] usb 4-1: USB disconnect, device number 2
[ 542.956912] usb 5-1: USB disconnect, device number 2
[ 542.959802] usb 5-1.1: USB disconnect, device number 3
[ 542.977962] usb 5-1.2: USB disconnect, device number 4
[ 542.986287] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 542.989232] sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x28 28 00 00 01 f6 00 00 00 f0 00
[ 542.990275] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[ 542.990284] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 01 73 b6 00 00 08 00 00
[ 542.990289] blk_update_request: I/O error, dev sdb, sector 24360448
[ 542.990481] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[ 542.990488] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 01 73 be 00 00 08 00 00
[ 542.990491] blk_update_request: I/O error, dev sdb, sector 24362496
[ 543.009644] blk_update_request: I/O error, dev sdc, sector 128512
[ 543.043358] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 543.046621] sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x28 28 00 00 01 f6 f0 00 00 10 00
[ 543.049930] blk_update_request: I/O error, dev sdc, sector 128752
[ 543.083261] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 543.086773] sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x28 28 00 00 01 f7 00 00 00 f0 00
[ 543.090248] blk_update_request: I/O error, dev sdc, sector 128768
[ 543.124265] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 543.127869] sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x28 28 00 00 01 f7 f0 00 00 10 00
[ 543.131518] blk_update_request: I/O error, dev sdc, sector 129008
[ 543.167252] sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 543.171131] sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x28 28 00 00 01 f6 00 00 00 08 00
[ 543.175063] blk_update_request: I/O error, dev sdc, sector 128512
[ 543.178874] Buffer I/O error on dev sdc, logical block 16064, async page read
[ 544.306086] usb 5-1.3: USB disconnect, device number 5
Code: [ 86.613946] usb 5-1.2: reset SuperSpeed USB device number 4 using xhci-hcd
[ 91.115965] usb 5-1.3: reset SuperSpeed USB device number 5 using xhci-hcd
[ 106.101604] usb 5-1.2: reset SuperSpeed USB device number 4 using xhci-hcd
[ 120.967035] usb 5-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
[ 124.326313] usb 5-1.2: reset SuperSpeed USB device number 4 using xhci-hcd
[ 132.806598] xhci-hcd xhci-hcd.8.auto: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 1
[ 132.807731] xhci-hcd xhci-hcd.8.auto: Looking for event-dma 003f000000000000 trb-start 000000004f11abe0 trb-end 000000004f11ac10 seg-start 000000004f11a000 seg-end 000000004f11aff0
[ 133.727522] usb 5-1.3: reset SuperSpeed USB device number 5 using xhci-hcd
[ 134.952223] xhci-hcd xhci-hcd.8.auto: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 1
[ 134.953355] xhci-hcd xhci-hcd.8.auto: Looking for event-dma 003ef00000000000 trb-start 000000004f044b10 trb-end 000000004f044b40 seg-start 000000004f044000 seg-end 000000004f044ff0
[ 135.848533] usb 5-1.3: reset SuperSpeed USB device number 5 using xhci-hcd
[ 167.944738] usb 5-1.2: reset SuperSpeed USB device number 4 using xhci-hcd
Code: [ 3.221233] usb 4-1: device descriptor read/64, error -71
[ 3.427214] usb 4-1: new low-speed USB device number 4 using xhci-hcd
[ 3.533216] usb 4-1: device descriptor read/64, error -71
[ 3.739169] usb 4-1: device descriptor read/64, error -71
[ 3.945206] usb 4-1: new low-speed USB device number 5 using xhci-hcd
[ 3.956377] usb 4-1: Device not responding to setup address.
[ 4.168381] usb 4-1: Device not responding to setup address.
[ 4.380201] usb 4-1: device not accepting address 5, error -71
[ 4.493192] usb 4-1: new low-speed USB device number 6 using xhci-hcd
[ 4.504378] usb 4-1: Device not responding to setup address.
[ 4.716373] usb 4-1: Device not responding to setup address.
[ 4.927197] usb 4-1: device not accepting address 6, error -71
[ 4.937910] usb usb4-port1: unable to enumerate USB device
Code: [ 693.135416] xhci-hcd xhci-hcd.8.auto: WARN Event TRB for slot 3 ep 2 with no TDs queued?
[ 724.023537] usb 5-1.1: reset SuperSpeed USB device number 3 using xhci-hcd
Code: [ 909.970759] xhci-hcd xhci-hcd.8.auto: xHCI host not responding to stop endpoint command.
[ 909.983792] xhci-hcd xhci-hcd.8.auto: Assuming host is dying, halting host.
[ 910.017740] xhci-hcd xhci-hcd.8.auto: Host not halted after 16000 microseconds.
[ 910.022301] xhci-hcd xhci-hcd.8.auto: Non-responsive xHCI host is not halting.
[ 910.026873] xhci-hcd xhci-hcd.8.auto: Completing active URBs anyway.
[ 910.031396] hub 5-1:1.0: hub_port_status failed (err = -108)
[ 910.031404] xhci-hcd xhci-hcd.8.auto: HC died; cleaning up
[ 910.031438] xhci-hcd xhci-hcd.8.auto: xHCI host not responding to stop endpoint command.
[ 910.031445] xhci-hcd xhci-hcd.8.auto: Assuming host is dying, halting host.
[ 910.031466] xhci-hcd xhci-hcd.8.auto: HC died; cleaning up
[ 910.032583] usb 4-1: USB disconnect, device number 2
[ 910.033237] usb 5-1: USB disconnect, device number 2
[ 910.033246] usb 5-1.1: USB disconnect, device number 5
[ 910.061780] sd 4:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 910.061789] sd 4:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 00 12 96 00 00 00 f0 00
[ 910.061793] blk_update_request: I/O error, dev sdb, sector 1218048
[ 910.085847] sd 5:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[ 910.090574] sd 5:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 17 fd 00 00 00 f0 00
[ 910.091851] sd 4:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 910.091861] sd 4:0:0:0: [sdb] tag#0 CDB: opcode=0x28 28 00 00 12 96 f0 00 00 10 00
[ 910.091866] blk_update_request: I/O error, dev sdb, sector 1218288
[ 910.109030] blk_update_request: I/O error, dev sda, sector 1572096
[ 910.113781] scsi 5:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
[ 910.118622] scsi 5:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 17 fd f0 00 00 10 00
[ 910.123388] blk_update_request: I/O error, dev sda, sector 1572336
[ 910.135964] usb 5-1.3: USB disconnect, device number 4
Even when I'm keeping only 2 hard drives connected, the error still occurs. But everything works well when I'm plugging an USB hub cable to a USB 2.0 port of the ROCK64. Also, everything works perfectly when I'm connecting the USB hub to my Intel laptop (using the same set of cables and a PSU).
The ROCK64 computer is powered by an official 3A PSU. The USB hub is powered by 2A PSU. Tried several PSUs - no difference. Kernel version is 4.4.77-rockchip-ayufan-136, distro is Debian 9 (stretch).
|
|
|
|
| [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
|
|
|
|
|