[mdlug] Minicom device permission error [Was:USB device not accepting new address]
R Kannan
rkannan at peoplepc.com
Thu Jan 25 19:12:19 EST 2007
On Thu, 2007-01-25 at 09:29, Ingles, Raymond wrote:
> > From: R Kannan
>
> > drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver
> > visor ttyUSB0: Device lied about number of ports, please use a lower one.
>
> > Note that I do not have the 'Handspring Visor' PDA but a mobile phone.
>
> Try temporarily moving/renaming the "visor.ko" driver module so that it's not
> loaded, and see if it works then.
>
Thanks. That worked. Now the usb serial device is back to /dev/ACM0.
'dmesg' returns
usb 2-2: new full speed USB device using uhci_hcd and address 5
usb 2-2: new device found, idVendor=04e8, idProduct=6601
usb 2-2: new device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-2: Product: SAMSUNG CDMA Technologies
usb 2-2: Manufacturer: SAMSUNG Electronics Co.,Ltd.
usb 2-2: SerialNumber:
usb 2-2: configuration #1 chosen from 1 choice
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for
generic
usbcore: registered new driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
cdc_acm 2-2:1.0: ttyACM0: USB ACM device
usbcore: registered new driver cdc_acm
How does 'hotsync' decide what device to use (/dev/ttyACM0 or
/dev/ttyUSB2) and what driver module to load?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mdlug.org/pipermail/mdlug/attachments/20070125/41daf7de/attachment-0001.html>
More information about the mdlug
mailing list