On 8/11/07, Florian Kulzer <[EMAIL PROTECTED]> wrote:

> On Fri, Aug 10, 2007 at 21:34:08 -0400, Michael Habashy wrote:
> > On 8/10/07, Florian Kulzer wrote:
>
> [...]
>
> > > Now, coming back to your problem: Since your example configuration
> file
> > > mentions /dev/ttyS0 it would seem that kannel wants to talk to the
> phone
> > > like to a serial modem. Therefore you will probably have to use
> > > something like /dev/ttyUSB0 for a USB-connected mobile. If you cannot
> > > find such a device node after plugging in the phone then it may be
> > > necessary to do "modprobe usb_serial" as root. If that does not help
> > > then you might have to load an additional kernel module specific to
> your
> > > type of cell phone. (Please note that I have never used kannel,
> > > therefore I can only offer speculation based on what I know about USB
> > > devices and udev in general.)
> >
> > Thanks for the great reply. I think you put me closer ---but I am not
> really
> > there yet.  To recap:
> > 1. the usbdev1.1_ep00 are basically useless.
>
> I am sure that they serve a purpose in the system, but I think the
> normal user does not have to interact directly with them.
>
> > 2. I have to load something else in order to get a usefull /dev/tty*  to
> > refer to.
>
> If the kernel recognizes a new device then the proper module(s) will be
> loaded (if they are available) and udev will create the necessary device
> nodes in /dev/. For fully supported devices this should all happen
> automatically. If a device is not well supported then it can be very
> difficult, or even impossible, to get it to work.
>
> > Do you know what that driver or module that I need to load for Cingular
> 8125
> > ?
>
> Unfortunately not. I just grepped for "cingular" in my kernel source
> directory and I did not get any hits. We would probably have to know
> what the relevant chipset or interface standard is called, but I have no
> clue about mobile phones (I don't own one), so I do not even know where
> to begin here.
>
> > I have loaded usbserial...but nothing happened...or at least i do not
> know
> > if anything happened..nothing was referenced that was usefull.  Do you
> know
> > where I can check?
>
> I am not sure if this was already covered earlier in this thread: Plug
> the phone into the USB port, switch the phone on, wait for a few seconds
> and then run "lsusb" and "lsusb -t". Post the output of these two
> commands and we will know more. (An important indicator is whether your
> system recognizes the vendor and product ID number of the device.)
>
> > Does anyone know a Cellphone from ATT that can work with debian...so I
> can
> > use it with a sms text messeging program ???
> >
> > I guess the phone would have to have a usb cable...Does anyone know of
> one
> > please????????????please???????
> >
> >
> > thanks
> > mjh
>
> --
> Regards,            | http://users.icfo.es/Florian.Kulzer
>          Florian   |


I did a modprobe on usb-serial and ftdi_sio and they both load great...after
loading what am i suppose to see?  Should it say ttyUSB0 device ready or
somehting like that ?
 The strange thing is that i have a bluetooth dongle --that is in one of th
usb ports..and that works ..b/c i am able to hook it up to my phone.
I am further able to connect to it with rfcomm.  It looks like i can take
the modem off the hook..but I am at a dead end there..because i can not
reference the device in Kannel.
my dmesg looks like this:

 drivers/usb/serial/usb-serial.c: USB Serial support registered for
FTDI USBSerial Device
usbcore: registered new driver ftdi_sio
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver

and my lsusb looks like this:
Bus 002 Device 003: ID 0bb4:0bce High Tech Computer Corp.
Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
Dongle (HCI mode)
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 004: ID 0d49:5020 Maxtor
Bus 001 Device 001: ID 0000:0000


and my lsmod looks like this:

usbserial              39152  1 ftdi_sio
hci_usb                22812  2
bluetooth              61572  7 rfcomm,l2cap,hci_usb
usb_storage            87616  1
scsi_mod              153008  3 sd_mod,libata,usb_storage
ide_core              147584  5
ide_generic,ide_cd,usb_storage,generic,amd74xx

and my lusb -t looks like this:

rider:~# lsusb -t
Bus#  2
`-Dev#   1 Vendor 0x0000 Product 0x0000
  |-Dev#   2 Vendor 0x0a12 Product 0x0001
  `-Dev#   3 Vendor 0x0bb4 Product 0x0bce
Bus#  1
`-Dev#   1 Vendor 0x0000 Product 0x0000
  `-Dev#   4 Vendor 0x0d49 Product 0x5020

where would it tell me that the phone is this this ttty* device???
thanks
mjh

Reply via email to