From: Marc Packenius <marc-dated-1107791918.6bb4b2@zappa.freenet-rz.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Problem with udev & Vodafone UMTS card
Date: Mon, 24 Jan 2005 15:58:37 +0000 [thread overview]
Message-ID: <873bwqn7iq.fsf@yerbouti.a42.de> (raw)
In-Reply-To: <87ekga9alm.fsf@yerbouti.a42.de>
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
next prev parent reply other threads:[~2005-01-24 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 14:15 Problem with udev & Vodafone UMTS card Marc Packenius
2005-01-24 14:30 ` Kay Sievers
2005-01-24 15:58 ` Marc Packenius [this message]
2005-01-24 16:17 ` Kay Sievers
2005-01-31 8:20 ` Greg KH
2005-02-02 1:44 ` Marc Packenius
2005-02-02 4:13 ` Kay Sievers
2005-02-03 23:38 ` Greg KH
2005-02-05 2:02 ` Marc Packenius
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873bwqn7iq.fsf@yerbouti.a42.de \
--to=marc-dated-1107791918.6bb4b2@zappa.freenet-rz.de \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).