From: Marc Packenius <marc@freenet-rz.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Problem with udev & Vodafone UMTS card
Date: Wed, 02 Feb 2005 01:44:05 +0000 [thread overview]
Message-ID: <87pszj3fdm.fsf@yerbouti.a42.de> (raw)
In-Reply-To: <87ekga9alm.fsf@yerbouti.a42.de>
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
next prev parent reply other threads:[~2005-02-02 1:44 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
2005-01-24 16:17 ` Kay Sievers
2005-01-31 8:20 ` Greg KH
2005-02-02 1:44 ` Marc Packenius [this message]
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=87pszj3fdm.fsf@yerbouti.a42.de \
--to=marc@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).