Discussion:
io_edgeport problem - Digi Edgeport/4r with 3.2.0 linux
Doug Minett
2013-02-14 23:07:38 UTC
Permalink
Hi,

I am using Ubuntu's 3.2.0-37 distribution of linux. Is there a known problem with the module in this version of the kernel?

cat /dev/ttyUSB0 results in "no such device" message (checked device is present with rw r r root root permissions)

I have tried a number of things to get the Digi Edgeport/4r to work.

1) loaded module: modprobe io_edgeport

2) manually created devices: mknod /dev/ttyUSB[0-3] c 188 0 (is io_edgeport supposed to do this?)

3) output from dmesg:

[ 3075.917619] usbcore: deregistering interface driver io_edgeport
[ 3075.917652] USB Serial deregistering driver Edgeport 2 port adapter
[ 3075.917666] USB Serial deregistering driver Edgeport 4 port adapter
[ 3075.917676] USB Serial deregistering driver Edgeport 8 port adapter
[ 3075.917685] USB Serial deregistering driver EPiC device
[ 3085.878341] usb 2-1.5: USB disconnect, device number 21
[ 3085.878345] usb 2-1.5.1: USB disconnect, device number 22
[ 3131.433041] USB Serial support registered for Edgeport 2 port adapter
[ 3131.433050] USB Serial support registered for Edgeport 4 port adapter
[ 3131.433058] USB Serial support registered for Edgeport 8 port adapter
[ 3131.433066] USB Serial support registered for EPiC device
[ 3131.433082] usbcore: registered new interface driver io_edgeport
[ 3131.433083] io_edgeport: v2.7:Edgeport USB Serial Driver
[ 3149.701038] usb 2-1.5: new full-speed USB device number 23 using ehci_hcd
[ 3149.793794] hub 2-1.5:1.0: USB hub found
[ 3149.793950] hub 2-1.5:1.0: 1 port detected
[ 3150.064329] usb 2-1.5.1: new full-speed USB device number 24 using ehci_hcd

4) output from lsmod:

Module Size Used by
nls_iso8859_1 12713 0
nls_cp437 16991 0
vfat 17585 0
fat 61512 1 vfat
io_edgeport 49444 0
uas 18180 0
usb_storage 49198 0
rfcomm 47604 0
bnep 18281 2
bluetooth 180153 10 rfcomm,bnep
parport_pc 32866 0
ppdev 17113 0
binfmt_misc 17540 1
ext2 73795 1
dm_crypt 23125 0
usbserial 47077 1 io_edgeport
dcdbas 14490 0
mac_hid 13253 0
lp 17799 0
parport 46562 3 parport_pc,ppdev,lp
vesafb 13844 1
usbhid 47238 0
hid 99636 1 usbhid
mpt2sas 157976 2
scsi_transport_sas 40558 1 mpt2sas
tg3 152032 0
raid_class 13554 1 mpt2sas

5) output from lsusb:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
Bus 002 Device 004: ID 413c:3012 Dell Computer Corp. Optical Wheel Mouse
Bus 002 Device 005: ID 0c2e:0200 Metro Metrologic Scanner
Bus 002 Device 023: ID 1608:0288 Inside Out Networks [hex]
Bus 002 Device 024: ID 1608:0202 Inside Out Networks [hex]

Any help would be appreciated. Thanks.

Doug Minett
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Greg KH
2013-02-14 23:32:22 UTC
Permalink
Post by Doug Minett
Hi,
I am using Ubuntu's 3.2.0-37 distribution of linux. Is there a known
problem with the module in this version of the kernel?
I don't know, but as this is a distro kernel, you really should contact
the distro to get support for it, there's nothing we can do with their
kernel directly, sorry.
Post by Doug Minett
cat /dev/ttyUSB0 results in "no such device" message (checked device
is present with rw r r root root permissions)
I have tried a number of things to get the Digi Edgeport/4r to work.
1) loaded module: modprobe io_edgeport
If you plug the device in, the driver should be automatically loaded.
Post by Doug Minett
2) manually created devices: mknod /dev/ttyUSB[0-3] c 188 0 (is io_edgeport supposed to do this?)
You should never have to do this, if the device is present, the device
nodes will be created automatically.
Post by Doug Minett
[ 3075.917619] usbcore: deregistering interface driver io_edgeport
[ 3075.917652] USB Serial deregistering driver Edgeport 2 port adapter
[ 3075.917666] USB Serial deregistering driver Edgeport 4 port adapter
[ 3075.917676] USB Serial deregistering driver Edgeport 8 port adapter
[ 3075.917685] USB Serial deregistering driver EPiC device
[ 3085.878341] usb 2-1.5: USB disconnect, device number 21
[ 3085.878345] usb 2-1.5.1: USB disconnect, device number 22
This is your device being removed from the system, can you provide log
messages from before this?
Post by Doug Minett
[ 3131.433041] USB Serial support registered for Edgeport 2 port adapter
[ 3131.433050] USB Serial support registered for Edgeport 4 port adapter
[ 3131.433058] USB Serial support registered for Edgeport 8 port adapter
[ 3131.433066] USB Serial support registered for EPiC device
[ 3131.433082] usbcore: registered new interface driver io_edgeport
[ 3131.433083] io_edgeport: v2.7:Edgeport USB Serial Driver
Did you just load the driver by hand here?

Can you try, as root, without the device plugged in:
- clear the kernel log:
dmesg -c
- plug the device in
- provide the kernel log output
dmesg

that should help us here.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Doug Minett
2013-02-15 04:52:19 UTC
Permalink
followup below. many thanks for your help.
Post by Greg KH
Post by Doug Minett
Hi,
I am using Ubuntu's 3.2.0-37 distribution of linux. Is there a known
problem with the module in this version of the kernel?
I don't know, but as this is a distro kernel, you really should contact
the distro to get support for it, there's nothing we can do with their
kernel directly, sorry.
Post by Doug Minett
cat /dev/ttyUSB0 results in "no such device" message (checked device
is present with rw r r root root permissions)
I have tried a number of things to get the Digi Edgeport/4r to work.
1) loaded module: modprobe io_edgeport
If you plug the device in, the driver should be automatically loaded.
Post by Doug Minett
2) manually created devices: mknod /dev/ttyUSB[0-3] c 188 0 (is io_edgeport supposed to do this?)
You should never have to do this, if the device is present, the device
nodes will be created automatically.
Post by Doug Minett
[ 3075.917619] usbcore: deregistering interface driver io_edgeport
[ 3075.917652] USB Serial deregistering driver Edgeport 2 port adapter
[ 3075.917666] USB Serial deregistering driver Edgeport 4 port adapter
[ 3075.917676] USB Serial deregistering driver Edgeport 8 port adapter
[ 3075.917685] USB Serial deregistering driver EPiC device
[ 3085.878341] usb 2-1.5: USB disconnect, device number 21
[ 3085.878345] usb 2-1.5.1: USB disconnect, device number 22
This is your device being removed from the system, can you provide log
messages from before this?
Post by Doug Minett
[ 3131.433041] USB Serial support registered for Edgeport 2 port adapter
[ 3131.433050] USB Serial support registered for Edgeport 4 port adapter
[ 3131.433058] USB Serial support registered for Edgeport 8 port adapter
[ 3131.433066] USB Serial support registered for EPiC device
[ 3131.433082] usbcore: registered new interface driver io_edgeport
[ 3131.433083] io_edgeport: v2.7:Edgeport USB Serial Driver
Did you just load the driver by hand here?
yes, I loaded it manually.
Post by Greg KH
dmesg -c
I unloaded the io_edgeport module, and deleted the devices that I had created in /dev with mknod manually.

rebooted, cleared dmesg.
Post by Greg KH
- plug the device in
- provide the kernel log output
dmesg
here is the resulting dmesg:

[ 192.866565] usb 2-1.6: new full-speed USB device number 6 using ehci_hcd
[ 192.959323] hub 2-1.6:1.0: USB hub found
[ 192.959477] hub 2-1.6:1.0: 1 port detected
[ 193.229880] usb 2-1.6.1: new full-speed USB device number 7 using ehci_hcd

(no /dev devices were created)

thanks Greg.
doug.
Post by Greg KH
that should help us here.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Greg KH
2013-02-15 05:23:55 UTC
Permalink
Post by Doug Minett
followup below. many thanks for your help.
Post by Greg KH
Post by Doug Minett
Hi,
I am using Ubuntu's 3.2.0-37 distribution of linux. Is there a known
problem with the module in this version of the kernel?
I don't know, but as this is a distro kernel, you really should contact
the distro to get support for it, there's nothing we can do with their
kernel directly, sorry.
Post by Doug Minett
cat /dev/ttyUSB0 results in "no such device" message (checked device
is present with rw r r root root permissions)
I have tried a number of things to get the Digi Edgeport/4r to work.
1) loaded module: modprobe io_edgeport
If you plug the device in, the driver should be automatically loaded.
Post by Doug Minett
2) manually created devices: mknod /dev/ttyUSB[0-3] c 188 0 (is io_edgeport supposed to do this?)
You should never have to do this, if the device is present, the device
nodes will be created automatically.
Post by Doug Minett
[ 3075.917619] usbcore: deregistering interface driver io_edgeport
[ 3075.917652] USB Serial deregistering driver Edgeport 2 port adapter
[ 3075.917666] USB Serial deregistering driver Edgeport 4 port adapter
[ 3075.917676] USB Serial deregistering driver Edgeport 8 port adapter
[ 3075.917685] USB Serial deregistering driver EPiC device
[ 3085.878341] usb 2-1.5: USB disconnect, device number 21
[ 3085.878345] usb 2-1.5.1: USB disconnect, device number 22
This is your device being removed from the system, can you provide log
messages from before this?
Post by Doug Minett
[ 3131.433041] USB Serial support registered for Edgeport 2 port adapter
[ 3131.433050] USB Serial support registered for Edgeport 4 port adapter
[ 3131.433058] USB Serial support registered for Edgeport 8 port adapter
[ 3131.433066] USB Serial support registered for EPiC device
[ 3131.433082] usbcore: registered new interface driver io_edgeport
[ 3131.433083] io_edgeport: v2.7:Edgeport USB Serial Driver
Did you just load the driver by hand here?
yes, I loaded it manually.
Post by Greg KH
dmesg -c
I unloaded the io_edgeport module, and deleted the devices that I had created in /dev with mknod manually.
rebooted, cleared dmesg.
Post by Greg KH
- plug the device in
- provide the kernel log output
dmesg
[ 192.866565] usb 2-1.6: new full-speed USB device number 6 using ehci_hcd
[ 192.959323] hub 2-1.6:1.0: USB hub found
[ 192.959477] hub 2-1.6:1.0: 1 port detected
[ 193.229880] usb 2-1.6.1: new full-speed USB device number 7 using ehci_hcd
(no /dev devices were created)
Wow, that's really bad. Something is keeping the io_edgeport driver
from being loaded. It should be automatically found and bound to this
device when you plug it in.

I don't know what to suggest at this point in time other than to file a
bug with Ubuntu, sorry.

If you can build your own kernel version, from kernel.org, then I can
try to help you out. If you can, grab the latest 3.7-stable kernel
(it's at the front page of kernel.org), build and install that, and then
we can go from there.

sorry,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Doug Minett
2013-02-15 05:51:06 UTC
Permalink
thanks Greg. My plan A is to see if I can get the Ubuntu folks to fix what is awry. Thanks for your analysis and suggestions.

Doug Minett
Post by Greg KH
Post by Doug Minett
followup below. many thanks for your help.
Post by Greg KH
Post by Doug Minett
Hi,
I am using Ubuntu's 3.2.0-37 distribution of linux. Is there a known
problem with the module in this version of the kernel?
I don't know, but as this is a distro kernel, you really should contact
the distro to get support for it, there's nothing we can do with their
kernel directly, sorry.
Post by Doug Minett
cat /dev/ttyUSB0 results in "no such device" message (checked device
is present with rw r r root root permissions)
I have tried a number of things to get the Digi Edgeport/4r to work.
1) loaded module: modprobe io_edgeport
If you plug the device in, the driver should be automatically loaded.
Post by Doug Minett
2) manually created devices: mknod /dev/ttyUSB[0-3] c 188 0 (is io_edgeport supposed to do this?)
You should never have to do this, if the device is present, the device
nodes will be created automatically.
Post by Doug Minett
[ 3075.917619] usbcore: deregistering interface driver io_edgeport
[ 3075.917652] USB Serial deregistering driver Edgeport 2 port adapter
[ 3075.917666] USB Serial deregistering driver Edgeport 4 port adapter
[ 3075.917676] USB Serial deregistering driver Edgeport 8 port adapter
[ 3075.917685] USB Serial deregistering driver EPiC device
[ 3085.878341] usb 2-1.5: USB disconnect, device number 21
[ 3085.878345] usb 2-1.5.1: USB disconnect, device number 22
This is your device being removed from the system, can you provide log
messages from before this?
Post by Doug Minett
[ 3131.433041] USB Serial support registered for Edgeport 2 port adapter
[ 3131.433050] USB Serial support registered for Edgeport 4 port adapter
[ 3131.433058] USB Serial support registered for Edgeport 8 port adapter
[ 3131.433066] USB Serial support registered for EPiC device
[ 3131.433082] usbcore: registered new interface driver io_edgeport
[ 3131.433083] io_edgeport: v2.7:Edgeport USB Serial Driver
Did you just load the driver by hand here?
yes, I loaded it manually.
Post by Greg KH
dmesg -c
I unloaded the io_edgeport module, and deleted the devices that I had created in /dev with mknod manually.
rebooted, cleared dmesg.
Post by Greg KH
- plug the device in
- provide the kernel log output
dmesg
[ 192.866565] usb 2-1.6: new full-speed USB device number 6 using ehci_hcd
[ 192.959323] hub 2-1.6:1.0: USB hub found
[ 192.959477] hub 2-1.6:1.0: 1 port detected
[ 193.229880] usb 2-1.6.1: new full-speed USB device number 7 using ehci_hcd
(no /dev devices were created)
Wow, that's really bad. Something is keeping the io_edgeport driver
from being loaded. It should be automatically found and bound to this
device when you plug it in.
I don't know what to suggest at this point in time other than to file a
bug with Ubuntu, sorry.
If you can build your own kernel version, from kernel.org, then I can
try to help you out. If you can, grab the latest 3.7-stable kernel
(it's at the front page of kernel.org), build and install that, and then
we can go from there.
sorry,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
simon-wM4F9T/
2013-02-15 16:07:41 UTC
Permalink
Post by Greg KH
Wow, that's really bad. Something is keeping the io_edgeport driver
from being loaded. It should be automatically found and bound to this
device when you plug it in.
I don't know what to suggest at this point in time other than to file a
bug with Ubuntu, sorry.
I happen to have an Edgeport4/RS-232 next to me (PN (1P) 500000787) and
that appears to work OK on Xubuntu (11.10), but does not appear to load
the 'io_edgeport' module even though it is present in '/lib/modules'.
Post by Greg KH
If you can build your own kernel version, from kernel.org, then I can
try to help you out. If you can, grab the latest 3.7-stable kernel
(it's at the front page of kernel.org), build and install that, and then
we can go from there.
From helping someone else out last week I have a few pre-built (stock)
kernels here, if you want to give them a try...

x86 one here:
http://dl.dropbox.com/u/34518077/linux-headers-3.8.0-rc4-srws1%2B_20130125_i386.deb
http://dl.dropbox.com/u/34518077/linux-image-3.8.0-rc4-srws1%2B_20130125_i386.deb

amd64 one here:
http://dl.dropbox.com/u/34518077/linux-headers-3.8.0-rc4-srws1%2B_20130125_amd64.deb
http://dl.dropbox.com/u/34518077/linux-image-3.8.0-rc4-srws1%2B_20130125_amd64.deb

Cheers,
Simon
Doug Minett
2013-02-15 18:21:48 UTC
Permalink
Simon: Thanks for checking it out in your environment. I think that your Xubuntu (11.10) is based on an earlier Ubuntu Kernel than I'm using (12.04 LTS). I appreciate the link to your Debian image and will check it out - but that is yet another kernel..

Greg: Any idea why Simon's Xubuntu seems to work while also _not_ loading io_edgeport - or would you guess that it is a earlier variant on the bug that I am experiencing? I've filed a bug report with Ubuntu.

cheers,
doug.
Post by simon-wM4F9T/
Post by Greg KH
Wow, that's really bad. Something is keeping the io_edgeport driver
from being loaded. It should be automatically found and bound to this
device when you plug it in.
I don't know what to suggest at this point in time other than to file a
bug with Ubuntu, sorry.
I happen to have an Edgeport4/RS-232 next to me (PN (1P) 500000787) and
that appears to work OK on Xubuntu (11.10), but does not appear to load
the 'io_edgeport' module even though it is present in '/lib/modules'.
Post by Greg KH
If you can build your own kernel version, from kernel.org, then I can
try to help you out. If you can, grab the latest 3.7-stable kernel
(it's at the front page of kernel.org), build and install that, and then
we can go from there.
From helping someone else out last week I have a few pre-built (stock)
kernels here, if you want to give them a try...
http://dl.dropbox.com/u/34518077/linux-headers-3.8.0-rc4-srws1%2B_20130125_i386.deb
http://dl.dropbox.com/u/34518077/linux-image-3.8.0-rc4-srws1%2B_20130125_i386.deb
http://dl.dropbox.com/u/34518077/linux-headers-3.8.0-rc4-srws1%2B_20130125_amd64.deb
http://dl.dropbox.com/u/34518077/linux-image-3.8.0-rc4-srws1%2B_20130125_amd64.deb
Cheers,
Simon<edgeport_test.txt>
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Greg KH
2013-02-15 18:29:26 UTC
Permalink
Post by Doug Minett
Greg: Any idea why Simon's Xubuntu seems to work while also _not_
loading io_edgeport - or would you guess that it is a earlier variant
on the bug that I am experiencing? I've filed a bug report with
Ubuntu.
I have no idea, sorry, take it up with the Ubuntu developers.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Doug Minett
2013-02-15 23:25:00 UTC
Permalink
I did some followup on another machine at my disposal running a Debian 2.6.32-5-686-bigmem on the same hardware as the Ubuntu box - Dell Poweredge T110 II

I plugged Digi in and had the same response as with the Ubuntu box - io_edgeport was not loaded/no new devices/same dmesg report.

Then I manually loaded io_edgeport and plugged the Digi in again.

dmesg (after manual load) is a bit different than with Ubuntu:

[29735001.555230] usb 2-1.6: new full speed USB device using ehci_hcd and address 65
[29735001.647709] usb 2-1.6: New USB device found, idVendor=1608, idProduct=0288
[29735001.647713] usb 2-1.6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[29735001.647788] usb 2-1.6: configuration #1 chosen from 1 choice
[29735001.647964] hub 2-1.6:1.0: USB hub found
[29735001.648148] hub 2-1.6:1.0: 1 port detected
[29735001.918939] usb 2-1.6.1: new full speed USB device using ehci_hcd and address 66
[29735002.017518] usb 2-1.6.1: New USB device found, idVendor=1608, idProduct=0202
[29735002.017522] usb 2-1.6.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[29735002.017600] usb 2-1.6.1: configuration #1 chosen from 1 choice

Could it be that Digi has changed something that is causing the problem?

Digi info:

Model: Edgeport/4r (your website lists Edgeport/4i as supported - not 4r) could this be the problem?
Part Number: 301-1002-16
Serial Number: W21045264

thanks Greg,
doug.




--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Greg KH
2013-02-15 23:29:55 UTC
Permalink
Post by Doug Minett
I did some followup on another machine at my disposal running a Debian 2.6.32-5-686-bigmem on the same hardware as the Ubuntu box - Dell Poweredge T110 II
I plugged Digi in and had the same response as with the Ubuntu box - io_edgeport was not loaded/no new devices/same dmesg report.
Then I manually loaded io_edgeport and plugged the Digi in again.
[29735001.555230] usb 2-1.6: new full speed USB device using ehci_hcd and address 65
[29735001.647709] usb 2-1.6: New USB device found, idVendor=1608, idProduct=0288
Ah, this is a new device id, that's why things aren't working. Linux
doesn't know how to control this device.

Perhaps if we add it to the existing io_edgeport driver, it would work,
can you try that?

You can do the following, as root:
- unplug the device
- load the module:
modprobe io_edgeport
- add a new device id:
echo "0x1608 0x0288" > /sys/bus/usb-serial/drivers/io_edgeport/new_id
- plug the device in.

Let us know if that works or not.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Doug Minett
2013-02-15 23:44:28 UTC
Permalink
ah hah.. I'll give it try later. Eating and drinking..
Post by Greg KH
Post by Doug Minett
I did some followup on another machine at my disposal running a Debian 2.6.32-5-686-bigmem on the same hardware as the Ubuntu box - Dell Poweredge T110 II
I plugged Digi in and had the same response as with the Ubuntu box - io_edgeport was not loaded/no new devices/same dmesg report.
Then I manually loaded io_edgeport and plugged the Digi in again.
[29735001.555230] usb 2-1.6: new full speed USB device using ehci_hcd and address 65
[29735001.647709] usb 2-1.6: New USB device found, idVendor=1608, idProduct=0288
Ah, this is a new device id, that's why things aren't working. Linux
doesn't know how to control this device.
Perhaps if we add it to the existing io_edgeport driver, it would work,
can you try that?
- unplug the device
modprobe io_edgeport
echo "0x1608 0x0288" > /sys/bus/usb-serial/drivers/io_edgeport/new_id
- plug the device in.
Let us know if that works or not.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Doug Minett
2013-02-16 14:11:17 UTC
Permalink
Before I tried what you suggested below, I had a look at file structure in /sys.

The tree looks like this:

/sys/bus/usb-serial/drivers/

with subdirectories there as follows:

edgeport_2/
edgeport_4/
edgeport_8/
epic/
generic/

There is no sign of io_edgeport/ (which would be required in your suggestion below). Do you want me to create this directory before adding the new_id file within it?

Also, although the permissions for /sys/bus/usb-serial/drivers/ would appear to permit writing by root, I am not allowed to write in this directory (or anywhere else in the /sys tree. What's the trick?

Thanks.
doug.
Post by Greg KH
Post by Doug Minett
I did some followup on another machine at my disposal running a Debian 2.6.32-5-686-bigmem on the same hardware as the Ubuntu box - Dell Poweredge T110 II
I plugged Digi in and had the same response as with the Ubuntu box - io_edgeport was not loaded/no new devices/same dmesg report.
Then I manually loaded io_edgeport and plugged the Digi in again.
[29735001.555230] usb 2-1.6: new full speed USB device using ehci_hcd and address 65
[29735001.647709] usb 2-1.6: New USB device found, idVendor=1608, idProduct=0288
Ah, this is a new device id, that's why things aren't working. Linux
doesn't know how to control this device.
Perhaps if we add it to the existing io_edgeport driver, it would work,
can you try that?
- unplug the device
modprobe io_edgeport
echo "0x1608 0x0288" > /sys/bus/usb-serial/drivers/io_edgeport/new_id
- plug the device in.
Let us know if that works or not.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Greg KH
2013-02-17 18:44:44 UTC
Permalink
A: No.
Q: Should I include quotations after my reply?

http://daringfireball.net/2007/07/on_top
Post by Doug Minett
Before I tried what you suggested below, I had a look at file structure in /sys.
/sys/bus/usb-serial/drivers/
edgeport_2/
edgeport_4/
edgeport_8/
epic/
generic/
There is no sign of io_edgeport/ (which would be required in your
suggestion below). Do you want me to create this directory before
adding the new_id file within it?
Ah, sorry, no, I forgot about this, just use the "edgeport_4" name
instead.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Doug Minett
2013-02-17 21:50:21 UTC
Permalink
The suggested echo command (itself) was successful using "edgeport_4" directory.

After loading io_edgeport on the ubuntu 3.2 kernel, dmesg still reported:

[ 192.866565] usb 2-1.6: new full-speed USB device number 6 using ehci_hcd
[ 192.959323] hub 2-1.6:1.0: USB hub found
[ 192.959477] hub 2-1.6:1.0: 1 port detected
[ 193.229880] usb 2-1.6.1: new full-speed USB device number 7 using ehci_hcd

I was going to try the echo/manual load on the Debian 2.6 kernel, but I see that the /sys structure is pretty different. If it would be useful, let me know where to echo the data.

thanks.
doug. --
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Doug Minett
2013-02-22 00:15:52 UTC
Permalink
I contacted Digi about this issue and the tech rep indicated that he had no record of the device number previously reported by me (0x0288).
%Ep4rDeviceName% = Edgeport.Install, USB\VID_1608&PID_0202

With 0x0202 as the device, my con was filled with messages when I plugged the Edgeport/4r in. Then the system froze.

Let me know what other diagnostics you'd like me to perform.

Thanks.
doug. --
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
simon-wM4F9T/
2013-02-22 01:02:28 UTC
Permalink
Post by Doug Minett
I contacted Digi about this issue and the tech rep indicated that he had
no record of the device number previously reported by me (0x0288).
I was provided with a file of Digi devices as far as he was aware. Shall I
From this file I performed the 'echo' suggested by Greg earlier with a
%Ep4rDeviceName% = Edgeport.Install, USB\VID_1608&PID_0202
With 0x0202 as the device, my con was filled with messages when I plugged
the Edgeport/4r in. Then the system froze.
Perhaps it does not use the 'io_edgeport' module. As noted in my earlier
test the Edgeport4/RS232 I have uses 'io_ti'.
--
$ lsmod >> edgeport_test.txt
Module Size Used by
io_ti 23277 0
usbserial 27395 1 io_ti
--
Post by Doug Minett
Let me know what other diagnostics you'd like me to perform.
You perhaps can try Greg's trick of enable a new USBID for that module.
Simon


--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Doug Minett
2013-02-22 03:43:41 UTC
Permalink
In looking further at the Digi device file it looks like Digi may keep the same product name (in this case Edgeport 4/i) across different product versions under the hood.

Snipped from the Digi device file provided by tech support:

[Digi.NTAMD64]
; 1st Generation (930) VID/PIDs

%Ep4iDeviceName% = Edgeport.Install, USB\VID_1608&PID_0006

; 2nd Generation (80251/Netchip) VID/PIDs

%Ep4iDeviceName% = Edgeport.Install, USB\VID_1608&PID_0106

; 3rd Generation (Ti 5152 UMP) VID/PIDs

%Ep4iDeviceName% = Edgeport.Install, USB\VID_1608&PID_0206--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-***@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Loading...