modem-manager not working

[xlearner]

Alexfish,

I did as you have suggested. I am displaying the output of 'tail -f /var/log/syslog'. There is a line in the middle. It signifies the instant after which I plugged the modem.

Xlearner

Jul 7 02:52:51 sath-VPCSA35GG mtp-probe: checking bus 2, device 13: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3"
Jul 7 02:52:51 sath-VPCSA35GG mtp-probe: bus: 2, device: 13 was not an MTP device
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266834] CPU3: Package power limit notification (total events = 76333)
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266837] CPU2: Package power limit notification (total events = 76333)
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266841] CPU1: Package power limit notification (total events = 75807)
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266843] CPU0: Package power limit notification (total events = 75791)
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266924] CPU1: Package power limit normal
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266927] CPU3: Package power limit normal
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266929] CPU2: Package power limit normal
Jul 7 02:53:12 sath-VPCSA35GG kernel: [18025.266931] CPU0: Package power limit normal
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.795452] usb 3-1: new full-speed USB device number 5 using xhci_hcd
Jul 7 02:55:43 sath-VPCSA35GG mtp-probe: checking bus 3, device 5: "/sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0/usb3/3-1"
Jul 7 02:55:43 sath-VPCSA35GG mtp-probe: bus: 3, device: 5 was not an MTP device
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.837011] scsi9 : usb-storage 3-1:1.0
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.920135] usbcore: registered new interface driver usbserial
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.920144] USB Serial support registered for generic
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.920162] usbcore: registered new interface driver usbserial_generic
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.920163] usbserial: USB Serial Driver core
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.940683] USB Serial support registered for GSM modem (1-port)
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.940757] usbcore: registered new interface driver option
Jul 7 02:55:43 sath-VPCSA35GG kernel: [18175.940758] option: v0.7.2:USB Driver for GSM modems
Jul 7 02:55:44 sath-VPCSA35GG kernel: [18176.838650] scsi 9:0:0:0: CD-ROM HUAWEI Mass Storage 2.31 PQ: 0 ANSI: 0
Jul 7 02:55:44 sath-VPCSA35GG kernel: [18176.851555] sr1: scsi-1 drive
Jul 7 02:55:44 sath-VPCSA35GG kernel: [18176.851691] sr 9:0:0:0: Attached scsi CD-ROM sr1
Jul 7 02:55:44 sath-VPCSA35GG kernel: [18176.851822] sr 9:0:0:0: Attached scsi generic sg4 type 5
Jul 7 02:55:45 sath-VPCSA35GG usb_modeswitch: switching device 12d1:1446 on 003/005

[alexfish]

looks like mtpbrobe having a look at the device first, for me this is a new one

Looked at, possible mtp-probe may be part of mtp-tools , for media transfere

if the probe is holding the device then it could be a problem

suggest look at the System Monitor to see if a daemon is running , RE apart of the mtp-tools

if there is suggest killing the daemon , can do that from the System monitor

or from the terminal

sudo killall <name of daemon>

also check and see if there are two instances of udev running

can also suggest dissable usb_modeswitch

sudo gedit /etc/usb_modeswitch.conf

edit the line

DisableSwitching=0

to

DisableSwitching=1

save and exit

after the probing , wait a while then issue the usb_modeswitch command , have already posted how to do this.

see what happens

regards

alexfish

[xlearner]

Alexfish,

I tried to look for mtp daemon as you suggested. But I could not find any such process in the system monitor. I tried it on the terminal as well:
$ ps -ef|grep mtp
sath 3518 3219 0 17:32 pts/0 00:00:00 grep --color=auto mtp
I could not find any such process. I have attached log from the output of the command, 'ps -ef'.

Next, I wanted to execute the other steps mentioned in your post. But I was not clear on one thing: Do you still want me to disable usb_modeswitch, probe it and issue usb_modeswitch command? I am asking this as I was not sure if this is related to mtp probe daemon or unrelated to it.
If they are not unrelated, then I will execute these steps.

Thanks
Xlearner

[xlearner]

Alexfish,

Continuing with my previous reply, I executed the other steps as well. First I edited, /etc/usb_modeswitch.conf and set DisableSwitching=1. Then I plugged the usb modem, "12d1 1446". The output of usb-devices for this device after plugging the device is as follows:

T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=1446 Rev=00.00
S: Manufacturer=HUAÿWEI TECHNOLOGIES
S: Product=HUAWEI Mobile
S: SerialNumber=ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage

So I can see that the driver is set to usb-storage. Next, I tried to switch the usb modem using the command you suggested previously on the terminal. But surprisingly, it is giving an error. The output is as follows:

$ sudo usb_modeswitch -v 0x12d1 -p 0x1446 -M "5553424312345678000000000000001106000000000000000 0000000000000"

Looking for default devices ...
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Accessing device 002 on bus 003 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using first interface: 0x00
Using endpoints 0x08 (out) and 0x87 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
OK, driver found ("usb-storage")
OK, driver "usb-storage" detached

Could not get INQUIRY response (error -19)
Error: could not get description string "manufacturer"
Error: could not get description string "product"
Error: could not get description string "serial number"

USB description data (for identification)
-------------------------
Manufacturer:
Product:
Serial No.:
-------------------------
Looking for active driver ...
No driver found. Either detached before or never attached
Setting up communication with interface 0
Could not claim interface (error -19). Skipping message sending
-> Run lsusb to note any changes. Bye.

So any suggestions?

Xlearner

[alexfish]

Hi

Not sure what is happening , I have not install 12.04 as of yet.

Yet Last reports I received , indicated that the Device ID 12d1,1446 worked in both modes . See last page
How To : Mobile Broadband Connections [ Ubuntu 11.04 : 10.10 : 10.04 : 9.10] ( 1 2 3 ... Last Page)

Please Note this Tutorial is now closed.

on Ubuntu 12.04 , but now wondering if there is diff between 64 bit and 32 bit systems

can post if system 32 or 64 bit

I do know some devices may work with a different message , this will not implement the ethernet type interface $g mode, present on newer devices , sakis3g ,usually gets them working in the 3g mode, but still operate at the faster speeds (4g) of the standard 3g method of connecting.

So,
from what I am seeing , best advice , Visit the usb_modeswitch forum.

They may advise installing usb_modeswitch from source , IE , compile it ,for and on your
system , It is easy to do, even for a novice ,also Josh is very helpful , but not in a direction,
where usb_modeswitch scripts have been adapted to suit some systems, the main one
for some Ubuntu versions , could be the lack of tcl ,

regards

alexfish

[xlearner]

Alexfish,

I am currently running 32 bit version of ubuntu 12.04.

I will ask the same query at usb_modeswitch forum. Let me hope for the best!

In the meantime, I will also try to get hold of a system that has 11.10 (since I know that it works perfectly well on that system). I will see the output of /var/log and compare it with the output in 12.04 when I plugin the usb modem.

Xlearner

[surja]

sad that Ubuntu isn't issuing a permanent fix for this irritating problem. I had to switch to Fedora where this problem with 3G dongles does not exist.

[alexfish]

sad that Ubuntu isn't issuing a permanent fix for this irritating problem. I had to switch to Fedora where this problem with 3G dongles does not exist.

Hi surga

I am not sure if this a specific as in "Ubuntu" , if it were , then I would have presumed to have seen a lot more , "Can't Connect" , Threads ,

Lets see what the out come is between the two version + the out come , if any, via usb_modeswitch forum

alexfish

[xlearner]

Surja,

Yes, I know it can be frustrating. Strangely, this modem was working well on ubuntu 11.10. But somehow it stopped working on ubuntu 12.04.

Xlearner

[alexfish]

Hi all


Not sure if this has any bearing on the subject but worth

looking at POST #7

had been on that thread , re serial port problem

but worth checking out

regards


alexfish