<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.0.8">
</HEAD>
<BODY>
On Mon, 2007-01-22 at 19:39, R Kannan wrote:
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#737373"><I>On Mon, 2007-01-22 at 08:41, Joseph C. Bender wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>R Kannan wrote:
> LANG/ja
> LANG/ko
> LANG/ru
> minicom: cannot open /dev/ttyACM0: Permission denied
> I checked the permissions on the device 'file' and it seems to have the
> same permission on both machines.
>
Care to share what those perms are?
Generally, if the user isn't part of the group that the port is "owned"
by and the perms are not at least rw for the group, it's not going to work.
ls -l output for my EVDO card on my laptop (Ubuntu 6.06) looks like this:
crw-rw---- 1 root dialout 166,0 2007-01-22 08:31 /dev/ttyACM0
Then in /etc/group, the dialout entry is as follows:
dialout:x:20:cupsys,jcbender</PRE>
</BLOCKQUOTE>
<BR>
ls -l /dev/ACM0<BR>
<BR>
crw-rw---- 1 root uucp 166, 0 2007-01-22 19:19 /dev/ttyACM0<BR>
<BR>
The group uucp includes the user who is running 'minicom'<BR>
<BR>
grep uucp /etc/group<BR>
uucp:x:14:<user1>,<user2><BR>
</I></FONT><BR>
</BLOCKQUOTE>
<BR>
I was wrong. The group 'uucp' did not include the user who was running 'minicom' which explains why I could not run minicom as a user.<BR>
<BR>
But now I have another problem. I used to talk to the mobile phone through /tty/usbACM0 but now suddenly the 'hotsync' decided to make the phone available through /dev/ttyUSB2. 'minicom' works the same way with the device set to /dev/ttyUSB2 but I wonder how that got changed. 'dmesg' returns<BR>
<BR>
usb 2-2: new full speed USB device using uhci_hcd and address 9<BR>
usb 2-2: new device found, idVendor=04e8, idProduct=6601<BR>
usb 2-2: new device strings: Mfr=1, Product=2, SerialNumber=3<BR>
usb 2-2: Product: SAMSUNG CDMA Technologies<BR>
usb 2-2: Manufacturer: SAMSUNG Electronics Co.,Ltd.<BR>
usb 2-2: SerialNumber:<BR>
<BR>
usb 2-2: configuration #1 chosen from 1 choice<BR>
usbcore: registered new driver usbserial<BR>
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic<BR>
usbcore: registered new driver usbserial_generic<BR>
drivers/usb/serial/usb-serial.c: USB Serial Driver core<BR>
drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OS<BR>
drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5<BR>
drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 5.0<BR>
usb 2-2: palm_os_4_probe - error -32 getting connection info<BR>
visor 2-2:1.0: Handspring Visor / Palm OS converter detected<BR>
usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB0<BR>
usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB1<BR>
usb 2-2: palm_os_4_probe - error -32 getting connection info<BR>
visor 2-2:1.1: Handspring Visor / Palm OS converter detected<BR>
usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB2<BR>
usb 2-2: Handspring Visor / Palm OS converter now attached to ttyUSB3<BR>
usbcore: registered new driver visor<BR>
drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver<BR>
usbcore: registered new driver cdc_acm<BR>
drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters<BR>
visor ttyUSB0: Device lied about number of ports, please use a lower one.<BR>
<BR>
Note that I do not have the 'Handspring Visor' PDA but a mobile phone.<BR>
<BR>
Any ideas?<BR>
<BR>
TIA<BR>
<BR>
</BODY>
</HTML>