Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread
Posted by JeffS
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 22, 2017 09:20PM |
Registered: 9 years ago Posts: 1,516 |
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 22, 2017 09:36PM |
Admin Registered: 13 years ago Posts: 18,898 |
The 2-USB small card is where I connected the power Hub to.
One port is for the USB 3.0 drive. One port is for USB cable to the hub.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/22/2017 09:38PM by bodhi.
One port is for the USB 3.0 drive. One port is for USB cable to the hub.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/22/2017 09:38PM by bodhi.
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 22, 2017 09:54PM |
Registered: 9 years ago Posts: 1,516 |
bodhi Wrote:
-------------------------------------------------------
> The 2-USB small card is where I connected the powe
> r Hub to.
>
> One port is for the USB 3.0 drive. One port is for
> USB cable to the hub.
I did that, and the only reliable 5v nearby is the one from the Pogoplug, and I got a little further but still that same "dying" error.
I might be able to look around tomorrow for a better 5v source, but let it rest for tonight, my health is kind of going south. Not yer fault :-)
=========
-= Cloud 9 =-
-------------------------------------------------------
> The 2-USB small card is where I connected the powe
> r Hub to.
>
> One port is for the USB 3.0 drive. One port is for
> USB cable to the hub.
I did that, and the only reliable 5v nearby is the one from the Pogoplug, and I got a little further but still that same "dying" error.
I might be able to look around tomorrow for a better 5v source, but let it rest for tonight, my health is kind of going south. Not yer fault :-)
=========
-= Cloud 9 =-
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 22, 2017 11:29PM |
Admin Registered: 13 years ago Posts: 18,898 |
OK. I declare that it was a failed expirement for the Pogo V3 :))
It seems the timing is not correct, most likely we need a different XHCI driver for OXNAS than the one we are using from mainline.
About their claim that the card is Intel XHCI compliance. I'm reserving my judgement until I try this on the iConnect box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
It seems the timing is not correct, most likely we need a different XHCI driver for OXNAS than the one we are using from mainline.
About their claim that the card is Intel XHCI compliance. I'm reserving my judgement until I try this on the iConnect box.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 22, 2017 11:41PM |
Registered: 9 years ago Posts: 1,516 |
bodhi Wrote:
-------------------------------------------------------
> About their claim that the card is Intel XHCI comp
> liance. I'm reserving my judgement until I try thi
> s on the iConnect box.
Best of luck with that. I'm not too far away and who knows, maybe having this mpcie card around will serve an even greater purpose in the future. Like the plaque on my wall says "You have only failed when you fail to try". So here's to computer science :-)
=========
-= Cloud 9 =-
-------------------------------------------------------
> About their claim that the card is Intel XHCI comp
> liance. I'm reserving my judgement until I try thi
> s on the iConnect box.
Best of luck with that. I'm not too far away and who knows, maybe having this mpcie card around will serve an even greater purpose in the future. Like the plaque on my wall says "You have only failed when you fail to try". So here's to computer science :-)
=========
-= Cloud 9 =-
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 23, 2017 12:26AM |
Admin Registered: 13 years ago Posts: 18,898 |
> Best of luck with that. I'm not too far away and w
> ho knows, maybe having this mpcie card around will
> serve an even greater purpose in the future. Like
> the plaque on my wall says "You have only failed w
> hen you fail to try". So here's to computer scienc
> e :-)
Keep it around handy. If I can get it to work on the iConnect, then we'll know it is not junk :) and it is just waiting for its time on the Pogo V3. The OXNAS SoC is quite problematic, that's why we can buy it cheaply. I was abandon it for a while, too. And if it was not for you and Leggo (who did an excellent job modding the HW), I would just run the old kernel on my box until it dies :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> ho knows, maybe having this mpcie card around will
> serve an even greater purpose in the future. Like
> the plaque on my wall says "You have only failed w
> hen you fail to try". So here's to computer scienc
> e :-)
Keep it around handy. If I can get it to work on the iConnect, then we'll know it is not junk :) and it is just waiting for its time on the Pogo V3. The OXNAS SoC is quite problematic, that's why we can buy it cheaply. I was abandon it for a while, too. And if it was not for you and Leggo (who did an excellent job modding the HW), I would just run the old kernel on my box until it dies :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 23, 2017 08:55AM |
Registered: 11 years ago Posts: 1,303 |
JoeyPogoPlugE02 Wrote:
-------------------------------------------------------
> Yeah Pogoplug's own USB 5v really is 5 volts. I just tried starting it up and mounting the hard drive one last time and right when it was mounting it froze. It acted a lot friendlier than previous trials. So I'll try one last time with a USB stick formatted from Mint, and shelve this and have answered the question.
>
If you still have the USB Volt / Amp / Wattage meter dongle, use it to measure how much current is drawn by the HDD.
-------------------------------------------------------
> Yeah Pogoplug's own USB 5v really is 5 volts. I just tried starting it up and mounting the hard drive one last time and right when it was mounting it froze. It acted a lot friendlier than previous trials. So I'll try one last time with a USB stick formatted from Mint, and shelve this and have answered the question.
>
If you still have the USB Volt / Amp / Wattage meter dongle, use it to measure how much current is drawn by the HDD.
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 23, 2017 12:51PM |
Registered: 9 years ago Posts: 1,516 |
Working?
Here's a nice diversion :-D Got the idea to clone the Debian OS from 8GB USB stick to the SATA drive and boot from that.
(side story) Bodhi helped change the Envs a while back so anything on the USB stick cloned to SATA drive would boot it straight up if it were plugged-in. Unfortunately today that's where I discovered that particular OS on USB is missing or lost. So I went the old way, booted from my everyday USB 2 stick, and pulled it out as the cloned 8GB partition of SATA drive started chattering, which shifted it to run from the SATA drive.
Now that we're booted into SATA drive, logged in and plug in newly-Minted USB storage stick from yesterday:
fdisk -l
dmesg
lsusb
lsusb -vvv
Mountin' Dew
It would appear it worked, though write permissions aren't set to work and I don't know how to do that. If you have any idea to try something simple,commands to enter do tell and I'll leave this run a while.
=========
-= Cloud 9 =-
Edited 3 time(s). Last edit at 03/23/2017 01:25PM by JoeyPogoPlugE02.
Here's a nice diversion :-D Got the idea to clone the Debian OS from 8GB USB stick to the SATA drive and boot from that.
(side story) Bodhi helped change the Envs a while back so anything on the USB stick cloned to SATA drive would boot it straight up if it were plugged-in. Unfortunately today that's where I discovered that particular OS on USB is missing or lost. So I went the old way, booted from my everyday USB 2 stick, and pulled it out as the cloned 8GB partition of SATA drive started chattering, which shifted it to run from the SATA drive.
Now that we're booted into SATA drive, logged in and plug in newly-Minted USB storage stick from yesterday:
fdisk -l
root@DebianPlug:~# fdisk -l Disk /dev/mtdblock0: 14 MiB, 14680064 bytes, 28672 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xaaaaaaaa Device Boot Start End Sectors Size Id Type /dev/mtdblock0p1 ? 2863311530 5726623059 2863311530 1.3T aa unknown /dev/mtdblock0p2 ? 2863311530 5726623059 2863311530 1.3T aa unknown /dev/mtdblock0p3 ? 2863311530 4294989139 1431677610 682.7G aa unknown /dev/mtdblock0p4 ? 2863311530 5721052499 2857740970 1.3T aa unknown Disk /dev/mtdblock1: 114 MiB, 119537664 bytes, 233472 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sda: 149.1 GiB, 160041885696 bytes, 312581808 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x57cbcc49 Device Boot Start End Sectors Size Id Type /dev/sda1 2048 15147007 15144960 7.2G 83 Linux Disk /dev/zram0: 22.1 MiB, 23220224 bytes, 5669 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram1: 22.1 MiB, 23220224 bytes, 5669 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram2: 22.1 MiB, 23220224 bytes, 5669 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/zram3: 22.1 MiB, 23220224 bytes, 5669 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/sdb: 28.7 GiB, 30752000000 bytes, 60062500 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xeebf5747 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 60061695 60059648 28.7G 83 Linux
dmesg
root@DebianPlug:~# dmesg
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.4.48-oxnas-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP PREEMPT Wed Feb 15 02:59:11 PST 2017
[ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5787d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Pogoplug V3 Pro
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 32768
[ 0.000000] free_area_init_node: node 0, pgdat c08a6980, node_mem_map c7ef9000
[ 0.000000] Normal zone: 256 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 32768 pages, LIFO batch:7
[ 0.000000] DT missing boot CPU MPIDR[23:0], fall back to default cpu_logical_map
[ 0.000000] PERCPU: Embedded 12 pages/cpu @c7eda000 s17696 r8192 d23264 u49152
[ 0.000000] pcpu-alloc: s17696 r8192 d23264 u49152 alloc=12*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 117048K/131072K available (6406K kernel code, 288K rwdata, 1908K rodata, 228K init, 247K bss, 14024K reserved, 0K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xc8800000 - 0xff800000 ( 880 MB)
lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.text : 0xc0008000 - 0xc0826ddc (8316 kB)
.init : 0xc0827000 - 0xc0860000 ( 228 kB)
.data : 0xc0860000 - 0xc08a8338 ( 289 kB)
.bss : 0xc08a8338 - 0xc08e6310 ( 248 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:160
[ 0.000000] clocksource: rps_clocksource_timer: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 19112603332 ns
[ 0.000010] sched_clock: 24 bits at 390kHz, resolution 2560ns, wraps every 21474835200ns
[ 0.000161] Console: colour dummy device 80x30
[ 0.000192] Calibrating delay loop... 339.14 BogoMIPS (lpj=1695744)
[ 0.050022] pid_max: default: 32768 minimum: 301
[ 0.050186] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.050204] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.051008] Initializing cgroup subsys net_cls
[ 0.051092] CPU: Testing write buffer coherency: ok
[ 0.051514] Setting up static identity map for 0x60008220 - 0x60008258
[ 0.190136] Brought up 2 CPUs
[ 0.190159] SMP: Total of 2 processors activated (678.29 BogoMIPS).
[ 0.190932] devtmpfs: initialized
[ 0.195760] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.196021] prandom: seed boundary self test passed
[ 0.200432] prandom: 100 self tests passed
[ 0.200460] pinctrl core: initialized pinctrl subsystem
[ 0.201282] NET: Registered protocol family 16
[ 0.201825] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.230018] cpuidle: using governor ladder
[ 0.260014] cpuidle: using governor menu
[ 0.265018] gpio-oxnas 44000000.gpio: at address c8848000
[ 0.265397] gpio-oxnas 44100000.gpio: at address c884a000
[ 0.265958] pinctrl-oxnas pinctrl: initialized OX820 pinctrl driver
[ 0.388569] oxnas-pcie 47c00000.pcie-controller: PCIe version/deviceID 0x82510b5
[ 0.388687] oxnas-pcie 47c00000.pcie-controller: link up
[ 0.389002] oxnas-pcie 47c00000.pcie-controller: PCI host bridge to bus 0000:00
[ 0.389030] pci_bus 0000:00: root bus resource [mem 0x48000000-0x49ffffff]
[ 0.389048] pci_bus 0000:00: root bus resource [mem 0x4a000000-0x4bdfffff pref]
[ 0.389063] pci_bus 0000:00: root bus resource [io 0x0000-0xfffff]
[ 0.389081] pci_bus 0000:00: root bus resource [bus 00-7f]
[ 0.389143] pci 0000:00:00.0: [1912:0015] type 00 class 0x0c0330
[ 0.389230] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x00001fff 64bit]
[ 0.389411] pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
[ 0.389762] PCI: bus0: Fast back to back transfers disabled
[ 0.389857] pci 0000:00:00.0: BAR 0: assigned [mem 0x48000000-0x48001fff 64bit]
[ 0.390397] vgaarb: loaded
[ 0.390886] SCSI subsystem initialized
[ 0.391247] libata version 3.00 loaded.
[ 0.391754] usbcore: registered new interface driver usbfs
[ 0.391854] usbcore: registered new interface driver hub
[ 0.392012] usbcore: registered new device driver usb
[ 0.392220] pps_core: LinuxPPS API ver. 1 registered
[ 0.392232] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.392279] PTP clock support registered
[ 0.394396] clocksource: Switched to clocksource rps_clocksource_timer
[ 0.413227] NET: Registered protocol family 2
[ 0.414115] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.414159] TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
[ 0.414192] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.414289] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.414330] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.414597] NET: Registered protocol family 1
[ 0.415139] RPC: Registered named UNIX socket transport module.
[ 0.415160] RPC: Registered udp transport module.
[ 0.415170] RPC: Registered tcp transport module.
[ 0.415180] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.415242] pci 0000:00:00.0: enabling device (0140 -> 0142)
[ 0.415311] PCI: CLS 32 bytes, default 32
[ 0.415644] Unpacking initramfs...
[ 0.806359] Freeing initrd memory: 3644K (c7a99000 - c7e28000)
[ 0.807756] futex hash table entries: 512 (order: 2, 16384 bytes)
[ 0.807930] Initialise system trusted keyring
[ 0.832545] zbud: loaded
[ 0.851353] NFS: Registering the id_resolver key type
[ 0.851427] Key type id_resolver registered
[ 0.851443] Key type id_legacy registered
[ 0.851484] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.851507] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 0.852398] fuse init (API version 7.23)
[ 0.854407] Key type big_key registered
[ 0.933703] Key type asymmetric registered
[ 0.933731] Asymmetric key parser 'x509' registered
[ 0.933859] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.933885] io scheduler noop registered
[ 0.933903] io scheduler deadline registered
[ 0.933964] io scheduler cfq registered (default)
[ 0.934617] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[ 0.936199] console [ttyS0] disabled
[ 0.936294] 44200000.uart: ttyS0 at MMIO 0x44200000 (irq = 6, base_baud = 390625) is a 16550A
[ 1.521623] console [ttyS0] enabled
[ 1.568939] loop: module loaded
[ 1.820971] scsi host0: sata_oxnas
[ 1.874206] ata1: SATA max UDMA/133 irq 7
[ 1.878289] sata_oxnas: resetting SATA core
[ 1.879324] nand: Could not find valid ONFI parameter page; aborting
[ 1.879367] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[ 1.879375] nand: Hynix NAND 128MiB 3,3V 8-bit
[ 1.879383] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.879400] Scanning device for bad blocks
[ 1.961218] 2 ofpart partitions found on MTD device 41000000.nand
[ 1.967285] Creating 2 MTD partitions on "41000000.nand":
[ 1.972695] 0x000000000000-0x000000e00000 : "boot"
[ 1.979384] 0x000000e00000-0x000008000000 : "data"
[ 1.986670] oxnas-gmac 40400000.ethernet: no reset control found
[ 1.992696] stmmac - user ID: 0x12, Synopsys ID: 0x35
[ 1.997721] Ring mode enabled
[ 2.000788] DMA HW capability register supported
[ 2.005294] Enhanced/Alternate descriptors
[ 2.009625] Enabled extended descriptors
[ 2.013713] RX Checksum Offload Engine supported (type 2)
[ 2.019171] TX Checksum insertion supported
[ 2.023436] Wake-Up On Lan supported
[ 2.027079] Enable RX Mitigation via HW Watchdog Timer
[ 2.048465] libphy: stmmac: probed
[ 2.051927] eth%d: PHY ID 001cc914 at 0 IRQ POLL (stmmac-0:00) active
[ 2.058342] eth%d: PHY ID 001cc914 at 3 IRQ POLL (stmmac-0:03)
[ 2.065018] PPP generic driver version 2.4.2
[ 2.069836] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.076405] ehci-pci: EHCI PCI platform driver
[ 2.081290] oxnas-ehci 40200100.ehci: EHCI Host Controller
[ 2.086786] oxnas-ehci 40200100.ehci: new USB bus registered, assigned bus number 1
[ 2.094632] oxnas-ehci 40200100.ehci: irq 10, io mem 0x40200100
[ 2.120151] oxnas-ehci 40200100.ehci: USB 2.0 started, EHCI 1.00
[ 2.126471] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 2.133268] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.140472] usb usb1: Product: EHCI Host Controller
[ 2.145326] usb usb1: Manufacturer: Linux 4.4.48-oxnas-tld-1 ehci_hcd
[ 2.151751] usb usb1: SerialNumber: 40200100.ehci
[ 2.157365] hub 1-0:1.0: USB hub found
[ 2.161228] hub 1-0:1.0: 2 ports detected
[ 2.166238] xhci_hcd 0000:00:00.0: xHCI Host Controller
[ 2.171537] xhci_hcd 0000:00:00.0: new USB bus registered, assigned bus number 2
[ 2.184458] xhci_hcd 0000:00:00.0: hcc params 0x014051cf hci version 0x100 quirks 0x00000090
[ 2.193320] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 2.200081] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.207313] usb usb2: Product: xHCI Host Controller
[ 2.212188] usb usb2: Manufacturer: Linux 4.4.48-oxnas-tld-1 xhci-hcd
[ 2.218595] usb usb2: SerialNumber: 0000:00:00.0
[ 2.224166] hub 2-0:1.0: USB hub found
[ 2.227978] hub 2-0:1.0: 2 ports detected
[ 2.232926] xhci_hcd 0000:00:00.0: xHCI Host Controller
[ 2.238154] xhci_hcd 0000:00:00.0: new USB bus registered, assigned bus number 3
[ 2.245749] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[ 2.254110] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
[ 2.261086] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.268277] usb usb3: Product: xHCI Host Controller
[ 2.273175] usb usb3: Manufacturer: Linux 4.4.48-oxnas-tld-1 xhci-hcd
[ 2.279587] usb usb3: SerialNumber: 0000:00:00.0
[ 2.285186] hub 3-0:1.0: USB hub found
[ 2.288995] hub 3-0:1.0: 2 ports detected
[ 2.294154] usbcore: registered new interface driver cdc_acm
[ 2.299791] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 2.307893] usbcore: registered new interface driver cdc_wdm
[ 2.313797] usbcore: registered new interface driver usb-storage
[ 2.319953] usbcore: registered new interface driver usbserial
[ 2.325870] usbcore: registered new interface driver usbserial_generic
[ 2.332700] usbserial: USB Serial support registered for generic
[ 2.339095] mousedev: PS/2 mouse device common for all mice
[ 2.344898] i2c /dev entries driver
[ 2.349690] hidraw: raw HID events driver (C) Jiri Kosina
[ 2.355358] usbcore: registered new interface driver usbhid
[ 2.361162] usbhid: USB HID core driver
[ 2.367185] NET: Registered protocol family 10
[ 2.373199] sit: IPv6 over IPv4 tunneling driver
[ 2.378736] NET: Registered protocol family 17
[ 2.383441] Key type dns_resolver registered
[ 2.388984] registered taskstats version 1
[ 2.393671] Loading compiled-in X.509 certificates
[ 2.398581] zswap: loaded using pool lzo/zbud
[ 2.418513] Key type encrypted registered
[ 2.430036] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.480156] usb 1-1: new high-speed USB device number 2 using oxnas-ehci
[ 2.632030] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[ 2.638707] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 2.645841] usb 1-1: Product: USB2.0 Hub
[ 2.650867] hub 1-1:1.0: USB hub found
[ 2.655032] hub 1-1:1.0: 4 ports detected
[ 2.670594] usb 3-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 2.694026] usb 3-1: New USB device found, idVendor=1f75, idProduct=0621
[ 2.700751] usb 3-1: New USB device strings: Mfr=4, Product=5, SerialNumber=6
[ 2.707855] usb 3-1: Product: FX-D0002.HDD
[ 2.711956] usb 3-1: Manufacturer: ULT-Best
[ 2.716119] usb 3-1: SerialNumber: 20150718
[ 2.871951] ata1.00: ATA-8: TOSHIBA MK1652GSX, LV010M, max UDMA/100
[ 2.878195] ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 2.885882] ata1.00: configured for UDMA/100
[ 2.910686] scsi 0:0:0:0: Direct-Access ATA TOSHIBA MK1652GS 0M PQ: 0 ANSI: 5
[ 2.920204] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
[ 2.928373] sd 0:0:0:0: [sda] Write Protect is off
[ 2.933240] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 2.933463] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.940282] usb-storage 3-1:1.0: USB Mass Storage device detected
[ 2.940887] scsi host1: usb-storage 3-1:1.0
[ 2.952798] usb 1-1.1: new high-speed USB device number 3 using oxnas-ehci
[ 3.024327] sda: sda1
[ 3.028541] sd 0:0:0:0: [sda] Attached SCSI disk
[ 3.033605] Freeing unused kernel memory: 228K (c0827000 - c0860000)
[ 3.071306] usb 1-1.1: New USB device found, idVendor=0781, idProduct=5575
[ 3.078159] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.089822] usb 1-1.1: Product: Cruzer Glide
[ 3.094195] usb 1-1.1: Manufacturer: SanDisk
[ 3.098449] usb 1-1.1: SerialNumber: 4C530201370809103182
[ 3.105359] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[ 3.130488] scsi host2: usb-storage 1-1.1:1.0
[ 3.192148] udevd[108]: starting version 175
[ 4.150912] scsi 2:0:0:0: Direct-Access SanDisk Cruzer Glide 1.27 PQ: 0 ANSI: 6
[ 4.166712] sd 2:0:0:0: [sdb] 15330304 512-byte logical blocks: (7.85 GB/7.31 GiB)
[ 4.177295] sd 2:0:0:0: [sdb] Write Protect is off
[ 4.182302] sd 2:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 4.183275] sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 4.204134] sdb: sdb1
[ 4.210892] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[ 5.953684] scsi 1:0:0:0: Direct-Access ULT-Best FX-D0002.HDD PQ: 0 ANSI: 6
[ 5.967654] sd 1:0:0:0: [sdc] Attached SCSI removable disk
[ 8.502914] usb 1-1.1: USB disconnect, device number 3
[ 15.631777] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
[ 15.659525] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 17.643837] random: nonblocking pool is initialized
[ 17.784373] udevd[318]: starting version 175
[ 19.943884] EXT4-fs (sda1): re-mounted. Opts: (null)
[ 20.465597] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ 25.578050] Adding 1048572k swap on /swapfile1. Priority:-1 extents:360 across:1169636k FS
[ 28.122964] zram: Added device: zram0
[ 28.146534] zram: Added device: zram1
[ 28.171279] zram: Added device: zram2
[ 28.191377] zram: Added device: zram3
[ 28.243904] zram0: detected capacity change from 0 to 23220224
[ 28.318187] Adding 22672k swap on /dev/zram0. Priority:10 extents:1 across:22672k SSFS
[ 28.328908] zram1: detected capacity change from 0 to 23220224
[ 28.383150] Adding 22672k swap on /dev/zram1. Priority:10 extents:1 across:22672k SSFS
[ 28.394629] zram2: detected capacity change from 0 to 23220224
[ 28.451742] Adding 22672k swap on /dev/zram2. Priority:10 extents:1 across:22672k SSFS
[ 28.463677] zram3: detected capacity change from 0 to 23220224
[ 28.536230] Adding 22672k swap on /dev/zram3. Priority:10 extents:1 across:22672k SSFS
[ 34.130293] oxnas-gmac 40400000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 56.545395] zram: Cannot change disksize for initialized device
[ 56.632015] zram: Cannot change disksize for initialized device
[ 56.731909] zram: Cannot change disksize for initialized device
[ 56.814922] zram: Cannot change disksize for initialized device
[ 123.420915] usb 3-2: new SuperSpeed USB device number 3 using xhci_hcd
[ 123.445109] usb 3-2: New USB device found, idVendor=0781, idProduct=5581
[ 123.460083] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 123.467392] usb 3-2: Product: Ultra
[ 123.470960] usb 3-2: Manufacturer: SanDisk
[ 123.490032] usb 3-2: SerialNumber: 4C530001320111116341
[ 123.498339] usb-storage 3-2:1.0: USB Mass Storage device detected
[ 123.570232] scsi host3: usb-storage 3-2:1.0
[ 124.027673] usbcore: registered new interface driver uas
[ 124.591091] scsi 3:0:0:0: Direct-Access SanDisk Ultra 1.00 PQ: 0 ANSI: 6
[ 124.607462] sd 3:0:0:0: [sdb] 60062500 512-byte logical blocks: (30.8 GB/28.6 GiB)
[ 124.618662] sd 3:0:0:0: [sdb] Write Protect is off
[ 124.624814] sd 3:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 124.627712] sd 3:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 124.658365] sdb: sdb1
[ 124.666214] sd 3:0:0:0: [sdb] Attached SCSI removable disk
root@DebianPlug:~#
lsusb
root@DebianPlug:~# lsusb Bus 003 Device 003: ID 0781:5581 SanDisk Corp. Bus 003 Device 002: ID 1f75:0621 Innostor Technology Corporation Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@DebianPlug:~#
lsusb -vvv
root@DebianPlug:~# lsusb -vvv
Bus 003 Device 003: ID 0781:5581 SanDisk Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x0781 SanDisk Corp.
idProduct 0x5581
bcdDevice 1.00
iManufacturer 1 SanDisk
iProduct 2 Ultra
iSerial 3 4C530001320111116341
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 44
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 224mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 22
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 256 micro seconds
Device Status: 0x0000
(Bus Powered)
Bus 003 Device 002: ID 1f75:0621 Innostor Technology Corporation
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x1f75 Innostor Technology Corporation
idProduct 0x0621
bcdDevice 0.36
iManufacturer 4 ULT-Best
iProduct 5 FX-D0002.HDD
iSerial 6 20150718
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 44
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 22
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 2047 micro seconds
Device Status: 0x0000
(Bus Powered)
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 3
bMaxPacketSize0 9
idVendor 0x1d6b Linux Foundation
idProduct 0x0003 3.0 root hub
bcdDevice 4.04
iManufacturer 3 Linux 4.4.48-oxnas-tld-1 xhci-hcd
iProduct 2 xHCI Host Controller
iSerial 1 0000:00:00.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 31
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
bMaxBurst 0
Hub Descriptor:
bLength 12
bDescriptorType 42
nNbrPorts 2
wHubCharacteristic 0x0009
Per-port power switching
Per-port overcurrent protection
bPwrOn2PwrGood 10 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
bHubDecLat 0.0 micro seconds
wHubDelay 0 nano seconds
DeviceRemovable 0x00
Hub Port Status:
Port 1: 0000.0203 5Gbps power U0 enable connect
Port 2: 0000.0203 5Gbps power U0 enable connect
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 15
bNumDeviceCaps 1
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x02
Latency Tolerance Messages (LTM) Supported
wSpeedsSupported 0x0008
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 3
Lowest fully-functional device speed is SuperSpeed (5Gbps)
bU1DevExitLat 0 micro seconds
bU2DevExitLat 0 micro seconds
Device Status: 0x0001
Self Powered
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 4.04
iManufacturer 3 Linux 4.4.48-oxnas-tld-1 xhci-hcd
iProduct 2 xHCI Host Controller
iSerial 1 0000:00:00.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x0009
Per-port power switching
Per-port overcurrent protection
TT think time 8 FS bits
bPwrOn2PwrGood 10 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0100 power
Device Status: 0x0001
Self Powered
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x05e3 Genesys Logic, Inc.
idProduct 0x0608 USB-2.0 4-Port HUB
bcdDevice 77.64
iManufacturer 0
iProduct 1 USB2.0 Hub
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 4
wHubCharacteristic 0x00e0
Ganged power switching
Ganged overcurrent protection
TT think time 32 FS bits
Port indicators
bPwrOn2PwrGood 50 * 2 milli seconds
bHubContrCurrent 100 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0100 power
Port 2: 0000.0100 power
Port 3: 0000.0100 power
Port 4: 0000.0100 power
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0 Full speed (or root) hub
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 64
idVendor 0x1d6b Linux Foundation
idProduct 0x0002 2.0 root hub
bcdDevice 4.04
iManufacturer 3 Linux 4.4.48-oxnas-tld-1 ehci_hcd
iProduct 2 EHCI Host Controller
iSerial 1 40200100.ehci
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0 Full speed (or root) hub
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 12
Hub Descriptor:
bLength 9
bDescriptorType 41
nNbrPorts 2
wHubCharacteristic 0x0009
Per-port power switching
Per-port overcurrent protection
TT think time 8 FS bits
bPwrOn2PwrGood 10 * 2 milli seconds
bHubContrCurrent 0 milli Ampere
DeviceRemovable 0x00
PortPwrCtrlMask 0xff
Hub Port Status:
Port 1: 0000.0507 highspeed power suspend enable connect
Port 2: 0000.0100 power
Device Status: 0x0001
Self Powered
root@DebianPlug:~#
Mountin' Dew
root@DebianPlug:~# mkdir -p /media/JoeyUSB3 root@DebianPlug:~# mount -o noatime /dev/sdb1 /media/JoeyUSB3 root@DebianPlug:~#
It would appear it worked, though write permissions aren't set to work and I don't know how to do that. If you have any idea to try something simple,commands to enter do tell and I'll leave this run a while.
=========
-= Cloud 9 =-
Edited 3 time(s). Last edit at 03/23/2017 01:25PM by JoeyPogoPlugE02.
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 23, 2017 03:17PM |
Registered: 9 years ago Posts: 1,516 |
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 23, 2017 03:41PM |
Admin Registered: 13 years ago Posts: 18,898 |
Joey,
You are back to the point you were several posts ago :)
So
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
You are back to the point you were several posts ago :)
So
mount ls -l /media/JoeyUSB3 df -h
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 23, 2017 04:07PM |
Registered: 9 years ago Posts: 1,516 |
bodhi Wrote:
-------------------------------------------------------
> Joey,
>
> You are back to the point you were several posts a
> go :)
>
> So
>
Bodhi I got stuck in media because I don't know where to cd to. :-)
Still here's the result if it helps:
I have to note, I chmodded like a madman (media/JoeyUSB3) -but alas couldn't write/copy over LAN to it- so if this is too defiled I can copy the USB stick to hard drive again.
Beating a dead horse just for the bass now...
=========
-= Cloud 9 =-
Edited 3 time(s). Last edit at 03/23/2017 04:23PM by JoeyPogoPlugE02.
-------------------------------------------------------
> Joey,
>
> You are back to the point you were several posts a
> go :)
>
> So
>
> mount > ls -l /media/JoeyUSB3 > df -h >
Bodhi I got stuck in media because I don't know where to cd to. :-)
Still here's the result if it helps:
root@DebianPlug:/media# mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=14631,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=12092k,mode=755) /dev/sda1 on / type ext3 (rw,noatime,errors=remount-ro,data=ordered) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=24180k) tmpfs on /tmp type tmpfs (rw,relatime) rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime) /dev/sdb1 on /media/JoeyUSB3 type ext4 (ro,noatime,data=ordered) root@DebianPlug:/media# ls -l /media/JoeyUSB3 ls: reading directory /media/JoeyUSB3: Input/output error total 0 root@DebianPlug:/media# df -h Filesystem Size Used Avail Use% Mounted on udev 10M 0 10M 0% /dev tmpfs 12M 396K 12M 4% /run /dev/sda1 7.1G 2.6G 4.2G 38% / tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 24M 0 24M 0% /run/shm tmpfs 60M 28K 60M 1% /tmp /dev/sdb1 29G 1.8G 25G 7% /media/JoeyUSB3 root@DebianPlug:/media#
I have to note, I chmodded like a madman (media/JoeyUSB3) -but alas couldn't write/copy over LAN to it- so if this is too defiled I can copy the USB stick to hard drive again.
Beating a dead horse just for the bass now...
=========
-= Cloud 9 =-
Edited 3 time(s). Last edit at 03/23/2017 04:23PM by JoeyPogoPlugE02.
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 23, 2017 05:07PM |
Admin Registered: 13 years ago Posts: 18,898 |
Joey,
Can you measure the power at one of the 2 ports?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Can you measure the power at one of the 2 ports?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 23, 2017 05:25PM |
Registered: 9 years ago Posts: 1,516 |
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 23, 2017 08:22PM |
Registered: 7 years ago Posts: 49 |
Joey, you might try using chown if you think there may be permission issues. chown is used to change the owner of files and directories.
Example:
change owner, recursively, from root to joey, filepath= root, mnt, media
The recursive option means media and everything under it is changed from root to joey. This also assumes you have set up a user other than root.
With this said, chmod 777 should allow anyone to read, write, and execute.
I usually prefer to change owner rather than change permission unless its a quick chmod +x to make a script executable.
Also, off the top of my head, not sure about how using the various network file transfer protocols could effect whats allowed regarding writing to the root filesystem. Keep in mind that writing to the root file system in Linux is secured, therefore not allowed by any default settings, by anyone other than root.
In Linux, root can be:
1) the root user
2) the root file system, which is /
--------------------------------------------------------------
Blog: www.jeffstory.org
Edited 6 time(s). Last edit at 03/23/2017 08:40PM by JeffS.
Example:
chown -R joey /mnt/media
change owner, recursively, from root to joey, filepath= root, mnt, media
The recursive option means media and everything under it is changed from root to joey. This also assumes you have set up a user other than root.
With this said, chmod 777 should allow anyone to read, write, and execute.
I usually prefer to change owner rather than change permission unless its a quick chmod +x to make a script executable.
Also, off the top of my head, not sure about how using the various network file transfer protocols could effect whats allowed regarding writing to the root filesystem. Keep in mind that writing to the root file system in Linux is secured, therefore not allowed by any default settings, by anyone other than root.
In Linux, root can be:
1) the root user
2) the root file system, which is /
--------------------------------------------------------------
Blog: www.jeffstory.org
Edited 6 time(s). Last edit at 03/23/2017 08:40PM by JeffS.
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 26, 2017 02:34AM |
Admin Registered: 13 years ago Posts: 18,898 |
I've tried the card in the Kirkwood iConnect, and it works beautifully! it is powered by a USB 2.0 port on the iConnect (direct USB male-male cable), while the boot drive is on another USB 2.0 port. Everything checked out OK.
The raw performance is in the ballpark of what we'd expect. The Ultra Fit USB 3.0 is about x4 faster than the USB 2.0 Cruzer Fit.
So the real problem we have seen with the Pogo V3 is specific to the OXNAS box. Just what I've suspected, we will need a modified XHCI driver for the Pogo V3.
So the card is the real deal, not junk :) It works with mainline Linux XHCI driver. Their claim to be compliance with Intel XHCI standard is legit.
lspci
dmesg | grep pci
dmesg | grep xhci
lsusb -s 003:002 -v
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 3 time(s). Last edit at 03/26/2017 05:06PM by bodhi.
The raw performance is in the ballpark of what we'd expect. The Ultra Fit USB 3.0 is about x4 faster than the USB 2.0 Cruzer Fit.
hdparm -tT /dev/sda /dev/sda: Timing cached reads: 432 MB in 2.00 seconds = 215.64 MB/sec Timing buffered disk reads: 312 MB in 3.00 seconds = 103.83 MB/sec hdparm -tT /dev/sdb /dev/sdb: Timing cached reads: 426 MB in 2.00 seconds = 212.67 MB/sec Timing buffered disk reads: 82 MB in 3.00 seconds = 27.30 MB/sec
So the real problem we have seen with the Pogo V3 is specific to the OXNAS box. Just what I've suspected, we will need a modified XHCI driver for the Pogo V3.
So the card is the real deal, not junk :) It works with mainline Linux XHCI driver. Their claim to be compliance with Intel XHCI standard is legit.
Quote
Based on Renesas D720202 chipset USB 3.0 Host Controller IC
Compliant with Intel's Extensible Host Controller Interface (xHCI) Specification Revision 1.0
lspci
00:01.0 PCI bridge: Marvell Technology Group Ltd. 88F6281 [Kirkwood] ARM SoC (rev 02) 01:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02)
dmesg | grep pci
[ 6.067314] mvebu-pcie mbus@f1000000:pcie-controller@82000000: PCI host bridge to bus 0000:00 [ 6.067340] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff] [ 6.067356] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff] [ 6.067372] pci_bus 0000:00: root bus resource [bus 00-ff] [ 6.067386] pci_bus 0000:00: scanning bus [ 6.067424] pci 0000:00:01.0: [11ab:6281] type 01 class 0x060400 [ 6.067482] pci 0000:00:01.0: calling pci_fixup_ide_bases+0x0/0x40 [ 6.067757] pci_bus 0000:00: fixups for bus [ 6.067790] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 0 [ 6.067800] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 6.067821] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 1 [ 6.067983] pci_bus 0000:01: scanning bus [ 6.068042] pci 0000:01:00.0: [1912:0015] type 00 class 0x0c0330 [ 6.068089] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00001fff 64bit] [ 6.068178] pci 0000:01:00.0: calling pci_fixup_ide_bases+0x0/0x40 [ 6.068292] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold [ 6.068307] pci 0000:01:00.0: PME# disabled [ 6.093704] pci_bus 0000:01: fixups for bus [ 6.093737] pci_bus 0000:01: bus scan returning with max=01 [ 6.093752] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01 [ 6.093766] pci_bus 0000:00: bus scan returning with max=01 [ 6.093782] pci 0000:00:01.0: fixup irq: got 0 [ 6.093791] pci 0000:00:01.0: assigning IRQ 00 [ 6.093917] pci 0000:01:00.0: fixup irq: got 33 [ 6.093927] pci 0000:01:00.0: assigning IRQ 33 [ 6.093972] pci 0000:00:01.0: BAR 14: assigned [mem 0xe0000000-0xe00fffff] [ 6.093997] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe0001fff 64bit] [ 6.094028] pci 0000:00:01.0: PCI bridge to [bus 01] [ 6.094049] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff] [ 6.094148] pcieport 0000:00:01.0: enabling device (0140 -> 0142) [ 6.094179] pcieport 0000:00:01.0: enabling bus mastering [ 6.094230] pci 0000:01:00.0: calling quirk_usb_early_handoff+0x0/0x660 [ 6.094247] pci 0000:00:01.0: enabling bus mastering [ 6.094261] pci 0000:01:00.0: enabling device (0140 -> 0142)
dmesg | grep xhci
[ 8.529853] xhci_hcd 0000:01:00.0: enabling bus mastering [ 8.529867] xhci_hcd 0000:01:00.0: xHCI Host Controller [ 8.535219] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2 [ 8.548314] xhci_hcd 0000:01:00.0: hcc params 0x014051cf hci version 0x100 quirks 0x00000090 [ 8.556832] xhci_hcd 0000:01:00.0: enabling Mem-Wr-Inval [ 8.576158] usb usb2: Manufacturer: Linux 4.10.0-kirkwood-tld-1 xhci-hcd [ 8.596864] xhci_hcd 0000:01:00.0: xHCI Host Controller [ 8.602132] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3 [ 8.637284] usb usb3: Manufacturer: Linux 4.10.0-kirkwood-tld-1 xhci-hcd [ 9.754286] usb 3-2: new SuperSpeed USB device number 2 using xhci_hcd
lsusb -s 003:002 -v
Bus 003 Device 002: ID 0781:5583 SanDisk Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 3.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 9
idVendor 0x0781 SanDisk Corp.
idProduct 0x5583
bcdDevice 1.00
iManufacturer 1 SanDisk
iProduct 2 Ultra Fit
iSerial 3 xxxxxxxxxxxxxxxxxxxxxxxx
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 44
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 224mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0400 1x 1024 bytes
bInterval 0
bMaxBurst 15
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 22
bNumDeviceCaps 2
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000002
Link Power Management (LPM) Supported
SuperSpeed USB Device Capability:
bLength 10
bDescriptorType 16
bDevCapabilityType 3
bmAttributes 0x00
wSpeedsSupported 0x000e
Device can operate at Full Speed (12Mbps)
Device can operate at High Speed (480Mbps)
Device can operate at SuperSpeed (5Gbps)
bFunctionalitySupport 1
Lowest fully-functional device speed is Full Speed (12Mbps)
bU1DevExitLat 10 micro seconds
bU2DevExitLat 256 micro seconds
Device Status: 0x0000
(Bus Powered)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 3 time(s). Last edit at 03/26/2017 05:06PM by bodhi.
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 26, 2017 05:12PM |
Admin Registered: 13 years ago Posts: 18,898 |
Thanks Joey to have been a good guinea pig on the Pogo V3 Oxnas :) you've been a good tester, too bad we hit the road block on this box. I'll take a look of the differences when I have time to do it. If we get lucky (i.e. only the timing or IRQ) it might be possible. But no promise, because this subject is not easy.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 26, 2017 05:17PM |
Registered: 7 years ago Posts: 49 |
bodhi,
Are there any existing oxnas xhci Linux patches to try that are not already in kernel? I did a oxnas xhci search and came up with a few hits.
Is it possible for this hardware to contain bugs / problems, or is this more a documentation issue? I recall reading something about problems with the implementation of dual processors or related issues. Just curious and trying to get a better understanding.
Is there any chance this may get a fix down the road?
I'm grateful you have taken the time to keep this hardware update-able and interesting for us tinkerers. Thank you for that!
--------------------------------------------------------------
Blog: www.jeffstory.org
Edited 1 time(s). Last edit at 03/26/2017 05:23PM by JeffS.
Are there any existing oxnas xhci Linux patches to try that are not already in kernel? I did a oxnas xhci search and came up with a few hits.
Is it possible for this hardware to contain bugs / problems, or is this more a documentation issue? I recall reading something about problems with the implementation of dual processors or related issues. Just curious and trying to get a better understanding.
Is there any chance this may get a fix down the road?
I'm grateful you have taken the time to keep this hardware update-able and interesting for us tinkerers. Thank you for that!
--------------------------------------------------------------
Blog: www.jeffstory.org
Edited 1 time(s). Last edit at 03/26/2017 05:23PM by JeffS.
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 26, 2017 05:32PM |
Admin Registered: 13 years ago Posts: 18,898 |
Hi Jeff,
Regading "oxnas xhci Linux patches", I have not come across patches for this. The PCI and EHCI patches were worked on by kref (the originator of Pogo V3 OXNAS patch). I do believe that an NDA with Oxford Semi was needed to learn about these low lever drivers parameters, I think WarheadsSE and kref had NDA. Perhaps the NDA is no longer needed by now.
The mainline XHCI, which we use in Kirkwood boxes, is the goto driver for everybody. So I would think it is possible to modify that to use the HW specific timing, IRQs,... for the OXNAS. The problem is this we are the pioneers here, because XHCI is not something native to these OXNAS boxes (unlike the Kirkwood boxes).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Regading "oxnas xhci Linux patches", I have not come across patches for this. The PCI and EHCI patches were worked on by kref (the originator of Pogo V3 OXNAS patch). I do believe that an NDA with Oxford Semi was needed to learn about these low lever drivers parameters, I think WarheadsSE and kref had NDA. Perhaps the NDA is no longer needed by now.
The mainline XHCI, which we use in Kirkwood boxes, is the goto driver for everybody. So I would think it is possible to modify that to use the HW specific timing, IRQs,... for the OXNAS. The problem is this we are the pioneers here, because XHCI is not something native to these OXNAS boxes (unlike the Kirkwood boxes).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 26, 2017 05:33PM |
Admin Registered: 13 years ago Posts: 18,898 |
Let's google this, and perhaps we can find something out there.
Perhaps OpenWrt/LEDE has patches for this?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/26/2017 05:46PM by bodhi.
Perhaps OpenWrt/LEDE has patches for this?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/26/2017 05:46PM by bodhi.
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 26, 2017 07:25PM |
Registered: 7 years ago Posts: 49 |
Hi bodhi,
First, I need to say this kernel patch stuff is way above my knowledge. Most of what you replied is also over my head. Is NDA non disclosure agreement? If this is the case, I am amazed by the lengths a company will go to to guarantee income from non value related stuff.
My Google-fu says Oxford Semi was bought by PLX Technology in 2009, who is currently owned by Broadcom. And ARM just sells the designs or technology (ip-cores)? The Pogo v3 uses ARM11MPCore announced around 2005? .... and back on track...
I'm just Googling stuff I know very little to nothing about, but if I can help in any way, I'd be glad to. Here's a few hits that contain some related stuff. I'm thinking you probably already know about these, but who knows.
http://lists.infradead.org/pipermail/lede-commits/2016-September/000909.html
and
https://git.lede-project.org/?p=lede/dangole/staging.git;a=history;f=target/linux/oxnas;hb=refs/heads/oxnas-nand
Would be really cool to see this working after all you guy's put into it so far.
--------------------------------------------------------------
Blog: www.jeffstory.org
Edited 1 time(s). Last edit at 03/26/2017 07:27PM by JeffS.
First, I need to say this kernel patch stuff is way above my knowledge. Most of what you replied is also over my head. Is NDA non disclosure agreement? If this is the case, I am amazed by the lengths a company will go to to guarantee income from non value related stuff.
My Google-fu says Oxford Semi was bought by PLX Technology in 2009, who is currently owned by Broadcom. And ARM just sells the designs or technology (ip-cores)? The Pogo v3 uses ARM11MPCore announced around 2005? .... and back on track...
I'm just Googling stuff I know very little to nothing about, but if I can help in any way, I'd be glad to. Here's a few hits that contain some related stuff. I'm thinking you probably already know about these, but who knows.
http://lists.infradead.org/pipermail/lede-commits/2016-September/000909.html
and
https://git.lede-project.org/?p=lede/dangole/staging.git;a=history;f=target/linux/oxnas;hb=refs/heads/oxnas-nand
Would be really cool to see this working after all you guy's put into it so far.
--------------------------------------------------------------
Blog: www.jeffstory.org
Edited 1 time(s). Last edit at 03/26/2017 07:27PM by JeffS.
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 26, 2017 08:19PM |
Admin Registered: 13 years ago Posts: 18,898 |
Jeff,
> First, I need to say this kernel patch stuff is wa
> y above my knowledge. Most of what you replied is
> also over my head.
If you see xhci and OXNAS refered to in the same patch then we want to look at it.
> Is NDA non disclosure agreement
> ? If this is the case, I am amazed by the lengths
> a company will go to to guarantee income from non
> value related stuff.
Yes it is non disclosure agreement. Remember this box and other plugs (or their cousins) cost close to $US 100 when they were first release :) But I think because their SW were so lousy, they could not sell the products.
> My Google-fu says Oxford Semi was bought by PLX Te
> chnology in 2009, who is currently owned by Broadc
> om.
Yes.
>And ARM just sells the designs or technology (
> ip-cores)?
Correct.
> The Pogo v3 uses ARM11MPCore announced
> around 2005? ....
Yes. And this core apparently has a problem in the SMP (Symetric Multi-Processing) design. I did an extensive research on this problem and decided I'm staying with kernel 4.4 for now. Just to get it run with kernel 4.4 was a time consuming activity :)
People have been working around it ever since. And I dont think anybody use this core for new board anymore.
> Here's a few hits that contain some related
> stuff. I'm thinking you probably already know abou
> t these, but who knows.
Yes I knew about these patches!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> First, I need to say this kernel patch stuff is wa
> y above my knowledge. Most of what you replied is
> also over my head.
If you see xhci and OXNAS refered to in the same patch then we want to look at it.
> Is NDA non disclosure agreement
> ? If this is the case, I am amazed by the lengths
> a company will go to to guarantee income from non
> value related stuff.
Yes it is non disclosure agreement. Remember this box and other plugs (or their cousins) cost close to $US 100 when they were first release :) But I think because their SW were so lousy, they could not sell the products.
> My Google-fu says Oxford Semi was bought by PLX Te
> chnology in 2009, who is currently owned by Broadc
> om.
Yes.
>And ARM just sells the designs or technology (
> ip-cores)?
Correct.
> The Pogo v3 uses ARM11MPCore announced
> around 2005? ....
Yes. And this core apparently has a problem in the SMP (Symetric Multi-Processing) design. I did an extensive research on this problem and decided I'm staying with kernel 4.4 for now. Just to get it run with kernel 4.4 was a time consuming activity :)
People have been working around it ever since. And I dont think anybody use this core for new board anymore.
> Here's a few hits that contain some related
> stuff. I'm thinking you probably already know abou
> t these, but who knows.
Yes I knew about these patches!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 26, 2017 09:41PM |
Registered: 9 years ago Posts: 1,516 |
bodhi Wrote:
-------------------------------------------------------
> So the real problem we have seen with the Pogo V3
> is specific to the OXNAS box. Just what I've suspe
> cted, we will need a modified XHCI driver for the
> Pogo V3.
If it could be run from USB stick too. Seemed stable when the OS was running jump started to SATA,,but it was tedious so I moved on. The best use for that I see is Samba where any USB you plug in or SATA drive it's broadcasted to all corners of your LAN.
So yeah if you make a driver and t's easy go for it :-) Thing is, with an external hard drive plugged into a Pogoplug, it's the same power draw as it would have taken if it were 2.0. So there's not really power supply stress worries.
The suspense how fast this can move files over Gigabit connection is excruciating :-)
=========
-= Cloud 9 =-
-------------------------------------------------------
> So the real problem we have seen with the Pogo V3
> is specific to the OXNAS box. Just what I've suspe
> cted, we will need a modified XHCI driver for the
> Pogo V3.
If it could be run from USB stick too. Seemed stable when the OS was running jump started to SATA,,but it was tedious so I moved on. The best use for that I see is Samba where any USB you plug in or SATA drive it's broadcasted to all corners of your LAN.
So yeah if you make a driver and t's easy go for it :-) Thing is, with an external hard drive plugged into a Pogoplug, it's the same power draw as it would have taken if it were 2.0. So there's not really power supply stress worries.
The suspense how fast this can move files over Gigabit connection is excruciating :-)
=========
-= Cloud 9 =-
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 26, 2017 09:59PM |
Admin Registered: 13 years ago Posts: 18,898 |
> So yeah if you make a driver
Sorry, that will be difficult :) see the reason I posted above.
> The suspense how fast this can move files over Gig
> abit connection is excruciating :-)
Well, I can tel you that is only 60% improvement over USB 2.0 (about the same as SATA disk). This number is based on un-tuned NFS setup on both ends. I have not tried Samba yet!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Sorry, that will be difficult :) see the reason I posted above.
> The suspense how fast this can move files over Gig
> abit connection is excruciating :-)
Well, I can tel you that is only 60% improvement over USB 2.0 (about the same as SATA disk). This number is based on un-tuned NFS setup on both ends. I have not tried Samba yet!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 27, 2017 12:31AM |
Registered: 9 years ago Posts: 1,516 |
Well I got acquainted with Linux diagnostic commands again, which is a review.
But Bodhi, thanks a million for updating the kernel too, the stick is copied for both PogoPros here for the day E02 expires and I need torrents.
Now we know too it's a ridiculous shame most SOCs don't have a USB 3.0 port when you figure otherwise quadcore high numbers.
One of the Pi extension boards we saw lately has what looks like a mpcie slot and it states MSATA, so that's no good.
Well ladies & Gents your helps here are something I'll come back to for reference, but for now, thanks for the outreach.
=========
-= Cloud 9 =-
But Bodhi, thanks a million for updating the kernel too, the stick is copied for both PogoPros here for the day E02 expires and I need torrents.
Now we know too it's a ridiculous shame most SOCs don't have a USB 3.0 port when you figure otherwise quadcore high numbers.
One of the Pi extension boards we saw lately has what looks like a mpcie slot and it states MSATA, so that's no good.
Well ladies & Gents your helps here are something I'll come back to for reference, but for now, thanks for the outreach.
=========
-= Cloud 9 =-
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 28, 2017 11:29PM |
Admin Registered: 13 years ago Posts: 18,898 |
@Joey,
See this:
http://forum.doozan.com/read.php?2,33321,33390#msg-33390
Set your Pogo V3 to turn off flow control as instructed in the link above. And see if the SAMBA files xfer rate improved.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
See this:
http://forum.doozan.com/read.php?2,33321,33390#msg-33390
Set your Pogo V3 to turn off flow control as instructed in the link above. And see if the SAMBA files xfer rate improved.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 29, 2017 08:22PM |
Registered: 9 years ago Posts: 1,516 |
bodhi Wrote:
-------------------------------------------------------
> The reason network performance is degraded on the
> Pogo V3 OXNAS is: flow control. The OXNAS ethernet
> driver set this by default. We need to turn it off
> in the driver, but that will be incorprated in the
> next kernel release. At the moment, the workaround
> is to do turn it off with ethtool.
Is that something you only need to do once and flow control stays off from then on? My Pogo Pros are back together for spring cleaning but I'd turn off flow control for both of them if it's all set for the next round (if/when) I can find a reasonably-priced mpcie ribbon that isn't $15.
=========
-= Cloud 9 =-
-------------------------------------------------------
> The reason network performance is degraded on the
> Pogo V3 OXNAS is: flow control. The OXNAS ethernet
> driver set this by default. We need to turn it off
> in the driver, but that will be incorprated in the
> next kernel release. At the moment, the workaround
> is to do turn it off with ethtool.
ethtool -A eth0 rx off tx off
Is that something you only need to do once and flow control stays off from then on? My Pogo Pros are back together for spring cleaning but I'd turn off flow control for both of them if it's all set for the next round (if/when) I can find a reasonably-priced mpcie ribbon that isn't $15.
=========
-= Cloud 9 =-
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 30, 2017 12:18AM |
Admin Registered: 13 years ago Posts: 18,898 |
> Is that something you only need to do once and flo
> w control stays off from then on?
Yes, it will stay off. When in doubt, to double check after you reboot:
> My Pogo Pros are
> back together for spring cleaning but I'd turn off
> flow control for both of them if it's all set for
> the next round (if/when) I can find a reasonably-p
> riced mpcie ribbon that isn't $15.
I did not purchase that $US 15 ribbon! I figured we will need to either:
- cut a regtangular hole on the case wall to route that out, and then there is a problem with how to safeguard the mPCIe card outside the case,...
or
- fold the ribbon back to the other side of the board and just leave the mPCIe card somewhere safe. Logistically it is a tough one to figure out.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> w control stays off from then on?
Yes, it will stay off. When in doubt, to double check after you reboot:
ethtool -a eth0It should show both RX and TX are off.
> My Pogo Pros are
> back together for spring cleaning but I'd turn off
> flow control for both of them if it's all set for
> the next round (if/when) I can find a reasonably-p
> riced mpcie ribbon that isn't $15.
I did not purchase that $US 15 ribbon! I figured we will need to either:
- cut a regtangular hole on the case wall to route that out, and then there is a problem with how to safeguard the mPCIe card outside the case,...
or
- fold the ribbon back to the other side of the board and just leave the mPCIe card somewhere safe. Logistically it is a tough one to figure out.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 30, 2017 01:07AM |
Registered: 9 years ago Posts: 1,516 |
Are mSATA the same pins? Because there's what looks to be the same ones as the $15 mpcie cables for $10 including shipping (regular pcie ribbons go for $2)! We need the Habibie search engine :-) Maybe it's time I ordered a Mouser catalog. They might have it.
=========
-= Cloud 9 =-
=========
-= Cloud 9 =-
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 30, 2017 03:22AM |
Admin Registered: 13 years ago Posts: 18,898 |
Joey,
> Are mSATA the same pins?
You'll tell me :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Are mSATA the same pins?
You'll tell me :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug V3 OXNAS - USB 3.0 on mPCIe - Main thread March 30, 2017 06:34AM |
Registered: 11 years ago Posts: 1,303 |
JoeyPogoPlugE02 Wrote:
-------------------------------------------------------
> We need the Habibie search engine :-)
>
Joey, once I found an item through a Google search, then I compare the prices with the ones found on AliExpress and/or eBay. For me, I believe the hardest part is to know the correct market name of the item to search for.
-------------------------------------------------------
> We need the Habibie search engine :-)
>
Joey, once I found an item through a Google search, then I compare the prices with the ones found on AliExpress and/or eBay. For me, I believe the hardest part is to know the correct market name of the item to search for.
