I currently have 10 USB to serial adaptors all using PL2303 chip
Ubuntu detects them OK and assigns ttyUSBx numbers at it's choice on
bootup
This machine is rarely rebooted but I need it to assign fixed tty number
per device just incase a reboot/power fail happens and also if a device
is
The devices itself, if it cheap, may not have S/N due to EEPROM not
soldered (or so)... You can check this under Windows, and, imho, if re-
plugging to different ports under Windows gives you same COMxx port per
device, then maybe problem in linux (kernel)... For my FT232BM's, all
good in Windows,
I have some FTDI based FT232's and have the same issues with no s/n
I don't know what to do at this stage
maybe someone can confirm a device which works ok with s/n detected in
udev?
2008/11/11 jpka [EMAIL PROTECTED]
The devices itself, if it cheap, may not have S/N due to EEPROM not
Original poster: The only real solution is to find a USB serial adapter
that includes a serial number: I bought some from Dontronics in
Australia.
There is no real way to tell from the sales brochures, though. I was
just lucky. Spending more money is no guarantee, but it makes it more
likely that
I have tested another pl2303 based device (like in the original report)
and there is no serial number. This is maybe a bug in the driver, at
least if Windows is able to extract a serial number. Or does Windows use
some USB port id? Stephan, does Windows recognize each converter
correctly if you
** Attachment added: udevadm info --attribute-walk -p /class/tty/ttyUSB0
http://launchpadlibrarian.net/17951797/udevadm-attr-walk.txt
--
Two USB serial adapters get different /dev/ttyUSBn names after reboot
https://bugs.launchpad.net/bugs/107208
You received this bug notification because you
Sorry, those two logs are from the wrong system.
Is it possible to attach more than one file at a time?
** Attachment added: dmesg
http://launchpadlibrarian.net/17921767/dmesg
--
Two USB serial adapters get different /dev/ttyUSBn names after reboot
https://bugs.launchpad.net/bugs/107208
You
** Attachment added: udev
http://launchpadlibrarian.net/17921789/udev
--
Two USB serial adapters get different /dev/ttyUSBn names after reboot
https://bugs.launchpad.net/bugs/107208
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: lsusb -v
http://launchpadlibrarian.net/17921801/lsusb-v.txt
--
Two USB serial adapters get different /dev/ttyUSBn names after reboot
https://bugs.launchpad.net/bugs/107208
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The rules appear to be working.
However as you note, at least one of the devices doesn't get a name at
all -- this isn't a udev bug, but a kernel bug for not detecting it
(most likely the ftdi_sio driver).
Could you open a new bug against linux saying that a USB serial
adapter is not being
And this is still a Won't Fix.
** Changed in: udev (Ubuntu)
Assignee: Tormod Volden (tormodvolden) = (unassigned)
Status: Incomplete = Won't Fix
--
Two USB serial adapters get different /dev/ttyUSBn names after reboot
https://bugs.launchpad.net/bugs/107208
You received this bug
'lsusb -v' will show a unique serial number (iSerial) for each device.
I have three SIIG USB Serial adapters.
Bus 002 Device 004: ID 0b39:0421 Omnidirectional Control Technology, Inc.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.10
On Tue, 2008-09-23 at 19:24 +, Roger C. Pao wrote:
'lsusb -v' will show a unique serial number (iSerial) for each device.
I have three SIIG USB Serial adapters.
*snip*
iSerial 3 OCBAKZ7N
iSerial 3 OCBQH84W
iSerial 3 OCBPJ9HM
*snip*
Before touching /etc/udev/rules.d, only one USB Serial adapter would be
assigned ttyUSB0. The others would not be mapped in.
After adding the udev rules below, they are now working as expected, but
the computer required a power cycle or the USB Serial adapters required
being unplugged and
Could you attach /var/log/udev and /var/log/dmesg for a boot where they
are not mapped in correctly?
--
Two USB serial adapters get different /dev/ttyUSBn names after reboot
https://bugs.launchpad.net/bugs/107208
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: The three USB Serial adapters are plugged in, but only
two are detected.
http://launchpadlibrarian.net/17898314/udev
--
Two USB serial adapters get different /dev/ttyUSBn names after reboot
https://bugs.launchpad.net/bugs/107208
You received this bug notification
The three USB Serial adapters are plugged in, but only two are detected.
The previous attachement is /var/log/udev.
** Attachment added: /var/log/dmesg
http://launchpadlibrarian.net/17898329/dmesg
--
Two USB serial adapters get different /dev/ttyUSBn names after reboot
Could you also provide lsusb output
--
Two USB serial adapters get different /dev/ttyUSBn names after reboot
https://bugs.launchpad.net/bugs/107208
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I think this is the same in Intrepid (no way to distinguish two adapters
of the same brand). I will check.
** Changed in: udev (Ubuntu)
Assignee: (unassigned) = Tormod Volden (tormodvolden)
Status: Invalid = Incomplete
--
Two USB serial adapters get different /dev/ttyUSBn names
My USB serial adapter does not create /dev/ttyUSBn device at all!
See Bug #251952
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/251952
--
Two USB serial adapters get different /dev/ttyUSBn names after reboot
https://bugs.launchpad.net/bugs/107208
You received this bug notification because
Thanks to all people who write and debug Ubuntu!
I have same problem: ttyUSB* names assigns randomly when I replug devices.
All devices guaranteed to have S/N (it may be seen in Windows).
Ubuntu command-line tools not discover this.
I use last Ubuntu with all updates. I use 'apt-get remove
This is not a kernel issue, this is a by default behaviour:
You can/should use udev to force your kernel assign arbitrary names to devices
as it finds them.
Take a look at my file /etc/udev/rules.d/50-local.rules:
# REGLAS PARA LOS DISPOSITIVOS QUE QUEREMOS CONTROLAR POR NOMBRE
BUS==usb,
Thanks for the reply.I have read various HowTos and will try them out
shortly.
However, this is only a partial solution. It depends on having USB-
serial adapters from different manufacturers. At work, I have FOUR USB-
serial adapters, all made by Bafo, connected to the following devices:
* a
23 matches
Mail list logo
