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. On Feb 15, 2013, at 18:29 PM, Greg KH wrote: > On Fri, Feb 15, 2013 at 06:25:00PM -0500, Doug Minett wrote: >> 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 > > 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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
