hotplugging gprs modem in FC6

zhnupy · 03-25-2007, 05:30 AM

Hello,
I'm trying to use a multitech gprs modem in FC6.
I've already patched the kernel with support for TI 3410/5052 USB Serial Driver
Then copied firmware to /usr/lib/hotplug/firmware which I understand should now
be /lib/firmware.
Next step is to install some hotplug script (/etc/hotplug/usb/ti_usb_3410_5052)
but I'm reading hotplug is no longer used in FC6, so the script is no longer required?
or should I put it in different location?

Output of lsusb command shows:
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 008: ID 06e0:f111 Multi-Tech Systems, Inc.

but the modem's power LED is off. It is not clear to me if the driver is already
loaded or not (I was expecting to see the led turning on after connecting the modem
to usb port)

So how do I determine if the driver is loaded?
Is there a generic way to turn on usb devices?
If I manually load the driver how do I bind it to that particular device?

Excuse if some questions are out of order,
any help would be deeply appreciated.

Junior Hacker · 03-26-2007, 10:13 PM

Just a shot in the dark,
I wonder if it would be read from /etc/netplug (for the script)

I tried helping someone set up their modem a while back and we just could not get things happening, then this person told me it was some kind of wireless setup through his/her cell phone, I suggested looking into setting up wireless capability in his/her distribution's configuration. Never heard from this person again, don't know if it was a good suggestion or not.
There is also a couple entries in main menu/system/services for bluetooth, but they are usually enabled by default, plus yours is probably bluetooth to the USB device, then to the computer via USB.
Usually in FC6, USB devices are automaticaly detected and you should see something in System by clicking on that icon on the desktop.

Junior Hacker · 03-26-2007, 10:41 PM

In main menu/system/services, you may want to turn on "dund". In this web page link below is a section called "Modify Services/Daemons", this is good information, this is where I just learned about "dund".

http://www.mjmwired.net/resources/mjm-fedora-fc6.html

zhnupy · 03-27-2007, 01:58 AM

Thanks for the info but this issue is not bluetooth related, see I connect the modem with usb cable. Unfortunately I lack experience with linux device handling so I cannot diagnose what kind of problem I'm facing.
As I've said, after connecting the modem to usb socket, the command lsusb shows it is indeed attached, but that's it.

I followed these http://markus.wernig.net/en/it/usb-s...andy-ppp.phtml, I can replicate every step up to the point the reference to
/dev/ttyUSB0
or
/dev/usb/tts/0

These devices do not exists in my system nor are they created after attaching the modem.
Only thing reminiscent of USB in my /dev are some files which are always there:

usbdev1.1_ep00 usbdev2.1_ep00 usbdev3.1_ep00 usbdev4.1_ep00 usbdev5.1_ep00 usbdev5.2_ep00 usbdev1.1_ep81 usbdev2.1_ep81 usbdev3.1_ep81 usbdev4.1_ep81 usbdev5.1_ep81 usbdev5.2_ep83

I also see these files which could be equivalents
/dev/bus/usb/001/001
/dev/bus/usb/001/002
/dev/bus/usb/002/001
/dev/bus/usb/003/001
/dev/bus/usb/004/001
/dev/bus/usb/005/001
/dev/bus/usb/005/002

so I tried to use that with KPPP. Given that lsusb shows:
Bus 001 Device 002: ID 06e0:f111 Multi-Tech Systems, Inc.

I chose /dev/bus/usb/001/002 as modem device. after that, clicked 'Query Modem...' button. It displays 'Modem busy', at least it's not rejecting as before but yet no connection can be made. Modem LEDs were turned off all this time.

zhnupy · 03-27-2007, 02:07 AM

in /proc/bus/usb/devices I see a description of the modem, it says there is no driver associated:

T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=06e0 ProdID=f111 Rev= 1.01
S: Manufacturer=Texas Instruments
S: Product=TUSB3410 Serial Port
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms

How can I associate the driver I know the device uses (I already have loaded it with: modprobe ti_usb_3410_5052) ??

Junior Hacker · 03-27-2007, 02:28 AM

Because of the last person's situation, I thought you had a bluetooth module in between the phone & the computer. But it appears you have direct cable connection between phone & computer via USB.

Code:

Feb  9 21:03:25 blue kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
Feb  9 21:03:25 blue kernel: usbcore: registered new driver usbserial_generic
Feb  9 21:03:25 blue kernel: usbcore: registered new driver usbserial
Feb  9 21:03:25 blue kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
Feb  9 21:03:44 blue kernel: usb 1-2: new full speed USB device using ohci_hcd and address 2
Feb  9 21:03:44 blue kernel: usb 1-2: Product: Siemens USB Connectivity
Feb  9 21:03:44 blue kernel: usb 1-2: Manufacturer: Siemens AG
Feb  9 21:03:44 blue kernel: usb 1-2: SerialNumber:  353669000550637
Feb  9 21:03:45 blue kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for PL-2303
Feb  9 21:03:45 blue kernel: pl2303 1-2:1.0: PL-2303 converter detected
Feb  9 21:03:45 blue kernel: usb 1-2: PL-2303 converter now attached to ttyUSB0
Feb  9 21:03:45 blue kernel: usbcore: registered new driver pl2303
Feb  9 21:03:45 blue kernel: drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver v0.12

You should now have /dev/ttyUSB0 (or /dev/usb/tts/0 under devfs). This is your serial line modem. Use any dialer on it you want to.

So what you say is that all those lines in red above this last sentence, you've replicated, more or less. Even the part that says:

Quote:

Feb 9 21:03:45 blue kernel: usb 1-2: PL-2303 converter now attached to ttyUSB0

Junior Hacker · 03-27-2007, 02:30 AM

Keep in mind you don't have "devfs", you have "udev".

zhnupy · 03-27-2007, 11:43 PM

First part of my log is similar to yours, after doing:

Code:

modprobe usb_storage
modprobe cdc-acm
modprobe usbserial
modprobe pl2303
modprobe ti_usb_3410_5052

dmesg displays:

Code:

Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver cdc_acm
drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control Model driver for USB modems and ISDN adapters
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
drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303
usbcore: registered new driver pl2303
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver
drivers/usb/serial/usb-serial.c: USB Serial support registered for TI USB 3410 1 port adapter
drivers/usb/serial/usb-serial.c: USB Serial support registered for TI USB 5052 2 port adapter
usbcore: registered new driver ti_usb_3410_5052
drivers/usb/serial/ti_usb_3410_5052.c: TI USB 3410/5052 Serial Driver v0.9

then I plug the modem and dmesg shows:

Code:

usb 1-1: new full speed USB device using uhci_hcd and address 2
usb 1-1: configuration #1 chosen from 1 choice

But no /dev/ttyUSB0 or similar is created. What I'm missing? also, I didn't get your commentary about me having udev instead of devfs (newbie sorry, I read a little bit about this dynamic udev but don't know how to use that info in this case

)

Junior Hacker · 03-28-2007, 12:43 AM

On that web page you used as a guide it tells you basically "if successful, the port would be /dev/ttyUSB0 or /dev/usb/tts/0 under devfs". The quote I posted is from that web page that says he/she successfully created a port for the modem on /dev/ttyUSB0 according to the terminal output after he/she connected the cable between phone and computer. Here is a quote from that page:

Quote:

Now attach the phone with the USB cable to your computer.
You should see the kernel registering the necessary devices.

Feb 9 21:03:25 blue kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
Feb 9 21:03:25 blue kernel: usbcore: registered new driver usbserial_generic
Feb 9 21:03:25 blue kernel: usbcore: registered new driver usbserial
Feb 9 21:03:25 blue kernel: drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
Feb 9 21:03:44 blue kernel: usb 1-2: new full speed USB device using ohci_hcd and address 2
Feb 9 21:03:44 blue kernel: usb 1-2: Product: Siemens USB Connectivity
Feb 9 21:03:44 blue kernel: usb 1-2: Manufacturer: Siemens AG
Feb 9 21:03:44 blue kernel: usb 1-2: SerialNumber: 353669000550637
Feb 9 21:03:45 blue kernel: drivers/usb/serial/usb-serial.c: USB Serial support registered for PL-2303
Feb 9 21:03:45 blue kernel: pl2303 1-2:1.0: PL-2303 converter detected
Feb 9 21:03:45 blue kernel: usb 1-2: PL-2303 converter now attached to ttyUSB0
Feb 9 21:03:45 blue kernel: usbcore: registered new driver pl2303
Feb 9 21:03:45 blue kernel: drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver v0.12

You should now have /dev/ttyUSB0 (or /dev/usb/tts/0 under devfs). This is your serial line modem. Use any dialer on it you want to.

Add "noauth" to /etc/ppp/options, as your provider will most likely not authenticate to you. If you are a pppd expert, besides probably not needing this tutorial, you can configure pppd in /etc/ppp to your heart's content. In my case kppp does all that magic for me on the fly when dialling. You would probably want to add "defaultroute" and "usepeerdns" to the options file.

If you reached that point you would have something similar (not necessarily exactly) as what he/she got for a modem port which was /dev/ttyUSB0. Which by the way is consistent with modern distributions using udev which replaced devfs. If you had an older distro using devsf, it would be as he (OK, this person has a beard, I'll say "he") suggests, /dev/usb/tts/0.
Did you check to see if you have something similar to "/dev/gprsmodem" or "/dev/tyUSB0", if so, then all you need to do is create a symlink to /dev/modem to connect with kppp or 'main menu/administration/network' in Fedora. This symlink would have to be re-done upon every re-boot as symlinks disappear at shutdown with udev that Fedora and most modern distributions use.

From what I've seen so far, you're very close, you have to look in the /dev directory for something that resembles what should be the device allocated to your modem/phone when it is connected. According to buddy's experience, it was /dev/ttyUSB0.
If you do find a device associated with your phone, you need to create a symlink to it if it is not a default device in kppp, to do so, let's say it is called "/dev/gprsmodem", then from a terminal as root (probably super user terminal via main menu/system/more_applications), issue command:

Quote:

ln -s /dev/gprsmodem /dev/modem

Then set kppp to look at /dev/modem for the modem/phone.

zhnupy · 03-28-2007, 02:41 AM

nop, I do not have any /dev/ttyUSB0, /dev/usb/tts/0, whatsoever.

that is the point. I do not know why udev is not creating a device file for the modem when I attached it. I have not changed or aggregated any rule file in /etc/udev/rules.d so the default rules should have take care of.

I thing the main problem is the device is not bound with the driver. Even though the vendor-id : product-id (0x06e0:0xf111) tuple is the default supported by the driver which I understand is the condition to the binding.

So I found in http://lwn.net/Articles/143397/ that is possible to do the binding manually, so

given that

Code:

/sbin/lsusb

displays:

Code:

Bus 001 Device 002: ID 06e0:f111 Multi-Tech Systems, Inc.

and command:

Code:

ls /sys/bus/usb/devices/

displays

Code:

1-0:1.0  1-1  1-1:1.0  2-0:1.0  3-0:1.0  4-0:1.0  5-0:1.0  5-5  5-5:1.0  5-5:1.1  usb1  usb2  usb3  usb4  usb5

I guess "Bus 001 Device 002" corresponds to "1-1:1.0"

issuing command:

Code:

tree /sys/bus/usb/devices/

confirms there is no driver associated:

Code:

/sys/bus/usb/devices/1-1:1.0/
|-- bAlternateSetting
|-- bInterfaceClass
|-- bInterfaceNumber
|-- bInterfaceProtocol
|-- bInterfaceSubClass
|-- bNumEndpoints
|-- bus -> ../../../../../../bus/usb
|-- ep_01 -> ../../../../../../devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.0/usbdev1.3_ep01
|-- modalias
|-- power
|   |-- state
|   `-- wakeup
|-- subsystem -> ../../../../../../bus/usb
|-- uevent
|-- usb_endpoint:usbdev1.3_ep01 -> ../../../../../../devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.0/usbdev1.3_ep01
`-- usbdev1.3_ep01
    |-- bEndpointAddress
    |-- bInterval
    |-- bLength
    |-- bmAttributes
    |-- dev
    |-- device -> ../../../../../../../devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.0
    |-- direction
    |-- interval
    |-- power
    |   |-- state
    |   `-- wakeup
    |-- subsystem -> ../../../../../../../class/usb_endpoint
    |-- type
    |-- uevent
    `-- wMaxPacketSize

so I tried:

Code:

echo -n "1-1:1.0" > /sys/bus/usb/drivers/ti_usb_3410_5052/bind

but it fails, this is what displays

Code:

bash: echo: write error: No such device

I did same procedure with device ""1-0:1.0" (which by the way did have this driver associated: ../../../../../bus/usb/drivers/hub)
So I first unbind /bus/usb/drivers/hub and then rebind the same driver and it was succesful.
But when I tried to do the same with driver ti_usb_3410_5052, the error ocurrs

so I guess either there is something wrong with the driver or the modem is not attached to the usb port I tried to bind the driver to.

I don't have a darm clue. I wouldn't mind sharing some bucks with someone who give me a detailed solution. dead end till now

.

Junior Hacker · 03-28-2007, 03:55 AM

I hear you

That article mentions binding in user space, this is how my modem works. I have a pci modem, with 64bit Linux only one pci modem is presently supported, Lt/Agere with mars chip. I have to build a kernel module with kernel-devel and kernel-headers installed and build a second item called "martian_modem" in a 32bit environment as the vendor's proprietary source was compiled 32bit which is applied in "user space" every time I re-boot, the module gets pre-loaded upon boot-up. So it was an asset for me to have Mandrake 10.2 32bit to put together the martian_modem that is used in all my x86_64 systems. Including Debian Etch which has no 32 bit crap involved. This "user space" martian_modem gets placed in /usr/sbin. And I have to create the symlink to /dev/modem and apply martian_modem after every re-boot before using a dialer, kppp in my case.

Fedora comes with wvdial, usually pre-installed. Just for the hell of it, try running command:

#wvdialconf /etc/wvdial.conf

While the phone is connected to see if wvdial finds it, wvdial usually only looks at /dev/ttySxx.