qualcomm modem wont work

[Mauricio Pretto]

Binary package hint: modemmanager

.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: modemmanager 0.4+git.20110124t203624.00b6cce-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-10.44~lp771758v201106091502-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic x86_64
Architecture: amd64
Date: Mon Jun 13 20:09:23 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
ProcEnviron:
 LANGUAGE=en
 LANG=pt_BR.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: modemmanager
UpgradeStatus: Upgraded to natty on 2011-04-21 (53 days ago)

[Mathieu Trudel-Lapierre (cyphermox)]

Huh, this seems to have not worked as expected.

To figure out what was doing wrong, we'd need at least /var/log/syslog after reproducing the problem, and the output of 'lsusb' to know the exact USB ID for the modem.

Could you please add those to the report? Thanks!

[Mauricio Pretto (pretto)]

Bus 001 Device 003: ID 05c6:9211 Qualcomm, Inc. Acer Gobi Wireless Modem (QDL mode)

[Mathieu Trudel-Lapierre (cyphermox)]

Could you please follow the steps here: https://wiki.ubuntu.com/DebuggingModemmanager under Getting Debug logs to get the current debugging logs from MM while reproducing the issue?

Also, I suspect this may need to load the correct special firmware with gobi_loader if it's not already being done. I think the debug logs will say whether it's the case those (we should see from the return codes from the modem)

[Mauricio Pretto (pretto)]

is there a simple way to debug that ? I just took a look at that, and seems very technical .
I'm just a sales guy :)

[Mathieu Trudel-Lapierre (cyphermox)]

There is no simpler way ;)

The idea is to stop network-manager so that modemmanager can be stopped and started again with the right switch to list debug information, then restarting network-manager to test the connection. Then we will see all the messages passing back and forth
between MM and the modem.

[Mauricio Pretto (pretto)]

I hope this help

[Mauricio Pretto (pretto)]

Hi Mathieu,
do you need any other info for debuging ?

[Mathieu Trudel-Lapierre (cyphermox)]

No, we have everything:

modem-manager[12298]: <debug> [1308440689.323452] [mm-manager.c:793] device_added(): (tty/ttyUSB0): port's parent device is blacklisted

Looking at this it seems as though this particular Gobi modem doesn't properly gets its firmware loaded, perhaps?

Right now it's blacklisted by /lib/udev/rules.d/77-mm-qdl-device-blacklist.rules:
# Acer Gobi QDL device
ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9211", ENV{ID_MM_DEVICE_IGNORE}="1"

What you could try to do would be to comment out the line starting with ATTRS above in the file, reboot, and see if the device answers better.

[Mauricio Pretto (pretto)]

none of those firmwars worked ..... tried all of them

[Andrew Simpson (andrew-simpson)]

The blacklist lines in the udev rules '77-mm-qdl-device-blacklist' are to prevent modem-manager grabbing the port before the firmware is loaded. The firmware is loaded through a serial port on /dev/ttyUSB0. Once the firmware is correctly loaded a new port will open up on /dev/ttyUSB1.

The problem seems to be that the firmware is not loaded.

To the original poster: Check that you have 'qcserial' and 'gobi-loader' installed. You will also need the firmware files from a Windows install. If you Google around for 'gobi 2000 linux' you will find a number of instructions. It's a bit fiddly...

[Mathieu Trudel-Lapierre (cyphermox)]

Andrew, I've already looked into this with Mauricio outside of this bug report. The issue is that the firmware doesn't appear to be loaded, perhaps because there is no "valid" firmware to load for this provider (possibly, which is why I had Mauricio try all the firmware files available).

Sorry if the comment above about removing the blacklist got anyone confused, it was meant to try and see if we could get additional information from that aspect.