[413c:8147] Network Manager cannot connect using embedded Dell 5530 Mobile Broadband device (Ericsson F3507g)

Bug #1114575 reported by Bernadette Addison
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ModemManager
Unknown
Medium
modemmanager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Greetings, I am having this ongoing issue with Ubuntu. Network Manager sees "New GSM conncetion", and it walks me thru the setup for AT&T LaptopConnect (using 'broadband' as the APN). But it never ever connects successfully. I have tried this on Ubuntu 12.04, and now I am even trying it on Ubuntu 13.04. This just does NOT work.

I have the Dell 5530 Mobile Broadband card. I have gone thru all the steps for troubleshooting the network card. I am at a loss as to what the next steps are. I have created a *.doc file which contains all the outputs for the different test commands I have run. I will attach it here.

Assistance is badly needed here. I am considering rolling out Ubuntu to all of the project managers at my company....roughly 40 laptops. But they ALL have this internal mobile broadband card. Without a fix, I will have to settle on Windows8, and not too happy with that as a solution either.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: modemmanager 0.6.0.0.really-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.8-0ubuntu4
Architecture: i386
Date: Sun Feb 3 15:03:59 2013
InstallationDate: Installed on 2013-02-02 (1 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130202)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: modemmanager
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Bernadette Addison (baddison1968) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in modemmanager (Ubuntu):
status: New → Confirmed
Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Please attach debug logs for modemmanager.

Changed in modemmanager (Ubuntu):
status: Confirmed → Incomplete
tags: added: precise
Revision history for this message
Bernadette Addison (baddison1968) wrote :

bernadette@E4300HJZH1L1:~$ wget http://cgit.freedesktop.org/ModemManager/ModemManager/plain/test/mm-test.py
--2013-02-03 20:19:19-- http://cgit.freedesktop.org/ModemManager/ModemManager/plain/test/mm-test.py
Resolving cgit.freedesktop.org (cgit.freedesktop.org)... 131.252.210.161
Connecting to cgit.freedesktop.org (cgit.freedesktop.org)|131.252.210.161|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 15258 (15K) [text/plain]
Saving to: `mm-test.py'

100%[======================================>] 15,258 52.9K/s in 0.3s

2013-02-03 20:19:20 (52.9 KB/s) - `mm-test.py' saved [15258/15258]

bernadette@E4300HJZH1L1:~$ sudo killall NetworkManager
[sudo] password for bernadette:
bernadette@E4300HJZH1L1:~$ sudo killall NetworkManager
bernadette@E4300HJZH1L1:~$ sudo killall modem-manager; sudo modem-manager --debug 2>&1 | tee /tmp/modem.log.txt
modem-manager[3994]: <info> [1359940922.798109] [main.c:167] main(): ModemManager (version 0.5.2.0) starting...
modem-manager[3994]: <warn> [1359940922.813361] [main.c:98] create_dbus_proxy(): Could not acquire the org.freedesktop.ModemManager service as it is already taken. Return: 3
bernadette@E4300HJZH1L1:~$ export NM_PPP_DEBUG=1
bernadette@E4300HJZH1L1:~$ sudo NetworkManager --no-daemon 2>&1 | tee /tmp/nm.log.txt
NetworkManager is already running (pid 3976)
bernadette@E4300HJZH1L1:~$ python ./mm-test.py
GSM modem
Driver: 'cdc_ether'
Modem device: '/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-6'
Data device: 'wwan0'
Error enabling modem: org.freedesktop.ModemManager.Modem.SerialResponseTimeout: Serial command timed out
bernadette@E4300HJZH1L1:~$

Revision history for this message
Bernadette Addison (baddison1968) wrote :

also attaching modem.log.txt....

Revision history for this message
Bernadette Addison (baddison1968) wrote :

all logs have been attached.

Revision history for this message
Aleksander Morgado (aleksander-m) wrote :

Modem log is useless... :(

Revision history for this message
Aleksander Morgado (aleksander-m) wrote :

Could you retry to get MM logs, but this time making sure that you actually get the log properly?

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

I think you must ensure that modemmanager is actually stopped first. It might take some time, so don't put startup right after.

Also there might be a /etc/init.d/modemmanager to try to run "stop" on.

Revision history for this message
Bernadette Addison (baddison1968) wrote :

Sorry....better modem log attached

Revision history for this message
Bernadette Addison (baddison1968) wrote :

and better nm log attached...

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

The logs look all good, but it seems that you don't try to connect using the modem? Could you please include modemmanager debug logs after you have tried connecting.

Revision history for this message
Bernadette Addison (baddison1968) wrote :

clearly I am doing something wrong?? can you give me the proper syntax to run mm while still collecting debug logs? I keep getting this error when trying to do both:
bernadette@E4300HJZH1L1:~$ python ./mm-test.py
GSM modem
Driver: 'cdc_ether'
Modem device: '/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-6'
Data device: 'wwan0'
Vendor: Dell
Model: D5530
Version: R1D06
IMEI: <private>
IMSI: <private>
Signal quality: 0
Scanning...
Error scanning: org.freedesktop.ModemManager.Modem.Gsm.NoNetwork: No network service

bernadette@E4300HJZH1L1:~$ sudo killall modem-manager
bernadette@E4300HJZH1L1:~$ sudo modem-manager --debug 2>&1 | tee /tmp/modem.log.txt
modem-manager[4066]: <info> [1360074445.186148] [main.c:167] main(): ModemManager (version 0.5.2.0) starting...
modem-manager[4066]: <warn> [1360074445.188709] [main.c:98] create_dbus_proxy(): Could not acquire the org.freedesktop.ModemManager service as it is already taken. Return: 3
bernadette@E4300HJZH1L1:~$ sudo modem-manager --debug 2>&1 | tee /tmp/modem.log.txt
modem-manager[4085]: <info> [1360074474.037196] [main.c:167] main(): ModemManager (version 0.5.2.0) starting...
modem-manager[4085]: <warn> [1360074474.039562] [main.c:98] create_dbus_proxy(): Could not acquire the org.freedesktop.ModemManager service as it is already taken. Return: 3
bernadette@E4300HJZH1L1:~$ sudo modem-manager --debug 2>&1 | tee /tmp/modem.log.txt
modem-manager[4092]: <info> [1360074480.358083] [main.c:167] main(): ModemManager (version 0.5.2.0) starting...
modem-manager[4092]: <warn> [1360074480.365911] [main.c:98] create_dbus_proxy(): Could not acquire the org.freedesktop.ModemManager service as it is already taken. Return: 3

Still getting my feet wet here with Ubuntu....so I'm not sure what I'm doing wrong??? Thanks in advacne

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

It is important to first run "sudo stop network-manager" and then "sudo stop modemmanager". Then repeat " sudo killall modem-manager" until it says that no processes were killed, before starting it again with debug.

Revision history for this message
Bernadette Addison (baddison1968) wrote :

Did that. Got the same results in the modem.log.txt previously posted. Now that the network-manager has stopped, even after restartin mm in debug mode, there is no way for me to launch network connections to try to connect to the mobile broadband modem. When I go to apps, network...none of the connections are there anymore. Only a reboot brings everything back. It looks like once I disabel everything in order to get into debug mode, there's no way to start any connections.....???? Am I still missing a step or a command??

When I try to close TERMINAL, it tells me "There is still a process running in this terminal. Closing the terminal will kill it". But with my naked eyes, I don't see terminal doing anthing at all even after letting it sit for over 20minutes?

Revision history for this message
Aleksander Morgado (aleksander-m) wrote :

This page should have all the steps you need to gather proper debug logs:
https://wiki.ubuntu.com/DebuggingModemmanager

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Hmm, I'm not sure. I suggest you post a log here of all commands you run in which order, and post a screenshot when all is started in debug mode.

Which desktop environment do you use? In Unity, I have experienced that nm-applet dies when doing this. Running "nm-applet" after ALT-F2 or in a terminal should get it running again.

Revision history for this message
Bernadette Addison (baddison1968) wrote :

@Aleksander - this is EXACLY what I am following....in the order it is written.

@Marius - you are correct. I no longer have an NM applet available to me, so I cannot initiate a new connection. I will try your suggestion about restarting the applet.

Thanks to you both for your patience with me. Will be right back...... :-)

Revision history for this message
Bernadette Addison (baddison1968) wrote :
Download full text (6.4 KiB)

Ok....getting CLOSER and CLOSER!! Did a bit more digging, searching, reading, testing!!

I am able to manually configure wvdial.conf with some settings to initialize the Dell 5530 Mobile Broadband card.
I "think" I am even able to get it to talk to the AT&T Wireless network.

But that's where all the joy stops. aaarrrrrgggghhhh.....

I keep getting this output when I manually connect:

bernadette@E4300HJZH1L1:~$ sudo wvdial ATT
--> WvDial: Internet dialer version 1.61
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: AT+CFUN=1
AT+CFUN=1
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT+CGDCONT=1, "IP", "Broadband"
AT+CGDCONT=1, "IP", "Broadband"
OK
--> Modem initialized.
--> Sending: ATDT*99#
--> Waiting for carrier.
ATDT*99#
~[7f]}#@!}!}!} }9}#}%B#}%}(}"}'}"}"}&} } } } }%}&}1[1a]}=-0g~
CONNECT
--> Carrier detected. Waiting for prompt.
~[7f]}#@!}!}"} }9}#}%B#}%}(}"}'}"}"}&} } } } }%}&}1[1a]}=-|}*~
--> PPP negotiation detected.
--> Starting pppd at Tue Feb 5 11:23:44 2013
--> Pid of pppd: 3888
--> Using interface ppp0
--> pppd: [18]�x[08]�[02]y[08](�x[08]
--> pppd: [18]�x[08]�[02]y[08](�x[08]
--> pppd: [18]�x[08]�[02]y[08](�x[08]
--> pppd: [18]�x[08]�[02]y[08](�x[08]
--> pppd: [18]�x[08]�[02]y[08](�x[08]
--> pppd: [18]�x[08]�[02]y[08](�x[08]
--> pppd: [18]�x[08]�[02]y[08](�x[08]
--> Disconnecting at Tue Feb 5 11:23:45 2013
--> The PPP daemon has died: A modem hung up the phone (exit code = 16)
--> man pppd explains pppd error codes in more detail.
--> Try again and look into /var/log/messages and the wvdial and pppd man pages for more information.
--> Auto Reconnect will be attempted in 5 seconds
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: AT+CFUN=1
AT+CFUN=1
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT+CGDCONT=1, "IP", "Broadband"
AT+CGDCONT=1, "IP", "Broadband"
OK
--> Modem initialized.
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: AT+CFUN=1
AT+CFUN=1
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT+CGDCONT=1, "IP", "Broadband"
AT+CGDCONT=1, "IP", "Broadband"
OK
--> Modem initialized.
--> Sending: ATDT*99#
--> Waiting for carrier.
ATDT*99#
~[7f]}#@!}!}!} }9}#}%B#}%}(}"}'}"}"}&} } } } }%}&/9F}'<X~
CONNECT
--> Carrier detected. Waiting for prompt.
~[7f]}#@!}!}"} }9}#}%B#}%}(}"}'}"}"}&} } } } }%}&/9F}'p5~
--> PPP negotiation detected.
--> Starting pppd at Tue Feb 5 11:23:54 2013
--> Pid of pppd: 3905
--> Using interface ppp0
--> pppd: [18]�x[08]�[02]y[08](�x[08]
--> pppd: [18]�x[08]�[02]y[08](�x[08]
--> pppd: [18]�x[08]�[02]y[08](�x[08]
--> pppd: [18]�x[08]�[02]y[08](�x[08]
--> pppd: [18]�x[08]�[02]y[08](�x[08]
--> pppd: [18]�x[08]�[02]y[08](�x[08]
--> pppd: [18]�x[08]�[02]y[08](�x[08]
--> Disconnecting at Tue Feb 5 11:23:54 2013
--> The PPP daemon has died: A modem hung up the phone (exit code = 16)
--> man pppd explains pppd error codes in more detail.
--> Try again and look into /var/log/messages and the wvdial and pppd man pages for more information.
--> Auto Reconn...

Read more...

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Wvdial can be nice tool for testing and using unsupported modems (and for advanced users), but it will not be much user friendly, so you should really try to use modemmanager instead and get the logs as described above.

Revision history for this message
Bernadette Addison (baddison1968) wrote :

Ok......FINALLY!! I was able to capture an mmlog while attempting to connect to AT&T wireless, using the GSM connection in Network Manager. Here is the attached txt file. sorry to be jumping all over the place, but I really need to get this up and running.

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Still can't see any connection attempt. Cold you please include NM logs too.

Revision history for this message
Bernadette Addison (baddison1968) wrote :

OK....once again. New nm.log file

Revision history for this message
Bernadette Addison (baddison1968) wrote :

...and another modem.log file

Please tell me this time, they contain some valid information for you.....

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Hmm japp, looks better now. Which Ubuntu version do you use? I noticed the old modemmanager 0.5 used.

Anyway, looking quickly on it it seems that it report no signal. Are you sure that the antenna is connected and a correct SIM card is inserted and that the test location has network coverage?

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Are you able to test connection using Windows using the same test conditions?

Revision history for this message
Aleksander Morgado (aleksander-m) wrote :

Your modem is saying this:

CREG: 2,4

Which means that the registration state is UNKNOWN (4); so it wasn't registered to the network.

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Also it would be interesting to know how the latest version of network-/modemmanager works by adding this PPA: https://launchpad.net/~network-manager/+archive/trunk

Revision history for this message
Bernadette Addison (baddison1968) wrote :

@Marius - I was able to remove the SIM card from out of the back of the Dell laptop, and put the card in another AT&T USB wifi device. Then I installed it to my Windows7 machine using AT&T Connection Mananger v7.2 The card worked fine! I was on the AT&T network in no time at all. I was even able to use the GPS (Location) functions with the card.

Currently I am running UBUNTU 12.04-LTS, and using whatever modemmanager comes with the original CD *.iso I had to format the harddrive and downgrade from 13.04 because I want depserately to roll this out to about +/-40 project managers' laptops. So I need to get this working on the "stable" version of Ubuntu.

@Aleksander - I noticed that, too. However ...If you look at my post #19, you'll see that I actually DID make a successful connection to AT&T using the modified wvdial.conf script. Is there any way to make the modemmanager confing script use those AT commands that the wvdial.conf script is using? Maybe it can get me a successful registration state if it were sending the proper commands.

....Just thinking out loud here :-/

Oh - and Marius, I will go now and attempt to install the latest version of mm via PPA? Don't know what that means yet, or even how to do the install, but I am eternally grateful for all the learning , and knowledge I'm getting here!!

Revision history for this message
Bernadette Addison (baddison1968) wrote :

OK....so I added the PPA, and upgraded the modemmanager, and the network manager. Ran the mm debugging again and here are the log files. Still not getting connected to AT&T. :-/

Revision history for this message
Bernadette Addison (baddison1968) wrote :

...and newest nm log, too.

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Hmm, where did you get the wvdial config from? There is some "+FCLASS=0" there I haven't seen before.

Revision history for this message
Bernadette Addison (baddison1968) wrote :

I got this script from another launchpad bug report where the user was successful in getting his to connect:

https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/540003

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Please add the result of "lsusb" in a terminal.

no longer affects: modemmanager
Revision history for this message
Bernadette Addison (baddison1968) wrote :

Here it is....

bernadette@E4300HJZH1L1:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 413c:8147 Dell Computer Corp. F3507g Mobile Broadband Module
Bus 005 Device 002: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
bernadette@E4300HJZH1L1:~$

Revision history for this message
Bernadette Addison (baddison1968) wrote :

What does this mean: "no long affects:modemmanager" ???

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Oops, somehow the connection to the new upstream bug report I opened disappeared. Fixed it.

summary: - Network Manager cannot connect using embedded Dell 5530 Mobile Broadband
- device
+ [413c:8147] Network Manager cannot connect using embedded Dell 5530
+ Mobile Broadband device (Ericsson F3507g)
Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Closing as per upstream bug report. Antenna was not properly connected.

Changed in modemmanager (Ubuntu):
status: Incomplete → Invalid
Changed in modemmanager:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.