Re: Edgeport/416 io_edgeport problem.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Mar 13, 2015 at 11:37:15AM +0100, Dirk-Jan Wemmers wrote:
> Hi Greg, David, others,
> 
> sorry for digging up this old thread, but we seem to have the same issue.
> And as the device in front of me has a serial number that is only different
> in the least significant digit, I'm quite sure it's related :)
> 
> To summarize: We are trying to run a number of 'Digi' (Inside Out Networks)
> Edgeport/416 16x serial with integrated USB hub device on Linux
> (3.16.0-31-generic from Ubuntu 14.04.2 LTS). The device appears to be
> detected correctly, /dev/ttyUSB devices are being created, the two LEDs on
> the device go to a steady blinking green, until you try to open one of the
> newly created ports; this fails and the led on the 8-port halve that you
> tried to access will stop blinking. The related dmesg:
> 
> [19791.737671] usb 1-5: new full-speed USB device number 40 using xhci_hcd
> [19791.866336] usb 1-5: New USB device found, idVendor=0451, idProduct=2077
> [19791.866342] usb 1-5: New USB device strings: Mfr=0, Product=1,
> SerialNumber=0
> [19791.866344] usb 1-5: Product: General Purpose USB Hub
> [19791.866532] usb 1-5: ep 0x81 - rounding interval to 1024 microframes, ep
> desc says 2040 microframes
> [19791.867233] hub 1-5:1.0: USB hub found
> [19791.867311] hub 1-5:1.0: 7 ports detected
> [19792.137552] usb 1-5.5: new full-speed USB device number 41 using xhci_hcd
> [19792.233111] usb 1-5.5: New USB device found, idVendor=1608,
> idProduct=0012
> [19792.233116] usb 1-5.5: New USB device strings: Mfr=1, Product=2,
> SerialNumber=5
> [19792.233119] usb 1-5.5: Product: Edgeport/416
> [19792.233122] usb 1-5.5: Manufacturer: Inside Out Networks
> [19792.233124] usb 1-5.5: SerialNumber: V70430355-0
> [19792.236681] io_edgeport 1-5.5:1.0: Edgeport 8 port adapter converter
> detected
> [19792.239352] usb 1-5.5: Inside Out Networks Edgeport/416 detected
> [19792.836176] usb 1-5.5: Edgeport 8 port adapter converter now attached to
> ttyUSB0
> [19792.836296] usb 1-5.5: Edgeport 8 port adapter converter now attached to
> ttyUSB1
> [19792.836374] usb 1-5.5: Edgeport 8 port adapter converter now attached to
> ttyUSB2
> [19792.836489] usb 1-5.5: Edgeport 8 port adapter converter now attached to
> ttyUSB3
> [19792.836564] usb 1-5.5: Edgeport 8 port adapter converter now attached to
> ttyUSB4
> [19792.836640] usb 1-5.5: Edgeport 8 port adapter converter now attached to
> ttyUSB5
> [19792.836708] usb 1-5.5: Edgeport 8 port adapter converter now attached to
> ttyUSB6
> [19792.836766] usb 1-5.5: Edgeport 8 port adapter converter now attached to
> ttyUSB7
> [19792.909478] usb 1-5.6: new full-speed USB device number 42 using xhci_hcd
> [19793.004984] usb 1-5.6: New USB device found, idVendor=1608,
> idProduct=0012
> [19793.004990] usb 1-5.6: New USB device strings: Mfr=1, Product=2,
> SerialNumber=5
> [19793.004992] usb 1-5.6: Product: Edgeport/416
> [19793.004995] usb 1-5.6: Manufacturer: Inside Out Networks
> [19793.004997] usb 1-5.6: SerialNumber: V70430355-1
> [19793.008369] io_edgeport 1-5.6:1.0: Edgeport 8 port adapter converter
> detected
> [19793.011113] usb 1-5.6: Inside Out Networks Edgeport/416 detected
> [19793.608154] usb 1-5.6: Edgeport 8 port adapter converter now attached to
> ttyUSB8
> [19793.608226] usb 1-5.6: Edgeport 8 port adapter converter now attached to
> ttyUSB9
> [19793.608334] usb 1-5.6: Edgeport 8 port adapter converter now attached to
> ttyUSB10
> [19793.608411] usb 1-5.6: Edgeport 8 port adapter converter now attached to
> ttyUSB11
> [19793.608486] usb 1-5.6: Edgeport 8 port adapter converter now attached to
> ttyUSB12
> [19793.608564] usb 1-5.6: Edgeport 8 port adapter converter now attached to
> ttyUSB13
> [19793.608630] usb 1-5.6: Edgeport 8 port adapter converter now attached to
> ttyUSB14
> [19793.608690] usb 1-5.6: Edgeport 8 port adapter converter now attached to
> ttyUSB15
> 
> Unfortunately in my kernel the debug=1 parameter seems to be ignored on
> modprobing; I guess this has been replaced with another debugging method as
> I see a lot of dev_dbg statements in the source of the driver but I'm not
> sure how to enable these to show up :)
> 
> Did one of you ever get to the bottom of this issue? Or did I just happen to
> buy Davids old stash that he ditched because it was a dead end? Any
> suggestions as to what we can try to get these units to be more than
> expensive paperweights? Under Windows they appear to work...

I'm not going to be able to access my device for a few months to be able
to test it out, so I really have no idea.

sorry,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux PPP]     [Linux FS]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Linmodem]     [Device Mapper]     [Linux Kernel for ARM]

  Powered by Linux