Udev rule for HSDPA modem

Udev rule for HSDPA modem

[Jar]

Hello

I hope this is the correct list to ask this. I am not subscribed, so add
me to cc.

HSDPA modem (usb_serial+option modules) creates three ttyUSB devices.
The first one is the modem interface used for ppp connection. How to
write udev rule which will match to the first ttyUSB device? E.g. if the
devices are ttyUSB1, ttyUSB2 and ttyUSB3, how to create e.g. symlinks
modem0, modem1 and modem2, then it would be guaranteed that the modem0
device would be the first one.

I tried the above rule, but it's problem is that it match only ttyUSB0
and that is not always the HSDPA modem device.

ACTION="add", \
KERNEL="ttyUSB0", \
SUBSYSTEMS="usb", \
ATTRS{idVendor}="12d1", \
ATTRS{idProduct}="1003", \
SYMLINK+="modem", \
RUN+="/tmp/udev_test.sh"

Rule below will match all ttyUSB* devices and then the udev_test.sh will
run several times. I would want to run it only once for the first ttyUSB
of the modem.

ACTION="add", \
KERNEL="ttyUSB*", \
...
...

-- 
Best Regards, Jar

Re: Udev rule for HSDPA modem

[Greg KH]

On Fri, Nov 28, 2008 at 07:56:53PM +0200, Jar wrote:
> Hello
> 
> I hope this is the correct list to ask this. I am not subscribed, so add
> me to cc.
> 
> HSDPA modem (usb_serial+option modules) creates three ttyUSB devices.
> The first one is the modem interface used for ppp connection. How to
> write udev rule which will match to the first ttyUSB device? E.g. if the
> devices are ttyUSB1, ttyUSB2 and ttyUSB3, how to create e.g. symlinks
> modem0, modem1 and modem2, then it would be guaranteed that the modem0
> device would be the first one.

HAL contains a list of these modems and a mapping of each port to what
it does based on the specific device.

Try using that instead of udev specific rules for your accessed to the
modem, it will work much better.

good luck,

greg k-h

Re: Udev rule for HSDPA modem

[Jar]

Greg KH wrote:
> HAL contains a list of these modems and a mapping of each port to what
> it does based on the specific device.
> 
> Try using that instead of udev specific rules for your accessed to the
> modem, it will work much better.

Thanks for your reply! Does HAL require that I have desktop installed, 
this is my home "server" machine without X? Do you have any starting 
point or where to learn more how to do this with HAL.

-- 
Best Regards, Jar

Re: Udev rule for HSDPA modem

[Greg KH]

On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
> Greg KH wrote:
>> HAL contains a list of these modems and a mapping of each port to what
>> it does based on the specific device.
>> Try using that instead of udev specific rules for your accessed to the
>> modem, it will work much better.
>
> Thanks for your reply! Does HAL require that I have desktop installed, this 
> is my home "server" machine without X? Do you have any starting point or 
> where to learn more how to do this with HAL.

I do not think HAL requires X.  Try asking on your distro mailing list
for how they have incorporated HAL into the releases you are using.

good luck,

greg k-h

Re: Udev rule for HSDPA modem

[Kay Sievers]

On Sat, Nov 29, 2008 at 18:37, Greg KH <greg@kroah.com> wrote:
> On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
>> Greg KH wrote:
>>> HAL contains a list of these modems and a mapping of each port to what
>>> it does based on the specific device.
>>> Try using that instead of udev specific rules for your accessed to the
>>> modem, it will work much better.
>>
>> Thanks for your reply! Does HAL require that I have desktop installed, this
>> is my home "server" machine without X? Do you have any starting point or
>> where to learn more how to do this with HAL.
>
> I do not think HAL requires X.  Try asking on your distro mailing list
> for how they have incorporated HAL into the releases you are using.

It might get pretty complicated to use D-Bus/HAL for simple setups,
and rather static configurations like this. NetworkManager handles
that, and we will even get modem-probing soon, but in cases like this
it might be easier to have a simple - not very flexible - but working
solution.

Maybe we can have an "index" sysfs file at the serial device, which
carries the instance number, per usb device? This would allow us to
create persistent links which do not depend on the kernel device
enumeration across multiple device.

We did the same for v4l devices recently:
  http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;hS9a7555b31e65e66fb84c881d07d2bf18c974d0

Greg, what do you think?

Thanks,
Kay

Re: Udev rule for HSDPA modem

[Greg KH]

On Sun, Nov 30, 2008 at 06:21:11AM +0100, Kay Sievers wrote:
> On Sat, Nov 29, 2008 at 18:37, Greg KH <greg@kroah.com> wrote:
> > On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
> >> Greg KH wrote:
> >>> HAL contains a list of these modems and a mapping of each port to what
> >>> it does based on the specific device.
> >>> Try using that instead of udev specific rules for your accessed to the
> >>> modem, it will work much better.
> >>
> >> Thanks for your reply! Does HAL require that I have desktop installed, this
> >> is my home "server" machine without X? Do you have any starting point or
> >> where to learn more how to do this with HAL.
> >
> > I do not think HAL requires X.  Try asking on your distro mailing list
> > for how they have incorporated HAL into the releases you are using.
> 
> It might get pretty complicated to use D-Bus/HAL for simple setups,
> and rather static configurations like this. NetworkManager handles
> that, and we will even get modem-probing soon, but in cases like this
> it might be easier to have a simple - not very flexible - but working
> solution.
> 
> Maybe we can have an "index" sysfs file at the serial device, which
> carries the instance number, per usb device? This would allow us to
> create persistent links which do not depend on the kernel device
> enumeration across multiple device.
> 
> We did the same for v4l devices recently:
>   http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;hS9a7555b31e65e66fb84c881d07d2bf18c974d0
> 
> Greg, what do you think?

Don't we already have something like this today (the "ports" on an
individual usb-serial device)?  Or do we just need to export that a bit
better?

I have no objection to something like this if it would help out.  But I
think the bigger problem is that userspace doesn't always "know" which
port does what for which type of device.  That is something that we have
talked about adding as a sysfs attribute a while ago, but it never went
very far as no one had a patch :(

thanks,

greg k-h

Re: Udev rule for HSDPA modem

[Kay Sievers]

On Wed, Dec 3, 2008 at 07:45, Greg KH <greg@kroah.com> wrote:
> On Sun, Nov 30, 2008 at 06:21:11AM +0100, Kay Sievers wrote:
>> On Sat, Nov 29, 2008 at 18:37, Greg KH <greg@kroah.com> wrote:
>> > On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
>> >> Greg KH wrote:
>> >>> HAL contains a list of these modems and a mapping of each port to what
>> >>> it does based on the specific device.
>> >>> Try using that instead of udev specific rules for your accessed to the
>> >>> modem, it will work much better.
>> >>
>> >> Thanks for your reply! Does HAL require that I have desktop installed, this
>> >> is my home "server" machine without X? Do you have any starting point or
>> >> where to learn more how to do this with HAL.
>> >
>> > I do not think HAL requires X.  Try asking on your distro mailing list
>> > for how they have incorporated HAL into the releases you are using.
>>
>> It might get pretty complicated to use D-Bus/HAL for simple setups,
>> and rather static configurations like this. NetworkManager handles
>> that, and we will even get modem-probing soon, but in cases like this
>> it might be easier to have a simple - not very flexible - but working
>> solution.
>>
>> Maybe we can have an "index" sysfs file at the serial device, which
>> carries the instance number, per usb device? This would allow us to
>> create persistent links which do not depend on the kernel device
>> enumeration across multiple device.
>>
>> We did the same for v4l devices recently:
>>   http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;hS9a7555b31e65e66fb84c881d07d2bf18c974d0
>>
>> Greg, what do you think?
>
> Don't we already have something like this today (the "ports" on an
> individual usb-serial device)?  Or do we just need to export that a bit
> better?

Yeah, maybe that works already. I don't have such a device.

Jar, care to provide the output of:
  grep . /sys/bus/usb-serial/devices/*/*

> I have no objection to something like this if it would help out.  But I
> think the bigger problem is that userspace doesn't always "know" which
> port does what for which type of device.  That is something that we have
> talked about adding as a sysfs attribute a while ago, but it never went
> very far as no one had a patch :(

I think Dan Williams (dcbw) is working on something like that. We will
move stuff from HAL down to udev, and will get udev based modem
probing. NetworkManager needs something like this.

Thanks,
Kay

Re: Udev rule for HSDPA modem

[Kay Sievers]

On Wed, Dec 3, 2008 at 10:27, Kay Sievers <kay.sievers@vrfy.org> wrote:
> On Wed, Dec 3, 2008 at 07:45, Greg KH <greg@kroah.com> wrote:
>> On Sun, Nov 30, 2008 at 06:21:11AM +0100, Kay Sievers wrote:
>>> On Sat, Nov 29, 2008 at 18:37, Greg KH <greg@kroah.com> wrote:
>>> > On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
>>> >> Greg KH wrote:
>>> >>> HAL contains a list of these modems and a mapping of each port to what
>>> >>> it does based on the specific device.
>>> >>> Try using that instead of udev specific rules for your accessed to the
>>> >>> modem, it will work much better.
>>> >>
>>> >> Thanks for your reply! Does HAL require that I have desktop installed, this
>>> >> is my home "server" machine without X? Do you have any starting point or
>>> >> where to learn more how to do this with HAL.
>>> >
>>> > I do not think HAL requires X.  Try asking on your distro mailing list
>>> > for how they have incorporated HAL into the releases you are using.
>>>
>>> It might get pretty complicated to use D-Bus/HAL for simple setups,
>>> and rather static configurations like this. NetworkManager handles
>>> that, and we will even get modem-probing soon, but in cases like this
>>> it might be easier to have a simple - not very flexible - but working
>>> solution.
>>>
>>> Maybe we can have an "index" sysfs file at the serial device, which
>>> carries the instance number, per usb device? This would allow us to
>>> create persistent links which do not depend on the kernel device
>>> enumeration across multiple device.
>>>
>>> We did the same for v4l devices recently:
>>>   http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;hS9a7555b31e65e66fb84c881d07d2bf18c974d0
>>>
>>> Greg, what do you think?
>>
>> Don't we already have something like this today (the "ports" on an
>> individual usb-serial device)?  Or do we just need to export that a bit
>> better?
>
> Yeah, maybe that works already. I don't have such a device.

Ok, I found one. You mean "port_number", right? But unfortunately it
looks pretty useless in this case. :)

  $ grep . /sys/bus/usb-serial/devices/*/port_number
  /sys/bus/usb-serial/devices/ttyUSB1/port_number:0
  /sys/bus/usb-serial/devices/ttyUSB2/port_number:0

They would only be not "0" if the serial lines would be on the same
usb interface?

We would need a per-device enumeration, but that's nothing the
usb-serial stuff knows/cares about if we have different usb
interfaces, right?

Thanks,
Kay

Re: Udev rule for HSDPA modem

[Kay Sievers]

[-- Attachment #1: Type: text/plain, Size: 3279 bytes --]

On Wed, 2008-12-03 at 13:12 +0100, Kay Sievers wrote:
> On Wed, Dec 3, 2008 at 10:27, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > On Wed, Dec 3, 2008 at 07:45, Greg KH <greg@kroah.com> wrote:
> >> On Sun, Nov 30, 2008 at 06:21:11AM +0100, Kay Sievers wrote:
> >>> On Sat, Nov 29, 2008 at 18:37, Greg KH <greg@kroah.com> wrote:
> >>> > On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
> >>> >> Greg KH wrote:
> >>> >>> HAL contains a list of these modems and a mapping of each port to what
> >>> >>> it does based on the specific device.
> >>> >>> Try using that instead of udev specific rules for your accessed to the
> >>> >>> modem, it will work much better.
> >>> >>
> >>> >> Thanks for your reply! Does HAL require that I have desktop installed, this
> >>> >> is my home "server" machine without X? Do you have any starting point or
> >>> >> where to learn more how to do this with HAL.
> >>> >
> >>> > I do not think HAL requires X.  Try asking on your distro mailing list
> >>> > for how they have incorporated HAL into the releases you are using.
> >>>
> >>> It might get pretty complicated to use D-Bus/HAL for simple setups,
> >>> and rather static configurations like this. NetworkManager handles
> >>> that, and we will even get modem-probing soon, but in cases like this
> >>> it might be easier to have a simple - not very flexible - but working
> >>> solution.
> >>>
> >>> Maybe we can have an "index" sysfs file at the serial device, which
> >>> carries the instance number, per usb device? This would allow us to
> >>> create persistent links which do not depend on the kernel device
> >>> enumeration across multiple device.
> >>>
> >>> We did the same for v4l devices recently:
> >>>   http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=539a7555b31e65e66fb84c881d07d2bf18c974d0
> >>>
> >>> Greg, what do you think?
> >>
> >> Don't we already have something like this today (the "ports" on an
> >> individual usb-serial device)?  Or do we just need to export that a bit
> >> better?
> >
> > Yeah, maybe that works already. I don't have such a device.
> 
> Ok, I found one. You mean "port_number", right? But unfortunately it
> looks pretty useless in this case. :)
> 
>   $ grep . /sys/bus/usb-serial/devices/*/port_number
>   /sys/bus/usb-serial/devices/ttyUSB1/port_number:0
>   /sys/bus/usb-serial/devices/ttyUSB2/port_number:0
> 
> They would only be not "0" if the serial lines would be on the same
> usb interface?
> 
> We would need a per-device enumeration, but that's nothing the
> usb-serial stuff knows/cares about if we have different usb
> interfaces, right?

Greg, do you have a usb multi-port serial card? Can you possibly give
this a try, and show us "tree /dev/serial"?

I have this here now for my "simple" devices:
  /dev/serial
  `-- by-id
      |-- usb-067b_2303-serial-if00-port0 -> ../../ttyUSB0
      |-- usb-HUAWEI_Technology_HUAWEI_Mobile-serial-if00-port0 -> ../../ttyUSB1
      `-- usb-HUAWEI_Technology_HUAWEI_Mobile-serial-if01-port0 -> ../../ttyUSB2

If we can make that work as expected, I'll look into by-path/, so we can
have identical devices properly identified, if needed. Then we can check
how we should finally name all that, and possibly add that stuff to the
default rule set.

Thanks,
Kay

[-- Attachment #2: Type: text/plain, Size: 625 bytes --]

# do not edit this file, it will be overwritten on update

ACTION!="add|change", GOTO="persistent_serial_end"
SUBSYSTEM!="tty", GOTO="persistent_serial_end"
KERNEL!="ttyUSB[0-9]*", GOTO="persistent_serial_end"

IMPORT="usb_id --export"
ENV{ID_SERIAL}=="", GOTO="persistent_serial_end"
SUBSYSTEMS=="usb-serial", ENV{ID_PORT}="$attr{port_number}"
ENV{ID_PORT}=="", GOTO="persistent_serial_end"
SUBSYSTEMS=="usb", ENV{ID_IFACE}="$attr{bInterfaceNumber}"
ENV{ID_IFACE}=="", GOTO="persistent_serial_end"
SYMLINK+="serial/by-id/$env{ID_BUS}-$env{ID_SERIAL}-serial-if$env{ID_IFACE}-port$env{ID_PORT}"

LABEL="persistent_serial_end"

Re: Udev rule for HSDPA modem

[Karl O. Pinc]

On 12/03/2008 09:11:29 AM, Kay Sievers wrote:
> On Wed, 2008-12-03 at 13:12 +0100, Kay Sievers wrote:
> > On Wed, Dec 3, 2008 at 10:27, Kay Sievers <kay.sievers@vrfy.org>
> wrote:
> > > On Wed, Dec 3, 2008 at 07:45, Greg KH <greg@kroah.com> wrote:
> > >> On Sun, Nov 30, 2008 at 06:21:11AM +0100, Kay Sievers wrote:
> > >>> On Sat, Nov 29, 2008 at 18:37, Greg KH <greg@kroah.com> wrote:
> > >>> > On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
> > >>> >> Greg KH wrote:

> > Ok, I found one. You mean "port_number", right? But unfortunately it
> > looks pretty useless in this case. :)
> >
> >   $ grep . /sys/bus/usb-serial/devices/*/port_number
> >   /sys/bus/usb-serial/devices/ttyUSB1/port_number:0
> >   /sys/bus/usb-serial/devices/ttyUSB2/port_number:0
> >
> > They would only be not "0" if the serial lines would be on the same
> > usb interface?
> >
> > We would need a per-device enumeration, but that's nothing the
> > usb-serial stuff knows/cares about if we have different usb
> > interfaces, right?
> 
> Greg, do you have a usb multi-port serial card? Can you possibly give
> this a try, and show us "tree /dev/serial"?

I've been following this thread, and don't fully understand it
but have what may be a related problem.  I'll describe it here
just so that you can keep it in mind in case it's relevant
or if you want some information on my device.

I put my problem on hold some months ago and will eventually
get back to it.

I've a Digi Edgeport 4/16.  It's got 16 serial ports.
It's been a while and I don't really know what I'm doing
with udev but as I recall the device
has an internal USB hub and the kernel seems to discover the
different "plugs" on the "hub" in a different order at various times.
(There's either 2 or 4 serial ports on each internal "endpoint",
I forget.)
Hence, there's no persistent correspondence between physical
serial port and /dev device.  I tried writing some udev rules
akin to the persistent rule generation for network devices,
posted the results here, and got what seemed to be better
ideas back I've not followed up on.

Anyhow, I tried "tree /dev/serial/" to post the results
here and there is no /dev/serial.  Let me know if you'd
like some other information on the device.

Debian etch
Linux 2.6.18-6-686
udev 0.105-4

Regards,

Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein

Re: Udev rule for HSDPA modem

[Kay Sievers]

On Wed, Dec 3, 2008 at 18:06, Karl O. Pinc <kop@meme.com> wrote:
> On 12/03/2008 09:11:29 AM, Kay Sievers wrote:
>>
>> On Wed, 2008-12-03 at 13:12 +0100, Kay Sievers wrote:
>> > On Wed, Dec 3, 2008 at 10:27, Kay Sievers <kay.sievers@vrfy.org>
>> wrote:
>> > > On Wed, Dec 3, 2008 at 07:45, Greg KH <greg@kroah.com> wrote:
>> > >> On Sun, Nov 30, 2008 at 06:21:11AM +0100, Kay Sievers wrote:
>> > >>> On Sat, Nov 29, 2008 at 18:37, Greg KH <greg@kroah.com> wrote:
>> > >>> > On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
>> > >>> >> Greg KH wrote:
>
>> > Ok, I found one. You mean "port_number", right? But unfortunately it
>> > looks pretty useless in this case. :)
>> >
>> >   $ grep . /sys/bus/usb-serial/devices/*/port_number
>> >   /sys/bus/usb-serial/devices/ttyUSB1/port_number:0
>> >   /sys/bus/usb-serial/devices/ttyUSB2/port_number:0
>> >
>> > They would only be not "0" if the serial lines would be on the same
>> > usb interface?
>> >
>> > We would need a per-device enumeration, but that's nothing the
>> > usb-serial stuff knows/cares about if we have different usb
>> > interfaces, right?
>>
>> Greg, do you have a usb multi-port serial card? Can you possibly give
>> this a try, and show us "tree /dev/serial"?
>
> I've been following this thread, and don't fully understand it
> but have what may be a related problem.  I'll describe it here
> just so that you can keep it in mind in case it's relevant
> or if you want some information on my device.
>
> I put my problem on hold some months ago and will eventually
> get back to it.
>
> I've a Digi Edgeport 4/16.  It's got 16 serial ports.
> It's been a while and I don't really know what I'm doing
> with udev but as I recall the device
> has an internal USB hub and the kernel seems to discover the
> different "plugs" on the "hub" in a different order at various times.
> (There's either 2 or 4 serial ports on each internal "endpoint",
> I forget.)
> Hence, there's no persistent correspondence between physical
> serial port and /dev device.  I tried writing some udev rules
> akin to the persistent rule generation for network devices,
> posted the results here, and got what seemed to be better
> ideas back I've not followed up on.
>
> Anyhow, I tried "tree /dev/serial/" to post the results
> here and there is no /dev/serial.

Did you copy the in the earlier mail attached file  to
/etc/udev/rules.d/, and diconnect/reconnect the device? Only this
would create the /dev/serial/ stuff.

> Let me know if you'd
> like some other information on the device.
>
> Debian etch
> Linux 2.6.18-6-686
> udev 0.105-4

I hope udev 105 will work with the rules, I'm not entirely sure.

Kay

Re: Udev rule for HSDPA modem

[Karl O. Pinc]

On 12/03/2008 11:37:10 AM, Kay Sievers wrote:
> On Wed, Dec 3, 2008 at 18:06, Karl O. Pinc <kop@meme.com> wrote:
> > On 12/03/2008 09:11:29 AM, Kay Sievers wrote:
> >>
> >> On Wed, 2008-12-03 at 13:12 +0100, Kay Sievers wrote:
> >> > On Wed, Dec 3, 2008 at 10:27, Kay Sievers <kay.sievers@vrfy.org>
> >> wrote:
> >> > > On Wed, Dec 3, 2008 at 07:45, Greg KH <greg@kroah.com> wrote:
> >> > >> On Sun, Nov 30, 2008 at 06:21:11AM +0100, Kay Sievers wrote:
> >> > >>> On Sat, Nov 29, 2008 at 18:37, Greg KH <greg@kroah.com>
> wrote:
> >> > >>> > On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
> >> > >>> >> Greg KH wrote:

> >> Greg, do you have a usb multi-port serial card? Can you possibly
> give
> >> this a try, and show us "tree /dev/serial"?

> > I've a Digi Edgeport 4/16.  It's got 16 serial ports.
> > It's been a while and I don't really know what I'm doing
> > with udev but as I recall the device
> > has an internal USB hub and the kernel seems to discover the
> > different "plugs" on the "hub" in a different order at various
> times.
> > (There's either 2 or 4 serial ports on each internal "endpoint",
> > I forget.)
> > Hence, there's no persistent correspondence between physical
> > serial port and /dev device.  I tried writing some udev rules
> > akin to the persistent rule generation for network devices,
> > posted the results here, and got what seemed to be better
> > ideas back I've not followed up on.
> >
> > Anyhow, I tried "tree /dev/serial/" to post the results
> > here and there is no /dev/serial.
> 
> Did you copy the in the earlier mail attached file  to
> /etc/udev/rules.d/, and diconnect/reconnect the device? Only this
> would create the /dev/serial/ stuff.

No.  Now I have and it does not seem to work,
but then I don't see the ttyUSB devices either.
I'm thinking that my kernel does not yet have
support and I need something newer.  (I know
I got ttyUSB devices created the last time
I tested the device....)

I'm sorry, I have to stop now.  I will try
to report back in a few days.  I hope I've
not distracted you too much.

I tried udevtest and didn't get any parse errors.

> >
> > Debian etch
> > Linux 2.6.18-6-686
> > udev 0.105-4


Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein

Re: Udev rule for HSDPA modem

[Greg KH]

On Wed, Dec 03, 2008 at 04:11:29PM +0100, Kay Sievers wrote:
> On Wed, 2008-12-03 at 13:12 +0100, Kay Sievers wrote:
> > On Wed, Dec 3, 2008 at 10:27, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > > On Wed, Dec 3, 2008 at 07:45, Greg KH <greg@kroah.com> wrote:
> > >> On Sun, Nov 30, 2008 at 06:21:11AM +0100, Kay Sievers wrote:
> > >>> On Sat, Nov 29, 2008 at 18:37, Greg KH <greg@kroah.com> wrote:
> > >>> > On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
> > >>> >> Greg KH wrote:
> > >>> >>> HAL contains a list of these modems and a mapping of each port to what
> > >>> >>> it does based on the specific device.
> > >>> >>> Try using that instead of udev specific rules for your accessed to the
> > >>> >>> modem, it will work much better.
> > >>> >>
> > >>> >> Thanks for your reply! Does HAL require that I have desktop installed, this
> > >>> >> is my home "server" machine without X? Do you have any starting point or
> > >>> >> where to learn more how to do this with HAL.
> > >>> >
> > >>> > I do not think HAL requires X.  Try asking on your distro mailing list
> > >>> > for how they have incorporated HAL into the releases you are using.
> > >>>
> > >>> It might get pretty complicated to use D-Bus/HAL for simple setups,
> > >>> and rather static configurations like this. NetworkManager handles
> > >>> that, and we will even get modem-probing soon, but in cases like this
> > >>> it might be easier to have a simple - not very flexible - but working
> > >>> solution.
> > >>>
> > >>> Maybe we can have an "index" sysfs file at the serial device, which
> > >>> carries the instance number, per usb device? This would allow us to
> > >>> create persistent links which do not depend on the kernel device
> > >>> enumeration across multiple device.
> > >>>
> > >>> We did the same for v4l devices recently:
> > >>>   http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;hS9a7555b31e65e66fb84c881d07d2bf18c974d0
> > >>>
> > >>> Greg, what do you think?
> > >>
> > >> Don't we already have something like this today (the "ports" on an
> > >> individual usb-serial device)?  Or do we just need to export that a bit
> > >> better?
> > >
> > > Yeah, maybe that works already. I don't have such a device.
> > 
> > Ok, I found one. You mean "port_number", right? But unfortunately it
> > looks pretty useless in this case. :)
> > 
> >   $ grep . /sys/bus/usb-serial/devices/*/port_number
> >   /sys/bus/usb-serial/devices/ttyUSB1/port_number:0
> >   /sys/bus/usb-serial/devices/ttyUSB2/port_number:0
> > 
> > They would only be not "0" if the serial lines would be on the same
> > usb interface?
> > 
> > We would need a per-device enumeration, but that's nothing the
> > usb-serial stuff knows/cares about if we have different usb
> > interfaces, right?
> 
> Greg, do you have a usb multi-port serial card? Can you possibly give
> this a try, and show us "tree /dev/serial"?
> 
> I have this here now for my "simple" devices:
>   /dev/serial
>   `-- by-id
>       |-- usb-067b_2303-serial-if00-port0 -> ../../ttyUSB0
>       |-- usb-HUAWEI_Technology_HUAWEI_Mobile-serial-if00-port0 -> ../../ttyUSB1
>       `-- usb-HUAWEI_Technology_HUAWEI_Mobile-serial-if01-port0 -> ../../ttyUSB2
> 
> If we can make that work as expected, I'll look into by-path/, so we can
> have identical devices properly identified, if needed. Then we can check
> how we should finally name all that, and possibly add that stuff to the
> default rule set.


This looks good, here's the output using udev 133 and the rules and a
few usb-serial devices plugged into the system at the same time:

$ tree /dev/serial/
/dev/serial/
`-- by-id
    |-- usb-Inside_Out_Networks_Edgeport
    |   |-- 4_04-01-006467-serial-if00-port0 -> ../../../ttyUSB0
    |   |-- 4_04-01-006467-serial-if00-port1 -> ../../../ttyUSB1
    |   |-- 4_04-01-006467-serial-if00-port2 -> ../../../ttyUSB2
    |   `-- 4_04-01-006467-serial-if00-port3 -> ../../../ttyUSB3
    |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port0 -> ../../ttyUSB8
    |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port1 -> ../../ttyUSB9
    |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port2 -> ../../ttyUSB10
    |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port3 -> ../../ttyUSB11
    |-- usb-Prolific_Technology_Inc._USB-Serial_Controller-serial-if00-port0 -> ../../ttyUSB7
    |-- usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port0 -> ../../ttyUSB4
    |-- usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port1 -> ../../ttyUSB5
    `-- usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port2 -> ../../ttyUSB6

I'm not so sure about the long names, but it is unique :)

thanks,

greg k-h

Re: Udev rule for HSDPA modem

[Kay Sievers]

[-- Attachment #1: Type: text/plain, Size: 5322 bytes --]

On Wed, 2008-12-03 at 15:10 -0800, Greg KH wrote:
> On Wed, Dec 03, 2008 at 04:11:29PM +0100, Kay Sievers wrote:
> > On Wed, 2008-12-03 at 13:12 +0100, Kay Sievers wrote:
> > > On Wed, Dec 3, 2008 at 10:27, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > > > On Wed, Dec 3, 2008 at 07:45, Greg KH <greg@kroah.com> wrote:
> > > >> On Sun, Nov 30, 2008 at 06:21:11AM +0100, Kay Sievers wrote:
> > > >>> On Sat, Nov 29, 2008 at 18:37, Greg KH <greg@kroah.com> wrote:
> > > >>> > On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
> > > >>> >> Greg KH wrote:
> > > >>> >>> HAL contains a list of these modems and a mapping of each port to what
> > > >>> >>> it does based on the specific device.
> > > >>> >>> Try using that instead of udev specific rules for your accessed to the
> > > >>> >>> modem, it will work much better.
> > > >>> >>
> > > >>> >> Thanks for your reply! Does HAL require that I have desktop installed, this
> > > >>> >> is my home "server" machine without X? Do you have any starting point or
> > > >>> >> where to learn more how to do this with HAL.
> > > >>> >
> > > >>> > I do not think HAL requires X.  Try asking on your distro mailing list
> > > >>> > for how they have incorporated HAL into the releases you are using.
> > > >>>
> > > >>> It might get pretty complicated to use D-Bus/HAL for simple setups,
> > > >>> and rather static configurations like this. NetworkManager handles
> > > >>> that, and we will even get modem-probing soon, but in cases like this
> > > >>> it might be easier to have a simple - not very flexible - but working
> > > >>> solution.
> > > >>>
> > > >>> Maybe we can have an "index" sysfs file at the serial device, which
> > > >>> carries the instance number, per usb device? This would allow us to
> > > >>> create persistent links which do not depend on the kernel device
> > > >>> enumeration across multiple device.
> > > >>>
> > > >>> We did the same for v4l devices recently:
> > > >>>   http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=539a7555b31e65e66fb84c881d07d2bf18c974d0
> > > >>>
> > > >>> Greg, what do you think?
> > > >>
> > > >> Don't we already have something like this today (the "ports" on an
> > > >> individual usb-serial device)?  Or do we just need to export that a bit
> > > >> better?
> > > >
> > > > Yeah, maybe that works already. I don't have such a device.
> > > 
> > > Ok, I found one. You mean "port_number", right? But unfortunately it
> > > looks pretty useless in this case. :)
> > > 
> > >   $ grep . /sys/bus/usb-serial/devices/*/port_number
> > >   /sys/bus/usb-serial/devices/ttyUSB1/port_number:0
> > >   /sys/bus/usb-serial/devices/ttyUSB2/port_number:0
> > > 
> > > They would only be not "0" if the serial lines would be on the same
> > > usb interface?
> > > 
> > > We would need a per-device enumeration, but that's nothing the
> > > usb-serial stuff knows/cares about if we have different usb
> > > interfaces, right?
> > 
> > Greg, do you have a usb multi-port serial card? Can you possibly give
> > this a try, and show us "tree /dev/serial"?
> > 
> > I have this here now for my "simple" devices:
> >   /dev/serial
> >   `-- by-id
> >       |-- usb-067b_2303-serial-if00-port0 -> ../../ttyUSB0
> >       |-- usb-HUAWEI_Technology_HUAWEI_Mobile-serial-if00-port0 -> ../../ttyUSB1
> >       `-- usb-HUAWEI_Technology_HUAWEI_Mobile-serial-if01-port0 -> ../../ttyUSB2
> > 
> > If we can make that work as expected, I'll look into by-path/, so we can
> > have identical devices properly identified, if needed. Then we can check
> > how we should finally name all that, and possibly add that stuff to the
> > default rule set.
> 
> 
> This looks good, here's the output using udev 133 and the rules and a
> few usb-serial devices plugged into the system at the same time:
> 
> $ tree /dev/serial/
> /dev/serial/
> `-- by-id
>     |-- usb-Inside_Out_Networks_Edgeport
>     |   |-- 4_04-01-006467-serial-if00-port0 -> ../../../ttyUSB0
>     |   |-- 4_04-01-006467-serial-if00-port1 -> ../../../ttyUSB1
>     |   |-- 4_04-01-006467-serial-if00-port2 -> ../../../ttyUSB2
>     |   `-- 4_04-01-006467-serial-if00-port3 -> ../../../ttyUSB3
>     |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port0 -> ../../ttyUSB8
>     |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port1 -> ../../ttyUSB9
>     |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port2 -> ../../ttyUSB10
>     |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port3 -> ../../ttyUSB11
>     |-- usb-Prolific_Technology_Inc._USB-Serial_Controller-serial-if00-port0 -> ../../ttyUSB7
>     |-- usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port0 -> ../../ttyUSB4
>     |-- usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port1 -> ../../ttyUSB5
>     `-- usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port2 -> ../../ttyUSB6
> 
> I'm not so sure about the long names, but it is unique :)

Yeah, it looks really strange with your devices. Why put people poetry
in the device strings? :)

But it seems to work, which is great. Here is a new version of the
serial.rules and a /lib/udev/path_id which needs to be replaced.

Can you try that again on your "collection"? :)

Thanks,
Kay

[-- Attachment #2: Type: application/x-shellscript, Size: 11841 bytes --]

[-- Attachment #3: Type: text/plain, Size: 715 bytes --]

# do not edit this file, it will be overwritten on update

ACTION!="add|change", GOTO="persistent_serial_end"
SUBSYSTEM!="tty", GOTO="persistent_serial_end"
KERNEL!="ttyUSB[0-9]*", GOTO="persistent_serial_end"

SUBSYSTEMS=="usb-serial", ENV{ID_PORT}="$attr{port_number}"
ENV{ID_PORT}=="", GOTO="persistent_serial_end"

IMPORT="path_id"
ENV{ID_PATH}=="?*", SYMLINK+="serial/by-path/$env{ID_PATH}-port$env{ID_PORT}"

IMPORT="usb_id --export"
ENV{ID_SERIAL}=="", GOTO="persistent_serial_end"
SUBSYSTEMS=="usb", ENV{ID_IFACE}="$attr{bInterfaceNumber}"
ENV{ID_IFACE}=="", GOTO="persistent_serial_end"
SYMLINK+="serial/by-id/$env{ID_BUS}-$env{ID_SERIAL}-if$env{ID_IFACE}-port$env{ID_PORT}"

LABEL="persistent_serial_end"

Re: Udev rule for HSDPA modem

[Greg KH]

On Thu, Dec 04, 2008 at 12:54:31AM +0100, Kay Sievers wrote:
> Yeah, it looks really strange with your devices. Why put people poetry
> in the device strings? :)
> 
> But it seems to work, which is great. Here is a new version of the
> serial.rules and a /lib/udev/path_id which needs to be replaced.
> 
> Can you try that again on your "collection"? :)

Here you go.  I'm not so sure the "by-path" is that useful, as it has
the ttyUSB number in the name, which can be different from boot-to-boot.

How about putting the usb path in there and not truncate it?

thanks,

greg k-h

$ tree /dev/serial/
/dev/serial/
|-- by-id
|   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port0 -> ../../ttyUSB0
|   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port1 -> ../../ttyUSB1
|   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port2 -> ../../ttyUSB2
|   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port3 -> ../../ttyUSB3
|   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port0 -> ../../ttyUSB8
|   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port1 -> ../../ttyUSB9
|   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port2 -> ../../ttyUSB10
|   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port3 -> ../../ttyUSB11
|   `-- usb-Prolific_Technology_Inc._USB-Serial_Controller-if00-port0 -> ../../ttyUSB7
`-- by-path
    |-- pci-0000:00:1d.2-usb-0:ttyUSB7-port0 -> ../../ttyUSB7
    |-- pci-0000:00:1d.7-usb-0:ttyUSB0-port0 -> ../../ttyUSB0
    |-- pci-0000:00:1d.7-usb-0:ttyUSB1-port1 -> ../../ttyUSB1
    |-- pci-0000:00:1d.7-usb-0:ttyUSB10-port2 -> ../../ttyUSB10
    |-- pci-0000:00:1d.7-usb-0:ttyUSB11-port3 -> ../../ttyUSB11
    |-- pci-0000:00:1d.7-usb-0:ttyUSB2-port2 -> ../../ttyUSB2
    |-- pci-0000:00:1d.7-usb-0:ttyUSB3-port3 -> ../../ttyUSB3
    |-- pci-0000:00:1d.7-usb-0:ttyUSB8-port0 -> ../../ttyUSB8
    `-- pci-0000:00:1d.7-usb-0:ttyUSB9-port1 -> ../../ttyUSB9

Re: Udev rule for HSDPA modem

[Kay Sievers]

On Thu, Dec 4, 2008 at 01:04, Greg KH <greg@kroah.com> wrote:
> On Thu, Dec 04, 2008 at 12:54:31AM +0100, Kay Sievers wrote:
>> Yeah, it looks really strange with your devices. Why put people poetry
>> in the device strings? :)
>>
>> But it seems to work, which is great. Here is a new version of the
>> serial.rules and a /lib/udev/path_id which needs to be replaced.
>>
>> Can you try that again on your "collection"? :)
>
> Here you go.  I'm not so sure the "by-path" is that useful, as it has
> the ttyUSB number in the name, which can be different from boot-to-boot.
>
> How about putting the usb path in there and not truncate it?
>
> thanks,
>
> greg k-h
>
> $ tree /dev/serial/
> /dev/serial/
> |-- by-id
> |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port0 -> ../../ttyUSB0
> |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port1 -> ../../ttyUSB1
> |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port2 -> ../../ttyUSB2
> |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port3 -> ../../ttyUSB3
> |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port0 -> ../../ttyUSB8
> |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port1 -> ../../ttyUSB9
> |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port2 -> ../../ttyUSB10
> |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port3 -> ../../ttyUSB11
> |   `-- usb-Prolific_Technology_Inc._USB-Serial_Controller-if00-port0 -> ../../ttyUSB7
> `-- by-path
>    |-- pci-0000:00:1d.2-usb-0:ttyUSB7-port0 -> ../../ttyUSB7
>    |-- pci-0000:00:1d.7-usb-0:ttyUSB0-port0 -> ../../ttyUSB0
>    |-- pci-0000:00:1d.7-usb-0:ttyUSB1-port1 -> ../../ttyUSB1
>    |-- pci-0000:00:1d.7-usb-0:ttyUSB10-port2 -> ../../ttyUSB10
>    |-- pci-0000:00:1d.7-usb-0:ttyUSB11-port3 -> ../../ttyUSB11
>    |-- pci-0000:00:1d.7-usb-0:ttyUSB2-port2 -> ../../ttyUSB2
>    |-- pci-0000:00:1d.7-usb-0:ttyUSB3-port3 -> ../../ttyUSB3
>    |-- pci-0000:00:1d.7-usb-0:ttyUSB8-port0 -> ../../ttyUSB8
>    `-- pci-0000:00:1d.7-usb-0:ttyUSB9-port1 -> ../../ttyUSB9

You did replace /lib/udev/path_id? That should not happen.

It looks like this here:
  $ tree /dev/serial/
  /dev/serial/
  |-- by-id
  |   |-- usb-067b_2303-if00-port0 -> ../../ttyUSB0
  |   |-- usb-HUAWEI_Technology_HUAWEI_Mobile-if00-port0 -> ../../ttyUSB1
  |   `-- usb-HUAWEI_Technology_HUAWEI_Mobile-if01-port0 -> ../../ttyUSB2
  `-- by-path
      |-- pci-0000:00:1d.0-usb-0:1.2:1.0-port0 -> ../../ttyUSB0
      |-- pci-0000:00:1d.7-usb-0:2:1.0-port0 -> ../../ttyUSB1
      `-- pci-0000:00:1d.7-usb-0:2:1.1-port0 -> ../../ttyUSB2

Kay

Re: Udev rule for HSDPA modem

[Greg KH]

On Thu, Dec 04, 2008 at 01:12:27AM +0100, Kay Sievers wrote:
> On Thu, Dec 4, 2008 at 01:04, Greg KH <greg@kroah.com> wrote:
> > On Thu, Dec 04, 2008 at 12:54:31AM +0100, Kay Sievers wrote:
> >> Yeah, it looks really strange with your devices. Why put people poetry
> >> in the device strings? :)
> >>
> >> But it seems to work, which is great. Here is a new version of the
> >> serial.rules and a /lib/udev/path_id which needs to be replaced.
> >>
> >> Can you try that again on your "collection"? :)
> >
> > Here you go.  I'm not so sure the "by-path" is that useful, as it has
> > the ttyUSB number in the name, which can be different from boot-to-boot.
> >
> > How about putting the usb path in there and not truncate it?
> >
> > thanks,
> >
> > greg k-h
> >
> > $ tree /dev/serial/
> > /dev/serial/
> > |-- by-id
> > |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port0 -> ../../ttyUSB0
> > |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port1 -> ../../ttyUSB1
> > |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port2 -> ../../ttyUSB2
> > |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port3 -> ../../ttyUSB3
> > |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port0 -> ../../ttyUSB8
> > |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port1 -> ../../ttyUSB9
> > |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port2 -> ../../ttyUSB10
> > |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port3 -> ../../ttyUSB11
> > |   `-- usb-Prolific_Technology_Inc._USB-Serial_Controller-if00-port0 -> ../../ttyUSB7
> > `-- by-path
> >    |-- pci-0000:00:1d.2-usb-0:ttyUSB7-port0 -> ../../ttyUSB7
> >    |-- pci-0000:00:1d.7-usb-0:ttyUSB0-port0 -> ../../ttyUSB0
> >    |-- pci-0000:00:1d.7-usb-0:ttyUSB1-port1 -> ../../ttyUSB1
> >    |-- pci-0000:00:1d.7-usb-0:ttyUSB10-port2 -> ../../ttyUSB10
> >    |-- pci-0000:00:1d.7-usb-0:ttyUSB11-port3 -> ../../ttyUSB11
> >    |-- pci-0000:00:1d.7-usb-0:ttyUSB2-port2 -> ../../ttyUSB2
> >    |-- pci-0000:00:1d.7-usb-0:ttyUSB3-port3 -> ../../ttyUSB3
> >    |-- pci-0000:00:1d.7-usb-0:ttyUSB8-port0 -> ../../ttyUSB8
> >    `-- pci-0000:00:1d.7-usb-0:ttyUSB9-port1 -> ../../ttyUSB9
> 
> You did replace /lib/udev/path_id? That should not happen.

oops, missed that, sorry.

Yes, much better now, see below.  This looks fine to me, nice job.

thanks,

greg k-h

$ tree /dev/serial/by-path/
/dev/serial/by-path/
|-- pci-0000:00:1d.2-usb-0:1.3:1.0-port0 -> ../../ttyUSB7
|-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port0 -> ../../ttyUSB4
|-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port1 -> ../../ttyUSB5
|-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port2 -> ../../ttyUSB6
|-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port0 -> ../../ttyUSB0
|-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port1 -> ../../ttyUSB1
|-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port2 -> ../../ttyUSB2
|-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port3 -> ../../ttyUSB3
|-- pci-0000:00:1d.7-usb-0:6.3:1.0-port0 -> ../../ttyUSB8
|-- pci-0000:00:1d.7-usb-0:6.3:1.0-port1 -> ../../ttyUSB9
|-- pci-0000:00:1d.7-usb-0:6.3:1.0-port2 -> ../../ttyUSB10
`-- pci-0000:00:1d.7-usb-0:6.3:1.0-port3 -> ../../ttyUSB11

Re: Udev rule for HSDPA modem

[Kay Sievers]

On Thu, Dec 4, 2008 at 01:40, Greg KH <greg@kroah.com> wrote:
> On Thu, Dec 04, 2008 at 01:12:27AM +0100, Kay Sievers wrote:
>> On Thu, Dec 4, 2008 at 01:04, Greg KH <greg@kroah.com> wrote:
>> > On Thu, Dec 04, 2008 at 12:54:31AM +0100, Kay Sievers wrote:
>> >> Yeah, it looks really strange with your devices. Why put people poetry
>> >> in the device strings? :)
>> >>
>> >> But it seems to work, which is great. Here is a new version of the
>> >> serial.rules and a /lib/udev/path_id which needs to be replaced.
>> >>
>> >> Can you try that again on your "collection"? :)
>> >
>> > Here you go.  I'm not so sure the "by-path" is that useful, as it has
>> > the ttyUSB number in the name, which can be different from boot-to-boot.
>> >
>> > How about putting the usb path in there and not truncate it?
>> >
>> > $ tree /dev/serial/
>> > /dev/serial/
>> > |-- by-id
>> > |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port0 -> ../../ttyUSB0
>> > |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port1 -> ../../ttyUSB1
>> > |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port2 -> ../../ttyUSB2
>> > |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port3 -> ../../ttyUSB3
>> > |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port0 -> ../../ttyUSB8
>> > |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port1 -> ../../ttyUSB9
>> > |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port2 -> ../../ttyUSB10
>> > |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-if00-port3 -> ../../ttyUSB11
>> > |   `-- usb-Prolific_Technology_Inc._USB-Serial_Controller-if00-port0 -> ../../ttyUSB7
>> > `-- by-path
>> >    |-- pci-0000:00:1d.2-usb-0:ttyUSB7-port0 -> ../../ttyUSB7
>> >    |-- pci-0000:00:1d.7-usb-0:ttyUSB0-port0 -> ../../ttyUSB0
>> >    |-- pci-0000:00:1d.7-usb-0:ttyUSB1-port1 -> ../../ttyUSB1
>> >    |-- pci-0000:00:1d.7-usb-0:ttyUSB10-port2 -> ../../ttyUSB10
>> >    |-- pci-0000:00:1d.7-usb-0:ttyUSB11-port3 -> ../../ttyUSB11
>> >    |-- pci-0000:00:1d.7-usb-0:ttyUSB2-port2 -> ../../ttyUSB2
>> >    |-- pci-0000:00:1d.7-usb-0:ttyUSB3-port3 -> ../../ttyUSB3
>> >    |-- pci-0000:00:1d.7-usb-0:ttyUSB8-port0 -> ../../ttyUSB8
>> >    `-- pci-0000:00:1d.7-usb-0:ttyUSB9-port1 -> ../../ttyUSB9
>>
>> You did replace /lib/udev/path_id? That should not happen.
>
> oops, missed that, sorry.
>
> Yes, much better now, see below.  This looks fine to me, nice job.
>
> $ tree /dev/serial/by-path/
> /dev/serial/by-path/
> |-- pci-0000:00:1d.2-usb-0:1.3:1.0-port0 -> ../../ttyUSB7
> |-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port0 -> ../../ttyUSB4
> |-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port1 -> ../../ttyUSB5
> |-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port2 -> ../../ttyUSB6
> |-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port0 -> ../../ttyUSB0
> |-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port1 -> ../../ttyUSB1
> |-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port2 -> ../../ttyUSB2
> |-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port3 -> ../../ttyUSB3
> |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port0 -> ../../ttyUSB8
> |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port1 -> ../../ttyUSB9
> |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port2 -> ../../ttyUSB10
> `-- pci-0000:00:1d.7-usb-0:6.3:1.0-port3 -> ../../ttyUSB11

Ah, nice. I've committed it. Thanks a lot for the tests!

Kay

Re: Udev rule for HSDPA modem

[Jar]

> On Wed, 2008-12-03 at 15:10 -0800, Greg KH wrote:
>> On Wed, Dec 03, 2008 at 04:11:29PM +0100, Kay Sievers wrote:
>> > On Wed, 2008-12-03 at 13:12 +0100, Kay Sievers wrote:
>> > > On Wed, Dec 3, 2008 at 10:27, Kay Sievers <kay.sievers@vrfy.org> wrote:
>> > > > On Wed, Dec 3, 2008 at 07:45, Greg KH <greg@kroah.com> wrote:
>> > > >> On Sun, Nov 30, 2008 at 06:21:11AM +0100, Kay Sievers wrote:
>> > > >>> On Sat, Nov 29, 2008 at 18:37, Greg KH <greg@kroah.com> wrote:
>> > > >>> > On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
>> > > >>> >> Greg KH wrote:
>> > > >>> >>> HAL contains a list of these modems and a mapping of each port to what
>> > > >>> >>> it does based on the specific device.
>> > > >>> >>> Try using that instead of udev specific rules for your accessed to the
>> > > >>> >>> modem, it will work much better.
>> > > >>> >>
>> > > >>> >> Thanks for your reply! Does HAL require that I have desktop installed,
>> this
>> > > >>> >> is my home "server" machine without X? Do you have any starting point
>> or
>> > > >>> >> where to learn more how to do this with HAL.
>> > > >>> >
>> > > >>> > I do not think HAL requires X.  Try asking on your distro mailing list
>> > > >>> > for how they have incorporated HAL into the releases you are using.
>> > > >>>
>> > > >>> It might get pretty complicated to use D-Bus/HAL for simple setups,
>> > > >>> and rather static configurations like this. NetworkManager handles
>> > > >>> that, and we will even get modem-probing soon, but in cases like this
>> > > >>> it might be easier to have a simple - not very flexible - but working
>> > > >>> solution.
>> > > >>>
>> > > >>> Maybe we can have an "index" sysfs file at the serial device, which
>> > > >>> carries the instance number, per usb device? This would allow us to
>> > > >>> create persistent links which do not depend on the kernel device
>> > > >>> enumeration across multiple device.
>> > > >>>
>> > > >>> We did the same for v4l devices recently:
>> > > >>>   http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;hS9a7555b31e65e66fb84c881d07d2bf18c974d0
>> > > >>>
>> > > >>> Greg, what do you think?
>> > > >>
>> > > >> Don't we already have something like this today (the "ports" on an
>> > > >> individual usb-serial device)?  Or do we just need to export that a bit
>> > > >> better?
>> > > >
>> > > > Yeah, maybe that works already. I don't have such a device.
>> > >
>> > > Ok, I found one. You mean "port_number", right? But unfortunately it
>> > > looks pretty useless in this case. :)
>> > >
>> > >   $ grep . /sys/bus/usb-serial/devices/*/port_number
>> > >   /sys/bus/usb-serial/devices/ttyUSB1/port_number:0
>> > >   /sys/bus/usb-serial/devices/ttyUSB2/port_number:0
>> > >
>> > > They would only be not "0" if the serial lines would be on the same
>> > > usb interface?
>> > >
>> > > We would need a per-device enumeration, but that's nothing the
>> > > usb-serial stuff knows/cares about if we have different usb
>> > > interfaces, right?
>> >
>> > Greg, do you have a usb multi-port serial card? Can you possibly give
>> > this a try, and show us "tree /dev/serial"?
>> >
>> > I have this here now for my "simple" devices:
>> >   /dev/serial
>> >   `-- by-id
>> >       |-- usb-067b_2303-serial-if00-port0 -> ../../ttyUSB0
>> >       |-- usb-HUAWEI_Technology_HUAWEI_Mobile-serial-if00-port0 -> ../../ttyUSB1
>> >       `-- usb-HUAWEI_Technology_HUAWEI_Mobile-serial-if01-port0 -> ../../ttyUSB2
>> >
>> > If we can make that work as expected, I'll look into by-path/, so we can
>> > have identical devices properly identified, if needed. Then we can check
>> > how we should finally name all that, and possibly add that stuff to the
>> > default rule set.
>>
>>
>> This looks good, here's the output using udev 133 and the rules and a
>> few usb-serial devices plugged into the system at the same time:
>>
>> $ tree /dev/serial/
>> /dev/serial/
>> `-- by-id
>>     |-- usb-Inside_Out_Networks_Edgeport
>>     |   |-- 4_04-01-006467-serial-if00-port0 -> ../../../ttyUSB0
>>     |   |-- 4_04-01-006467-serial-if00-port1 -> ../../../ttyUSB1
>>     |   |-- 4_04-01-006467-serial-if00-port2 -> ../../../ttyUSB2
>>     |   `-- 4_04-01-006467-serial-if00-port3 -> ../../../ttyUSB3
>>     |--
>> usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port0
>> -> ../../ttyUSB8
>>     |--
>> usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port1
>> -> ../../ttyUSB9
>>     |--
>> usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port2
>> -> ../../ttyUSB10
>>     |--
>> usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port3
>> -> ../../ttyUSB11
>>     |-- usb-Prolific_Technology_Inc._USB-Serial_Controller-serial-if00-port0 ->
>> ../../ttyUSB7
>>     |-- usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port0 ->
>> ../../ttyUSB4
>>     |-- usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port1 ->
>> ../../ttyUSB5
>>     `-- usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port2 ->
>> ../../ttyUSB6
>>
>> I'm not so sure about the long names, but it is unique :)
>
> Yeah, it looks really strange with your devices. Why put people poetry
> in the device strings? :)
>
> But it seems to work, which is great. Here is a new version of the
> serial.rules and a /lib/udev/path_id which needs to be replaced.
>
> Can you try that again on your "collection"? :)
>
> Thanks,
> Kay
> # do not edit this file, it will be overwritten on update
>
> ACTION!="add|change", GOTO="persistent_serial_end"
> SUBSYSTEM!="tty", GOTO="persistent_serial_end"
> KERNEL!="ttyUSB[0-9]*", GOTO="persistent_serial_end"
>
> SUBSYSTEMS="usb-serial", ENV{ID_PORT}="$attr{port_number}"
> ENV{ID_PORT}="", GOTO="persistent_serial_end"
>
> IMPORT="path_id"
> ENV{ID_PATH}="?*", SYMLINK+="serial/by-path/$env{ID_PATH}-port$env{ID_PORT}"
>
> IMPORT="usb_id --export"
> ENV{ID_SERIAL}="", GOTO="persistent_serial_end"
> SUBSYSTEMS="usb", ENV{ID_IFACE}="$attr{bInterfaceNumber}"
> ENV{ID_IFACE}="", GOTO="persistent_serial_end"
> SYMLINK+="serial/by-id/$env{ID_BUS}-$env{ID_SERIAL}-if$env{ID_IFACE}-port$env{ID_PORT}"
>
> LABEL="persistent_serial_end"
>

I can't test this right now, but doesn't quite understand what this will do. Does
this solve the problem where the ttyUSBx interface changes and make it always be the
same?

If I have e.g. ttyUSB1,ttyUSB2 and ttyUSB3 devices, what will be the symlink to
ttyUSB1 (used for pppd), which only interests? And how about the other thing, how to
trigger some wvdial connect script via udev at the same time the ttyUSB1 thing comes
up?


-- 
Best Regards, Jar

Re: Udev rule for HSDPA modem

[Kay Sievers]

On Thu, Dec 4, 2008 at 07:28, Jar <jar@pcuf.fi> wrote:
>> On Wed, 2008-12-03 at 15:10 -0800, Greg KH wrote:
>>> On Wed, Dec 03, 2008 at 04:11:29PM +0100, Kay Sievers wrote:
>>> > On Wed, 2008-12-03 at 13:12 +0100, Kay Sievers wrote:
>>> > > On Wed, Dec 3, 2008 at 10:27, Kay Sievers <kay.sievers@vrfy.org> wrote:
>>> > > > On Wed, Dec 3, 2008 at 07:45, Greg KH <greg@kroah.com> wrote:
>>> > > >> On Sun, Nov 30, 2008 at 06:21:11AM +0100, Kay Sievers wrote:
>>> > > >>> On Sat, Nov 29, 2008 at 18:37, Greg KH <greg@kroah.com> wrote:
>>> > > >>> > On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
>>> > > >>> >> Greg KH wrote:
>>> > > >>> >>> HAL contains a list of these modems and a mapping of each port to what
>>> > > >>> >>> it does based on the specific device.
>>> > > >>> >>> Try using that instead of udev specific rules for your accessed to the
>>> > > >>> >>> modem, it will work much better.
>>> > > >>> >>
>>> > > >>> >> Thanks for your reply! Does HAL require that I have desktop installed,
>>> this
>>> > > >>> >> is my home "server" machine without X? Do you have any starting point
>>> or
>>> > > >>> >> where to learn more how to do this with HAL.
>>> > > >>> >
>>> > > >>> > I do not think HAL requires X.  Try asking on your distro mailing list
>>> > > >>> > for how they have incorporated HAL into the releases you are using.
>>> > > >>>
>>> > > >>> It might get pretty complicated to use D-Bus/HAL for simple setups,
>>> > > >>> and rather static configurations like this. NetworkManager handles
>>> > > >>> that, and we will even get modem-probing soon, but in cases like this
>>> > > >>> it might be easier to have a simple - not very flexible - but working
>>> > > >>> solution.
>>> > > >>>
>>> > > >>> Maybe we can have an "index" sysfs file at the serial device, which
>>> > > >>> carries the instance number, per usb device? This would allow us to
>>> > > >>> create persistent links which do not depend on the kernel device
>>> > > >>> enumeration across multiple device.
>>> > > >>>
>>> > > >>> We did the same for v4l devices recently:
>>> > > >>>   http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;hS9a7555b31e65e66fb84c881d07d2bf18c974d0
>>> > > >>>
>>> > > >>> Greg, what do you think?
>>> > > >>
>>> > > >> Don't we already have something like this today (the "ports" on an
>>> > > >> individual usb-serial device)?  Or do we just need to export that a bit
>>> > > >> better?
>>> > > >
>>> > > > Yeah, maybe that works already. I don't have such a device.
>>> > >
>>> > > Ok, I found one. You mean "port_number", right? But unfortunately it
>>> > > looks pretty useless in this case. :)
>>> > >
>>> > >   $ grep . /sys/bus/usb-serial/devices/*/port_number
>>> > >   /sys/bus/usb-serial/devices/ttyUSB1/port_number:0
>>> > >   /sys/bus/usb-serial/devices/ttyUSB2/port_number:0
>>> > >
>>> > > They would only be not "0" if the serial lines would be on the same
>>> > > usb interface?
>>> > >
>>> > > We would need a per-device enumeration, but that's nothing the
>>> > > usb-serial stuff knows/cares about if we have different usb
>>> > > interfaces, right?
>>> >
>>> > Greg, do you have a usb multi-port serial card? Can you possibly give
>>> > this a try, and show us "tree /dev/serial"?
>>> >
>>> > I have this here now for my "simple" devices:
>>> >   /dev/serial
>>> >   `-- by-id
>>> >       |-- usb-067b_2303-serial-if00-port0 -> ../../ttyUSB0
>>> >       |-- usb-HUAWEI_Technology_HUAWEI_Mobile-serial-if00-port0 -> ../../ttyUSB1
>>> >       `-- usb-HUAWEI_Technology_HUAWEI_Mobile-serial-if01-port0 -> ../../ttyUSB2
>>> >
>>> > If we can make that work as expected, I'll look into by-path/, so we can
>>> > have identical devices properly identified, if needed. Then we can check
>>> > how we should finally name all that, and possibly add that stuff to the
>>> > default rule set.
>>>
>>>
>>> This looks good, here's the output using udev 133 and the rules and a
>>> few usb-serial devices plugged into the system at the same time:
>>>
>>> $ tree /dev/serial/
>>> /dev/serial/
>>> `-- by-id
>>>     |-- usb-Inside_Out_Networks_Edgeport
>>>     |   |-- 4_04-01-006467-serial-if00-port0 -> ../../../ttyUSB0
>>>     |   |-- 4_04-01-006467-serial-if00-port1 -> ../../../ttyUSB1
>>>     |   |-- 4_04-01-006467-serial-if00-port2 -> ../../../ttyUSB2
>>>     |   `-- 4_04-01-006467-serial-if00-port3 -> ../../../ttyUSB3
>>>     |--
>>> usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port0
>>> -> ../../ttyUSB8
>>>     |--
>>> usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port1
>>> -> ../../ttyUSB9
>>>     |--
>>> usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port2
>>> -> ../../ttyUSB10
>>>     |--
>>> usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port3
>>> -> ../../ttyUSB11
>>>     |-- usb-Prolific_Technology_Inc._USB-Serial_Controller-serial-if00-port0 ->
>>> ../../ttyUSB7
>>>     |-- usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port0 ->
>>> ../../ttyUSB4
>>>     |-- usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port1 ->
>>> ../../ttyUSB5
>>>     `-- usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port2 ->
>>> ../../ttyUSB6
>>>
>>> I'm not so sure about the long names, but it is unique :)
>>
>> Yeah, it looks really strange with your devices. Why put people poetry
>> in the device strings? :)
>>
>> But it seems to work, which is great. Here is a new version of the
>> serial.rules and a /lib/udev/path_id which needs to be replaced.
>>
>> Can you try that again on your "collection"? :)
>>
>> Thanks,
>> Kay
>> # do not edit this file, it will be overwritten on update
>>
>> ACTION!="add|change", GOTO="persistent_serial_end"
>> SUBSYSTEM!="tty", GOTO="persistent_serial_end"
>> KERNEL!="ttyUSB[0-9]*", GOTO="persistent_serial_end"
>>
>> SUBSYSTEMS="usb-serial", ENV{ID_PORT}="$attr{port_number}"
>> ENV{ID_PORT}="", GOTO="persistent_serial_end"
>>
>> IMPORT="path_id"
>> ENV{ID_PATH}="?*", SYMLINK+="serial/by-path/$env{ID_PATH}-port$env{ID_PORT}"
>>
>> IMPORT="usb_id --export"
>> ENV{ID_SERIAL}="", GOTO="persistent_serial_end"
>> SUBSYSTEMS="usb", ENV{ID_IFACE}="$attr{bInterfaceNumber}"
>> ENV{ID_IFACE}="", GOTO="persistent_serial_end"
>> SYMLINK+="serial/by-id/$env{ID_BUS}-$env{ID_SERIAL}-if$env{ID_IFACE}-port$env{ID_PORT}"
>>
>> LABEL="persistent_serial_end"
>
> I can't test this right now, but doesn't quite understand what this will do. Does
> this solve the problem where the ttyUSBx interface changes and make it always be the
> same?
>
> If I have e.g. ttyUSB1,ttyUSB2 and ttyUSB3 devices, what will be the symlink to
> ttyUSB1 (used for pppd), which only interests?

If you have different devices, all links in /dev/serial/by-id/ will
stay the same, regardless of the order, or the USB hub/port they are
plugged in. If you have identical devices, without any serial number,
only the controller/hub/port number can be used to distinguish them.
The /dev/serial/by-id/ links will overwrite each other for identical
devices, and /dev/serial/by-path/ must be used.

> And how about the other thing, how to
> trigger some wvdial connect script via udev at the same time the
> ttyUSB1 thing comes up?

You can match on properties of the device, or even the link name
itself with SYMLINK="serial/by-..." with udev rules, that come after
the 60-*.rules. These rules can trigger anything you need.

Kay

Re: Udev rule for HSDPA modem

[Jar]

>> I can't test this right now, but doesn't quite understand what this will do. Does
>> this solve the problem where the ttyUSBx interface changes and make it always be
>> the
>> same?
>>
>> If I have e.g. ttyUSB1,ttyUSB2 and ttyUSB3 devices, what will be the symlink to
>> ttyUSB1 (used for pppd), which only interests?
>
> If you have different devices, all links in /dev/serial/by-id/ will
> stay the same, regardless of the order, or the USB hub/port they are
> plugged in. If you have identical devices, without any serial number,
> only the controller/hub/port number can be used to distinguish them.
> The /dev/serial/by-id/ links will overwrite each other for identical
> devices, and /dev/serial/by-path/ must be used.
>
>> And how about the other thing, how to
>> trigger some wvdial connect script via udev at the same time the
>> ttyUSB1 thing comes up?
>
> You can match on properties of the device, or even the link name
> itself with SYMLINK="serial/by-..." with udev rules, that come after
> the 60-*.rules. These rules can trigger anything you need.
>
> Kay


OK, thanks, I will try these when I have time. My udev is version udev-118-1.fc8,
any idea if this works with it?


-- 
Best Regards, Jar

Re: Udev rule for HSDPA modem

[Karl O. Pinc]

[-- Attachment #1: Type: text/plain, Size: 9097 bytes --]


On 12/04/2008 01:23:53 AM, Kay Sievers wrote:
> On Thu, Dec 4, 2008 at 07:28, Jar <jar@pcuf.fi> wrote:
> >> On Wed, 2008-12-03 at 15:10 -0800, Greg KH wrote:
> >>> On Wed, Dec 03, 2008 at 04:11:29PM +0100, Kay Sievers wrote:
> >>> > On Wed, 2008-12-03 at 13:12 +0100, Kay Sievers wrote:
> >>> > > On Wed, Dec 3, 2008 at 10:27, Kay Sievers
> <kay.sievers@vrfy.org> wrote:
> >>> > > > On Wed, Dec 3, 2008 at 07:45, Greg KH <greg@kroah.com>
> wrote:
> >>> > > >> On Sun, Nov 30, 2008 at 06:21:11AM +0100, Kay Sievers
> wrote:
> >>> > > >>> On Sat, Nov 29, 2008 at 18:37, Greg KH <greg@kroah.com>
> wrote:
> >>> > > >>> > On Sat, Nov 29, 2008 at 10:00:59AM +0200, Jar wrote:
> >>> > > >>> >> Greg KH wrote:
> >>> > > >>> >>> HAL contains a list of these modems and a mapping of
> each port to what
> >>> > > >>> >>> it does based on the specific device.
> >>> > > >>> >>> Try using that instead of udev specific rules for your
> accessed to the
> >>> > > >>> >>> modem, it will work much better.
> >>> > > >>> >>
> >>> > > >>> >> Thanks for your reply! Does HAL require that I have
> desktop installed,
> >>> this
> >>> > > >>> >> is my home "server" machine without X? Do you have any
> starting point
> >>> or
> >>> > > >>> >> where to learn more how to do this with HAL.
> >>> > > >>> >
> >>> > > >>> > I do not think HAL requires X.  Try asking on your
> distro mailing list
> >>> > > >>> > for how they have incorporated HAL into the releases you
> are using.
> >>> > > >>>
> >>> > > >>> It might get pretty complicated to use D-Bus/HAL for
> simple setups,
> >>> > > >>> and rather static configurations like this. NetworkManager
> handles
> >>> > > >>> that, and we will even get modem-probing soon, but in
> cases like this
> >>> > > >>> it might be easier to have a simple - not very flexible -
> but working
> >>> > > >>> solution.
> >>> > > >>>
> >>> > > >>> Maybe we can have an "index" sysfs file at the serial
> device, which
> >>> > > >>> carries the instance number, per usb device? This would
> allow us to
> >>> > > >>> create persistent links which do not depend on the kernel
> device
> >>> > > >>> enumeration across multiple device.
> >>> > > >>>
> >>> > > >>> We did the same for v4l devices recently:
> >>> > > >>>    
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=539a7555b31e65e66fb84c881d07d2bf18c974d0
> >>> > > >>>
> >>> > > >>> Greg, what do you think?
> >>> > > >>
> >>> > > >> Don't we already have something like this today (the
> "ports" on an
> >>> > > >> individual usb-serial device)?  Or do we just need to
> export that a bit
> >>> > > >> better?
> >>> > > >
> >>> > > > Yeah, maybe that works already. I don't have such a device.
> >>> > >
> >>> > > Ok, I found one. You mean "port_number", right? But
> unfortunately it
> >>> > > looks pretty useless in this case. :)
> >>> > >
> >>> > >   $ grep . /sys/bus/usb-serial/devices/*/port_number
> >>> > >   /sys/bus/usb-serial/devices/ttyUSB1/port_number:0
> >>> > >   /sys/bus/usb-serial/devices/ttyUSB2/port_number:0
> >>> > >
> >>> > > They would only be not "0" if the serial lines would be on the
> same
> >>> > > usb interface?
> >>> > >
> >>> > > We would need a per-device enumeration, but that's nothing the
> >>> > > usb-serial stuff knows/cares about if we have different usb
> >>> > > interfaces, right?
> >>> >
> >>> > Greg, do you have a usb multi-port serial card? Can you possibly
> give
> >>> > this a try, and show us "tree /dev/serial"?
> >>> >
> >>> > I have this here now for my "simple" devices:
> >>> >   /dev/serial
> >>> >   `-- by-id
> >>> >       |-- usb-067b_2303-serial-if00-port0 -> ../../ttyUSB0
> >>> >       |-- usb-HUAWEI_Technology_HUAWEI_Mobile-serial-if00-port0
> -> ../../ttyUSB1
> >>> >       `-- usb-HUAWEI_Technology_HUAWEI_Mobile-serial-if01-port0
> -> ../../ttyUSB2
> >>> >
> >>> > If we can make that work as expected, I'll look into by-path/,
> so we can
> >>> > have identical devices properly identified, if needed. Then we
> can check
> >>> > how we should finally name all that, and possibly add that stuff
> to the
> >>> > default rule set.
> >>>
> >>>
> >>> This looks good, here's the output using udev 133 and the rules
> and a
> >>> few usb-serial devices plugged into the system at the same time:
> >>>
> >>> $ tree /dev/serial/
> >>> /dev/serial/
> >>> `-- by-id
> >>>     |-- usb-Inside_Out_Networks_Edgeport
> >>>     |   |-- 4_04-01-006467-serial-if00-port0 -> ../../../ttyUSB0
> >>>     |   |-- 4_04-01-006467-serial-if00-port1 -> ../../../ttyUSB1
> >>>     |   |-- 4_04-01-006467-serial-if00-port2 -> ../../../ttyUSB2
> >>>     |   `-- 4_04-01-006467-serial-if00-port3 -> ../../../ttyUSB3
> >>>     |--
> >>>  
> usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port0
> >>> -> ../../ttyUSB8
> >>>     |--
> >>>  
> usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port1
> >>> -> ../../ttyUSB9
> >>>     |--
> >>>  
> usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port2
> >>> -> ../../ttyUSB10
> >>>     |--
> >>>  
> usb-Keyspan__a_division_of_InnoSys_Inc._USB_4-port_Serial_Adapter-serial-if00-port3
> >>> -> ../../ttyUSB11
> >>>     |--  
> usb-Prolific_Technology_Inc._USB-Serial_Controller-serial-if00-port0
> ->
> >>> ../../ttyUSB7
> >>>     |--  
> usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port0
> ->
> >>> ../../ttyUSB4
> >>>     |--  
> usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port1
> ->
> >>> ../../ttyUSB5
> >>>     `--  
> usb-Sierra_Wireless__Incorporated_AirCard-serial-if00-port2
> ->
> >>> ../../ttyUSB6
> >>>
> >>> I'm not so sure about the long names, but it is unique :)
> >>
> >> Yeah, it looks really strange with your devices. Why put people
> poetry
> >> in the device strings? :)
> >>
> >> But it seems to work, which is great. Here is a new version of the
> >> serial.rules and a /lib/udev/path_id which needs to be replaced.
> >>
> >> Can you try that again on your "collection"? :)
> >>
> >> Thanks,
> >> Kay
> >> # do not edit this file, it will be overwritten on update
> >>
> >> ACTION!="add|change", GOTO="persistent_serial_end"
> >> SUBSYSTEM!="tty", GOTO="persistent_serial_end"
> >> KERNEL!="ttyUSB[0-9]*", GOTO="persistent_serial_end"
> >>
> >> SUBSYSTEMS=="usb-serial", ENV{ID_PORT}="$attr{port_number}"
> >> ENV{ID_PORT}=="", GOTO="persistent_serial_end"
> >>
> >> IMPORT="path_id"
> >> ENV{ID_PATH}=="?*",  
> SYMLINK+="serial/by-path/$env{ID_PATH}-port$env{ID_PORT}"
> >>
> >> IMPORT="usb_id --export"
> >> ENV{ID_SERIAL}=="", GOTO="persistent_serial_end"
> >> SUBSYSTEMS=="usb", ENV{ID_IFACE}="$attr{bInterfaceNumber}"
> >> ENV{ID_IFACE}=="", GOTO="persistent_serial_end"
> >>  
> SYMLINK+="serial/by-id/$env{ID_BUS}-$env{ID_SERIAL}-if$env{ID_IFACE}-port$env{ID_PORT}"
> >>
> >> LABEL="persistent_serial_end"
> >
> > I can't test this right now, but doesn't quite understand what this
> will do. Does
> > this solve the problem where the ttyUSBx interface changes and make
> it always be the
> > same?
> >
> > If I have e.g. ttyUSB1,ttyUSB2 and ttyUSB3 devices, what will be the
> symlink to
> > ttyUSB1 (used for pppd), which only interests?
> 
> If you have different devices, all links in /dev/serial/by-id/ will
> stay the same, regardless of the order, or the USB hub/port they are
> plugged in. If you have identical devices, without any serial number,
> only the controller/hub/port number can be used to distinguish them.
> The /dev/serial/by-id/ links will overwrite each other for identical
> devices, and /dev/serial/by-path/ must be used.

I think what the Digi Edgeport 4/16 needs is the same rule set, but
with the serial number also included in the name.  This is because
it has an internal hub with 8 endpoints, each endpoint driving 2
serial ports (io_ti), and my understanding is that the ports on the
internal hub may not be discovered in the same order every time.
However, each internal endpoint does have it's own serial
number.  If that showed in the name then there'd be no
problem.

Of course I could be completely misunderstanding.

Anyway, I can't really hack on it because the
60-persistent-serial.rules don't seem to work
on udev 115. :-( It seems they should....)

I'm now running:
Linux 2.6.28-rc7 (built myself)
udev 115
Debian etch

Attached is a udevinfo -a on ttyUSB-0
Also attached is /var/log/messages and dmesg
recording what happens when the device is
plugged in.  I turned on verbosity in the kernel.

I found that I needed to "modprobe usbserial" manually
before the ttyUSB* devices would be created.
Should I be reporting this to somebody?  Who?

(Although the device has 16 ports, after one unplug/plug
cycle I found only 14 ttyUSB devices.)

Thanks for your time.

Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein

[-- Attachment #2: edgeport416 --]
[-- Type: text/plain, Size: 5395 bytes --]


Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/class/tty/ttyUSB0':
    KERNEL=="ttyUSB0"
    SUBSYSTEM=="tty"
    DRIVER==""
    ATTR{dev}=="188:0"

  looking at parent device '/devices/pci0000:00/0000:00:1a.1/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1:1.0/ttyUSB0':
    KERNELS=="ttyUSB0"
    SUBSYSTEMS=="usb-serial"
    DRIVERS=="edgeport_ti_2"
    ATTRS{uart_mode}=="0"
    ATTRS{port_number}=="0"

  looking at parent device '/devices/pci0000:00/0000:00:1a.1/usb2/2-1/2-1.1/2-1.1.1/2-1.1.1:1.0':
    KERNELS=="2-1.1.1:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="io_ti"
    ATTRS{bInterfaceNumber}=="00"
    ATTRS{bAlternateSetting}==" 0"
    ATTRS{bNumEndpoints}=="05"
    ATTRS{bInterfaceClass}=="ff"
    ATTRS{bInterfaceSubClass}=="00"
    ATTRS{bInterfaceProtocol}=="ff"
    ATTRS{modalias}=="usb:v1608p0247d0001dcFFdsc00dpFFicFFisc00ipFF"
    ATTRS{supports_autosuspend}=="0"

  looking at parent device '/devices/pci0000:00/0000:00:1a.1/usb2/2-1/2-1.1/2-1.1.1':
    KERNELS=="2-1.1.1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{dev}=="189:192"
    ATTRS{configuration}==""
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bmAttributes}=="e0"
    ATTRS{bMaxPower}=="  0mA"
    ATTRS{urbnum}=="33"
    ATTRS{idVendor}=="1608"
    ATTRS{idProduct}=="0247"
    ATTRS{bcdDevice}=="0001"
    ATTRS{bDeviceClass}=="ff"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceProtocol}=="ff"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bMaxPacketSize0}=="8"
    ATTRS{speed}=="12"
    ATTRS{busnum}=="2"
    ATTRS{devnum}=="65"
    ATTRS{version}==" 1.10"
    ATTRS{maxchild}=="0"
    ATTRS{quirks}=="0x0"
    ATTRS{authorized}=="1"
    ATTRS{manufacturer}=="Digi International"
    ATTRS{product}=="Edgeport/416"
    ATTRS{serial}=="V70008669-0"

  looking at parent device '/devices/pci0000:00/0000:00:1a.1/usb2/2-1/2-1.1':
    KERNELS=="2-1.1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{dev}=="189:190"
    ATTRS{configuration}==""
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bmAttributes}=="e0"
    ATTRS{bMaxPower}=="  0mA"
    ATTRS{urbnum}=="54"
    ATTRS{idVendor}=="1608"
    ATTRS{idProduct}=="02c7"
    ATTRS{bcdDevice}=="0151"
    ATTRS{bDeviceClass}=="09"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bMaxPacketSize0}=="8"
    ATTRS{speed}=="12"
    ATTRS{busnum}=="2"
    ATTRS{devnum}=="63"
    ATTRS{version}==" 1.10"
    ATTRS{maxchild}=="4"
    ATTRS{quirks}=="0x0"
    ATTRS{authorized}=="1"

  looking at parent device '/devices/pci0000:00/0000:00:1a.1/usb2/2-1':
    KERNELS=="2-1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{dev}=="189:189"
    ATTRS{configuration}==""
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bmAttributes}=="e0"
    ATTRS{bMaxPower}=="  2mA"
    ATTRS{urbnum}=="58"
    ATTRS{idVendor}=="1608"
    ATTRS{idProduct}=="0184"
    ATTRS{bcdDevice}=="0100"
    ATTRS{bDeviceClass}=="09"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{speed}=="12"
    ATTRS{busnum}=="2"
    ATTRS{devnum}=="62"
    ATTRS{version}==" 2.00"
    ATTRS{maxchild}=="6"
    ATTRS{quirks}=="0x0"
    ATTRS{authorized}=="1"

  looking at parent device '/devices/pci0000:00/0000:00:1a.1/usb2':
    KERNELS=="usb2"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{dev}=="189:128"
    ATTRS{configuration}==""
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bmAttributes}=="e0"
    ATTRS{bMaxPower}=="  0mA"
    ATTRS{urbnum}=="154"
    ATTRS{idVendor}=="1d6b"
    ATTRS{idProduct}=="0001"
    ATTRS{bcdDevice}=="0206"
    ATTRS{bDeviceClass}=="09"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{speed}=="12"
    ATTRS{busnum}=="2"
    ATTRS{devnum}=="1"
    ATTRS{version}==" 1.10"
    ATTRS{maxchild}=="2"
    ATTRS{quirks}=="0x0"
    ATTRS{authorized}=="1"
    ATTRS{manufacturer}=="Linux 2.6.28-rc7 uhci_hcd"
    ATTRS{product}=="UHCI Host Controller"
    ATTRS{serial}=="0000:00:1a.1"
    ATTRS{authorized_default}=="1"

  looking at parent device '/devices/pci0000:00/0000:00:1a.1':
    KERNELS=="0000:00:1a.1"
    SUBSYSTEMS=="pci"
    DRIVERS=="uhci_hcd"
    ATTRS{vendor}=="0x8086"
    ATTRS{device}=="0x2938"
    ATTRS{subsystem_vendor}=="0x1043"
    ATTRS{subsystem_device}=="0x8277"
    ATTRS{class}=="0x0c0300"
    ATTRS{irq}=="21"
    ATTRS{local_cpus}=="00000003"
    ATTRS{local_cpulist}=="0-1"
    ATTRS{modalias}=="pci:v00008086d00002938sv00001043sd00008277bc0Csc03i00"
    ATTRS{numa_node}=="0"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}==""

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""
    ATTRS{uevent}==""



[-- Attachment #3: log --]
[-- Type: text/plain, Size: 19316 bytes --]

Dec  4 08:43:46 allen kernel: usb 2-1: new full speed USB device using uhci_hcd and address 52
Dec  4 08:43:47 allen kernel: usb 2-1: configuration #1 chosen from 1 choice
Dec  4 08:43:47 allen kernel: hub 2-1:1.0: USB hub found
Dec  4 08:43:47 allen kernel: hub 2-1:1.0: 6 ports detected
Dec  4 08:43:47 allen kernel: usb 2-1: New USB device found, idVendor=1608, idProduct=0184
Dec  4 08:43:47 allen kernel: usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Dec  4 08:43:51 allen kernel: usb 2-1.1: new full speed USB device using uhci_hcd and address 53
Dec  4 08:43:51 allen kernel: usb 2-1.1: configuration #1 chosen from 1 choice
Dec  4 08:43:51 allen kernel: hub 2-1.1:1.0: USB hub found
Dec  4 08:43:51 allen kernel: hub 2-1.1:1.0: 4 ports detected
Dec  4 08:43:51 allen kernel: usb 2-1.1: New USB device found, idVendor=1608, idProduct=02c7
Dec  4 08:43:51 allen kernel: usb 2-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Dec  4 08:43:52 allen kernel: usb 2-1.2: new full speed USB device using uhci_hcd and address 54
Dec  4 08:43:52 allen kernel: usb 2-1.2: configuration #1 chosen from 1 choice
Dec  4 08:43:52 allen kernel: hub 2-1.2:1.0: USB hub found
Dec  4 08:43:52 allen kernel: hub 2-1.2:1.0: 4 ports detected
Dec  4 08:43:52 allen kernel: usb 2-1.2: New USB device found, idVendor=1608, idProduct=02c7
Dec  4 08:43:52 allen kernel: usb 2-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Dec  4 08:43:52 allen kernel: usb 2-1.1.1: new full speed USB device using uhci_hcd and address 55
Dec  4 08:43:52 allen kernel: usb 2-1.1.1: configuration #1 chosen from 1 choice
Dec  4 08:43:52 allen kernel: io_ti 2-1.1.1:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:43:52 allen kernel: usb 2-1.1.1: Edgeport TI 2 port adapter converter now attached to ttyUSB0
Dec  4 08:43:52 allen kernel: usb 2-1.1.1: Edgeport TI 2 port adapter converter now attached to ttyUSB1
Dec  4 08:43:52 allen kernel: usb 2-1.1.1: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:43:52 allen kernel: usb 2-1.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:43:52 allen kernel: usb 2-1.1.1: Product: Edgeport/416
Dec  4 08:43:52 allen kernel: usb 2-1.1.1: Manufacturer: Digi International
Dec  4 08:43:52 allen kernel: usb 2-1.1.1: SerialNumber: V70008669-0
Dec  4 08:43:52 allen kernel: usb 2-1.1.2: new full speed USB device using uhci_hcd and address 56
Dec  4 08:43:53 allen kernel: usb 2-1.1.2: configuration #1 chosen from 1 choice
Dec  4 08:43:53 allen kernel: io_ti 2-1.1.2:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:43:53 allen kernel: usb 2-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB2
Dec  4 08:43:53 allen kernel: usb 2-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB3
Dec  4 08:43:53 allen kernel: usb 2-1.1.2: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:43:53 allen kernel: usb 2-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:43:53 allen kernel: usb 2-1.1.2: Product: Edgeport/416
Dec  4 08:43:53 allen kernel: usb 2-1.1.2: Manufacturer: Digi International
Dec  4 08:43:53 allen kernel: usb 2-1.1.2: SerialNumber: V70008669-1
Dec  4 08:43:53 allen kernel: usb 2-1.1.3: new full speed USB device using uhci_hcd and address 57
Dec  4 08:43:53 allen kernel: usb 2-1.1.3: configuration #1 chosen from 1 choice
Dec  4 08:43:53 allen kernel: io_ti 2-1.1.3:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:43:53 allen kernel: usb 2-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB4
Dec  4 08:43:53 allen kernel: usb 2-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB5
Dec  4 08:43:53 allen kernel: usb 2-1.1.3: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:43:53 allen kernel: usb 2-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:43:53 allen kernel: usb 2-1.1.3: Product: Edgeport/416
Dec  4 08:43:53 allen kernel: usb 2-1.1.3: Manufacturer: Digi International
Dec  4 08:43:53 allen kernel: usb 2-1.1.3: SerialNumber: V70008669-2
Dec  4 08:43:53 allen kernel: usb 2-1.1.4: new full speed USB device using uhci_hcd and address 58
Dec  4 08:43:54 allen kernel: usb 2-1.1.4: configuration #1 chosen from 1 choice
Dec  4 08:43:54 allen kernel: io_ti 2-1.1.4:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:43:54 allen kernel: usb 2-1.1.4: Edgeport TI 2 port adapter converter now attached to ttyUSB6
Dec  4 08:43:54 allen kernel: usb 2-1.1.4: Edgeport TI 2 port adapter converter now attached to ttyUSB7
Dec  4 08:43:54 allen kernel: usb 2-1.1.4: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:43:54 allen kernel: usb 2-1.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:43:54 allen kernel: usb 2-1.1.4: Product: Edgeport/416
Dec  4 08:43:54 allen kernel: usb 2-1.1.4: Manufacturer: Digi International
Dec  4 08:43:54 allen kernel: usb 2-1.1.4: SerialNumber: V70008669-3
Dec  4 08:43:54 allen kernel: usb 2-1.2.1: new full speed USB device using uhci_hcd and address 59
Dec  4 08:43:54 allen kernel: usb 2-1.2.1: configuration #1 chosen from 1 choice
Dec  4 08:43:54 allen kernel: io_ti 2-1.2.1:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:43:54 allen kernel: usb 2-1.2.1: Edgeport TI 2 port adapter converter now attached to ttyUSB8
Dec  4 08:43:54 allen kernel: usb 2-1.2.1: Edgeport TI 2 port adapter converter now attached to ttyUSB9
Dec  4 08:43:54 allen kernel: usb 2-1.2.1: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:43:54 allen kernel: usb 2-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:43:54 allen kernel: usb 2-1.2.1: Product: Edgeport/416
Dec  4 08:43:54 allen kernel: usb 2-1.2.1: Manufacturer: Digi International
Dec  4 08:43:54 allen kernel: usb 2-1.2.1: SerialNumber: V70008669-4
Dec  4 08:43:54 allen kernel: usb 2-1.2.2: new full speed USB device using uhci_hcd and address 60
Dec  4 08:43:55 allen kernel: usb 2-1.2.2: configuration #1 chosen from 1 choice
Dec  4 08:43:55 allen kernel: io_ti 2-1.2.2:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:43:55 allen kernel: usb 2-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB10
Dec  4 08:43:55 allen kernel: usb 2-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB11
Dec  4 08:43:55 allen kernel: usb 2-1.2.2: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:43:55 allen kernel: usb 2-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:43:55 allen kernel: usb 2-1.2.2: Product: Edgeport/416
Dec  4 08:43:55 allen kernel: usb 2-1.2.2: Manufacturer: Digi International
Dec  4 08:43:55 allen kernel: usb 2-1.2.2: SerialNumber: V70008669-5
Dec  4 08:43:55 allen kernel: usb 2-1.2.4: new full speed USB device using uhci_hcd and address 61
Dec  4 08:43:55 allen kernel: usb 2-1.2.4: configuration #1 chosen from 1 choice
Dec  4 08:43:55 allen kernel: io_ti 2-1.2.4:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:43:55 allen kernel: usb 2-1.2.4: Edgeport TI 2 port adapter converter now attached to ttyUSB12
Dec  4 08:43:55 allen kernel: usb 2-1.2.4: Edgeport TI 2 port adapter converter now attached to ttyUSB13
Dec  4 08:43:55 allen kernel: usb 2-1.2.4: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:43:55 allen kernel: usb 2-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:43:55 allen kernel: usb 2-1.2.4: Product: Edgeport/416
Dec  4 08:43:55 allen kernel: usb 2-1.2.4: Manufacturer: Digi International
Dec  4 08:43:55 allen kernel: usb 2-1.2.4: SerialNumber: V70008669-7
Dec  4 08:45:49 allen kernel: usb 2-1: USB disconnect, address 52
Dec  4 08:45:49 allen kernel: usb 2-1.1: USB disconnect, address 53
Dec  4 08:45:49 allen kernel: usb 2-1.1.1: USB disconnect, address 55
Dec  4 08:45:49 allen kernel: edgeport_ti_2 ttyUSB0: Edgeport TI 2 port adapter converter now disconnected from ttyUSB0
Dec  4 08:45:49 allen kernel: edgeport_ti_2 ttyUSB1: Edgeport TI 2 port adapter converter now disconnected from ttyUSB1
Dec  4 08:45:49 allen kernel: io_ti 2-1.1.1:1.0: device disconnected
Dec  4 08:45:49 allen kernel: usb 2-1.1.2: USB disconnect, address 56
Dec  4 08:45:49 allen kernel: edgeport_ti_2 ttyUSB2: Edgeport TI 2 port adapter converter now disconnected from ttyUSB2
Dec  4 08:45:49 allen kernel: edgeport_ti_2 ttyUSB3: Edgeport TI 2 port adapter converter now disconnected from ttyUSB3
Dec  4 08:45:49 allen kernel: io_ti 2-1.1.2:1.0: device disconnected
Dec  4 08:45:49 allen kernel: usb 2-1.1.3: USB disconnect, address 57
Dec  4 08:45:49 allen kernel: edgeport_ti_2 ttyUSB4: Edgeport TI 2 port adapter converter now disconnected from ttyUSB4
Dec  4 08:45:49 allen kernel: edgeport_ti_2 ttyUSB5: Edgeport TI 2 port adapter converter now disconnected from ttyUSB5
Dec  4 08:45:49 allen kernel: io_ti 2-1.1.3:1.0: device disconnected
Dec  4 08:45:49 allen kernel: usb 2-1.1.4: USB disconnect, address 58
Dec  4 08:45:49 allen kernel: edgeport_ti_2 ttyUSB6: Edgeport TI 2 port adapter converter now disconnected from ttyUSB6
Dec  4 08:45:49 allen kernel: edgeport_ti_2 ttyUSB7: Edgeport TI 2 port adapter converter now disconnected from ttyUSB7
Dec  4 08:45:49 allen kernel: io_ti 2-1.1.4:1.0: device disconnected
Dec  4 08:45:49 allen kernel: usb 2-1.2: USB disconnect, address 54
Dec  4 08:45:49 allen kernel: usb 2-1.2.1: USB disconnect, address 59
Dec  4 08:45:49 allen kernel: edgeport_ti_2 ttyUSB8: Edgeport TI 2 port adapter converter now disconnected from ttyUSB8
Dec  4 08:45:49 allen kernel: edgeport_ti_2 ttyUSB9: Edgeport TI 2 port adapter converter now disconnected from ttyUSB9
Dec  4 08:45:49 allen kernel: io_ti 2-1.2.1:1.0: device disconnected
Dec  4 08:45:49 allen kernel: usb 2-1.2.2: USB disconnect, address 60
Dec  4 08:45:49 allen kernel: edgeport_ti_2 ttyUSB10: Edgeport TI 2 port adapter converter now disconnected from ttyUSB10
Dec  4 08:45:49 allen kernel: edgeport_ti_2 ttyUSB11: Edgeport TI 2 port adapter converter now disconnected from ttyUSB11
Dec  4 08:45:49 allen kernel: io_ti 2-1.2.2:1.0: device disconnected
Dec  4 08:45:49 allen kernel: usb 2-1.2.4: USB disconnect, address 61
Dec  4 08:45:49 allen kernel: edgeport_ti_2 ttyUSB12: Edgeport TI 2 port adapter converter now disconnected from ttyUSB12
Dec  4 08:45:49 allen kernel: edgeport_ti_2 ttyUSB13: Edgeport TI 2 port adapter converter now disconnected from ttyUSB13
Dec  4 08:45:49 allen kernel: io_ti 2-1.2.4:1.0: device disconnected
Dec  4 08:45:51 allen kernel: usb 2-1: new full speed USB device using uhci_hcd and address 62
Dec  4 08:45:51 allen kernel: usb 2-1: configuration #1 chosen from 1 choice
Dec  4 08:45:51 allen kernel: hub 2-1:1.0: USB hub found
Dec  4 08:45:51 allen kernel: hub 2-1:1.0: 6 ports detected
Dec  4 08:45:51 allen kernel: usb 2-1: New USB device found, idVendor=1608, idProduct=0184
Dec  4 08:45:51 allen kernel: usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Dec  4 08:45:56 allen kernel: usb 2-1.1: new full speed USB device using uhci_hcd and address 63
Dec  4 08:45:56 allen kernel: usb 2-1.1: configuration #1 chosen from 1 choice
Dec  4 08:45:56 allen kernel: hub 2-1.1:1.0: USB hub found
Dec  4 08:45:56 allen kernel: hub 2-1.1:1.0: 4 ports detected
Dec  4 08:45:56 allen kernel: usb 2-1.1: New USB device found, idVendor=1608, idProduct=02c7
Dec  4 08:45:56 allen kernel: usb 2-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Dec  4 08:45:56 allen kernel: usb 2-1.2: new full speed USB device using uhci_hcd and address 64
Dec  4 08:45:56 allen kernel: usb 2-1.2: configuration #1 chosen from 1 choice
Dec  4 08:45:56 allen kernel: hub 2-1.2:1.0: USB hub found
Dec  4 08:45:56 allen kernel: hub 2-1.2:1.0: 4 ports detected
Dec  4 08:45:56 allen kernel: usb 2-1.2: New USB device found, idVendor=1608, idProduct=02c7
Dec  4 08:45:56 allen kernel: usb 2-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Dec  4 08:45:56 allen kernel: usb 2-1.1.1: new full speed USB device using uhci_hcd and address 65
Dec  4 08:45:56 allen kernel: usb 2-1.1.1: configuration #1 chosen from 1 choice
Dec  4 08:45:56 allen kernel: io_ti 2-1.1.1:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:45:57 allen kernel: usb 2-1.1.1: Edgeport TI 2 port adapter converter now attached to ttyUSB0
Dec  4 08:45:57 allen kernel: usb 2-1.1.1: Edgeport TI 2 port adapter converter now attached to ttyUSB1
Dec  4 08:45:57 allen kernel: usb 2-1.1.1: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:45:57 allen kernel: usb 2-1.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:45:57 allen kernel: usb 2-1.1.1: Product: Edgeport/416
Dec  4 08:45:57 allen kernel: usb 2-1.1.1: Manufacturer: Digi International
Dec  4 08:45:57 allen kernel: usb 2-1.1.1: SerialNumber: V70008669-0
Dec  4 08:45:57 allen kernel: usb 2-1.1.2: new full speed USB device using uhci_hcd and address 66
Dec  4 08:45:57 allen kernel: usb 2-1.1.2: configuration #1 chosen from 1 choice
Dec  4 08:45:57 allen kernel: io_ti 2-1.1.2:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:45:57 allen kernel: usb 2-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB2
Dec  4 08:45:57 allen kernel: usb 2-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB3
Dec  4 08:45:57 allen kernel: usb 2-1.1.2: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:45:57 allen kernel: usb 2-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:45:57 allen kernel: usb 2-1.1.2: Product: Edgeport/416
Dec  4 08:45:57 allen kernel: usb 2-1.1.2: Manufacturer: Digi International
Dec  4 08:45:57 allen kernel: usb 2-1.1.2: SerialNumber: V70008669-1
Dec  4 08:45:57 allen kernel: usb 2-1.1.3: new full speed USB device using uhci_hcd and address 67
Dec  4 08:45:58 allen kernel: usb 2-1.1.3: configuration #1 chosen from 1 choice
Dec  4 08:45:58 allen kernel: io_ti 2-1.1.3:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:45:58 allen kernel: usb 2-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB4
Dec  4 08:45:58 allen kernel: usb 2-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB5
Dec  4 08:45:58 allen kernel: usb 2-1.1.3: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:45:58 allen kernel: usb 2-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:45:58 allen kernel: usb 2-1.1.3: Product: Edgeport/416
Dec  4 08:45:58 allen kernel: usb 2-1.1.3: Manufacturer: Digi International
Dec  4 08:45:58 allen kernel: usb 2-1.1.3: SerialNumber: V70008669-2
Dec  4 08:45:58 allen kernel: usb 2-1.1.4: new full speed USB device using uhci_hcd and address 68
Dec  4 08:45:58 allen kernel: usb 2-1.1.4: configuration #1 chosen from 1 choice
Dec  4 08:45:58 allen kernel: io_ti 2-1.1.4:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:45:58 allen kernel: usb 2-1.1.4: Edgeport TI 2 port adapter converter now attached to ttyUSB6
Dec  4 08:45:58 allen kernel: usb 2-1.1.4: Edgeport TI 2 port adapter converter now attached to ttyUSB7
Dec  4 08:45:58 allen kernel: usb 2-1.1.4: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:45:58 allen kernel: usb 2-1.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:45:58 allen kernel: usb 2-1.1.4: Product: Edgeport/416
Dec  4 08:45:58 allen kernel: usb 2-1.1.4: Manufacturer: Digi International
Dec  4 08:45:58 allen kernel: usb 2-1.1.4: SerialNumber: V70008669-3
Dec  4 08:45:58 allen kernel: usb 2-1.2.1: new full speed USB device using uhci_hcd and address 69
Dec  4 08:45:59 allen kernel: usb 2-1.2.1: configuration #1 chosen from 1 choice
Dec  4 08:45:59 allen kernel: io_ti 2-1.2.1:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:45:59 allen kernel: usb 2-1.2.1: Edgeport TI 2 port adapter converter now attached to ttyUSB8
Dec  4 08:45:59 allen kernel: usb 2-1.2.1: Edgeport TI 2 port adapter converter now attached to ttyUSB9
Dec  4 08:45:59 allen kernel: usb 2-1.2.1: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:45:59 allen kernel: usb 2-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:45:59 allen kernel: usb 2-1.2.1: Product: Edgeport/416
Dec  4 08:45:59 allen kernel: usb 2-1.2.1: Manufacturer: Digi International
Dec  4 08:45:59 allen kernel: usb 2-1.2.1: SerialNumber: V70008669-4
Dec  4 08:45:59 allen kernel: usb 2-1.2.2: new full speed USB device using uhci_hcd and address 70
Dec  4 08:45:59 allen kernel: usb 2-1.2.2: configuration #1 chosen from 1 choice
Dec  4 08:45:59 allen kernel: io_ti 2-1.2.2:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:45:59 allen kernel: usb 2-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB10
Dec  4 08:45:59 allen kernel: usb 2-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB11
Dec  4 08:45:59 allen kernel: usb 2-1.2.2: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:45:59 allen kernel: usb 2-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:45:59 allen kernel: usb 2-1.2.2: Product: Edgeport/416
Dec  4 08:45:59 allen kernel: usb 2-1.2.2: Manufacturer: Digi International
Dec  4 08:45:59 allen kernel: usb 2-1.2.2: SerialNumber: V70008669-5
Dec  4 08:45:59 allen kernel: usb 2-1.2.3: new full speed USB device using uhci_hcd and address 71
Dec  4 08:46:00 allen kernel: usb 2-1.2.3: configuration #1 chosen from 1 choice
Dec  4 08:46:00 allen kernel: io_ti 2-1.2.3:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:46:00 allen kernel: usb 2-1.2.3: Edgeport TI 2 port adapter converter now attached to ttyUSB12
Dec  4 08:46:00 allen kernel: usb 2-1.2.3: Edgeport TI 2 port adapter converter now attached to ttyUSB13
Dec  4 08:46:00 allen kernel: usb 2-1.2.3: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:46:00 allen kernel: usb 2-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:46:00 allen kernel: usb 2-1.2.3: Product: Edgeport/416
Dec  4 08:46:00 allen kernel: usb 2-1.2.3: Manufacturer: Digi International
Dec  4 08:46:00 allen kernel: usb 2-1.2.3: SerialNumber: V70008669-6
Dec  4 08:46:00 allen kernel: usb 2-1.2.4: new full speed USB device using uhci_hcd and address 72
Dec  4 08:46:00 allen kernel: usb 2-1.2.4: configuration #1 chosen from 1 choice
Dec  4 08:46:00 allen kernel: io_ti 2-1.2.4:1.0: Edgeport TI 2 port adapter converter detected
Dec  4 08:46:00 allen kernel: usb 2-1.2.4: Edgeport TI 2 port adapter converter now attached to ttyUSB14
Dec  4 08:46:00 allen kernel: usb 2-1.2.4: Edgeport TI 2 port adapter converter now attached to ttyUSB15
Dec  4 08:46:00 allen kernel: usb 2-1.2.4: New USB device found, idVendor=1608, idProduct=0247
Dec  4 08:46:00 allen kernel: usb 2-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  4 08:46:00 allen kernel: usb 2-1.2.4: Product: Edgeport/416
Dec  4 08:46:00 allen kernel: usb 2-1.2.4: Manufacturer: Digi International
Dec  4 08:46:00 allen kernel: usb 2-1.2.4: SerialNumber: V70008669-7


[-- Attachment #4: dmesg --]
[-- Type: text/plain, Size: 14582 bytes --]

hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100
usb usb2: suspend_rh (auto-stop)
usb usb7: usb resume
ehci_hcd 0000:00:1a.7: resume root hub
ehci_hcd 0000:00:1a.7: port 3 full speed --> companion
ehci_hcd 0000:00:1a.7: GetStatus port 3 status 003801 POWER OWNER sig=j CONNECT
usb usb2: wakeup_rh (auto-start)
hub 2-0:1.0: state 7 ports 2 chg 0000 evt 0002
uhci_hcd 0000:00:1a.1: port 1 portsc 0093,00
hub 2-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
hub 7-0:1.0: hub_resume
ehci_hcd 0000:00:1a.7: GetStatus port 3 status 003002 POWER OWNER sig=se0 CSC
hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
usb 2-1: new full speed USB device using uhci_hcd and address 62
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: configuration #1 chosen from 1 choice
usb 2-1: adding 2-1:1.0 (config #1, interface 0)
usb 2-1:1.0: uevent
hub 2-1:1.0: usb_probe_interface
hub 2-1:1.0: usb_probe_interface - got id
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 6 ports detected
hub 2-1:1.0: compound device; port removable status: FFRRRR
hub 2-1:1.0: individual port power switching
hub 2-1:1.0: individual port over-current protection
hub 2-1:1.0: Port indicators are supported
hub 2-1:1.0: power on to power good time: 100ms
hub 2-1:1.0: local power source is good
hub 2-1:1.0: enabling power on all ports
drivers/usb/core/inode.c: creating file '062'
usb 2-1: New USB device found, idVendor=1608, idProduct=0184
usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 7-0:1.0: state 7 ports 6 chg 0000 evt 0000
uhci_hcd 0000:00:1a.1: reserve dev 62 ep81-INT, period 128, phase 0, 12 us
hub 2-1:1.0: state 7 ports 6 chg 0000 evt 0000
hub 7-0:1.0: hub_suspend
usb usb7: bus auto-suspend
ehci_hcd 0000:00:1a.7: suspend root hub
hub 2-1:1.0: hub_suspend
uhci_hcd 0000:00:1a.1: release dev 62 ep81-INT, period 128, phase 0, 12 us
usb 2-1: usb auto-suspend
hub 2-0:1.0: hub_suspend
usb usb2: bus auto-suspend
usb usb2: suspend_rh
usb usb2: usb resume
usb usb2: wakeup_rh
hub 2-0:1.0: hub_resume
uhci_hcd 0000:00:1a.1: port 1 portsc 0095,01
hub 2-0:1.0: port 1: status 0103 change 0004
hub 2-0:1.0: state 7 ports 2 chg 0002 evt 0000
uhci_hcd 0000:00:1a.1: port 1 portsc 0095,01
usb 2-1: usb wakeup-resume
usb 2-1: finish resume
hub 2-1:1.0: hub_resume
hub 2-1:1.0: port 1: status 0101 change 0001
hub 2-1:1.0: port 2: status 0101 change 0001
uhci_hcd 0000:00:1a.1: reserve dev 62 ep81-INT, period 128, phase 0, 12 us
hub 2-0:1.0: resume on port 1, status 0
hub 2-0:1.0: port 1, status 0103, change 0004, 12 Mb/s
hub 2-1:1.0: state 7 ports 6 chg 0006 evt 0000
hub 2-1:1.0: port 1, status 0101, change 0000, 12 Mb/s
usb 2-1.1: new full speed USB device using uhci_hcd and address 63
hub 2-1:1.0: port 1 not reset yet, waiting 10ms
usb 2-1.1: ep0 maxpacket = 8
usb 2-1.1: uevent
usb 2-1.1: usb_probe_device
usb 2-1.1: configuration #1 chosen from 1 choice
usb 2-1.1: adding 2-1.1:1.0 (config #1, interface 0)
usb 2-1.1:1.0: uevent
hub 2-1.1:1.0: usb_probe_interface
hub 2-1.1:1.0: usb_probe_interface - got id
hub 2-1.1:1.0: USB hub found
hub 2-1.1:1.0: 4 ports detected
hub 2-1.1:1.0: compound device; port removable status: FFFF
hub 2-1.1:1.0: individual port power switching
hub 2-1.1:1.0: individual port over-current protection
hub 2-1.1:1.0: power on to power good time: 0ms
hub 2-1.1:1.0: local power source is good
hub 2-1.1:1.0: enabling power on all ports
drivers/usb/core/inode.c: creating file '063'
usb 2-1.1: New USB device found, idVendor=1608, idProduct=02c7
usb 2-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 2-1:1.0: port 2, status 0101, change 0000, 12 Mb/s
hub 2-1:1.0: port 2 not reset yet, waiting 10ms
usb 2-1.2: new full speed USB device using uhci_hcd and address 64
hub 2-1.1:1.0: port 1: status 0101 change 0001
hub 2-1.1:1.0: port 2: status 0101 change 0001
hub 2-1.1:1.0: port 3: status 0101 change 0001
hub 2-1.1:1.0: port 4: status 0101 change 0001
hub 2-1:1.0: port 2 not reset yet, waiting 10ms
uhci_hcd 0000:00:1a.1: reserve dev 63 ep81-INT, period 128, phase 0, 12 us
usb 2-1.2: ep0 maxpacket = 8
usb 2-1.2: uevent
usb 2-1.2: usb_probe_device
usb 2-1.2: configuration #1 chosen from 1 choice
usb 2-1.2: adding 2-1.2:1.0 (config #1, interface 0)
usb 2-1.2:1.0: uevent
hub 2-1.2:1.0: usb_probe_interface
hub 2-1.2:1.0: usb_probe_interface - got id
hub 2-1.2:1.0: USB hub found
hub 2-1.2:1.0: 4 ports detected
hub 2-1.2:1.0: compound device; port removable status: FFFF
hub 2-1.2:1.0: individual port power switching
hub 2-1.2:1.0: individual port over-current protection
hub 2-1.2:1.0: power on to power good time: 0ms
hub 2-1.2:1.0: local power source is good
hub 2-1.2:1.0: enabling power on all ports
drivers/usb/core/inode.c: creating file '064'
usb 2-1.2: New USB device found, idVendor=1608, idProduct=02c7
usb 2-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 2-1:1.0: state 7 ports 6 chg 0000 evt 0002
hub 2-1.1:1.0: state 7 ports 4 chg 001e evt 0000
hub 2-1.1:1.0: port 1, status 0101, change 0000, 12 Mb/s
usb 2-1.1.1: new full speed USB device using uhci_hcd and address 65
hub 2-1.2:1.0: port 1: status 0101 change 0001
hub 2-1.2:1.0: port 2: status 0101 change 0001
hub 2-1.2:1.0: port 3: status 0101 change 0001
hub 2-1.2:1.0: port 4: status 0101 change 0001
usb 2-1.1.1: ep0 maxpacket = 8
uhci_hcd 0000:00:1a.1: reserve dev 64 ep81-INT, period 128, phase 0, 12 us
usb 2-1.1.1: default language 0x0409
usb 2-1.1.1: uevent
usb 2-1.1.1: usb_probe_device
usb 2-1.1.1: configuration #1 chosen from 1 choice
usb 2-1.1.1: adding 2-1.1.1:1.0 (config #1, interface 0)
usb 2-1.1.1:1.0: uevent
usbserial_generic 2-1.1.1:1.0: usb_probe_interface
usbserial_generic 2-1.1.1:1.0: usb_probe_interface - got id
io_ti 2-1.1.1:1.0: usb_probe_interface
io_ti 2-1.1.1:1.0: usb_probe_interface - got id
io_ti 2-1.1.1:1.0: Edgeport TI 2 port adapter converter detected
usb 2-1.1.1: Edgeport TI 2 port adapter converter now attached to ttyUSB0
usb 2-1.1.1: Edgeport TI 2 port adapter converter now attached to ttyUSB1
drivers/usb/core/inode.c: creating file '065'
usb 2-1.1.1: New USB device found, idVendor=1608, idProduct=0247
usb 2-1.1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.1.1: Product: Edgeport/416
usb 2-1.1.1: Manufacturer: Digi International
usb 2-1.1.1: SerialNumber: V70008669-0
hub 2-1.1:1.0: port 2, status 0101, change 0000, 12 Mb/s
usb 2-1.1.2: new full speed USB device using uhci_hcd and address 66
usb 2-1.1.2: ep0 maxpacket = 8
usb 2-1.1.2: default language 0x0409
usb 2-1.1.2: uevent
usb 2-1.1.2: usb_probe_device
usb 2-1.1.2: configuration #1 chosen from 1 choice
usb 2-1.1.2: adding 2-1.1.2:1.0 (config #1, interface 0)
usb 2-1.1.2:1.0: uevent
usbserial_generic 2-1.1.2:1.0: usb_probe_interface
usbserial_generic 2-1.1.2:1.0: usb_probe_interface - got id
io_ti 2-1.1.2:1.0: usb_probe_interface
io_ti 2-1.1.2:1.0: usb_probe_interface - got id
io_ti 2-1.1.2:1.0: Edgeport TI 2 port adapter converter detected
usb 2-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB2
usb 2-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB3
drivers/usb/core/inode.c: creating file '066'
usb 2-1.1.2: New USB device found, idVendor=1608, idProduct=0247
usb 2-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.1.2: Product: Edgeport/416
usb 2-1.1.2: Manufacturer: Digi International
usb 2-1.1.2: SerialNumber: V70008669-1
hub 2-1.1:1.0: port 3, status 0101, change 0000, 12 Mb/s
usb 2-1.1.3: new full speed USB device using uhci_hcd and address 67
usb 2-1.1.3: ep0 maxpacket = 8
usb 2-1.1.3: default language 0x0409
usb 2-1.1.3: uevent
usb 2-1.1.3: usb_probe_device
usb 2-1.1.3: configuration #1 chosen from 1 choice
usb 2-1.1.3: adding 2-1.1.3:1.0 (config #1, interface 0)
usb 2-1.1.3:1.0: uevent
usbserial_generic 2-1.1.3:1.0: usb_probe_interface
usbserial_generic 2-1.1.3:1.0: usb_probe_interface - got id
io_ti 2-1.1.3:1.0: usb_probe_interface
io_ti 2-1.1.3:1.0: usb_probe_interface - got id
io_ti 2-1.1.3:1.0: Edgeport TI 2 port adapter converter detected
usb 2-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB4
usb 2-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB5
drivers/usb/core/inode.c: creating file '067'
usb 2-1.1.3: New USB device found, idVendor=1608, idProduct=0247
usb 2-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.1.3: Product: Edgeport/416
usb 2-1.1.3: Manufacturer: Digi International
usb 2-1.1.3: SerialNumber: V70008669-2
hub 2-1.1:1.0: port 4, status 0101, change 0000, 12 Mb/s
usb 2-1.1.4: new full speed USB device using uhci_hcd and address 68
usb 2-1.1.4: ep0 maxpacket = 8
usb 2-1.1.4: default language 0x0409
usb 2-1.1.4: uevent
usb 2-1.1.4: usb_probe_device
usb 2-1.1.4: configuration #1 chosen from 1 choice
usb 2-1.1.4: adding 2-1.1.4:1.0 (config #1, interface 0)
usb 2-1.1.4:1.0: uevent
usbserial_generic 2-1.1.4:1.0: usb_probe_interface
usbserial_generic 2-1.1.4:1.0: usb_probe_interface - got id
io_ti 2-1.1.4:1.0: usb_probe_interface
io_ti 2-1.1.4:1.0: usb_probe_interface - got id
io_ti 2-1.1.4:1.0: Edgeport TI 2 port adapter converter detected
usb 2-1.1.4: Edgeport TI 2 port adapter converter now attached to ttyUSB6
usb 2-1.1.4: Edgeport TI 2 port adapter converter now attached to ttyUSB7
drivers/usb/core/inode.c: creating file '068'
usb 2-1.1.4: New USB device found, idVendor=1608, idProduct=0247
usb 2-1.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.1.4: Product: Edgeport/416
usb 2-1.1.4: Manufacturer: Digi International
usb 2-1.1.4: SerialNumber: V70008669-3
hub 2-1.1:1.0: state 7 ports 4 chg 0000 evt 0010
hub 2-1.2:1.0: state 7 ports 4 chg 001e evt 0000
hub 2-1.2:1.0: port 1, status 0101, change 0000, 12 Mb/s
usb 2-1.2.1: new full speed USB device using uhci_hcd and address 69
usb 2-1.2.1: ep0 maxpacket = 8
usb 2-1.2.1: default language 0x0409
usb 2-1.2.1: uevent
usb 2-1.2.1: usb_probe_device
usb 2-1.2.1: configuration #1 chosen from 1 choice
usb 2-1.2.1: adding 2-1.2.1:1.0 (config #1, interface 0)
usb 2-1.2.1:1.0: uevent
usbserial_generic 2-1.2.1:1.0: usb_probe_interface
usbserial_generic 2-1.2.1:1.0: usb_probe_interface - got id
io_ti 2-1.2.1:1.0: usb_probe_interface
io_ti 2-1.2.1:1.0: usb_probe_interface - got id
io_ti 2-1.2.1:1.0: Edgeport TI 2 port adapter converter detected
usb 2-1.2.1: Edgeport TI 2 port adapter converter now attached to ttyUSB8
usb 2-1.2.1: Edgeport TI 2 port adapter converter now attached to ttyUSB9
drivers/usb/core/inode.c: creating file '069'
usb 2-1.2.1: New USB device found, idVendor=1608, idProduct=0247
usb 2-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.2.1: Product: Edgeport/416
usb 2-1.2.1: Manufacturer: Digi International
usb 2-1.2.1: SerialNumber: V70008669-4
hub 2-1.2:1.0: port 2, status 0101, change 0000, 12 Mb/s
usb 2-1.2.2: new full speed USB device using uhci_hcd and address 70
usb 2-1.2.2: ep0 maxpacket = 8
usb 2-1.2.2: default language 0x0409
usb 2-1.2.2: uevent
usb 2-1.2.2: usb_probe_device
usb 2-1.2.2: configuration #1 chosen from 1 choice
usb 2-1.2.2: adding 2-1.2.2:1.0 (config #1, interface 0)
usb 2-1.2.2:1.0: uevent
usbserial_generic 2-1.2.2:1.0: usb_probe_interface
usbserial_generic 2-1.2.2:1.0: usb_probe_interface - got id
io_ti 2-1.2.2:1.0: usb_probe_interface
io_ti 2-1.2.2:1.0: usb_probe_interface - got id
io_ti 2-1.2.2:1.0: Edgeport TI 2 port adapter converter detected
usb 2-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB10
usb 2-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB11
drivers/usb/core/inode.c: creating file '070'
usb 2-1.2.2: New USB device found, idVendor=1608, idProduct=0247
usb 2-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.2.2: Product: Edgeport/416
usb 2-1.2.2: Manufacturer: Digi International
usb 2-1.2.2: SerialNumber: V70008669-5
hub 2-1.2:1.0: port 3, status 0101, change 0000, 12 Mb/s
usb 2-1.2.3: new full speed USB device using uhci_hcd and address 71
usb 2-1.2.3: ep0 maxpacket = 8
usb 2-1.2.3: default language 0x0409
usb 2-1.2.3: uevent
usb 2-1.2.3: usb_probe_device
usb 2-1.2.3: configuration #1 chosen from 1 choice
usb 2-1.2.3: adding 2-1.2.3:1.0 (config #1, interface 0)
usb 2-1.2.3:1.0: uevent
usbserial_generic 2-1.2.3:1.0: usb_probe_interface
usbserial_generic 2-1.2.3:1.0: usb_probe_interface - got id
io_ti 2-1.2.3:1.0: usb_probe_interface
io_ti 2-1.2.3:1.0: usb_probe_interface - got id
io_ti 2-1.2.3:1.0: Edgeport TI 2 port adapter converter detected
usb 2-1.2.3: Edgeport TI 2 port adapter converter now attached to ttyUSB12
usb 2-1.2.3: Edgeport TI 2 port adapter converter now attached to ttyUSB13
drivers/usb/core/inode.c: creating file '071'
usb 2-1.2.3: New USB device found, idVendor=1608, idProduct=0247
usb 2-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.2.3: Product: Edgeport/416
usb 2-1.2.3: Manufacturer: Digi International
usb 2-1.2.3: SerialNumber: V70008669-6
hub 2-1.2:1.0: port 4, status 0101, change 0000, 12 Mb/s
usb 2-1.2.4: new full speed USB device using uhci_hcd and address 72
usb 2-1.2.4: ep0 maxpacket = 8
usb 2-1.2.4: default language 0x0409
usb 2-1.2.4: uevent
usb 2-1.2.4: usb_probe_device
usb 2-1.2.4: configuration #1 chosen from 1 choice
usb 2-1.2.4: adding 2-1.2.4:1.0 (config #1, interface 0)
usb 2-1.2.4:1.0: uevent
usbserial_generic 2-1.2.4:1.0: usb_probe_interface
usbserial_generic 2-1.2.4:1.0: usb_probe_interface - got id
io_ti 2-1.2.4:1.0: usb_probe_interface
io_ti 2-1.2.4:1.0: usb_probe_interface - got id
io_ti 2-1.2.4:1.0: Edgeport TI 2 port adapter converter detected
usb 2-1.2.4: Edgeport TI 2 port adapter converter now attached to ttyUSB14
usb 2-1.2.4: Edgeport TI 2 port adapter converter now attached to ttyUSB15
drivers/usb/core/inode.c: creating file '072'
usb 2-1.2.4: New USB device found, idVendor=1608, idProduct=0247
usb 2-1.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.2.4: Product: Edgeport/416
usb 2-1.2.4: Manufacturer: Digi International
usb 2-1.2.4: SerialNumber: V70008669-7
hub 2-1.2:1.0: state 7 ports 4 chg 0000 evt 0008
usb 2-1.1.1:1.0: uevent
usb 2-1.1.1: uevent
usb 2-1.1: uevent
usb 2-1: uevent
usb usb2: uevent
usb 2-1.1.1:1.0: uevent
usb 2-1.1.1: uevent
usb 2-1.1: uevent
usb 2-1: uevent
usb usb2: uevent

Re: Udev rule for HSDPA modem

[Greg KH]

On Thu, Dec 04, 2008 at 09:27:15AM -0600, Karl O. Pinc wrote:
>
> I think what the Digi Edgeport 4/16 needs is the same rule set, but
> with the serial number also included in the name.  This is because
> it has an internal hub with 8 endpoints, each endpoint driving 2
> serial ports (io_ti), and my understanding is that the ports on the
> internal hub may not be discovered in the same order every time.
> However, each internal endpoint does have it's own serial
> number.  If that showed in the name then there'd be no
> problem.
>
> Of course I could be completely misunderstanding.

Hm, good point, I think the by_id stuff will start conflicting if 2 of
the same types of devices are plugged in at the same time.

Let me go dig through my boxes of usb stuff to find some duplicate
devices, and one of the 4/16 edgeport devices as well...

thanks,

greg k-h

Re: Udev rule for HSDPA modem

[Greg KH]

On Thu, Dec 04, 2008 at 10:56:32AM -0800, Greg KH wrote:
> On Thu, Dec 04, 2008 at 09:27:15AM -0600, Karl O. Pinc wrote:
> >
> > I think what the Digi Edgeport 4/16 needs is the same rule set, but
> > with the serial number also included in the name.  This is because
> > it has an internal hub with 8 endpoints, each endpoint driving 2
> > serial ports (io_ti), and my understanding is that the ports on the
> > internal hub may not be discovered in the same order every time.
> > However, each internal endpoint does have it's own serial
> > number.  If that showed in the name then there'd be no
> > problem.
> >
> > Of course I could be completely misunderstanding.
> 
> Hm, good point, I think the by_id stuff will start conflicting if 2 of
> the same types of devices are plugged in at the same time.
> 
> Let me go dig through my boxes of usb stuff to find some duplicate
> devices, and one of the 4/16 edgeport devices as well...

Not a problem, the serial number is added to the "by-id" tree if it is
present:

$ tree /dev/serial/
/dev/serial/
|-- by-id
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port0 -> ../../ttyUSB8
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port1 -> ../../ttyUSB9
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port2 -> ../../ttyUSB10
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port3 -> ../../ttyUSB11
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port4 -> ../../ttyUSB12
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port5 -> ../../ttyUSB13
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port6 -> ../../ttyUSB14
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port7 -> ../../ttyUSB15
|   |-- usb-Keyspan_Serial-if00-port0 -> ../../ttyUSB0
|   |-- usb-Keyspan__a_division_of_InnoSys_Inc._Keyspan_USB_Serial_Adapter-if00-port0 -> ../../ttyUSB1
|   |-- usb-Keyspan__a_division_of_InnoSys_Inc._Keyspan_USB_Serial_Adapter-if00-port1 -> ../../ttyUSB2
|   `-- usb-Prolific_Technology_Inc._USB-Serial_Controller-if00-port0 -> ../../ttyUSB7
`-- by-path
    |-- pci-0000:00:1d.2-usb-0:1.3:1.0-port0 -> ../../ttyUSB7
    |-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port0 -> ../../ttyUSB0
    |-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port0 -> ../../ttyUSB1
    |-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port1 -> ../../ttyUSB2
    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port0 -> ../../ttyUSB8
    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port1 -> ../../ttyUSB9
    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port2 -> ../../ttyUSB10
    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port3 -> ../../ttyUSB11
    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port4 -> ../../ttyUSB12
    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port5 -> ../../ttyUSB13
    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port6 -> ../../ttyUSB14
    `-- pci-0000:00:1d.7-usb-0:6.3:1.0-port7 -> ../../ttyUSB15


The problem is when you have 2 devices with no serial numbers, the last
one in wins the "by_id" classification:

$ tree /dev/serial/
/dev/serial/
|-- by-id
|   `-- usb-067b_2303-if00-port0 -> ../../ttyUSB3
`-- by-path
    |-- pci-0000:00:1d.7-usb-0:6.1.4.2.1:1.0-port0 -> ../../ttyUSB0
    |-- pci-0000:00:1d.7-usb-0:6.1.4.2.2:1.0-port0 -> ../../ttyUSB1
    |-- pci-0000:00:1d.7-usb-0:6.1.4.2.3:1.0-port0 -> ../../ttyUSB2
    `-- pci-0000:00:1d.7-usb-0:6.1.4.2.4:1.0-port0 -> ../../ttyUSB3

This is a 4 port, pl2303 device that is really a hub with 4 devices
behind it.  No serial number either, so the by-id path isn't the best
choice, but the by-path one is.

And, just for fun, here's a bunch of usb-serial devices all plugged in
at the same time:

/dev/serial
|-- by-id
|   |-- usb-067b_2303-if00-port0 -> ../../ttyUSB3
|   |-- usb-ACME_usb_widgets_ACME_USB_serial_widget_47-if00-port0 -> ../../ttyUSB19
|   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port0 -> ../../ttyUSB20
|   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port1 -> ../../ttyUSB21
|   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port2 -> ../../ttyUSB22
|   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port3 -> ../../ttyUSB23
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port0 -> ../../ttyUSB4
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port1 -> ../../ttyUSB5
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port2 -> ../../ttyUSB6
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port3 -> ../../ttyUSB7
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port4 -> ../../ttyUSB8
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port5 -> ../../ttyUSB9
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port6 -> ../../ttyUSB10
|   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port7 -> ../../ttyUSB11
|   |-- usb-Keyspan_Serial-if00-port0 -> ../../ttyUSB14
|   |-- usb-Keyspan__a_division_of_InnoSys_Inc._Keyspan_USB_Serial_Adapter-if00-port0 -> ../../ttyUSB24
|   |-- usb-Keyspan__a_division_of_InnoSys_Inc._Keyspan_USB_Serial_Adapter-if00-port1 -> ../../ttyUSB25
|   |-- usb-Prolific_Technology_Inc._USB-Serial_Controller-if00-port0 -> ../../ttyUSB17
|   `-- usb-USB-RS232_Interface_Converter_USB_Ver1.1_Device_679016-if00-port0 -> ../../ttyUSB18
`-- by-path
    |-- pci-0000:00:1d.2-usb-0:1.2:1.0-port0 -> ../../ttyUSB19
    |-- pci-0000:00:1d.2-usb-0:1.3:1.0-port0 -> ../../ttyUSB17
    |-- pci-0000:00:1d.7-usb-0:6.1.1:1.0-port0 -> ../../ttyUSB24
    |-- pci-0000:00:1d.7-usb-0:6.1.1:1.0-port1 -> ../../ttyUSB25
    |-- pci-0000:00:1d.7-usb-0:6.1.2:1.0-port0 -> ../../ttyUSB20
    |-- pci-0000:00:1d.7-usb-0:6.1.2:1.0-port1 -> ../../ttyUSB21
    |-- pci-0000:00:1d.7-usb-0:6.1.2:1.0-port2 -> ../../ttyUSB22
    |-- pci-0000:00:1d.7-usb-0:6.1.2:1.0-port3 -> ../../ttyUSB23
    |-- pci-0000:00:1d.7-usb-0:6.1.3:1.0-port0 -> ../../ttyUSB18
    |-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port0 -> ../../ttyUSB15
    |-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port1 -> ../../ttyUSB16
    |-- pci-0000:00:1d.7-usb-0:6.1.4.2.1:1.0-port0 -> ../../ttyUSB0
    |-- pci-0000:00:1d.7-usb-0:6.1.4.2.2:1.0-port0 -> ../../ttyUSB1
    |-- pci-0000:00:1d.7-usb-0:6.1.4.2.3:1.0-port0 -> ../../ttyUSB2
    |-- pci-0000:00:1d.7-usb-0:6.1.4.2.4:1.0-port0 -> ../../ttyUSB3
    |-- pci-0000:00:1d.7-usb-0:6.1.4.3:1.0-port0 -> ../../ttyUSB14
    |-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port0 -> ../../ttyUSB12
    |-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port1 -> ../../ttyUSB13
    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port0 -> ../../ttyUSB4
    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port1 -> ../../ttyUSB5
    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port2 -> ../../ttyUSB6
    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port3 -> ../../ttyUSB7
    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port4 -> ../../ttyUSB8
    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port5 -> ../../ttyUSB9
    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port6 -> ../../ttyUSB10
    `-- pci-0000:00:1d.7-usb-0:6.3:1.0-port7 -> ../../ttyUSB11


Hope this helps,

greg k-h

Re: Udev rule for HSDPA modem

[Kay Sievers]

On Thu, Dec 4, 2008 at 20:11, Greg KH <greg@kroah.com> wrote:
> On Thu, Dec 04, 2008 at 10:56:32AM -0800, Greg KH wrote:
>> On Thu, Dec 04, 2008 at 09:27:15AM -0600, Karl O. Pinc wrote:
>> >
>> > I think what the Digi Edgeport 4/16 needs is the same rule set, but
>> > with the serial number also included in the name.  This is because
>> > it has an internal hub with 8 endpoints, each endpoint driving 2
>> > serial ports (io_ti), and my understanding is that the ports on the
>> > internal hub may not be discovered in the same order every time.
>> > However, each internal endpoint does have it's own serial
>> > number.  If that showed in the name then there'd be no
>> > problem.
>> >
>> > Of course I could be completely misunderstanding.
>>
>> Hm, good point, I think the by_id stuff will start conflicting if 2 of
>> the same types of devices are plugged in at the same time.

Yeah, that's intentional for by-id/, it should be independent of the
order of plug-in and the physical location it is plugged in, so the
usual case where you have only one device, or devices with proper
serial numbers, you always find it with exactly the same link name.

If you have multiple completely indentical devices this can obviously
not work, just like multiple partitions with the same filesystem label
overwrite the disk/by-label/ links. The you need to use the slightly
less convenient by-path/ links, and can not move the devices to
different ports.

>> Let me go dig through my boxes of usb stuff to find some duplicate
>> devices, and one of the 4/16 edgeport devices as well...
>
> Not a problem, the serial number is added to the "by-id" tree if it is
> present:

Yeah, usb_id always appends the serial number if it finds one.

> $ tree /dev/serial/
> /dev/serial/
> |-- by-id
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port0 -> ../../ttyUSB8
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port1 -> ../../ttyUSB9
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port2 -> ../../ttyUSB10
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port3 -> ../../ttyUSB11
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port4 -> ../../ttyUSB12
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port5 -> ../../ttyUSB13
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port6 -> ../../ttyUSB14
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port7 -> ../../ttyUSB15
> |   |-- usb-Keyspan_Serial-if00-port0 -> ../../ttyUSB0
> |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._Keyspan_USB_Serial_Adapter-if00-port0 -> ../../ttyUSB1
> |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._Keyspan_USB_Serial_Adapter-if00-port1 -> ../../ttyUSB2
> |   `-- usb-Prolific_Technology_Inc._USB-Serial_Controller-if00-port0 -> ../../ttyUSB7
> `-- by-path
>    |-- pci-0000:00:1d.2-usb-0:1.3:1.0-port0 -> ../../ttyUSB7
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port0 -> ../../ttyUSB0
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port0 -> ../../ttyUSB1
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port1 -> ../../ttyUSB2
>    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port0 -> ../../ttyUSB8
>    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port1 -> ../../ttyUSB9
>    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port2 -> ../../ttyUSB10
>    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port3 -> ../../ttyUSB11
>    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port4 -> ../../ttyUSB12
>    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port5 -> ../../ttyUSB13
>    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port6 -> ../../ttyUSB14
>    `-- pci-0000:00:1d.7-usb-0:6.3:1.0-port7 -> ../../ttyUSB15
>
> The problem is when you have 2 devices with no serial numbers, the last
> one in wins the "by_id" classification:
>
> $ tree /dev/serial/
> /dev/serial/
> |-- by-id
> |   `-- usb-067b_2303-if00-port0 -> ../../ttyUSB3
> `-- by-path
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.2.1:1.0-port0 -> ../../ttyUSB0
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.2.2:1.0-port0 -> ../../ttyUSB1
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.2.3:1.0-port0 -> ../../ttyUSB2
>    `-- pci-0000:00:1d.7-usb-0:6.1.4.2.4:1.0-port0 -> ../../ttyUSB3

Yeah, only by-path/ will work here. There is nothing we could do, just
like with the filesystem labels.

The nice thing is, if you would remove the device the link currently
points to, udev would re-create the link for the next device in the
stack of links with the same name. :)

> This is a 4 port, pl2303 device that is really a hub with 4 devices
> behind it.  No serial number either, so the by-id path isn't the best
> choice, but the by-path one is.
>
> And, just for fun, here's a bunch of usb-serial devices all plugged in
> at the same time:
>
> /dev/serial
> |-- by-id
> |   |-- usb-067b_2303-if00-port0 -> ../../ttyUSB3
> |   |-- usb-ACME_usb_widgets_ACME_USB_serial_widget_47-if00-port0 -> ../../ttyUSB19
> |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port0 -> ../../ttyUSB20
> |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port1 -> ../../ttyUSB21
> |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port2 -> ../../ttyUSB22
> |   |-- usb-Inside_Out_Networks_Edgeport_4_04-01-006467-if00-port3 -> ../../ttyUSB23
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port0 -> ../../ttyUSB4
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port1 -> ../../ttyUSB5
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port2 -> ../../ttyUSB6
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port3 -> ../../ttyUSB7
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port4 -> ../../ttyUSB8
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port5 -> ../../ttyUSB9
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port6 -> ../../ttyUSB10
> |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port7 -> ../../ttyUSB11
> |   |-- usb-Keyspan_Serial-if00-port0 -> ../../ttyUSB14
> |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._Keyspan_USB_Serial_Adapter-if00-port0 -> ../../ttyUSB24
> |   |-- usb-Keyspan__a_division_of_InnoSys_Inc._Keyspan_USB_Serial_Adapter-if00-port1 -> ../../ttyUSB25
> |   |-- usb-Prolific_Technology_Inc._USB-Serial_Controller-if00-port0 -> ../../ttyUSB17
> |   `-- usb-USB-RS232_Interface_Converter_USB_Ver1.1_Device_679016-if00-port0 -> ../../ttyUSB18
> `-- by-path
>    |-- pci-0000:00:1d.2-usb-0:1.2:1.0-port0 -> ../../ttyUSB19
>    |-- pci-0000:00:1d.2-usb-0:1.3:1.0-port0 -> ../../ttyUSB17
>    |-- pci-0000:00:1d.7-usb-0:6.1.1:1.0-port0 -> ../../ttyUSB24
>    |-- pci-0000:00:1d.7-usb-0:6.1.1:1.0-port1 -> ../../ttyUSB25
>    |-- pci-0000:00:1d.7-usb-0:6.1.2:1.0-port0 -> ../../ttyUSB20
>    |-- pci-0000:00:1d.7-usb-0:6.1.2:1.0-port1 -> ../../ttyUSB21
>    |-- pci-0000:00:1d.7-usb-0:6.1.2:1.0-port2 -> ../../ttyUSB22
>    |-- pci-0000:00:1d.7-usb-0:6.1.2:1.0-port3 -> ../../ttyUSB23
>    |-- pci-0000:00:1d.7-usb-0:6.1.3:1.0-port0 -> ../../ttyUSB18
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port0 -> ../../ttyUSB15
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.1:1.0-port1 -> ../../ttyUSB16
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.2.1:1.0-port0 -> ../../ttyUSB0
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.2.2:1.0-port0 -> ../../ttyUSB1
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.2.3:1.0-port0 -> ../../ttyUSB2
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.2.4:1.0-port0 -> ../../ttyUSB3
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.3:1.0-port0 -> ../../ttyUSB14
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port0 -> ../../ttyUSB12
>    |-- pci-0000:00:1d.7-usb-0:6.1.4.4:1.0-port1 -> ../../ttyUSB13
>    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port0 -> ../../ttyUSB4
>    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port1 -> ../../ttyUSB5
>    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port2 -> ../../ttyUSB6
>    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port3 -> ../../ttyUSB7
>    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port4 -> ../../ttyUSB8
>    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port5 -> ../../ttyUSB9
>    |-- pci-0000:00:1d.7-usb-0:6.3:1.0-port6 -> ../../ttyUSB10
>    `-- pci-0000:00:1d.7-usb-0:6.3:1.0-port7 -> ../../ttyUSB11

Looks good. It think it's useful for many setups with more than one
serial device. And I still like the fact, that we can do that with
just 15 simple lines of udev rules.

Thanks,
Kay

Re: Udev rule for HSDPA modem

[Karl O. Pinc]

On 12/04/2008 08:53:46 PM, Kay Sievers wrote:
> On Thu, Dec 4, 2008 at 20:11, Greg KH <greg@kroah.com> wrote:

> 
> Yeah, that's intentional for by-id/, it should be independent of the
> order of plug-in and the physical location it is plugged in, so the
> usual case where you have only one device, or devices with proper
> serial numbers, you always find it with exactly the same link name.

> 
> > $ tree /dev/serial/
> > /dev/serial/
> > |-- by-id
> > |   |-- usb-Inside_Out_Networks_Edgeport_8_V12124599-if00-port0 ->
> ../../ttyUSB8

Why is it that the symlink is a single name, and not a path?

On the one hand it's probably because that's the way other
parts of udev work, which is a good reason to leave the design well
enough alone.

But I'm drawn to having a path like:

/dev/serial/by-id/usb/Inside_Out_Networks/Edgeport_8/V12124559/if00/port0

The last component would be the actual symlink.

It makes the name painless to parse and is just as easy to type.
To parse the one-big-name approach, in the general case,
you'd have to be sure that - does not appear in the strings
supplied by the device.  (The answer's probably obvious to
someone who's read the udev manual, but still....)

Come to think of it even better would be (shamelessly
adding a new "kind" of tree):

/dev/serial/by-label/bus.usb/make.Inside_Out_Networks/model.Edgeport_8/serial.V12124559/iface.if00/port.port0

What's nice here is that if a component is missing it still can have
an element in the tree.  If you wanted to omit missing elements,
if there was a missing serial number for instance, then it'd
be more basename friendly to put the labels into the directory
components as suffixes, like:

/dev/serial/by-label/usb.bug/Inside_Out_Networks.make/Edgeport_8.model/V12124559.serial/if00.iface/port0.port

Maybe this info is exposed elsewhere.  This is from the perspective
of someone who always winds up going in circles when rooting through
/sys/.

Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein