Hi all,

I am running Slackware 11 on my laptop. I have a device that uses the usbserial module. Every time I start the system I have to make the /dev/ttyUSB0 node and then insert the module with the vendor and product parameters. I thought that the node should be permanent and the vendor, product stuff was added to a file somewhere so every time I plugged in my device it would be recognized.

So I just added

modprobe usbserial vendor=0x03EB product=0x6124
mknod -m 0666 /dev/ttyUSB0 c 188 0

(this coresponds to Atmel's AT91SAM7S-EK evaluation board if you were curious)

to rc.local and called it good.

Now I have a USB to Serial converter that uses the module pl2303 and this one depends on the usbserial module. So now the usbserial module is already loaded when rc.local gets called and my device doesn't work till I

remove pl2303
remove usbserial
add usbserial with the vendor=0x03EB product=0x6124 parameters
add pl2303
make a second node for USB1 (for the usb to serial converter, Atmel is on USB0)

What am I missing here? As of now I have that whole process in rc.local but I dont feel that I should have to do that every time I want to use this thing.

Ryan

In recent 2.6 kernels, most (all?) of the entries in the /dev directory are dynamically created by udev. So they won't persist across boots. Sadly, at this time, that is about the extent of my knowledge of udev. (Just enough to be dangerous. ) But my guess is the solution to your problem lies in figuring out how udev works with all of this.

Good luck.

I've had similar problems on Slackware 11.0, but they just went away after upgrading to Slackware 12.0. Could it be HAL or something that's helping out in all this ?

Ok so I know to look into udev. I have been reading for a day or so and I will get that straightened out and report back. How about the modules problem though, how do I get them to load properly without having to remove and add them in rc.local?

Within my ignorance (let the buyer beware! ) I am thinking it is all tied together within the udev paradigm. Have you considered trying Slackware 12.0 and seeing if the whole problem goes away as H_TeXMeX_H suggested?