GNOME Bugzilla – Bug 602979
gobi 2000 device not usable by network manager
Last modified: 2010-11-28 15:22:39 UTC
I have a mobile broadband device (gobi) on an HP 5310m. NetworkManager can't detect it so I reported it here as instructed on the wiki. Full details also here: https://bugzilla.redhat.com/show_bug.cgi?id=533266
Not a ton I can do until the device shows up as a TTY port and responds to AT commands... let me know when it gets to that state and we can work on supporting it.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
You'll get the info today.
Well I have a /dev/ttyUSB0 file, how do I check if it's associated with the gobi device?
A kernel person says the device is in the F13 kernel: https://bugzilla.redhat.com/show_bug.cgi?id=533266#c6
> Not a ton I can do until the device shows up as a TTY port and responds > to AT commands... let me know when it gets to that state and we can work > on supporting it. Good news! I added this line: ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="231d", RUN+="gobi_loader -2000 $env{DEVNAME} /lib/firmware/gobi" to the file: /lib/udev/rules.d/60-gobi.rules then rebooted. udev hangs if I reboot with wireless enabled, so I reboot with wireless disabled then enable it. I see this in /var/log/messages: Jul 4 22:33:59 localhost kernel: qcserial 1-2:1.1: Qualcomm USB modem converter detected Jul 4 22:33:59 localhost kernel: usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0 Hurrah! So it all seems to work, BUT... NetworkManager doesn't see it!
So we need to figure out why it's not getting exposed to ModemManager. Cna you do the following for me? 1) get your ttyUSB0 2) mv /usr/sbin/modem-manager / 3) killall -TERM modem-manager 4) /modem-manager --debug and then attach/paste the output of modem-manager here? THanks!
# /modem-manager --debug ** Message: Loaded plugin Generic ** Message: Loaded plugin Option ** Message: Loaded plugin Sierra ** Message: Loaded plugin MotoC ** Message: Loaded plugin Nokia ** Message: Loaded plugin Novatel ** Message: Loaded plugin AnyData ** Message: Loaded plugin ZTE ** Message: Loaded plugin Huawei ** Message: Loaded plugin Gobi ** Message: Loaded plugin Option High-Speed ** Message: Loaded plugin Longcheer ** Message: Loaded plugin Ericsson MBM ** (modem-manager:2465): DEBUG: (tty/ttyS0): port's parent platform driver is not whitelisted ** (modem-manager:2465): DEBUG: (tty/ttyS1): port's parent platform driver is not whitelisted ** (modem-manager:2465): DEBUG: (tty/ttyS2): port's parent platform driver is not whitelisted ** (modem-manager:2465): DEBUG: (tty/ttyS3): port's parent platform driver is not whitelisted ** (modem-manager:2465): DEBUG: (net/pan0): could not get port's parent device ** Message: (ttyUSB0) opening serial device... ** (modem-manager:2465): DEBUG: <1279312907.309360> (ttyUSB0) device open count is 1 (open) ** (modem-manager:2465): DEBUG: (ttyUSB0): probe requested by plugin 'Gobi' ** (modem-manager:2465): DEBUG: <1279312907.408634> (ttyUSB0): --> 'AT+GCAP<CR>' ** (modem-manager:2465): DEBUG: <1279312910.313920> (ttyUSB0): --> 'AT+GCAP<CR>' ** (modem-manager:2465): DEBUG: <1279312913.221313> (ttyUSB0): --> 'AT+GCAP<CR>' ** (modem-manager:2465): DEBUG: <1279312916.130131> (ttyUSB0): --> 'ATI<CR>' ** (modem-manager:2465): DEBUG: <1279312919.37631> (ttyUSB0): --> 'AT+CPIN?<CR>' ** (modem-manager:2465): DEBUG: <1279312921.946211> (ttyUSB0): --> 'AT+CGMM<CR>' ** (modem-manager:2465): DEBUG: <1279312924.855848> (ttyUSB0) device open count is 0 (close) ** Message: (ttyUSB0) closing serial device...
So this doesn't seem like the firmware is actually getting pushed to the modem; before the firmware is downloaed you'll still get ttyUSB0, which gobi-loader uses to push the firmware down. Then, after the firmware is loaded the gobi will reboot, drop off the USB bus, and then re-enumerate as ttyUSB0 again. Can you include all your dmesg from when you turn wireless back on until about a minute after? Note that Gobi 2000 devices need *3* firmware files, not 2 like the Gobi 1000s.
Any chance you could advise me on which firmware files to use? I have these: 918ecc998ca0b151f01111ff8cca39d2 ./HP/03f0251d.did 6b96bb2a6e05f34080e17bbd3ad346ed ./HP/0/uqcn.mbn 6011b5b0ce4c4005479efaf683a25ed2 ./HP/14/uqcn.mbn 5dbe1eec7734ecfd414e661742f5cb3d ./HP/1/amss.mbn 88a60ed745d75fb1b92c539574ecc972 ./HP/1/apps.mbn 01205da52615a43e97b0ad291d3a7912 ./HP/1/uqcn.mbn e5b60e32410972f07d516e0879809c51 ./HP/2/uqcn.mbn ea3616f0eea1a3f2b4870bb0d67c2ec0 ./HP/3/amss.mbn 46fcb2423c31fd96e4645a90956264d2 ./HP/3/apps.mbn d52dbd2912c0af3747ff69ff7b88c72b ./HP/3/uqcn.mbn 0510767ac0f4f43c4f9a0bebd0df0d35 ./HP/4/uqcn.mbn b682fd549d26f75afd01f7695a759e04 ./HP/6/uqcn.mbn ff4931778fac0230290d762ef0e76fd4 ./HP/7/uqcn.mbn 043b743e7ff5d934e16aaf0bb5c0da47 ./HP/8/uqcn.mbn 8bd0286673573e172434de9e9eecdbd9 ./HP/9/uqcn.mbn 16b3f8ab096500bc012facc12b160525 ./HP/UMTS/amss.mbn 00cbd411048cdadc3e4caf0d89d14fca ./HP/UMTS/apps.mbn
Created attachment 169896 [details] dmesg output as requested (using HP/1/ firmware)
(uqcn above is really UQCN)
Created attachment 169897 [details] dmesg output using HP/3/ firmware
With the HP/3/ firmware, udev doesn't hang forever at boot. Must be a good sign.
Well I thought it was going to work, but it didn't: If I right click the NM icon I can tick the "enable mobile broadband" box. I do that. If I then left click the NM icon, under "Mobile broadband" I see "not enabled". Strange, because I just enabled it. Below that "New Mobile Broadband (CDMA) connection". We don't use CDMA. Maybe it's a typo. I click that option it anyway. After selecting my country I see no providers listed, which is again strange, because with the same sim card in my external 3g modem I normally see four service providers listed. So I guess the 3g card is in the wrong mode, or I loaded the wrong firmware, or NM is confused and trying to use CDMA which doesn't exist here.
One last go: I downloaded the latest firmware from the hp website and found a new folder! HP/16/ - however it does not work. So I went back to the HP/3/ firmware, the only firmware that doesn't hang udev at boot, but with the two files from the HP/UMTS/ directory. That doesn't work either. I can't really go much further with trial and error. Any help appreciated.
If NM says "CDMA" then you probably loaded the wrong firmware. The Gobi devices switch firmware to switch between CDMA/EVDO and GSM/UMTS operation. So if you give the Gobi a CDMA firmware, the modem is in CDMA mode. If you give it a GSM/UMTS firmware, it will show up in GSM/UMTS mode. There had been problems with gobi_loader and kernels after 2.6.34 due to a change in the kernel. Make sure you use the latest kernel and the latest gobi_loader, or else you may experience hangs when trying to load firmware, especially on the Gobi 2000 parts. Basically, it appears you need to use different firwmare, but if that firmware is hanging in udev, then the problem needs to be handled upstream in the kernel and/or in gobi_loader, since NetworkManger/ModemManager aren't involved yet. The device isn't actually in modem modem (and thus available to NM) until the firmware has successfully loaded.
So why is my non-CDMA usb modem also listed as CDMA?
In follow up to comment 8, I now get this output: # uname -a Linux box 2.6.34.7-56.fc13.x86_64 #1 SMP Wed Sep 15 03:36:55 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux # /modem-manager --debug ** Message: ModemManager (version 0.4-4.git20100720.fc13) starting... ** Message: Loaded plugin SimTech ** Message: Loaded plugin Generic ** Message: Loaded plugin Option ** Message: Loaded plugin Sierra ** Message: Loaded plugin MotoC ** Message: Loaded plugin Nokia ** Message: Loaded plugin Novatel ** Message: Loaded plugin AnyData ** Message: Loaded plugin ZTE ** Message: Loaded plugin Huawei ** Message: Loaded plugin Gobi ** Message: Loaded plugin Option High-Speed ** Message: Loaded plugin Longcheer ** Message: Loaded plugin Ericsson MBM ** (modem-manager:2551): DEBUG: (tty/ttyS0): port's parent platform driver is not whitelisted ** (modem-manager:2551): DEBUG: (tty/ttyS1): port's parent platform driver is not whitelisted ** (modem-manager:2551): DEBUG: (tty/ttyS2): port's parent platform driver is not whitelisted ** (modem-manager:2551): DEBUG: (tty/ttyS3): port's parent platform driver is not whitelisted ** Message: (ttyUSB0) opening serial device... ** (modem-manager:2551): DEBUG: <1285447468.859044> (ttyUSB0) device open count is 1 (open) ** (modem-manager:2551): DEBUG: (ttyUSB0): probe requested by plugin 'Gobi' ** (modem-manager:2551): DEBUG: <1285447468.958737> (ttyUSB0): --> 'AT+GCAP<CR>' ** (modem-manager:2551): DEBUG: <1285447469.761189> (ttyUSB0): <-- '<CR><LF>+GCAP: +CGSM,+DS<CR><LF><CR><LF>OK<CR><LF>' ** (modem-manager:2551): DEBUG: <1285447469.761461> (ttyUSB0) device open count is 0 (close) ** Message: (ttyUSB0) closing serial device... ** Message: (ttyUSB0) type primary claimed by /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2 ** Message: (ttyUSB0) opening serial device... ** (modem-manager:2551): DEBUG: <1285447469.765542> (ttyUSB0) device open count is 1 (open) ** (modem-manager:2551): DEBUG: <1285447469.765608> (ttyUSB0) device open count is 2 (open) ** Message: (Gobi): GSM modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2 claimed port ttyUSB0 ** (modem-manager:2551): DEBUG: Added modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2 ** (modem-manager:2551): DEBUG: (tty/ttyUSB0): outstanding support task prevents export of /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2 ** (modem-manager:2551): DEBUG: <1285447469.765911> (ttyUSB0): --> 'AT+CPIN?<CR>' ** (modem-manager:2551): DEBUG: <1285447469.783115> (ttyUSB0): <-- '<CR><LF>+CPIN: READY<CR><LF><CR><LF>OK<CR><LF>' ** (modem-manager:2551): DEBUG: <1285447469.783309> (ttyUSB0) device open count is 1 (close) ** (modem-manager:2551): DEBUG: Exported modem /sys/devices/pci0000:00/0000:00:1a.7/usb1/1-2 as /org/freedesktop/ModemManager/Modems/0 ** (modem-manager:2551): DEBUG: (/org/freedesktop/ModemManager/Modems/0): data port is ttyUSB0 ** (modem-manager:2551): DEBUG: <1285447469.783730> (ttyUSB0): --> 'ATE0<CR>' ** (modem-manager:2551): DEBUG: <1285447469.799327> (ttyUSB0): <-- '<CR><LF>OK<CR><LF>' ** (modem-manager:2551): DEBUG: <1285447469.799601> (ttyUSB0): --> 'AT+CGSN<CR>' ** (modem-manager:2551): DEBUG: <1285447469.832090> (ttyUSB0): <-- '<CR><LF>123456789012345<CR><LF><CR><LF>OK<CR><LF>' ** Message: Modem /org/freedesktop/ModemManager/Modems/0: Equipment identifier set (123456789012345) ** (modem-manager:2551): DEBUG: <1285447469.832247> (ttyUSB0) device open count is 0 (close) ** Message: (ttyUSB0) closing serial device... Looks better at least...
I guess this is to be reopened then.
(In reply to comment #18) > So why is my non-CDMA usb modem also listed as CDMA? It depends, I'd need to see the modem-manager --debug output for it. Some devices like the Pantech UM190 actually advertise support for both CDMA and GSM/UMTS at the same time. What kind of device is this? Next, is the Gobi 2000 work for you now that it's got the right firmware loading and is recognized by as GSM by ModemManager?
Folks, I am using Ubuntu 10.10 which has ModemManager 0.4+git.20100809t153145.be28 ...and managed to make my Gobi2000 work! See http://ubuntuforums.org/showthread.php?p=9955451#post9955451 My environment: Lenovo Thinkpad X201 (3626-A14) Gobi2000: Bus 002 Device 004: ID 05c6:9205 Qualcomm, Inc. Ubuntu 10.10 Operator: Swisscom (.ch)
I guess this is OBSOLETE then :-) If this is not the case, please reopen.
Please can you tell me the version in which this is fixed?
Please have a look at the forum comment posted above, I described my setup in detail. Ubuntu 10.10 uses NetworkManager 0.8.1.
Okay, so I upgraded to Fedora 14 to test this, and it's the same as in Fedora 13: NetworkManager sees the modem, but it chooses CDMA. This is a problem of how a user can choose the correct firmware. @Alexander List: how did you choose which firmware was right for your modem? What was your strategy?
I used "strings" on the binary files and made an educated guess that the one I was choosing was a generic UMTS one... ;) - it had something like "umts_gen" close to the end of the strings output. Other firmware files had operator names, so I avoided those and the ones containing "CDMA"... Maybe it's just trial and error until you succeed... I think that decent distros should provide packages that will take care of downloading the firmware for the user... the entry barrier is way too high for the average user.
A quick update. Trial and error on all available files in my downloaded firmware failed. strings identified a generic image. That didn't work. I will download newer firmware and try again. btw cabextract can be used to extract the files without wine, doesn't seem to work for newer msi files for some reason.
It works! Here are the md5sums: 2e2477b70787a739e6d9d5f664d1a8fc ./SWSetup/SP50377/Qualcomm/GobiInstaller.msi 54eca52dc3d25f80420339358f0316ff /lib/firmware/gobi/amss.mbn 7d12b38ec6851bef5039b74bffffd423 /lib/firmware/gobi/apps.mbn b458ade5ce489d7ba35a56cf305184c9 /lib/firmware/gobi/uqcn.mbn
One more: 6eb2030dc16c82a15d00c62bd54c5c44 sp50377.exe