| 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: 289
|
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: 185
|
compass pdf link expired:...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
11-10-2025, 12:39 PM
» Replies: 4
» Views: 307
|
|
|
| Moonlight embedded & NX client |
|
Posted by: Maor - 01-11-2018, 12:34 PM - Forum: Linux on Pine A64(+)
- No Replies
|
 |
I am looking to buy the ROCK64 board, as it seems a bang for the buck.
I do need to know 2 things:
Will I be able to get Moonlight embedded and NoMachine NX client working with mainline?
|
|
|
|
| Custom OS |
|
Posted by: MaskOfLoki - 01-11-2018, 11:55 AM - Forum: General Discussion on Pinebook
- Replies (8)
|
 |
I'm going to be buying a Pinebook here soon, and I was curious if it's possible to run a custom OS I've written on it. Specifically, does the booting partition have to be FAT32, or does it allow for custom bootloaders and such?
Sorry if this isn't the correct section to post this.
|
|
|
|
Where is my parcel? |
|
Posted by: ladoleo - 01-11-2018, 04:19 AM - Forum: Shipment Related Discussion
- Replies (4)
|
 |
Unfortunately, I have to write to the forum, since at the address sales@pine64.org I was probably ignored.
The order was sent on time 2017-11-17, but according to the current day 2018-01-11 its status does not change: In transit https://t.17track.net/ru?nums=LM047411278CN
Today is 55 days as the delivery goes. I'm not sure that I can get the long-awaited order. Can someone tell me what to do in this case? Were there such cases that people did not receive their parcels with microcomputers?
|
|
|
|
| No HDMI Display need help with correct uEnv.txt settings |
|
Posted by: dkebler - 01-10-2018, 10:20 PM - Forum: General Discussion on PINE A64(+)
- Replies (7)
|
 |
I am trying Ayufan's latest minimal xenial image for pine64
https://github.com/ayufan-pine64/linux-build/releases
It is booting and I can ssh to the board. All seems fine except I can't get the HDMI port to function.
It is connected to my standard monitor which supports 1080p
Here is the only defaults (comments) I changed. I've fiddled some with these but nothing not even a hint of communication with my monitor (like a flicker).
I am assuming my issue is just getting these settings correct? Are there maybe other things I must do to get HDMI working?
Code: # To enable LCD or HDMI, if not changed it will use default (experimental)
#disp_screen0=lcd or hdmi
disp_screen0=hdmi
disp_screen1=hdmi
# disp_mode=screen0 or screen1 or dualhead or xinerama or clone or disabled
disp_mode=screen0
# USB OTG port mode (experimental)
# otg_mode=device or host or otg
otg_mode=host
# Configure contiguous memory allocation
# This maybe required to be enlarged for 4K displays
cma=384M
# To change HDMI display mode:
# hdmi_mode=480i
# hdmi_mode=576i
# hdmi_mode=480p
# hdmi_mode=576p
# hdmi_mode=720p50
# hdmi_mode=720p60
# hdmi_mode=1080i50
# hdmi_mode=1080i60
# hdmi_mode=1080p24
# hdmi_mode=1080p50
hdmi_mode=1080p60
# hdmi_mode=2160p30
# hdmi_mode=2160p25
# hdmi_mode=2160p24
# hdmi_mode=800x480p
# hdmi_mode=1024x600p
|
|
|
|
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).
|
|
|
|
|