From: Marc Packenius <marc-dated-1107785560.cbb185-dated-1107785750.770de9@zappa.freen
To: linux-hotplug@vger.kernel.org
Subject: Problem with udev & Vodafone UMTS card
Date: Mon, 24 Jan 2005 14:15:49 +0000 [thread overview]
Message-ID: <87ekga9alm.fsf@yerbouti.a42.de> (raw)
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
next reply other threads:[~2005-01-24 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 14:15 Marc Packenius [this message]
2005-01-24 14:30 ` Problem with udev & Vodafone UMTS card Kay Sievers
2005-01-24 15:58 ` Marc Packenius
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=87ekga9alm.fsf@yerbouti.a42.de \
--to=marc-dated-1107785560.cbb185-dated-1107785750.770de9@zappa.freen \
--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).