View previous topic :: View next topic |
Author |
Message |
j3pup n00b

Joined: 04 Nov 2004 Posts: 4
|
Posted: Fri Mar 11, 2005 5:11 am Post subject: Bitpim Vx6000 UDev Guide |
|
|
I just upgraded to kernel 2.6 and switched to Udev. I couldn't find any help on UDEV and bitpim so here is how I got it to work. Bitpim doesn;t see any serial ports but, in my /var/log/messages file it said udev[21872]: configured rule in '/etc/udev/rules.d/50-udev.rules[137]' applied, 'ttyUSB0' becomes 'tts/USB%n'. So I pointed my bitpim towards /dev/tts/USB0 (Because USB0 was the only device in that directory). And voilla works...
Hope it helps someone..... |
|
Back to top |
|
 |
Hypnos Advocate


Joined: 18 Jul 2002 Posts: 2889 Location: Omnipresent
|
|
Back to top |
|
 |
ihd n00b

Joined: 31 Aug 2005 Posts: 9
|
Posted: Wed Dec 07, 2005 3:15 pm Post subject: |
|
|
I see the phone in Bitpim comm ports but i can't detect it.
/var/log/everything/current
Code: | Dec 7 16:02:53 [kernel] usb 5-2: new full speed USB device using uhci_hcd and address 14
Dec 7 16:02:53 [kernel] usb 5-2: Product: LG Mobile USB Modem
Dec 7 16:02:53 [kernel] usb 5-2: Manufacturer: LG Eletronics, Inc |
What should i do to get udev to make /dev/ttyUSB* ?
Code: | lsusb
Bus 005 Device 014: ID 1004:6000 LG Electronics, Inc. VX4400/VX6000 Cellphone |
|
|
Back to top |
|
 |
Hypnos Advocate


Joined: 18 Jul 2002 Posts: 2889 Location: Omnipresent
|
Posted: Thu Dec 08, 2005 5:19 am Post subject: |
|
|
As I understand it:
udev just provides a framework for identifying devices uniquely and setting consistent /dev/ filenames with consistent permissions.
However, hotplug is what really sets the access to the physical device, upon connecting and registering with the driver. If you follow the bitpim docs closely, it only instructs you to setup a hotplug rule. Bitpim doesn't even use /dev/ttyUSB* -- it uses the USB diagnostic interface which doesn't have a /dev/ file. _________________ Personal overlay | Simple backup scheme |
|
Back to top |
|
 |
|