Problem with udev & Vodafone UMTS card

Problem with udev & Vodafone UMTS card

[Marc Packenius]

Hi there,

after installing udev on a Debian/sid-powered Toshiba Satellite
notebook, the Vodafone UMTS card stopped working.

This pc-card includes a USB controller and feeds three serial character
devices when installed properly. They're called "/dev/ttyUSB[0-2]".

When using udev, those device nodes are not created properly, instead
the dev directory shows files with the filename "/dev/<NULL>[0-2]", e.g. 
"/dev/<NULL>0".

Here's what I do to reproduce the problem:

mudshark:~# modprobe -v usbserial vendor=0xaf0 product=0x5000
insmod /lib/modules/2.6.10-mudshark/kernel/drivers/usb/serial/usbserial.ko vendor=0xaf0 product=0x5000

Log messages:

=> /var/log/messages <=
Jan 24 14:59:35 mudshark kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
Jan 24 14:59:35 mudshark kernel: usbserial_generic 5-1:1.0: Generic converter detected
Jan 24 14:59:35 mudshark kernel: usb 5-1: Generic converter now attached to ttyUSB0
Jan 24 14:59:35 mudshark kernel: usbserial_generic 5-1:1.1: Generic converter detected
Jan 24 14:59:35 mudshark kernel: usb 5-1: Generic converter now attached to ttyUSB1
Jan 24 14:59:35 mudshark kernel: usbserial_generic 5-1:1.2: Generic converter detected
Jan 24 14:59:35 mudshark kernel: usb 5-1: Generic converter now attached to ttyUSB2
Jan 24 14:59:35 mudshark kernel: usbcore: registered new driver usbserial_generic
Jan 24 14:59:35 mudshark kernel: usbcore: registered new driver usbserial
Jan 24 14:59:35 mudshark kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0

=> /var/log/daemon.log <=
Jan 24 14:59:35 mudshark udev[3157]: creating device node '/dev/<NULL>0'
Jan 24 14:59:35 mudshark udev[3169]: creating device node '/dev/<NULL>1'
Jan 24 14:59:35 mudshark udev[3179]: creating device node '/dev/<NULL>2'

=> /var/log/kern.log <=
Jan 24 14:59:35 mudshark kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
Jan 24 14:59:35 mudshark kernel: usbserial_generic 5-1:1.0: Generic converter detected
Jan 24 14:59:35 mudshark kernel: usb 5-1: Generic converter now attached to ttyUSB0
Jan 24 14:59:35 mudshark kernel: usbserial_generic 5-1:1.1: Generic converter detected
Jan 24 14:59:35 mudshark kernel: usb 5-1: Generic converter now attached to ttyUSB1
Jan 24 14:59:35 mudshark kernel: usbserial_generic 5-1:1.2: Generic converter detected
Jan 24 14:59:35 mudshark kernel: usb 5-1: Generic converter now attached to ttyUSB2
Jan 24 14:59:35 mudshark kernel: usbcore: registered new driver usbserial_generic
Jan 24 14:59:35 mudshark kernel: usbcore: registered new driver usbserial
Jan 24 14:59:35 mudshark kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0

sysfs looks like this:

mudshark:~# ls -l /sys/bus/usb-serial/devices/
insgesamt 0
lrwxrwxrwx  1 root root 0 2005-01-24 14:59 ttyUSB0 -> ../../../devices/pci0000:00/0000:00:1e.0/0000:01:0b.0/0000:02:00.0/usb5/5-1/5-1:1.0/ttyUSB0
lrwxrwxrwx  1 root root 0 2005-01-24 14:59 ttyUSB1 -> ../../../devices/pci0000:00/0000:00:1e.0/0000:01:0b.0/0000:02:00.0/usb5/5-1/5-1:1.1/ttyUSB1
lrwxrwxrwx  1 root root 0 2005-01-24 14:59 ttyUSB2 -> ../../../devices/pci0000:00/0000:00:1e.0/0000:01:0b.0/0000:02:00.0/usb5/5-1/5-1:1.2/ttyUSB2

The entries in /dev look like this:

mudshark:~# ls -l /dev/*NULL*
crw-rw----  1 root root 0, 0 2005-01-24 14:59 /dev/<NULL>0
crw-rw----  1 root root 0, 1 2005-01-24 14:59 /dev/<NULL>1
crw-rw----  1 root root 0, 2 2005-01-24 14:59 /dev/<NULL>2

udev-version:

mudshark:~# dpkg -l udev
[...]
ii  udev                          0.050-5                       /dev/ management daemon

I reproduced the problem with several (debian-patched) kernels, incl. 
2.6.{8,9,10}.

Without udev, ie. with manually created device nodes, the card works
fine.

If there's further information I can provide, or if I should report this
to someone else, please let me know. Thanks!

Thanks for your advice,
-- 
Marc "Backlog" Packenius


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Problem with udev & Vodafone UMTS card

[Kay Sievers]

On Mon, 2005-01-24 at 15:15 +0100, Marc Packenius wrote:
> Hi there,
> 
> after installing udev on a Debian/sid-powered Toshiba Satellite
> notebook, the Vodafone UMTS card stopped working.
> 
> This pc-card includes a USB controller and feeds three serial character
> devices when installed properly. They're called "/dev/ttyUSB[0-2]".
> 
> When using udev, those device nodes are not created properly, instead
> the dev directory shows files with the filename "/dev/<NULL>[0-2]", e.g. 
> "/dev/<NULL>0".

> => /var/log/daemon.log <=
> Jan 24 14:59:35 mudshark udev[3157]: creating device node '/dev/<NULL>0'
> Jan 24 14:59:35 mudshark udev[3169]: creating device node '/dev/<NULL>1'
> Jan 24 14:59:35 mudshark udev[3179]: creating device node '/dev/<NULL>2'

How does:
  ls -l /sys/class/tty/ttyUSB*

look like, or any other suspicious entry in this directory?

What does:
  udevinfo -a -p /sys/class/tty/ttyUSB0

print?

Thanks,
Kay



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Problem with udev & Vodafone UMTS card

[Marc Packenius]

Hi Kay,

Kay Sievers <kay.sievers@vrfy.org> writes:

> On Mon, 2005-01-24 at 15:15 +0100, Marc Packenius wrote:
>> after installing udev on a Debian/sid-powered Toshiba Satellite
>> notebook, the Vodafone UMTS card stopped working.
>> 
>> This pc-card includes a USB controller and feeds three serial character
>> devices when installed properly. They're called "/dev/ttyUSB[0-2]".
>> 
>> When using udev, those device nodes are not created properly, instead
>> the dev directory shows files with the filename "/dev/<NULL>[0-2]", e.g. 
>> "/dev/<NULL>0".

>> => /var/log/daemon.log <=
>> Jan 24 14:59:35 mudshark udev[3157]: creating device node '/dev/<NULL>0'
>> Jan 24 14:59:35 mudshark udev[3169]: creating device node '/dev/<NULL>1'
>> Jan 24 14:59:35 mudshark udev[3179]: creating device node '/dev/<NULL>2'

> How does:
>   ls -l /sys/class/tty/ttyUSB*

> look like, or any other suspicious entry in this directory?

mudshark:~# ls -l /sys/class/tty/ttyUSB*
ls: /sys/class/tty/ttyUSB*: Datei oder Verzeichnis nicht gefunden
mudshark:~# ls -l /sys/class/tty/*NULL*
/sys/class/tty/<NULL>0:
insgesamt 0
-r--r--r--  1 root root 4096 2005-01-24 16:51 dev
lrwxrwxrwx  1 root root    0 2005-01-24 16:51 device -> ../../../devices/pci0000:00/0000:00:1e.0/0000:01:0b.0/0000:02:00.0/usb5/5-1/5-1:1.0/ttyUSB0
lrwxrwxrwx  1 root root    0 2005-01-24 16:51 driver -> ../../../bus/usb-serial/drivers/generic

/sys/class/tty/<NULL>1:
insgesamt 0
-r--r--r--  1 root root 4096 2005-01-24 16:51 dev
lrwxrwxrwx  1 root root    0 2005-01-24 16:51 device -> ../../../devices/pci0000:00/0000:00:1e.0/0000:01:0b.0/0000:02:00.0/usb5/5-1/5-1:1.1/ttyUSB1
lrwxrwxrwx  1 root root    0 2005-01-24 16:51 driver -> ../../../bus/usb-serial/drivers/generic

/sys/class/tty/<NULL>2:
insgesamt 0
-r--r--r--  1 root root 4096 2005-01-24 16:51 dev
lrwxrwxrwx  1 root root    0 2005-01-24 16:51 device -> ../../../devices/pci0000:00/0000:00:1e.0/0000:01:0b.0/0000:02:00.0/usb5/5-1/5-1:1.2/ttyUSB2
lrwxrwxrwx  1 root root    0 2005-01-24 16:51 driver -> ../../../bus/usb-serial/drivers/generic
mudshark:~#

> What does:
>   udevinfo -a -p /sys/class/tty/ttyUSB0

> print?

mudshark:~# udevinfo -a -p /sys/class/tty/ttyUSB0
couldn't get the class device
mudshark:~# udevinfo -a -p /sys/class/tty/\<NULL\>0/

udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.

device '/sys/class/tty/<NULL>0' has major:minor 0:0
  looking at class device '/sys/class/tty/<NULL>0':
    SYSFS{dev}="0:0"

follow the class device's "device"
  looking at the device chain at '/sys/devices/pci0000:00/0000:00:1e.0/0000:01:0b.0/0000:02:00.0/usb5/5-1/5-1:1.0/ttyUSB0':
    BUS="usb-serial"
    ID="ttyUSB0"
    SYSFS{detach_state}="0"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:1e.0/0000:01:0b.0/0000:02:00.0/usb5/5-1/5-1:1.0':
    BUS="usb"
    ID="5-1:1.0"
    SYSFS{bAlternateSetting}=" 0"
    SYSFS{bInterfaceClass}="ff"
    SYSFS{bInterfaceNumber}="00"
    SYSFS{bInterfaceProtocol}="ff"
    SYSFS{bInterfaceSubClass}="ff"
    SYSFS{bNumEndpoints}="03"
    SYSFS{detach_state}="0"
    SYSFS{interface}="Data Interface"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:1e.0/0000:01:0b.0/0000:02:00.0/usb5/5-1':
    BUS="usb"
    ID="5-1"
    SYSFS{bConfigurationValue}="1"
    SYSFS{bDeviceClass}="00"
    SYSFS{bDeviceProtocol}="00"
    SYSFS{bDeviceSubClass}="00"
    SYSFS{bMaxPower}="100mA"
    SYSFS{bNumConfigurations}="1"
    SYSFS{bNumInterfaces}=" 3"
    SYSFS{bcdDevice}="0000"
    SYSFS{bmAttributes}="e0"
    SYSFS{detach_state}="0"
    SYSFS{devnum}="2"
    SYSFS{idProduct}="5000"
    SYSFS{idVendor}="0af0"
    SYSFS{manufacturer}="Vodafone"
    SYSFS{maxchild}="0"
    SYSFS{product}="Vodafone Mobile Connect Card - 3G"
    SYSFS{serial}="Serial Number"
    SYSFS{speed}="12"
    SYSFS{version}=" 2.00"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:1e.0/0000:01:0b.0/0000:02:00.0/usb5':
    BUS="usb"
    ID="usb5"
    SYSFS{bConfigurationValue}="1"
    SYSFS{bDeviceClass}="09"
    SYSFS{bDeviceProtocol}="00"
    SYSFS{bDeviceSubClass}="00"
    SYSFS{bMaxPower}="  0mA"
    SYSFS{bNumConfigurations}="1"
    SYSFS{bNumInterfaces}=" 1"
    SYSFS{bcdDevice}="0206"
    SYSFS{bmAttributes}="c0"
    SYSFS{detach_state}="0"
    SYSFS{devnum}="1"
    SYSFS{idProduct}="0000"
    SYSFS{idVendor}="0000"
    SYSFS{manufacturer}="Linux 2.6.10-mudshark ohci_hcd"
    SYSFS{maxchild}="2"
    SYSFS{product}="OPTi Inc. 82C861"
    SYSFS{serial}="0000:02:00.0"
    SYSFS{speed}="12"
    SYSFS{version}=" 1.10"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:1e.0/0000:01:0b.0/0000:02:00.0':
    BUS="pci"
    ID="0000:02:00.0"
    SYSFS{class}="0x0c0310"
    SYSFS{detach_state}="0"
    SYSFS{device}="0xc861"
    SYSFS{irq}="11"
    SYSFS{local_cpus}="1"
    SYSFS{subsystem_device}="0xc861"
    SYSFS{subsystem_vendor}="0x1045"
    SYSFS{vendor}="0x1045"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:1e.0/0000:01:0b.0':
    BUS="pci"
    ID="0000:01:0b.0"
    SYSFS{class}="0x060700"
    SYSFS{detach_state}="0"
    SYSFS{device}="0x0617"
    SYSFS{irq}="11"
    SYSFS{local_cpus}="1"
    SYSFS{subsystem_device}="0x0001"
    SYSFS{subsystem_vendor}="0x1179"
    SYSFS{vendor}="0x1179"

  looking at the device chain at '/sys/devices/pci0000:00/0000:00:1e.0':
    BUS="pci"
    ID="0000:00:1e.0"
    SYSFS{class}="0x060400"
    SYSFS{detach_state}="0"
    SYSFS{device}="0x2448"
    SYSFS{irq}="0"
    SYSFS{local_cpus}="1"
    SYSFS{subsystem_device}="0x0000"
    SYSFS{subsystem_vendor}="0x0000"
    SYSFS{vendor}="0x8086"

  looking at the device chain at '/sys/devices/pci0000:00':
    BUS=""
    ID="pci0000:00"
    SYSFS{detach_state}="0"

Does this help?

Thanks for looking into the issue,
-- 
Marc "Backlog" Packenius


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Problem with udev & Vodafone UMTS card

[Kay Sievers]

On Mon, 2005-01-24 at 16:58 +0100, Marc Packenius wrote:
> Hi Kay,
> 
> Kay Sievers <kay.sievers@vrfy.org> writes:
> 
> > On Mon, 2005-01-24 at 15:15 +0100, Marc Packenius wrote:
> >> after installing udev on a Debian/sid-powered Toshiba Satellite
> >> notebook, the Vodafone UMTS card stopped working.
> >> 
> >> This pc-card includes a USB controller and feeds three serial character
> >> devices when installed properly. They're called "/dev/ttyUSB[0-2]".
> >> 
> >> When using udev, those device nodes are not created properly, instead
> >> the dev directory shows files with the filename "/dev/<NULL>[0-2]", e.g. 
> >> "/dev/<NULL>0".
> 
> >> => /var/log/daemon.log <=
> >> Jan 24 14:59:35 mudshark udev[3157]: creating device node '/dev/<NULL>0'
> >> Jan 24 14:59:35 mudshark udev[3169]: creating device node '/dev/<NULL>1'
> >> Jan 24 14:59:35 mudshark udev[3179]: creating device node '/dev/<NULL>2'
> 
> > How does:
> >   ls -l /sys/class/tty/ttyUSB*
> 
> > look like, or any other suspicious entry in this directory?
> 
> mudshark:~# ls -l /sys/class/tty/ttyUSB*
> ls: /sys/class/tty/ttyUSB*: Datei oder Verzeichnis nicht gefunden
> mudshark:~# ls -l /sys/class/tty/*NULL*

That's a kernel bug and not a udev issue. You may try to work around
this by placing:
  KERNEL="<NULL>*", NAME="ttyUSB%n"

in a /etc/udev/rules.d/ file.

Greg, any idea what is causing this in the serial driver?

Thanks,
Kay



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Problem with udev & Vodafone UMTS card

[Greg KH]

On Mon, Jan 24, 2005 at 05:17:53PM +0100, Kay Sievers wrote:
> On Mon, 2005-01-24 at 16:58 +0100, Marc Packenius wrote:
> > Hi Kay,
> > 
> > Kay Sievers <kay.sievers@vrfy.org> writes:
> > 
> > > On Mon, 2005-01-24 at 15:15 +0100, Marc Packenius wrote:
> > >> after installing udev on a Debian/sid-powered Toshiba Satellite
> > >> notebook, the Vodafone UMTS card stopped working.
> > >> 
> > >> This pc-card includes a USB controller and feeds three serial character
> > >> devices when installed properly. They're called "/dev/ttyUSB[0-2]".
> > >> 
> > >> When using udev, those device nodes are not created properly, instead
> > >> the dev directory shows files with the filename "/dev/<NULL>[0-2]", e.g. 
> > >> "/dev/<NULL>0".
> > 
> > >> => /var/log/daemon.log <=
> > >> Jan 24 14:59:35 mudshark udev[3157]: creating device node '/dev/<NULL>0'
> > >> Jan 24 14:59:35 mudshark udev[3169]: creating device node '/dev/<NULL>1'
> > >> Jan 24 14:59:35 mudshark udev[3179]: creating device node '/dev/<NULL>2'
> > 
> > > How does:
> > >   ls -l /sys/class/tty/ttyUSB*
> > 
> > > look like, or any other suspicious entry in this directory?
> > 
> > mudshark:~# ls -l /sys/class/tty/ttyUSB*
> > ls: /sys/class/tty/ttyUSB*: Datei oder Verzeichnis nicht gefunden
> > mudshark:~# ls -l /sys/class/tty/*NULL*
> 
> That's a kernel bug and not a udev issue. You may try to work around
> this by placing:
>   KERNEL="<NULL>*", NAME="ttyUSB%n"
> 
> in a /etc/udev/rules.d/ file.
> 
> Greg, any idea what is causing this in the serial driver?

No I do not.  What kernel version is this?  What driver is this (the
usb-serial generic driver, or some other usb-serial driver?)

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Problem with udev & Vodafone UMTS card

[Marc Packenius]

Hi Greg,

Greg KH <greg@kroah.com> writes:
> On Mon, Jan 24, 2005 at 05:17:53PM +0100, Kay Sievers wrote:
>> On Mon, 2005-01-24 at 16:58 +0100, Marc Packenius wrote:
>> > Hi Kay,
>> > 
>> > Kay Sievers <kay.sievers@vrfy.org> writes:
>> > 
>> > > On Mon, 2005-01-24 at 15:15 +0100, Marc Packenius wrote:
>> > >> after installing udev on a Debian/sid-powered Toshiba Satellite
>> > >> notebook, the Vodafone UMTS card stopped working.
>> > >> 
>> > >> This pc-card includes a USB controller and feeds three serial character
>> > >> devices when installed properly. They're called "/dev/ttyUSB[0-2]".
>> > >> 
>> > >> When using udev, those device nodes are not created properly, instead
>> > >> the dev directory shows files with the filename "/dev/<NULL>[0-2]", e.g. 
>> > >> "/dev/<NULL>0".
>> > 
>> > >> => /var/log/daemon.log <=
>> > >> Jan 24 14:59:35 mudshark udev[3157]: creating device node '/dev/<NULL>0'
>> > >> Jan 24 14:59:35 mudshark udev[3169]: creating device node '/dev/<NULL>1'
>> > >> Jan 24 14:59:35 mudshark udev[3179]: creating device node '/dev/<NULL>2'
>> > 
>> > > How does:
>> > >   ls -l /sys/class/tty/ttyUSB*
>> > 
>> > > look like, or any other suspicious entry in this directory?
>> > 
>> > mudshark:~# ls -l /sys/class/tty/ttyUSB*
>> > ls: /sys/class/tty/ttyUSB*: Datei oder Verzeichnis nicht gefunden
>> > mudshark:~# ls -l /sys/class/tty/*NULL*
>> 
>> That's a kernel bug and not a udev issue. You may try to work around
>> this by placing:
>> KERNEL="<NULL>*", NAME="ttyUSB%n"
>> 
>> in a /etc/udev/rules.d/ file.
>> 
>> Greg, any idea what is causing this in the serial driver?

> No I do not.  What kernel version is this?  What driver is this (the
> usb-serial generic driver, or some other usb-serial driver?)

That's with kernels that I built locally on a Debian/sid system. I can
reproduce the behaviour with Debian-patched 2.6.8 to 2.6.10 and vanilla
2.6.10.

The driver is usb-serial generic. Inserting the card and loading the
driver using

  modprobe -v usbserial vendor=0xaf0 product=0x5000

looks like this (with udev not installed):

Feb  1 23:49:03 mudshark kernel: PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
Feb  1 23:49:03 mudshark pci.agent[3255]:      ohci-hcd: already loaded
Feb  1 23:49:03 mudshark kernel: ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
Feb  1 23:49:03 mudshark kernel: ohci_hcd 0000:02:00.0: OPTi Inc. 82C861 (#2)
Feb  1 23:49:03 mudshark kernel: ohci_hcd 0000:02:00.0: irq 11, pci mem 0x1f800000
Feb  1 23:49:03 mudshark kernel: ohci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 5
Feb  1 23:49:03 mudshark kernel: ohci_hcd 0000:02:00.0: WARNING: OPTi workarounds unavailable
Feb  1 23:49:03 mudshark kernel: hub 5-0:1.0: USB hub found
Feb  1 23:49:03 mudshark kernel: hub 5-0:1.0: 2 ports detected
Feb  1 23:49:08 mudshark kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
Feb  1 23:49:08 mudshark kernel: usbcore: registered new driver usbserial_generic
Feb  1 23:49:08 mudshark kernel: usbcore: registered new driver usbserial
Feb  1 23:49:08 mudshark kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
Feb  1 23:49:14 mudshark kernel: usb 5-1: new full speed USB device using ohci_hcd and address 2
Feb  1 23:49:14 mudshark kernel: usbserial_generic 5-1:1.0: Generic converter detected
Feb  1 23:49:14 mudshark kernel: usb 5-1: Generic converter now attached to ttyUSB0
Feb  1 23:49:14 mudshark kernel: usbserial_generic 5-1:1.1: Generic converter detected
Feb  1 23:49:14 mudshark kernel: usb 5-1: Generic converter now attached to ttyUSB1
Feb  1 23:49:14 mudshark kernel: usbserial_generic 5-1:1.2: Generic converter detected
Feb  1 23:49:14 mudshark kernel: usb 5-1: Generic converter now attached to ttyUSB2

If I can provide more information, please let me know.

Regards,
-- 
Marc "Backlog" Packenius


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Problem with udev & Vodafone UMTS card

[Kay Sievers]

On Wed, Feb 02, 2005 at 02:44:05AM +0100, Marc Packenius wrote:
> Greg KH <greg@kroah.com> writes:
> > On Mon, Jan 24, 2005 at 05:17:53PM +0100, Kay Sievers wrote:
> >> On Mon, 2005-01-24 at 16:58 +0100, Marc Packenius wrote:
> >> > Kay Sievers <kay.sievers@vrfy.org> writes:
> >> > > On Mon, 2005-01-24 at 15:15 +0100, Marc Packenius wrote:
> >> > >> after installing udev on a Debian/sid-powered Toshiba Satellite
> >> > >> notebook, the Vodafone UMTS card stopped working.
> >> > >> 
> >> > >> This pc-card includes a USB controller and feeds three serial character
> >> > >> devices when installed properly. They're called "/dev/ttyUSB[0-2]".
> >> > >> 
> >> > >> When using udev, those device nodes are not created properly, instead
> >> > >> the dev directory shows files with the filename "/dev/<NULL>[0-2]", e.g. 
> >> > >> "/dev/<NULL>0".
> >> > 
> >> > >> => /var/log/daemon.log <=
> >> > >> Jan 24 14:59:35 mudshark udev[3157]: creating device node '/dev/<NULL>0'
> >> > >> Jan 24 14:59:35 mudshark udev[3169]: creating device node '/dev/<NULL>1'
> >> > >> Jan 24 14:59:35 mudshark udev[3179]: creating device node '/dev/<NULL>2'
> >> 
> >> That's a kernel bug and not a udev issue. You may try to work around
> >> this by placing:
> >> KERNEL="<NULL>*", NAME="ttyUSB%n"
> >> 
> >> in a /etc/udev/rules.d/ file.
> >> 
> >> Greg, any idea what is causing this in the serial driver?
> 
> > No I do not.  What kernel version is this?  What driver is this (the
> > usb-serial generic driver, or some other usb-serial driver?)
> 
> That's with kernels that I built locally on a Debian/sid system. I can
> reproduce the behaviour with Debian-patched 2.6.8 to 2.6.10 and vanilla
> 2.6.10.
> 
> The driver is usb-serial generic. Inserting the card and loading the
> driver using
> 
>   modprobe -v usbserial vendor=0xaf0 product=0x5000

This patch may fix it. We call the probe function before the driver
struct is initialized. You may be able to work around this bug by
loading the module without the card inserted.

Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>

=== drivers/usb/serial/usb-serial.c 1.128 vs edited ==--- 1.128/drivers/usb/serial/usb-serial.c	2004-12-21 02:15:10 +01:00
+++ edited/drivers/usb/serial/usb-serial.c	2005-02-02 04:51:32 +01:00
@@ -1286,6 +1286,19 @@ static int __init usb_serial_init(void)
 	if (!usb_serial_tty_driver)
 		return -ENOMEM;
 
+	usb_serial_tty_driver->owner = THIS_MODULE;
+	usb_serial_tty_driver->driver_name = "usbserial";
+	usb_serial_tty_driver->devfs_name = "usb/tts/";
+	usb_serial_tty_driver->name = 	"ttyUSB";
+	usb_serial_tty_driver->major = SERIAL_TTY_MAJOR;
+	usb_serial_tty_driver->minor_start = 0;
+	usb_serial_tty_driver->type = TTY_DRIVER_TYPE_SERIAL;
+	usb_serial_tty_driver->subtype = SERIAL_TYPE_NORMAL;
+	usb_serial_tty_driver->flags = TTY_DRIVER_REAL_RAW | TTY_DRIVER_NO_DEVFS;
+	usb_serial_tty_driver->init_termios = tty_std_termios;
+	usb_serial_tty_driver->init_termios.c_cflag = B9600 | CS8 | CREAD | HUPCL | CLOCAL;
+	tty_set_operations(usb_serial_tty_driver, &serial_ops);
+
 	/* Initialize our global data */
 	for (i = 0; i < SERIAL_TTY_MINORS; ++i) {
 		serial_table[i] = NULL;
@@ -1304,18 +1317,6 @@ static int __init usb_serial_init(void)
 		goto exit_generic;
 	}
 
-	usb_serial_tty_driver->owner = THIS_MODULE;
-	usb_serial_tty_driver->driver_name = "usbserial";
-	usb_serial_tty_driver->devfs_name = "usb/tts/";
-	usb_serial_tty_driver->name = 	"ttyUSB";
-	usb_serial_tty_driver->major = SERIAL_TTY_MAJOR;
-	usb_serial_tty_driver->minor_start = 0;
-	usb_serial_tty_driver->type = TTY_DRIVER_TYPE_SERIAL;
-	usb_serial_tty_driver->subtype = SERIAL_TYPE_NORMAL;
-	usb_serial_tty_driver->flags = TTY_DRIVER_REAL_RAW | TTY_DRIVER_NO_DEVFS;
-	usb_serial_tty_driver->init_termios = tty_std_termios;
-	usb_serial_tty_driver->init_termios.c_cflag = B9600 | CS8 | CREAD | HUPCL | CLOCAL;
-	tty_set_operations(usb_serial_tty_driver, &serial_ops);
 	result = tty_register_driver(usb_serial_tty_driver);
 	if (result) {
 		err("%s - tty_register_driver failed", __FUNCTION__);



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Problem with udev & Vodafone UMTS card

[Greg KH]

On Wed, Feb 02, 2005 at 05:13:26AM +0100, Kay Sievers wrote:
> On Wed, Feb 02, 2005 at 02:44:05AM +0100, Marc Packenius wrote:
> > Greg KH <greg@kroah.com> writes:
> > > On Mon, Jan 24, 2005 at 05:17:53PM +0100, Kay Sievers wrote:
> > >> On Mon, 2005-01-24 at 16:58 +0100, Marc Packenius wrote:
> > >> > Kay Sievers <kay.sievers@vrfy.org> writes:
> > >> > > On Mon, 2005-01-24 at 15:15 +0100, Marc Packenius wrote:
> > >> > >> after installing udev on a Debian/sid-powered Toshiba Satellite
> > >> > >> notebook, the Vodafone UMTS card stopped working.
> > >> > >> 
> > >> > >> This pc-card includes a USB controller and feeds three serial character
> > >> > >> devices when installed properly. They're called "/dev/ttyUSB[0-2]".
> > >> > >> 
> > >> > >> When using udev, those device nodes are not created properly, instead
> > >> > >> the dev directory shows files with the filename "/dev/<NULL>[0-2]", e.g. 
> > >> > >> "/dev/<NULL>0".
> > >> > 
> > >> > >> => /var/log/daemon.log <=
> > >> > >> Jan 24 14:59:35 mudshark udev[3157]: creating device node '/dev/<NULL>0'
> > >> > >> Jan 24 14:59:35 mudshark udev[3169]: creating device node '/dev/<NULL>1'
> > >> > >> Jan 24 14:59:35 mudshark udev[3179]: creating device node '/dev/<NULL>2'
> > >> 
> > >> That's a kernel bug and not a udev issue. You may try to work around
> > >> this by placing:
> > >> KERNEL="<NULL>*", NAME="ttyUSB%n"
> > >> 
> > >> in a /etc/udev/rules.d/ file.
> > >> 
> > >> Greg, any idea what is causing this in the serial driver?
> > 
> > > No I do not.  What kernel version is this?  What driver is this (the
> > > usb-serial generic driver, or some other usb-serial driver?)
> > 
> > That's with kernels that I built locally on a Debian/sid system. I can
> > reproduce the behaviour with Debian-patched 2.6.8 to 2.6.10 and vanilla
> > 2.6.10.
> > 
> > The driver is usb-serial generic. Inserting the card and loading the
> > driver using
> > 
> >   modprobe -v usbserial vendor=0xaf0 product=0x5000
> 
> This patch may fix it. We call the probe function before the driver
> struct is initialized. You may be able to work around this bug by
> loading the module without the card inserted.
> 
> Signed-off-by: Kay Sievers <kay.sievers@vrfy.org>

Marc, does this fix your issue?

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Problem with udev & Vodafone UMTS card

[Marc Packenius]

Hi all,

On Thu, 3 Feb 2005 15:38:13 -0800, Greg KH <greg@kroah.com> said:
> On Wed, Feb 02, 2005 at 05:13:26AM +0100, Kay Sievers wrote:
>> On Wed, Feb 02, 2005 at 02:44:05AM +0100, Marc Packenius wrote:
>> > The driver is usb-serial generic. Inserting the card and loading the
>> > driver using
>> > 
>> >   modprobe -v usbserial vendor=0xaf0 product=0x5000
>> 
>> This patch may fix it. We call the probe function before the driver
>> struct is initialized. You may be able to work around this bug by
>> loading the module without the card inserted.

> Marc, does this fix your issue?

Indeed, it does, apparently without any bad side effects and with the
card inserted all the time. Thanks to y'all for your efforts!

Regards,
-- 
Marc "Backlog" Packenius


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel