[karmic] Can't connect w/ Option Globesurfer Icon 1.8Mbit/s 3G usb Modem

[Simone Tolotti]

I can't connect to the net since Karmic and NM0.8 + modemmanager.
My usb 3G modem is an Option Globesurfer Icon 1.8Mbit/s.

network-manager_0.8~a~git.20090821t171617.0945978 (from networkmanager-daily PPA)
modemmanager 0.2.git.20090820t183237.cd75023-0ubuntu1 (from networkmanager-daily PPA)

lsusb
Bus 006 Device 004: ID 0af0:6600 Option GlobeTrotter 3G+ datacard

dmesg
[ 111.911256] usb 6-2: GSM modem (1-port) converter now attached to ttyUSB0
[ 111.933452] usb 6-2: GSM modem (1-port) converter now attached to ttyUSB1
[ 111.935756] usb 6-2: GSM modem (1-port) converter now attached to ttyUSB2

[Alexander Sack (asac)]

do you have your APN/username/password properly set?

[Simone Tolotti (simontol)]

Yes APN is correct and my provider don't ask for username/password so I left them blank as I do with Jaunty and NM 0.7

[Alexander Sack (asac)]

On Fri, Sep 04, 2009 at 05:33:53PM -0000, Simone Tolotti wrote:
> Yes APN is correct and my provider don't ask for username/password so I
> left them blank as I do with Jaunty and NM 0.7
>

yeah. most likely it doesnt help, but try to set them to something still.
Most likely this is because modemmanager somehow doesnt apply the APN
properly.

 - Alexander

[Simone Tolotti (simontol)]

I've tried to add username and password , I've also tried to disable some of the authentication methods, then I've added manual DNSs, but none of this action helped.

I've noticed that only the first time I try to connect, the connection seems to start (rotating nm-applet icon), when the connection fails, or I stop it, I have to restart NM daemon before I can try another time.

I've also noticed that on Jaunty when I start the connection the lights on the modem are blinking until a successful connection and then they stays on.
On Karmic there are no changes in the modem lights status when I try to connect. So I think that the problem isn't related to the authentication process, IMHO It doesn't start dialing the *99# number at all.
I'm using this modem on Linux since before NM has appeared on my desktop, I had to do a lot of attempts through wvdial (and pon/poff scripts) and I'm pretty sure that even with a wrong APN the lights starts blinking when I try to connect.

Please forgive me for my bad english...hope you understand anyway. ;-)

[Alexander Sack (asac)]

Two things:

1. try the latest daily builds from: https://edge.launchpad.net/~network-manager/+archive/trunk

2. if that does not work, create a file /etc/defaults/NetworkManager and put the following line in it:
   export NM_PPP_DEBUG=1
and restart everything. Attach the modem-manager --debug output and the syslog text for the startup and the first connect attempt to this bug. Thanks!

[Alexander Sack (asac)]

btw i dont really see a ttyUSB connect attempt in your daemon.log ... please attach syslog of such an attempt.

[Simone Tolotti (simontol)]

That's what I did:
- Upgraded packages
NM to 0.8~a~git.20090904t224209.bee58e3-0ubuntu1~nmt1
network-manager-gnome 0.8~a~git.20090906t102542.3835aa6-0ubuntu1~nmt1
modem-manager 0.2.git.20090904t192653.d317254-0ubuntu2~nmt1

- Added /etc/defaults/NetworkManager file
- Restarted my PC
- sudo /etc/init.d/NetworkManager stop
- sudo killall -9 modem-manager
- sudo modem-manager --debug
- sudo /etc/init.d/NetworkManager start
- started the connection through nm-applet.

[Simone Tolotti (simontol)]

I forgot to mention that I had pretty the same problem until Jaunty final.
https://bugs.launchpad.net/network-manager/+bug/347365

[Alexander Sack (asac)]

and there is no other output from ppp in syslog?

[heiko (hkos76)]

my nozomi pcmcia card doesn't show up in the network manager at all.
running karmic alpha with the latest updates from yesterday (including kernel 2.6.31-11)

from lspci:

16:00.2 Network controller: Option N.V. Qualcomm MSM6275 UMTS chip

from dmesg:

[141178.722036] Initializing Nozomi driver 2.1d (build date: Sep 25 2009 06:53:31)
[141178.722085] nozomi 0000:16:00.2: Init, new card found
[141178.722096] nozomi 0000:16:00.2: enabling device (0000 -> 0002)
[141178.722107] nozomi 0000:16:00.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[141178.722114] nozomi 0000:16:00.2: Card type is: 2048
[141179.044309] nozomi 0000:16:00.2: Version of card: 3
[141179.044564] nozomi 0000:16:00.2: Initialization OK!
[141179.687189] nozomi 0000:16:00.2: Device READY!

[Alexander Sack (asac)]

On Mon, Sep 28, 2009 at 08:19:26AM -0000, heiko wrote:
> my nozomi pcmcia card doesn't show up in the network manager at all.
> running karmic alpha with the latest updates from yesterday (including kernel 2.6.31-11)

yes nozomi hacks haven't been properly ported to modemmanager from 0.7 branch yet.

 - Alexander

[Simone Tolotti (simontol)]

Still confirming the bug in :
network-manager 0.8~a~git.20091005t192303.1d28ad1-0ubuntu2
modemmanager 0.2.git.20091003t063318.aa78b5f-0ubuntu1

[Simone Tolotti (simontol)]

It woked once... but NM don't set correct nameservers.

log of the succesful connection:
Oct 9 19:43:55 simone-desktop pppd[1887]: Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded.
Oct 9 19:43:55 simone-desktop pppd[1887]: pppd 2.4.5 started by root, uid 0
Oct 9 19:43:55 simone-desktop pppd[1887]: Using interface ppp0
Oct 9 19:43:55 simone-desktop pppd[1887]: Connect: ppp0 <--> /dev/ttyUSB0
Oct 9 19:43:55 simone-desktop pppd[1887]: CHAP authentication succeeded
Oct 9 19:43:55 simone-desktop pppd[1887]: CHAP authentication succeeded
Oct 9 19:44:03 simone-desktop pppd[1887]: Could not determine remote IP address: defaulting to 10.64.64.64
Oct 9 19:44:03 simone-desktop pppd[1887]: local IP address 217.201.158.125
Oct 9 19:44:03 simone-desktop pppd[1887]: remote IP address 10.64.64.64
Oct 9 19:45:12 simone-desktop pppd[1887]: Terminating on signal 15
Oct 9 19:45:12 simone-desktop pppd[1887]: Connect time 1.2 minutes.
Oct 9 19:45:12 simone-desktop pppd[1887]: Sent 80 bytes, received 96 bytes.
Oct 9 19:45:12 simone-desktop pppd[1887]: Connection terminated.
Oct 9 19:45:13 simone-desktop pppd[1887]: Exit.

/etc/resolv.conf:
# Generated by NetworkManager

When I connect with "pon" script i get:

Oct 9 19:48:55 simone-desktop pppd[2155]: pppd 2.4.5 started by root, uid 0
Oct 9 19:48:56 simone-desktop chat[2157]: timeout set to 60 seconds
Oct 9 19:48:56 simone-desktop chat[2157]: abort on (ERROR)
Oct 9 19:48:56 simone-desktop chat[2157]: abort on (BUSY)
Oct 9 19:48:56 simone-desktop chat[2157]: abort on (VOICE)
Oct 9 19:48:56 simone-desktop chat[2157]: abort on (NO CARRIER)
Oct 9 19:48:56 simone-desktop chat[2157]: abort on (NO DIALTONE)
Oct 9 19:48:56 simone-desktop chat[2157]: abort on (NO DIAL TONE)
Oct 9 19:48:56 simone-desktop chat[2157]: abort on (NO ANSWER)
Oct 9 19:48:56 simone-desktop chat[2157]: send (ATZ^M)
Oct 9 19:48:56 simone-desktop chat[2157]: send (AT&FH0M0^M)
Oct 9 19:48:57 simone-desktop chat[2157]: expect (OK)
Oct 9 19:48:57 simone-desktop chat[2157]: ATZ^M^M
Oct 9 19:48:57 simone-desktop chat[2157]: OK
Oct 9 19:48:57 simone-desktop chat[2157]: -- got it
Oct 9 19:48:57 simone-desktop chat[2157]: send (ATDT*99*#^M)
Oct 9 19:48:57 simone-desktop chat[2157]: timeout set to 75 seconds
Oct 9 19:48:57 simone-desktop chat[2157]: expect (CONNECT)
Oct 9 19:48:57 simone-desktop chat[2157]: ^M
Oct 9 19:48:57 simone-desktop chat[2157]: AT&FH0M0^M^M
Oct 9 19:48:57 simone-desktop chat[2157]: OK^M
Oct 9 19:48:57 simone-desktop chat[2157]: ATDT*99*#^M^M
Oct 9 19:48:57 simone-desktop chat[2157]: CONNECT
Oct 9 19:48:57 simone-desktop chat[2157]: -- got it
Oct 9 19:48:57 simone-desktop pppd[2155]: Serial connection established.
Oct 9 19:48:57 simone-des...

[Alexander Sack (asac)]

there were some parsing improvements that might have helped. can you check latest? Also getting a fresh full modemmanager --debug together with the full syslog would be helpful i think.

[Simone Tolotti (simontol)]

modemmanager 0.2.git.20091011t184434
network-manager 0.8~a~git.20091009t060001

[Alexander Sack (asac)]

did you change your /etc/ppp/options at some point?

[Simone Tolotti (simontol)]

No I didn't manually change /etc/ppp/options.

[Simone Tolotti (simontol)]

I've ugraded the packages:
network-manager_0.8~a~git.20091016t185227.8d65515-0ubuntu2~nmt1_amd64
modemmanager_0.2.git.20091027t005933.4e74953-0ubuntu2~nmt1_amd64
network-manager-gnome_0.8~a~git.20091027t225857.e4cd853-0ubuntu2~nmt1_amd64

Actually it connects (always at the second attempt after booting and restarting the machine) but it doesn't correctly sets DNSs.
It resets /etc/resolv.conf to "# Generated by NetworkManager".
To solve this I've set "chattr +i /etc/resolv.conf".
I've attached NM and MM logs as usual. Thanks for your attention and your work.

[Alexander Sack (asac)]

simone, the dns issue is a separate isseu? or was that always the problem?

[kasade (kasade)]

I'm a subscriber of bug #437766 (marked as a duplicate of this one) and just want to say that my Option Globetrotter 3G still does not work. I can connect with
sudo pon <providername>
but not with Network Manager (neither at the second nor any other attempt).

[Alexander Sack (asac)]

On Fri, Oct 30, 2009 at 06:26:23AM -0000, kasade wrote:
> I'm a subscriber of bug #437766 (marked as a duplicate of this one) and just want to say that my Option Globetrotter 3G still does not work. I can connect with
> sudo pon <providername>
> but not with Network Manager (neither at the second nor any other attempt).

ok. please get fresh logs as mentioned here:

  https://wiki.ubuntu.com/DebuggingModemmanager

 - Alexander

[Simone Tolotti (simontol)]

@alexander : ATM NetworkManager always works for me at the second attempt. The first time I try to connect it seems to start (nm-applet icon shows rotating arrows) but after few seconds it says that the netwok is disconnected. The second time it takes longer to start connecting (2-3 seconds before arrows start to rotate ... in the log I see that NM tries to inizialize the device) but the connection attempt is succesful.
The DNS problem happens every time. It didn't happened in NM 0.7.

[kasade (kasade)]

OK, here are my logs

modemmanager 0.2.git.20091027t005933.4e74953-0ubuntu2~nmt1
network-manager 0.8~a~git.20091016t185227.8d65515-0ubuntu2~nmt1

[Maciej Wisniowski (pigletto-gmail)]

Same problem here. I can't connect after upgrade to Karmic, which is severe bug for me...

modemmanager 0.2.git.20091014t233208.16f3e00-0ubuntu1

lspci:
07:00.0 Network controller: Option N.V. Qualcomm MSM6275 UMTS chip

mm-test:
:~$ python mm-test.py
GSM modem
Driver: 'nozomi'
Modem device: '/sys/devices/pci0000:00/0000:00:1e.0/0000:06:0b.0/0000:07:00.0'
Data device: 'noz0'
Vendor: Option N.V.
Model: GlobeTrotter 3G+
Version: 3.20.3Hd (Date: Sep 28 2006, Time: 14:18:42)
IMEI: <private>
IMSI: <private>
Signal quality: 51
Scanning...
Plus: current (UMTS)
Plus: available (GSM)
Era: forbidden (GSM)
Orange PL: forbidden (GSM)
Orange PL: forbidden (UMTS)
26006: forbidden (GSM)

Attached output of modem, network manager logs.

[Johannes Dahl (surreal)]

I'm using Option GlobeSurfer Icon (0af0:6600 Option GlobeTrotter 3G+ datacard) and therefore am also affected by this bug.

I can confirm that:
- in plain Karmic, I can not connect using NM, not the first or any subsequent time I try.
- in plain Karmic, I can connect by setting up /etc/ppp/peers/foobar (device /dev/ttyUSB0) and running "sudo pon foobar".
- with updates the NetworkManager PPA (https://launchpad.net/~network-manager/+archive/trunk) I can use NM to connect with success on the second try.

Simone Tolotti has already provided logs from situation similar to mine, but let me know if my own particular logs would be of use, I'd be happy to run through DebuggingModemManager in that case.

[Johannes Dahl (surreal)]

For what it's worth, I've noticed that it's not always the second attempt at connecting through NM that succeeds, it can be the third or fourth attempt. I only tried a couple of times without updates from NM PPA and can therefore not say for certain if it would have worked were I more persistent.

[Darren Albers (dalbers)]

I have this same option but if I tail /var/log/messages I see that it doesn't seem to think that a DNS server was passed back. I suspect that maybe the issue is with PPPD and not NetworkManager?

From my logs when it works:
Nov 2 10:18:01 gv00002346181 pppd[3487]: Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded.
Nov 2 10:18:01 gv00002346181 pppd[3487]: pppd 2.4.5 started by root, uid 0
Nov 2 10:18:01 gv00002346181 pppd[3487]: Using interface ppp0
Nov 2 10:18:01 gv00002346181 pppd[3487]: Connect: ppp0 <--> /dev/ttyUSB2
Nov 2 10:18:01 gv00002346181 pppd[3487]: CHAP authentication succeeded
Nov 2 10:18:01 gv00002346181 pppd[3487]: CHAP authentication succeeded
Nov 2 10:18:10 gv00002346181 pppd[3487]: Could not determine remote IP address: defaulting to 10.64.64.64
Nov 2 10:18:10 gv00002346181 pppd[3487]: local IP address 32.179.119.36
Nov 2 10:18:10 gv00002346181 pppd[3487]: remote IP address 10.64.64.64
Nov 2 10:18:10 gv00002346181 pppd[3487]: primary DNS address 209.183.35.23
Nov 2 10:18:10 gv00002346181 pppd[3487]: secondary DNS address 209.183.33.23

This is what I see when it fails:
Nov 2 12:00:04 gv00002346181 pppd[3748]: Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded.
Nov 2 12:00:04 gv00002346181 pppd[3748]: pppd 2.4.5 started by root, uid 0
Nov 2 12:00:04 gv00002346181 pppd[3748]: Using interface ppp0
Nov 2 12:00:04 gv00002346181 pppd[3748]: Connect: ppp0 <--> /dev/ttyUSB5
Nov 2 12:00:04 gv00002346181 NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Nov 2 12:00:04 gv00002346181 NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Nov 2 12:00:04 gv00002346181 pppd[3748]: CHAP authentication succeeded
Nov 2 12:00:04 gv00002346181 pppd[3748]: CHAP authentication succeeded
Nov 2 12:00:12 gv00002346181 pppd[3748]: Could not determine remote IP address: defaulting to 10.64.64.64
Nov 2 12:00:12 gv00002346181 pppd[3748]: Cannot determine ethernet address for proxy ARP
Nov 2 12:00:12 gv00002346181 pppd[3748]: local IP address 32.179.27.166
Nov 2 12:00:12 gv00002346181 pppd[3748]: remote IP address 10.64.64.64

When I manually set a DNS server in Network Manager it always works.

Thanks!

[Robert Hrovat (robi-hipnos)]

For Karmic this is a major step back. I've tried to use 3G connection with Option Globetrtotter, 3G Quad, Novatel MC950D and none of them works! They are all detected by kernel but NetworkManager doesn't do anything.

[akuklev (alexander-kuklev)]

Still doesn't work.

Network Card: Option GlobeTrotter 3G (Option N.V. Qualcomm MSM6275 UMTS chip)
network-manager 0.8~a~git.20091103t012953.dccdf5e-0ubuntu1~nmt1 (from networkmanager PPA)
modemmanager 0.2.git.20091031t001131.107f950-0ubuntu2~nmt1 (from networkmanager PPA)

When I try to connect for the first time, it tries for a while and says that it's disconnected. If I try again, machine becomes very slow and syslog grows at megabyte a minute rate by repeated entries of the following kind:

NetworkManager: <info> Activation (noz0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (noz0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info> (noz0): device state change: 6 -> 4 (reason 0)
NetworkManager: <info> (noz0): device state change: 4 -> 6 (reason 0)
NetworkManager: <info> Activation (noz0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <info> Activation (noz0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (noz0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <info> (noz0): device state change: 6 -> 4 (reason 0)
(and so on)

[Alexander Sack (asac)]

marking fix committed even though first connect attempt seems to still fail for some; that should go to a different bug.

[Alexander Sack (asac)]

akuklev, you have a nozomi modem ... not an option - which is what this bug is about. please file a new bug as you have a different issue.

[Alexander Sack (asac)]

On Mon, Nov 02, 2009 at 06:54:54PM -0000, Darren Albers wrote:
> I have this same option but if I tail /var/log/messages I see that it
> doesn't seem to think that a DNS server was passed back. I suspect
> that maybe the issue is with PPPD and not NetworkManager?

yes. its probably a pppd issue in combination with bad modem firmwares that have
troubles with pppd handshakes.

afaik we add a fallback dns now in daily builds if you dont get any DNS ... can you
try that?

 - Alexander

[Simone Tolotti (simontol)]

I'm wondering how it may have been marked as 'fix released'.
Today I've tried t connect 4 times without success, and I have to use my pon script to reach the net.
I've googled around and it seems that a lot of 3G modems aren't supported by NM0.8 and ModemManager.
I'm also wondering why NM0.8 was included in Karmic despite this kind of regressions.
I'm expecting to find an alert on ubuntu.com that says: "If you have a 3G modem please don't upgrade to Karmic!!!"

[Simone Tolotti (simontol)]

I have to add that Empathy depends on NM now, and if I connect to the net using the pon script, I can't use the IM app because it doesn't see an active internet connection.

[Alexander Sack (asac)]

On Mon, Nov 09, 2009 at 05:54:44PM -0000, Simone Tolotti wrote:
> I'm wondering how it may have been marked as 'fix released'.
> Today I've tried t connect 4 times without success, and I have to use my pon script to reach the net.
> I've googled around and it seems that a lot of 3G modems aren't supported by NM0.8 and ModemManager.
> I'm also wondering why NM0.8 was included in Karmic despite this kind of regressions.
> I'm expecting to find an alert on ubuntu.com that says: "If you have a 3G modem please don't upgrade to Karmic!!!"
>

you confirmed that it works on second attempt. the DNS issue is
unrelated, but should be fix committed too in daily ppa mentioned.

 - Alexander

[Simone Tolotti (simontol)]

Actually it doesn't ever connect at the second attempt, sometimes at the third fourth and so on...and sometimes it doesn't work at all.
I'm still wondering how you could say that the bug is fixed even if it would always working at the second attempt.
It seems that the DNS problem is corrected.

[Luca Aluffi (aluffilu)]

Come on Simone, don't bother them. They're trying to help, not to harm you. You can always install 9.04, which is a great release, and wait for the problem to be solved.

By this weekend, I'll have a partition set up only for test with you're PPA so feel free to call me for guinea pig duties :) :)

[Luca Aluffi (aluffilu)]

Read, before post, read... "...your PPA", not "...you're PPA"

:D

[Alexander Sack (asac)]

On Tue, Nov 10, 2009 at 10:23:19PM -0000, Luca Aluffi wrote:
> Come on Simone, don't bother them. They're trying to help, not to harm
> you. You can always install 9.04, which is a great release, and wait for
> the problem to be solved.
>
> By this weekend, I'll have a partition set up only for test with you're
> PPA so feel free to call me for guinea pig duties :) :)
>

Thanks, Luca. Can you reproduce this particular issue too?

please get the debug logs as here:
https://wiki.ubuntu.com/DebuggingModemmanager too ... with latest PPA
packages.

Thanks!

 - Alexander

[Simone Tolotti (simontol)]

@Luca, Alexander: I'm sending Nm and MM logs since about 3 months, so I'm also trying to help. I never asked them to hurry up or lamented about this bug.
The only thing that bother me is that the bug is marked as fixed when it is not.

Thanks,
Simone

PS. There is no problem for me to use a pon/poff script to connect with the modem (that is the only way I have to reach the web), but I'm thinking at the normal user that after upgrading to Karmic has lost his ability to connect to the net.
Moreover a lot of apps (at least in Gnome) depends on NM, for example Evolution and Empathy.
PPS. I have 4 partitions on my PC with Jaunty,Karmic (Gnome), Karmic (KDE, the one I use everyday) and OpenSUSE 11.2. ;-)

[Alexander Sack (asac)]

Simone, last log you sent was 28th Oct which does not show this bug because that one connects successfully, just doesn't get a DNS (and thats why i marked it fix committed) ... also that's why i asked you to send updated logs (with latest daily builds) in comment #48 that captures a failed connect attempt ... please follow the wiki page instructions for that!!

[Simone Tolotti (simontol)]

@alexander, my apologies , you're right.

Today's logs (NM worked at the second attempt):
nm 0.8~a~git.20091112t160951.16c18a0-0ubuntu1~nmt1~karmic
mm 0.2.git.20091104t211123.74f679a-0ubuntu2~nmt1

[Simone Tolotti (simontol)]

NM 0.8~a~git.20091113t224013.f7d7b31-0ubuntu1~nmt1~karmic
MM 0.2.git.20091104t211123.74f679a-0ubuntu2~nmt1

Today it doesn't worked at all. I've tried three times without success and then I've unplugged and re-plugged the modem and tried again two times.

[Simone Tolotti (simontol)]

Today network-manager worked at the 4th attempt:
0.8~a~git.20091117t004859.1151ac2-0ubuntu1~nmt1~karmic
0.2.git.20091104t211123.74f679a-0ubuntu2~nmt1

[pedrito (piotr-pass+ubuntu)]

Hi,

I think it's important to add that (at least in my case) the 3G PCMCIA
Option Globetrotter 3G+ modem worked (and works) correctly up to
kernel 2.6.28-11-generic, while the problem occurs with the standard
kernel 2.6.31-14-generic.

Regards,
Pedrito

[Alexander Sack (asac)]

On Wed, Nov 18, 2009 at 03:57:00PM -0000, pedrito wrote:
> Hi,
>
> I think it's important to add that (at least in my case) the 3G PCMCIA
> Option Globetrotter 3G+ modem worked (and works) correctly up to
> kernel 2.6.28-11-generic, while the problem occurs with the standard
> kernel 2.6.31-14-generic.

can you try to use that old kernel again?

 - Alexander

[pedrito (piotr-pass+ubuntu)]

On Wed, Nov 25, 2009 at 12:13, Alexander Sack <email address hidden> wrote:
> can you try to use that old kernel again?

I'm still using it whenever I need to connect via this modem.
With kernel 2.6.28-11-generic the connection works flawlessly. Other
thing is that the system in general doesn't - everything is slooow ;)

-- Pedrito

[Simone Tolotti (simontol)]

I can confirm that the issue could be kernel related. I've tried both 2.6.28-16 (from jaunty-updates) and 2.6.31-15 on the same system (Karmic amd64) with the same mm and nm version (latest from ppa).
When booting kernel 2.6.28-16 NM connects at the first attempt. When running 2.6.31-15 it connects at the sencond (third..fourth) and it takes much longer before connecting (10-20 sec.).
How do I get debug logs for this situation?

[Edouard Orcel (edouard-orcel)]

Alexander, you said "akuklev, you have a nozomi modem ... not an option - which is what this bug is about. please file a new bug as you have a different issue." but we created 2 bugs about the same modemmanager/networkmanager problems with a nozomi modem. The fact is that no developper is looking/working on these bugs 425312 and 481767...

Can you please have a look on these ?

Thanks

[Simone Tolotti (simontol)]

@Edouard: I think that the bugs are in some manner related. I've read that the workaround for nozomi modems is use the module from the 2.6.28 series kernel. I also had success running a 2.6.28 kernel.

I'll file a bug upstream (linux bugzilla), I think you should do the same.

[Simone Tolotti (simontol)]

I seems to be fixed. I'm succesfully running
network-manager 0.8~rc2~git.20100114t223002.d20c61a-0ubuntu1~nmt1~karmic
modemmanager 0.2.git.20100112t172936.a4fee86-0ubuntu1~nmt1~karmic
linux 2.6.31.18.31
Marking it as fixed - fix released, thanks to all!

[AlexHofbauer (alex-derhofbauer)]

I just compiled and tested master.

After installing network-manager and modemmanager I stopped the first one, killed modem-manager and started network-manager.

The first try to connect worked without any problems. Then, after disconnecting I could not get it to connect, with "Looks like pppd didn't initialize our dbus module" and "modem-manager: Got failure code 3: No carrier" as error messages.

Even after rebooting I can't get it to work any more. It worked once some days ago, also with installing a new master build and killing modem-manager / restarting network-manager and I also could not connect after disconnecting or reboot. There must be a reason for that.

[[e-mail] (kabiersch)]

Hi,
I was suprised and looked forward after the news. Indeed, modemmanager and network-manager could admin my "Qualcomm 3G CDMA" card, no stackdumps anymore.
But, it comes up, that no connection could be established, and no knwon reason found for that.
Main sniplet comes here:
...
Jan 19 12:40:46 CL0L3LTLB3 modem-manager: Modem /org/freedesktop/ModemManager/Modems/1: state changed (registered -> connecting)
Jan 19 12:41:46 CL0L3LTLB3 modem-manager: Modem /org/freedesktop/ModemManager/Modems/1: state changed (connecting -> registered)
Jan 19 12:41:46 CL0L3LTLB3 NetworkManager: <WARN> stage1_prepare_done(): GSM modem connection failed: (32) No cause information available
...
hope this helps investigating.

[[e-mail] (kabiersch)]

just another: modemmanager now complains about ppp0 missing config:

 20 19:29:27 CL0L3LTLB3 NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Jan 20 19:29:27 CL0L3LTLB3 NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Jan 20 19:29:47 CL0L3LTLB3 NetworkManager: <WARN> pppd_timed_out(): Looks like pppd didn't initialize our dbus module

[[e-mail] (kabiersch)]

After fix still the same:

0.3-0ubuntu1~nmt1~karmic
0.8~rc2-0ubuntu2~nmt3~karmic

updated by update-manager today

[Simone Tolotti (simontol)]

After kernel upgrade to 2.6.31-19 NM has stopped working again. :-(

[Simone Tolotti (simontol)]

I've found that linux-image-2.6.31-19 matches kernel version 2.6.31.6.
My previous (the working one) linux-image was 2.6.31-18 that matches kernel version 2.6.31.9.
More info here:
http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html

[Simone Tolotti (simontol)]

Upgrading to kernel 2.6.31-20 (based on 2.6.31.9) solves the problem again.