From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Karl O. Pinc" Date: Wed, 03 Dec 2008 18:49:58 +0000 Subject: Re: Udev rule for HSDPA modem Message-Id: <1228330198l.20654l.7l@mofo> List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On 12/03/2008 11:37:10 AM, Kay Sievers wrote: > On Wed, Dec 3, 2008 at 18:06, Karl O. Pinc 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 > >> wrote: > >> > > On Wed, Dec 3, 2008 at 07:45, Greg KH wrote: > >> > >> On Sun, Nov 30, 2008 at 06:21:11AM +0100, Kay Sievers wrote: > >> > >>> On Sat, Nov 29, 2008 at 18:37, Greg KH > 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 Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein