9 9
mindee

NanoPI M4

Recommended Posts

17 minutes ago, Jerry Jyrer said:

Newbie question, is there a tool to do it at the software level or something that I need to plug a voltmeter to port 1 and 4 of one of the USB ports?

 

You need a USB voltmeter. They are cheap and easy to find. Something like this. Just put it into a usb port, and it will show the voltage. If it's 5V while the cpu is maxed out, and maybe a 1A load on the USB, then you're ok, if it's a lot less. Then it's no good for powering a hard drive.
afbeelding.png.0df87ec6ed815a4f0b0394fa1d4a6717.png

Share this post


Link to post
Share on other sites
8 hours ago, Jerry Jyrer said:

I need to plug a voltmeter to port 1 and 4 of one of the USB ports?

Please do not start voltage testing with a multi-meter on a USB port. I have blown up lots of electronics and trying to measure a voltage on a naked USB port would be a guaranteed way of damaging or bricking a M4.

 

Either cut a old usb cable and clean off the red and black wires and then plug the usb connector into the M4 and then measure the voltage on the attached red and black wires with a multi-meter.

 

The other option is to spend $5 and buy a USB Volt-ammeter that just plugs into the USB port and gives a digital readout.

 

 

Share this post


Link to post
Share on other sites
21 hours ago, Jerry Jyrer said:

Do you have problems connecting 2 USB hard drives and rsync between them. My situation's both drive got disconnected after <10 minutes of rsyncing at max. 

If you want to do this reliably (connect two USB hard drives self powered ) you WILL have to connect a 4 amp power supply directly to the mother board of the M4 by wiring directly to the power pins.

 

Possibly Solder directly to the pins. Then on the power supply adjust the Voltage up very slightly so that the Measured Voltage at the M4 USB ports is maybe 5.15 volts then plug on one USB self powered hard drive let it boot.

 

See what happens to the voltage on the measured USB port. I would be happy if the voltage was still above 5volts.

 

Then plug in the second self powered USB drive. See if it boots. Check USB voltage if still above 5 volts and the second drive boots you will be probably be ok.

 

If it does not boot then turn everything off and disconnect both USB drives. Then restart and see what the USB voltage is booting with no drives attached.

 

I have my voltage set a 5.3 volts "input" voltage to the M4. I am not sure what voltage at the USB is though possibly 5.15volt. Be very careful going higher. I will be interested in others opinions on this.

Share this post


Link to post
Share on other sites
2 hours ago, Seasalt said:

Please do not start voltage testing with a multi-meter on a USB port. I have blown up lots of electronics and trying to measure a voltage on a naked USB port would be a guaranteed way of damaging or bricking a M4.

 

Thank you Seasalt. Much appreciated. It was a little too late but lucky enough that all it was just some spark. I stopped before much drama happening. All things seem to be working okay. : )

 

10 hours ago, NicoD said:

You need a USB voltmeter. They are cheap and easy to find. Something like this. Just put it into a usb port, and it will show the voltage.

 

Thanks NicoD. I'll get it to test things out.

 

2 hours ago, Seasalt said:

If you want to do this reliably (connect two USB hard drives self powered ) you WILL have to connect a 4 amp power supply directly to the mother board of the M4 by wiring directly to the power pins.

 

Possibly Solder directly to the pins. Then on the power supply adjust the Voltage up very slightly so that the Measured Voltage at the M4 USB ports is maybe 5.15 volts then plug on one USB self powered hard drive let it boot.

 

See what happens to the voltage on the measured USB port. I would be happy if the voltage was still above 5volts.

 

Then plug in the second self powered USB drive. See if it boots. Check USB voltage if still above 5 volts and the second drive boots you will be probably be ok.

 

If it does not boot then turn everything off and disconnect both USB drives. Then restart and see what the USB voltage is booting with no drives attached.

 

I have my voltage set a 5.3 volts "input" voltage to the M4. I am not sure what voltage at the USB is though possibly 5.15volt. Be very careful going higher. I will be interested in others opinions on this.

 

Thanks for the info. I would try my best to power the board with usb-c before going to the pin route. I have ordered the DashCharger 5V 4A. I'll get usb volt-meter and test things out. I initially thought that 5V 3A I have is good enough. That's the max spec for USB-C at 5V I believe. (. Anyone success on rsync between USB hard drives attaching to the board with 3A/4A adapter?

Share this post


Link to post
Share on other sites
18 hours ago, NicoD said:

There is a problem with undervoltage when you are using a bad cable and Armbian.


When you are using a bad cable.

 

1 hour ago, Jerry Jyrer said:

That's the max spec for USB-C at 5V I believe.

 

"USB Type-C is not PD-compliant". I think this is the core of the problem.

Share this post


Link to post
Share on other sites
1 hour ago, Igor said:
20 hours ago, NicoD said:

There is a problem with undervoltage when you are using a bad cable and Armbian.


When you are using a bad cable.

Because Armbian is clocked higher(what I like), it uses more power. 2A instead of 1.5A with FriendlyDesktop. So the undervoltage is bigger when using a bad cable + Armbian.
It`s just a fact Igor. I`m not talking bad about Armbian. The reason is a bad cable, but with FriendlyDesktop the problem is a lot less.

I don`t know if this is the problem here, but if we don`t measure, we don`t know.
Cheers

Share this post


Link to post
Share on other sites
46 minutes ago, NicoD said:

is bigger when using a bad cable + Armbian.


I agree with that. As it was initially written someone would think that this is our fault. Which is not the case. NanoPC T4 doesn't have this problem when powered with 12V.

Share this post


Link to post
Share on other sites
2 hours ago, Igor said:

NanoPC T4 doesn't have this problem when powered with 12V.

 

Igor do you have a way of measuring the USB port voltage on NanoPC t4 when powered by 12 volts. also what is the voltage of usb port when it has one or two 2.5 inch self powering hard drives mounted.

 

Thanks Seasalt.

Share this post


Link to post
Share on other sites
12 minutes ago, Seasalt said:

Igor do you have a way of measuring the USB port voltage on NanoPC t4 when powered by 12 volts.

 

4.97V and 4.95 with a mechanical drive on another USB port.

Share this post


Link to post
Share on other sites

Just a quick update, I've just received a brandnew USB-C 5V 4A. Same problem, no success. I'm waiting for an USB voltmeter to be sure if it's about under voltage or something else. dmesg similar to before 

 

kern  :warn  : [  +0.192987] xhci-hcd xhci-hcd.6.auto: xHCI host not responding to stop endpoint command.
kern  :warn  : [  +0.000020] xhci-hcd xhci-hcd.6.auto: Assuming host is dying, halting host.
kern  :err   : [  +0.013582] xhci-hcd xhci-hcd.6.auto: HC died; cleaning up
kern  :err   : [  +0.000051] hub 4-1:1.0: hub_port_status failed (err = -22)
kern  :err   : [  +0.000019] usb 4-1-port2: cannot reset (err = -22)
kern  :info  : [  +0.000050] usb 3-1: USB disconnect, device number 2
kern  :info  : [  +0.000068] usb 4-1.2: USB disconnect, device number 3
kern  :info  : [  +0.001052] usb 4-1: USB disconnect, device number 2

Share this post


Link to post
Share on other sites
2 hours ago, Jerry Jyrer said:

to be sure if it's about under voltage or something else


Those errors are typical for under voltage.  Limit CPU speed and see if that helps - nano etc/default/cpufrequtils and set MAX lower following by service restart or by rebooting.

Share this post


Link to post
Share on other sites
On 12/5/2018 at 10:31 PM, Igor said:

Limit CPU speed and see if that helps - nano etc/default/cpufrequtils and set MAX lower following by service restart or by rebooting.

tried, it doesn't help.

 

On 12/3/2018 at 12:06 PM, NicoD said:

You need a USB voltmeter. They are cheap and easy to find. Something like this. Just put it into a usb port, and it will show the voltage. If it's 5V while the cpu is maxed out, and maybe a 1A load on the USB, then you're ok, if it's a lot less. Then it's no good for powering a hard drive.

Got a USB voltmeter. 

 

Board Only: ~4.9V

One hard drive connected: ~4.8V

two hard drives connected: ~4.77V

 

Rsync, staying around 4.77V but the same problem occured with both of them lost connections. Results were similar either using 5V 3A adapter or 5V 4A one. 

 

I was wondering if this is really about under volate and amp supplying, can I get a 5V 8A (or higher) with a barrel to USB converter -- e.g.

 

https://www.amazon.com/JacobsParts-Barrel-Female-Connector-Adapter/dp/B00QHL2PTA

 

https://www.amazon.com/ALITOVE-Converter-Transformer-5-5x2-1mm-100V-240V/dp/B078RZBL8X

 

 

 

Share this post


Link to post
Share on other sites
1 hour ago, Jerry Jyrer said:

Board Only: ~4.9V

One hard drive connected: ~4.8V

two hard drives connected: ~4.77V

The power supply you have is not even getting the board alone to a 5v usb voltage.

 

Can you tweak a little trim pot on the power supply to get the voltage to say 5.15. Be very careful you do not blow anything up.

Share this post


Link to post
Share on other sites
10 hours ago, Seasalt said:

The power supply you have is not even getting the board alone to a 5v usb voltage.

 

Got another 5V 4A

 

Board only: 5.13V

Hard drives connected : 4.97

 

Same problem. Is it really the under-voltage problem still or something else might be covering this?

Share this post


Link to post
Share on other sites
41 minutes ago, Jerry Jyrer said:

I'm pretty sure that's not the case.

Are you simply trying to copied whole root "/" ?

But are you excluding "/lost+found" folder from rsync ?

If not, google about the meaning of this "/lost+found" folder, it simply can't be copied ...

 

Share this post


Link to post
Share on other sites

I got a normal DC power adapter 5V 8A powering via GPIO pin 4 (+) and 6(GDN).  The USB Voltmeter reports 5.2V to 5.0V.  The same problem occured. 

I really doubt that it's about under-votage nor power supply to the board. Is it possible this is a bad board? 

 

Can anyone try to rsync between two connected USB hard drives -- says successfully sync ~1TB of data on Nanopi M4?

 

Share this post


Link to post
Share on other sites

A normal cp creates the same problem also:

 

$ sudo cp -Rf /mnt/Photos-Videos/* /media/WDMyBook/Photos-Videos/

 

$dmesg -xH 

shows

Spoiler

kern  :warn  : [Dec11 20:10] xhci-hcd xhci-hcd.6.auto: xHCI host not responding to stop endpoint command.
kern  :warn  : [  +0.000027] xhci-hcd xhci-hcd.6.auto: Assuming host is dying, halting host.
kern  :warn  : [  +0.000019] xhci-hcd xhci-hcd.6.auto: xHCI host not responding to stop endpoint command.
kern  :warn  : [  +0.000018] xhci-hcd xhci-hcd.6.auto: Assuming host is dying, halting host.
kern  :err   : [  +0.013487] xhci-hcd xhci-hcd.6.auto: HC died; cleaning up
kern  :err   : [  +0.000049] xhci-hcd xhci-hcd.6.auto: HC died; cleaning up
kern  :info  : [  +0.000327] usb 3-1: USB disconnect, device number 2
kern  :info  : [  +0.004183] usb 4-1: USB disconnect, device number 2
kern  :info  : [  +0.000025] usb 4-1.1: USB disconnect, device number 3
kern  :info  : [  +0.005898] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
kern  :info  : [  +0.000026] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 cc 5b 75 60 00 00 f0 00
kern  :err   : [  +0.000011] blk_update_request: I/O error, dev sda, sector 3428545888
kern  :info  : [  +0.000158] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
kern  :info  : [  +0.000013] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 cc 5b 76 50 00 00 10 00
kern  :err   : [  +0.000008] blk_update_request: I/O error, dev sda, sector 3428546128
kern  :info  : [  +0.031692] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
kern  :info  : [  +0.000024] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 35 3e 90 00 00 00 f0 00 00
kern  :err   : [  +0.000010] blk_update_request: I/O error, dev sdb, sector 3489424
kern  :info  : [  +0.035909] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
kern  :info  : [  +0.000022] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 35 3f 80 00 00 00 80 00 00
kern  :err   : [  +0.000009] blk_update_request: I/O error, dev sdb, sector 3489664
kern  :warn  : [  +0.000013] EXT4-fs warning (device sdb1): ext4_end_bio:330: I/O error -5 writing to inode 40436064 (offset 0 size 2097152 starting block 43
kern  :err   : [  +0.000011] Buffer I/O error on device sdb1, logical block 435712
kern  :err   : [  +0.000025] Buffer I/O error on device sdb1, logical block 435713
kern  :err   : [  +0.000009] Buffer I/O error on device sdb1, logical block 435714
kern  :err   : [  +0.000008] Buffer I/O error on device sdb1, logical block 435715
kern  :err   : [  +0.000008] Buffer I/O error on device sdb1, logical block 435716
kern  :err   : [  +0.000007] Buffer I/O error on device sdb1, logical block 435717
kern  :err   : [  +0.000008] Buffer I/O error on device sdb1, logical block 435718
kern  :err   : [  +0.000008] Buffer I/O error on device sdb1, logical block 435719
kern  :err   : [  +0.000007] Buffer I/O error on device sdb1, logical block 435720
kern  :err   : [  +0.000008] Buffer I/O error on device sdb1, logical block 435721
kern  :info  : [  +0.039892] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
kern  :info  : [  +0.000020] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 01 d1 c4 0a 20 00 00 00 70 00 00
kern  :err   : [  +0.000008] blk_update_request: I/O error, dev sdb, sector 7814253088
kern  :info  : [  +0.035965] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
kern  :info  : [  +0.000039] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 35 40 00 00 00 00 f0 00 00
kern  :err   : [  +0.000026] blk_update_request: I/O error, dev sdb, sector 3489792
kern  :info  : [  +0.039941] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
kern  :info  : [  +0.000017] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 45 78 00 00 00 08 00 00
kern  :err   : [  +0.000007] blk_update_request: I/O error, dev sdb, sector 17784
kern  :err   : [  +0.000010] Buffer I/O error on dev sdb1, logical block 1967, lost async page write
kern  :info  : [  +0.035934] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
kern  :info  : [  +0.000019] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 35 40 f0 00 00 00 f0 00 00
kern  :err   : [  +0.000007] blk_update_request: I/O error, dev sdb, sector 3490032
kern  :info  : [  +0.040087] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
kern  :info  : [  +0.000041] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 35 41 e0 00 00 00 f0 00 00
kern  :err   : [  +0.000019] blk_update_request: I/O error, dev sdb, sector 3490272
kern  :notice: [  +0.014343] sd 0:0:0:0: [sda] Synchronizing SCSI cache
kern  :info  : [  +0.000131] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
kern  :info  : [  +0.022648] usb 4-1.3: USB disconnect, device number 4
kern  :info  : [  +0.006748] sd 1:0:0:0: [sdb] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
kern  :info  : [  +0.000021] sd 1:0:0:0: [sdb] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 35 42 d0 00 00 00 f0 00 00
kern  :err   : [  +0.000008] blk_update_request: I/O error, dev sdb, sector 3490512
kern  :warn  : [  +0.000092] EXT4-fs warning (device sdb1): ext4_end_bio:330: I/O error -5 writing to inode 40436064 (offset 0 size 2097152 starting block 43
kern  :warn  : [  +0.000559] EXT4-fs warning (device sdb1): ext4_end_bio:330: I/O error -5 writing to inode 40436064 (offset 2097152 size 192512 starting blo
kern  :warn  : [  +0.000322] EXT4-fs warning (device sdb1): ext4_end_bio:330: I/O error -5 writing to inode 40436065 (offset 0 size 917504 starting block 435
kern  :err   : [  +0.000201] Buffer I/O error on dev sda1, logical block 428548827, async page read
kern  :err   : [  +0.000200] Buffer I/O error on dev sda1, logical block 428548859, async page read
kern  :warn  : [  +0.000134] EXT4-fs warning (device sdb1): ext4_end_bio:330: I/O error -5 writing to inode 40436065 (offset 917504 size 98304 starting block
kern  :warn  : [  +0.000184] JBD2: Detected IO errors while flushing file data on sdb1-8
kern  :err   : [  +0.000035] Aborting journal on device sdb1-8.
kern  :err   : [  +0.000133] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
kern  :warn  : [  +0.000099] JBD2: Detected IO errors while flushing file data on sdb1-8
kern  :err   : [  +0.000641] Buffer I/O error on dev sda1, logical block 428548827, async page read
kern  :err   : [  +0.000694] Buffer I/O error on dev sda1, logical block 124112098, async page read
kern  :err   : [  +0.000300] Buffer I/O error on dev sda1, logical block 124112098, async page read
kern  :err   : [  +0.001101] Buffer I/O error on dev sda1, logical block 124112098, async page read
kern  :err   : [  +0.000441] Buffer I/O error on dev sda1, logical block 124112098, async page read
kern  :err   : [  +0.000576] Buffer I/O error on dev sda1, logical block 124112098, async page read
kern  :err   : [  +0.000795] Buffer I/O error on dev sda1, logical block 387667888, async page read
kern  :warn  : [ +10.817160] buffer_io_error: 41 callbacks suppressed
kern  :err   : [  +0.000025] Buffer I/O error on dev sda1, logical block 114076692, async page read
kern  :err   : [  +0.028778] Buffer I/O error on dev sda1, logical block 114076697, async page read

 

 

Edited by Tido
added spoiler

Share this post


Link to post
Share on other sites
On 7/2/2018 at 8:29 PM, TonyMac32 said:

Well, if the manufacturing is done intelligently, the tailings get recycled nicely.  You could argue the energy involved in it, but I'd probably counter the cast ones use far more energy than simply machining out of large blocks.  In general aluminum and steel are quite "eco" compared to any plastic, and certainly better than say copper as far as mining/refining are concerned.  (off topic, but interesting)

 

I would agree - not everyone mills aluminum cases out of larger blocks unless they're a certain company out of cupertino...

 

Silly Excess here - and for a startup - costing is going to be a problem...

 

spreedbox.png

spreedbox2.jpg

Share this post


Link to post
Share on other sites
23 hours ago, Jerry Jyrer said:

I really doubt that it's about under-votage nor power supply to the board. Is it possible this is a bad board? 

 

 

It looks like I might find the problems. I connected my Toshiba external hard drive (2TB) with another usb 2.0 extension cable. Basically, instead of contect it as usb 3.0, I made it as usb 2.0. My WD Mybook 8TB is connecting to the board directly as usb 3.0

 

Copying now going >1GB of data and still continue on going.  dmesg shows some errors and warnning about resetting the speed though but the rsync is still good and continue:

 

kern  :info  : [Dec12 19:26] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd
kern  :warn  : [  +0.138467] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes
kern  :warn  : [  +0.000055] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes
kern  :warn  : [  +6.776374] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued?
kern  :info  : [ +31.102096] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd
kern  :warn  : [  +0.133845] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes
kern  :warn  : [  +0.000056] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes
kern  :warn  : [Dec12 19:27] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued?
kern  :warn  : [  +4.933371] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued?
kern  :warn  : [ +35.645125] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued?
kern  :info  : [Dec12 19:28] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd
kern  :warn  : [  +0.138459] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes
kern  :warn  : [  +0.000057] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes
kern  :warn  : [ +17.781779] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued?
kern  :warn  : [  +4.944248] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued?
kern  :info  : [Dec12 19:29] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd
kern  :warn  : [  +0.134115] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes
kern  :warn  : [  +0.000055] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes
kern  :info  : [ +36.858678] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd
kern  :warn  : [  +0.133971] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes
kern  :warn  : [  +0.000056] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes
kern  :warn  : [Dec12 19:30] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued?
kern  :warn  : [  +9.477617] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued?
kern  :warn  : [  +6.977276] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued?
kern  :warn  : [Dec12 19:31] xhci-hcd xhci-hcd.6.auto: WARN Event TRB for slot 5 ep 2 with no TDs queued?
kern  :info  : [ +37.592164] usb 3-1.1.1: reset high-speed USB device number 4 using xhci-hcd
kern  :warn  : [  +0.134474] usb 3-1.1.1: ep 0x81 - rounding interval to 16 microframes, ep desc says 20 microframes
kern  :warn  : [  +0.000068] usb 3-1.1.1: ep 0x2 - rounding interval to 16 microframes, ep desc says 20 microframes
 

 

Share this post


Link to post
Share on other sites
On 12/8/2018 at 5:37 PM, Jerry Jyrer said:

Is it really the under-voltage problem

 

Of course. You need to fix this otherwise everything you do is just a waste of time. And it's under-VOLTAGE and not under-current so as long as you ignore Ohm's law you're getting nowhere. The problem is high resistance and most probably (and as usual) the cable between PSU and device is to blame.

Share this post


Link to post
Share on other sites
18 hours ago, tkaiser said:

Of course. You need to fix this otherwise everything you do is just a waste of time. And it's under-VOLTAGE and not under-current so as long as you ignore Ohm's law you're getting nowhere. The problem is high resistance and most probably (and as usual) the cable between PSU and device is to blame.

 

Half correct sir. I fixed the power things. The problem wasn't. What really did the trick was to connect one hard drive with an usb extension (usb 2.0). The extension has no external power supply whatsoever. If any of my cabel is bad, adding additional one result worse. But in fact, it did the trick. I successfully rsync 1.7TB as expected. Now, I'm going to just connect my original usb-c adapter --- the one that all of us said it's the problem -- instead of the DC power adapter 5V 8A powering via GPIO pin 4 (+) and 6(GDN).  I'm about 80% sure it wouldn't have any problem.  What would it be really a problem to connect 2 USB 3.0 gen 1 external hard drives to Nanopi M4 and doing their full capacity reading/writing. Driver, board, or kernel issues?

 

Thought?

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
9 9