Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,500
» Latest member: lemnigkleMoope
» Forum threads: 16,202
» Forum posts: 116,906

Full Statistics

Latest Threads
Goolge banning Sideloaded...
Forum: General Discussion of PinePhone Pro
Last Post: biketool
2 hours ago
» Replies: 0
» Views: 13
What's stopping you from ...
Forum: General Discussion of PinePhone Pro
Last Post: teekay
8 hours ago
» Replies: 8
» Views: 517
Pinephone (Pro) Keyboard ...
Forum: PinePhone Accessories
Last Post: zetabeta
Yesterday, 06:06 AM
» Replies: 3
» Views: 1,938
keyboard pogo pins part n...
Forum: General Discussion on PineTab
Last Post: starpp
Yesterday, 04:34 AM
» Replies: 0
» Views: 133
google will take control ...
Forum: General
Last Post: zetabeta
08-25-2025, 03:14 PM
» Replies: 22
» Views: 9,583
Booting Issues
Forum: PineNote Software
Last Post: serenopolveroso
08-25-2025, 11:14 AM
» Replies: 19
» Views: 5,270
PINETAB-V doesn't boot.
Forum: Getting Started
Last Post: Woazboat
08-23-2025, 02:58 PM
» Replies: 1
» Views: 477
PinePhone Pro: Camera App...
Forum: General Discussion of PinePhone Pro
Last Post: teekay
08-22-2025, 11:23 PM
» Replies: 3
» Views: 2,525
PinePhone Pro discontinue...
Forum: General Discussion of PinePhone Pro
Last Post: teekay
08-22-2025, 11:19 PM
» Replies: 9
» Views: 1,288
Multiple NEMA 17 stepper ...
Forum: General
Last Post: Harry
08-22-2025, 12:24 AM
» Replies: 0
» Views: 351

 
  HDD gets not detected after reboot
Posted by: pascal51882 - 03-10-2018, 02:25 AM - Forum: Linux on Rock64 - Replies (8)

Hi. 
I use Linux xenial minimal from the rock64 site. 
The version is the latest. 
The HDD is plugged in via the USB 3.0 Port. 
I tried different adapters.  it s always the same.
When I reboot my rock64 the HDD gets not detected. 
If i unplug it and plug it back in it gets detected. 
It s every time the same. 

Is this a siftware based problem?  
i think so. 
Is there a solution?


  Problems with USB 3.0 and SATA disk (UAS)
Posted by: diglam - 03-09-2018, 11:27 AM - Forum: Linux on Rock64 - Replies (6)

Hi,
I'm having problems with my 2.5" 500GB WD Blue disk connected to USB 3.0 port with Startech's USB 3.1 (10Gbps) Adapter Cable for 2.5" SATA Drives
(https://www.startech.com/HDD/Adapters/us...B312SAT3CB) under heavy disk usage.

Linux version installed to rock64: Ayufan's stretch-minimal-rock64-0.5.15-136-arm64
uname -a:
Linux rockBOX 4.4.77-rockchip-ayufan-136 #1 SMP Thu Oct 12 09:14:48 UTC 2017 aarch64 GNU/Linux
(It is upgraded to stretch-minimal-rock64-0.6.25-193-arm64 today, but problems still goes on)

after boot:

Code:
[    6.513428] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[    6.520230] xhci-hcd xhci-hcd.9.auto: @00000000f3a6d450 00000000 00000000 1b000000 01038001
[    6.566054]  sda: sda1
[    6.574262] sd 0:0:0:0: [sda] Attached SCSI disk
[    6.761739] random: nonblocking pool is initialized
[    7.065293] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[    7.751919] Adding 4194300k swap on /mnt/data/swap.file.  Priority:-1 extents:5 across:4636668k
[    9.387683] rk_gmac-dwmac ff540000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   10.267894] NFSD: starting 90-second grace period (net ffffff8009286480)
[   15.437115] tty_port_close_start: tty->count = 1 port count = 2.

After trying to extract files
Code:
[ 1160.867080] sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
[ 1160.867936] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 0a b7 cd 07 00 01 00 00
[ 1160.868798] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1160.869822] xhci-hcd xhci-hcd.9.auto: @00000000f3a6ddb0 00000000 00000000 1b000000 01038001
[ 1196.825676] sd 0:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT
[ 1196.826550] sd 0:0:0:0: [sda] tag#2 CDB: opcode=0x2a 2a 00 08 86 6c df 00 00 18 00
[ 1196.827424] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1196.828448] xhci-hcd xhci-hcd.9.auto: @00000000f3a6ddd0 00000000 00000000 1b000000 01048001
[ 1196.829399] scsi host0: uas_eh_bus_reset_handler start
[ 1196.830016] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1196.831037] xhci-hcd xhci-hcd.9.auto: @00000000f3a6ddf0 00000000 00000000 1b000000 01078001
[ 1196.832000] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1196.833018] xhci-hcd xhci-hcd.9.auto: @00000000f3a6de10 00000000 00000000 1b000000 01078001
[ 1196.833970] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1196.834987] xhci-hcd xhci-hcd.9.auto: @00000000f3a6de30 00000000 00000000 1b000000 01078001
[ 1196.835943] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1196.836958] xhci-hcd xhci-hcd.9.auto: @00000000f3a6de50 00000000 00000000 1b000000 01078001
[ 1196.837886] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1196.838902] xhci-hcd xhci-hcd.9.auto: @00000000f3a6de70 00000000 00000000 1b000000 01078001
[ 1196.839847] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1196.840864] xhci-hcd xhci-hcd.9.auto: @00000000f3a6de90 00000000 00000000 1b000000 01048001
[ 1196.841817] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1196.842830] xhci-hcd xhci-hcd.9.auto: @00000000f3a6deb0 00000000 00000000 1b000000 01048001
[ 1196.843745] sd 0:0:0:0: [sda] tag#1 uas_zap_pending 0 uas-tag 2 inflight: CMD
[ 1196.844536] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
[ 1196.845351] sd 0:0:0:0: [sda] tag#3 uas_zap_pending 0 uas-tag 4 inflight: CMD
[ 1196.846122] sd 0:0:0:0: [sda] tag#3 CDB: opcode=0x2a 2a 00 05 47 e7 0f 00 00 08 00
[ 1196.846933] sd 0:0:0:0: [sda] tag#4 uas_zap_pending 0 uas-tag 5 inflight: CMD
[ 1196.847704] sd 0:0:0:0: [sda] tag#4 CDB: opcode=0x2a 2a 00 0f bd f7 17 00 00 08 00
[ 1196.950752] usb 5-1: reset SuperSpeed USB device number 2 using xhci-hcd
[ 1196.963198] scsi host0: uas_eh_bus_reset_handler success
[ 1230.884233] sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT
[ 1230.885093] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 08 83 be 9f 00 00 08 00
[ 1230.885952] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1230.886973] xhci-hcd xhci-hcd.9.auto: @00000000f3a6d660 00000000 00000000 1b000000 01048000
[ 1236.842345] sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN
[ 1236.843202] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 0a b9 a2 07 00 01 00 00
[ 1236.844068] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1236.845088] xhci-hcd xhci-hcd.9.auto: @00000000f3a6d680 00000000 00000000 1b000000 01038000
[ 1236.846051] scsi host0: uas_eh_bus_reset_handler start
[ 1236.846674] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1236.847701] xhci-hcd xhci-hcd.9.auto: @00000000f3a6d6a0 00000000 00000000 1b000000 01078000
[ 1236.848652] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1236.849661] xhci-hcd xhci-hcd.9.auto: @00000000f3a6d6c0 00000000 00000000 1b000000 01078000
[ 1236.952435] usb 5-1: reset SuperSpeed USB device number 2 using xhci-hcd
[ 1236.969913] scsi host0: uas_eh_bus_reset_handler success
[ 1274.829062] sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT
[ 1274.835019] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 1d 05 41 af 00 00 30 00
[ 1274.842297] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1274.848302] xhci-hcd xhci-hcd.9.auto: @00000000f3a6d990 00000000 00000000 1b000000 01048000
[ 1274.855284] sd 0:0:0:0: [sda] tag#2 unexpected response iu 10 uas-tag 1 inflight: CMD IN
[ 1274.861118] sd 0:0:0:0: [sda] tag#2 CDB: opcode=0x28 28 00 1b bc 43 d7 00 01 00 00
[ 1274.866874] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1274.872858] xhci-hcd xhci-hcd.9.auto: @00000000f3a6d9d0 00000000 00000000 1b000000 01038000
[ 1297.883446] sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT
[ 1297.889265] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x2a 2a 00 00 00 ff ff 00 00 08 00
[ 1297.895058] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1297.901005] xhci-hcd xhci-hcd.9.auto: @00000000f3a6d9f0 00000000 00000000 1b000000 01048000
[ 1297.906843] scsi host0: uas_eh_bus_reset_handler start
[ 1297.912458] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1297.918438] xhci-hcd xhci-hcd.9.auto: @00000000f3a6da10 00000000 00000000 1b000000 01078000
[ 1297.924324] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1297.930314] xhci-hcd xhci-hcd.9.auto: @00000000f3a6da30 00000000 00000000 1b000000 01078000
[ 1298.038542] usb 5-1: reset SuperSpeed USB device number 2 using xhci-hcd
[ 1298.056157] scsi host0: uas_eh_bus_reset_handler success
[ 1376.854958] sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN
[ 1376.860801] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 1b bd 57 d7 00 01 00 00
[ 1376.868264] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1376.874292] xhci-hcd xhci-hcd.9.auto: @00000000f3a6d7a0 00000000 00000000 1b000000 01038000
[ 1376.880224] sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
[ 1376.886070] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 00 1d 05 50 07 00 00 88 00
[ 1376.894335] scsi host0: uas_eh_bus_reset_handler start
[ 1376.899985] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1376.906067] xhci-hcd xhci-hcd.9.auto: @00000000f3a6d7c0 00000000 00000000 1b000000 01078000
[ 1376.912106] xhci-hcd xhci-hcd.9.auto: ERROR Transfer event for disabled endpoint or incorrect stream ring
[ 1376.918243] xhci-hcd xhci-hcd.9.auto: @00000000f3a6d7e0 00000000 00000000 1b000000 01078000
[ 1377.027035] usb 5-1: reset SuperSpeed USB device number 2 using xhci-hcd
[ 1377.045562] scsi host0: uas_eh_bus_reset_handler success

and it hangs later:
Code:
Message from syslogd@rockBOX at Mar  9 20:00:23 ...
 kernel:[ 1680.499560] Kernel panic - not syncing: hung_task: blocked tasks

Message from syslogd@rockBOX at Mar  9 20:00:23 ...
 kernel:[ 1680.968260] Kernel Offset: disabled

Message from syslogd@rockBOX at Mar  9 20:00:23 ...
 kernel:[ 1680.970737] Memory Limit: none


I tested my disk and USB 3.0 SATA adapter on my other PCs (Arch Linux on laptop, Windows 7 & Windows 10 on desktop),
It is running perfect without any problem.

Anyone having similar problems?
I need help...

Thanks.


  Won't boot with GPS breakout attached
Posted by: v0rtex - 03-09-2018, 01:04 AM - Forum: General Discussion on ROCK64 - Replies (3)

I'm fairly new to the Rock64 boards and recently decided it would be fun to play around with one. I bought the 2GB RAM version plus 16GB eMMC and power adapter. I used Etcher to flash ayufan's minimal artful arm64 image which worked great! It booted and I plugged in the network and was able to shell in just fine. I ran into problems, however, when I attempted to attach this GPS board to it: https://store.uputronics.com/index.php?r...duct_id=81. After plugging it all in I can see that the GPS board powers up just fine and even acquires a GPS signal and starts the TIMEPULSE LED going...BUT the main board doesn't boot. The white power LED is on and the red standby LED is solid with the green LED on the left side of the ethernet jack on but it doesn't appear to actually boot at all. Any suggestions?

Note: my first thought was that the expansion board could be drawing too much power but I looked at the spec sheet for the ublox MAX-8Q and it only draws up to a max of 65mA. The power supply supposedly outputs up to 3000mA which I can only imagine should be sufficient. The expansion board is designed for any of the Raspberry Pi+ models and when I look at the traces from the ublox chip to the header on the GPS board it seems that the pins do match up where they should.


  booting a kernel over tftp
Posted by: hibernick - 03-08-2018, 10:37 AM - Forum: General Discussion on ROCK64 - No Replies

Hi ,

I have configured u-boot on my rock64 to load boot scripts over tftp and it works well.
What I'm missing is a little understanding how to setup kernel boot over tftp.

I've got kernel image compiled using ayufan-rock64/linux-build repo.
It's there linux-build/kernel/arch/arm64/boot/Image

System.map shows that these addresses:

Quote:ffffff8008080000 t _head
ffffff8008080000 T _text
ffffff8008080800 T __exception_text_start
ffffff8008080800 T _stext
ffffff8008080800 T do_undefinstr


I'm not sure whether they are physical but u-boot doesn't use MMU

Can I use this kernel for booting over tftp or I have to use another configuration for this.
If yes then what load address and entry point should I use for mkinage:

Quote:mkimage -A arm64 -T kernel -O linux -C none -n 'Kernel Image'  -a $load addres -e $entry point -d boot-image linux-build/kernel/arch/arm64/boot/Image


What memory layout does rock64 have?
To be more specific, what is RAM start address?

Does it matter where I load kernel image in u-boot:

Quote:tftpboot 0x02000000 or  tftpboot 0x8000



Thanks a lot in advsnce


  Basic question - Mali x11 WebGL?
Posted by: hhh1 - 03-08-2018, 06:53 AM - Forum: Linux on Pine H64 - No Replies

1st of all I must admit the board looks EXTREMELY beautiful. Great work. Thank you.
The only thing I didn't see on the PCB is screw holes for cooling.
Currently I'm using Odroids and VIMs. But your solution looks far better.


And basic software questions prior buying:
0) Do you have x11 Mali driver for your board for normal hardware acceleration?
1) Do you release Mainline Kernel linux (Ubuntu/Arch linux) software for your board?
2) Do you have a github kernel repo if I need a custom build and do you work on it constantly?


  SD Card (W10 IoT)
Posted by: zio69 - 03-08-2018, 04:30 AM - Forum: Windows 10 IoT - Replies (4)

Hello folks,

I've been playing with my A64+ for the last few days.... for some reason, whenever I leave my A64 "alone" for a few hours, it reboots (this is just an educated guess) and enters some kind of maintenance mode: if I connect it to a monitor, it shows the "usual" spinning gears. However, it never gets out of it (or at least, it doesn't in 32 hours). Power cycling does not help - the next boot is always to spinning gears, unless (of course) I re-flash the SD-Card.
I've tried 3 times with two different cards - same thing. Examining the SD, I've seen that in fact widows did resize the data partition to reclaim the unused space at the end of the card. Tonight I'm going to give it another spin, but this time I've expanded the partition on my PC right after re-flashing the ffu. I'm using IoT Dashboard to do the flashing (in case it matters).
What I'd like to know is..... Is this an expected behavior? Did any of you experience the same thing?


Lightbulb Any news about upgraded black Pinebook?
Posted by: joec33 - 03-07-2018, 09:34 PM - Forum: General Discussion on Pinebook - Replies (1)

Are there any news about black Pinebook with 1080p screen? (https://forum.pine64.org/showthread.php?tid=5614)
Probably, there is already some information about the approximate price or the release date? Will the hardware be updated too? Is it worth waiting for more RAM or a new processor? (Rockchip?)

In my opinion, the black case looks very wonderful.

Thanks.


  First boot questions
Posted by: jgullickson - 03-07-2018, 04:26 PM - Forum: Clusterboard - Replies (2)

Just got my Clusterboard + SOPINE today and very excited to start experimenting.

I inserted the SOPINE, hooked up a serial adapter and powered it up.  The screen attached is what I got.

I'm hoping that I just overlooked something and that this doesn't mean what I think it means...



Attached Files Thumbnail(s)
   

  Configuring the PCIe x4 slot to act as 4 individual x1 ports
Posted by: TimSmall - 03-07-2018, 08:39 AM - Forum: RockPro64 Hardware and Accessories - Replies (9)

Hello,

I'm interested in connecting more than a single PCIe device to the RockPro64.

I know that it woud be possible to use a card which includes a PCIe switch chip to connect multiple PCI Express devices to the RockPro64, but that would be expensive (as well as adding latency and power usage), so I wondered if there was a simpler solution, using a simple breakout card (or custom add-in card), along with a suitable firmware config e.g. device tree overlay, to reconfigure the PCIe x4 slot as four logical PCIe x1 ports?

A custom PCIe card (or breakout card) could then be used to connect multiple PCIe x1 devices to the slot.  The application I had in mind was connecting four Asmedia ASM1061 SATA AHCI host adaptors to give 8 SATA ports for a NAS setup.

I know that various Intel chipsets support this sort of flexible PCIe configuration, but didn't know if the RK3399 did?  Any ideas?

Thanks,

Tim.


  measurements in mm of the ROCKPRO64 SBC board?
Posted by: killor - 03-07-2018, 06:40 AM - Forum: General Discussion on ROCKPRO64 - Replies (2)

Hi !!!

Good morning to everyone..

There is already published some PDF with a sketch of the measurements in mm of the [url=https://forum.pine64.org/forumdisplay.php?fid=99][/url] ROCKPRO64 SBC board and
the location of the connectors.  

it's 2D better, I still work in 2D and 3D files do not work for me ..

Thank's   Angel