[nozomi] NetworkManager does not recognize Option Fusion+ PCMCIA-card

we need to debug logs as described here: https://wiki.ubuntu.com/DebuggingModemmanager

restarting modem-manager and NetworkManager now made NetworkManager recognice the device

Okay, I'm sorry, I should have checked that before. The card is actually recognized if it is already inserted on boot. It just does not show up if it is inserted after logging in.
Getting a connection with the card after it shows up is also not possible, daemon.log for this is attached. Should I also try connecting with the commands from https://wiki.ubuntu.com/DebuggingModemmanager ?

i seem to have the same card

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

with the latest packages, i also don't see "Mobile Broadband" in nm-applet, before restarting modem-manager and network-manager.

after restarting them, when i try to connect (to simyo), this is what modem-manager logs when i try to connect:

** Message: (noz0) opening serial device...
** (modem-manager:19780): DEBUG: (noz0): --> 'ATZ E0 V1 X4 &C1 +CMEE=1<CR>'
** (modem-manager:19780): DEBUG: (noz0): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:19780): DEBUG: (noz0): --> 'ATE0 +CMEE=1<CR>'
** (modem-manager:19780): DEBUG: (noz0): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:19780): DEBUG: (noz0): --> 'AT+CREG=0<CR>'
** (modem-manager:19780): DEBUG: (noz0): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:19780): DEBUG: (noz0): --> 'AT+CFUN=1<CR>'
** (modem-manager:19780): DEBUG: (noz0): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:19780): DEBUG: (noz0): --> 'AT+CPIN?<CR>'
** (modem-manager:19780): DEBUG: (noz0): <-- '<CR><LF>+CPIN: READY<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:19780): DEBUG: (noz0): --> 'AT+COPS=0,,<CR>'
** (modem-manager:19780): DEBUG: (noz0): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:19780): DEBUG: (noz0): --> 'AT+CREG?<CR>'
** (modem-manager:19780): DEBUG: (noz0): <-- '<CR><LF>+CREG: 0,1<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:19780): DEBUG: (noz0): --> 'AT+CGDCONT?<CR>'
** (modem-manager:19780): DEBUG: (noz0): <-- '<CR><LF>+CGDCONT: 1,"IP","internet.eplus.de","",0,0<CR><LF><CR><LF>OK<CR><LF>'
** (modem-manager:19780): DEBUG: (noz0): --> 'AT+CGDCONT=1, "IP", "internet.eplus.de"<CR>'
** (modem-manager:19780): DEBUG: (noz0): <-- '<CR><LF>OK<CR><LF>'
** (modem-manager:19780): DEBUG: (noz0): --> 'ATD*99***1#<CR>'
** (modem-manager:19780): DEBUG: (noz0): <-- '<CR><LF>CONNECT 1800000<CR><LF>'
** Message: (noz0) closing serial device...

output of the python script:

# python ./mm-test.py
GSM modem
Driver: 'nozomi'
Modem device: '/sys/devices/pci0000:00/0000:00:1e.0/0000:15:00.0/0000:16:00.2'
Data device: 'noz0'
Vendor: Option N.V.
Model: GlobeTrotter 3G+
Version: 3.20.0BHd (Date: Sep 21 2006, Time: 14:21:00)
IMEI: &lt;private&gt;
IMSI: &lt;private&gt;
Signal quality: 35
Scanning...
simyo: current
simyo: available
T-Mobile D: forbidden
o2 - de: forbidden
Vodafone.de: forbidden
Vodafone.de: forbidden
T-Mobile D: forbidden
o2 - de: forbidden

As this is still not working in the beta, is there any other info you need?

I tried running wvdial and getting a connection with that, but also to no luck. Output is:

--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
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","internet.eplus.de"
AT+CGDCONT=1,"IP","internet.eplus.de"
OK
--> Modem initialized.
--> Sending: ATD*99#
--> Waiting for carrier.
ATD*99#
CONNECT 1800000
--> Carrier detected. Starting PPP immediately.
--> Starting pppd at Tue Oct 6 16:59:39 2009
--> Pid of pppd: 5176
--> Using interface ppp0
--> pppd: �[7f]
--> pppd: �[7f]
--> pppd: �[7f]
--> pppd: �[7f]
--> pppd: �[7f]
--> Disconnecting at Tue Oct 6 17:00:10 2009
--> 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

/var/log/messages repeats the same message over and over:

Oct 6 16:45:42 Hamlet pppd[30668]: pppd 2.4.5 started by root, uid 0
Oct 6 16:45:42 Hamlet pppd[30668]: Using interface ppp0
Oct 6 16:45:42 Hamlet pppd[30668]: Connect: ppp0 <--> /dev/noz0
Oct 6 16:46:12 Hamlet pppd[30668]: LCP: timeout sending Config-Requests
Oct 6 16:46:12 Hamlet pppd[30668]: Connection terminated.
Oct 6 16:46:12 Hamlet pppd[30668]: Modem hangup
Oct 6 16:46:12 Hamlet pppd[30668]: Exit.

Can confirm the behavior on 9.10 (today) with a Globetrotter 3G+.

Problem still exist in Released Jaunty... Nozomi /dev/noz0 is there but network manager does not ick up the device ....
Any Ideas ?

Sorry shoul dhave read :Karmic ....

I can confirm the bug...

Ubuntu Karmic 32bit, all updates
modemmanager 0.2.git.20091014t233208.16f3e00-0ubuntu1
network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1

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

daemon.log:
modem-manager: (noz2) opening serial device...
modem-manager: (noz1) opening serial device...
modem-manager: (noz0) opening serial device...
modem-manager: (noz3) opening serial device...

modem log

nm log

mm-test.py log

Amazing... Network Manager Applet is showing a Mobile Broadband connection since the last restart...
So the bug is now unconfirmed

The Network Manager worked only once !
Since my last restart no mobile broadband is visible even if my qualcom card is connected before the boot.

I did some tests and network manager can now see my card but the connection doesn't work...

To see my card working with network manager I did :
sudo stop network-manager
sudo killall modem-manager; sudo modem-manager
sudo NetworkManager --no-daemon

NetworkManager: <debug> [1258055138.000790] ensure_killed(): waiting for ppp pid 2494 to exit
NetworkManager: <debug> [1258055138.257498] ensure_killed(): ppp pid 2494 cleaned up
NetworkManager: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
NetworkManager: Tried to set deprecated property gsm/band
NetworkManager: <info> Activation (noz0) starting connection 'Orange Business'
NetworkManager: <info> (noz0): device state change: 3 -> 4 (reason 0)
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: 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)
NetworkManager: <info> Activation (noz0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <info> Activation (noz0) Stage 2 of 5 (Device Configure) scheduled...
NetworkManager: <info> Activation (noz0) Stage 2 of 5 (Device Configure) starting...
NetworkManager: <info> (noz0): device state change: 4 -> 5 (reason 0)
NetworkManager: <info> Activation (noz0) Stage 2 of 5 (Device Configure) successful.
NetworkManager: <info> Activation (noz0) Stage 3 of 5 (IP Configure Start) scheduled.
NetworkManager: <info> Activation (noz0) Stage 2 of 5 (Device Configure) complete.
NetworkManager: <info> Activation (noz0) Stage 3 of 5 (IP Configure Start) started...
NetworkManager: <info> (noz0): device state change: 5 -> 7 (reason 0)
NetworkManager: <info> Starting pppd connection
NetworkManager: <debug> [1258055216.265407] nm_ppp_manager_start(): Command line: /usr/sbin/pppd nodetach lock nodefaultroute user orange noz0 noipdefault noauth usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/4 plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so
NetworkManager: <debug> [1258055216.269425] nm_ppp_manager_start(): ppp started with pid 2524
NetworkManager: <info> Activation (noz0) Stage 4 of 5 (IP6 Configure Get) scheduled...
NetworkManager: <info> Activation (noz0) Stage 3 of 5 (IP Configure Start) complete.
NetworkManager: <info> Activation (noz0) Stage 4 of 5 (IP6 Configure Get) started...
NetworkManager: <info> Activation (noz0) Stage 4 of 5 (IP6 Configure Get) complete.
Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded.
** Message: nm-ppp-plugin: (plugin_init): initializing
** Message: nm-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection'
Removed stale lock on noz0 (pid 2494)
NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
NetworkManager: SCPlugin-Ifupd...

mine; 0b:00.2 Network controller: Option N.V. Qualcomm MSM6275 UMTS chip also unable to work with karmic

Hi all,

we have two problems here.

1* Network Manager bug with recognice UMTS device - still does not work
and
2* nozomi bug: ppp do not get IP even if I try to use gcom for registration (this step working fine) and wvdial (but this step fail).

i get the same result as Franz Dietzmann wrote on 2009-10-06

Nov 15 21:45:49 hafalump pppd[25707]: pppd 2.4.5 started by root, uid 0
Nov 15 21:45:49 hafalump pppd[25707]: Using interface ppp0
Nov 15 21:45:49 hafalump pppd[25707]: Connect: ppp0 <--> /dev/noz0
Nov 15 21:46:19 hafalump pppd[25707]: LCP: timeout sending Config-Requests
Nov 15 21:46:19 hafalump pppd[25707]: Connection terminated.
Nov 15 21:46:19 hafalump pppd[25707]: Modem hangup
Nov 15 21:46:19 hafalump pppd[25707]: Exit.

i'm not programer so... i can't help with Network Manager. But I know how to make nozomi work with MSM6275 UMTS chip.

the solution is:
apt-get install linux-source
download linux-2.6.28.10 from kernel.org and unpack
cp linux-2.6.28.10/drivers/char/nozomi.c to /usr/src/linux-source-2.6.31/drivers/char/nozomi.c
(sha1sum) abca84ad887bce7b1e6cdaf6e7c69fbed950b84f nozomi.c - this one is working fine.
cp /boot/config-YOUR-UBUNTU-KERNEL-VERSION /usr/src/linux-source-2.6.31/.config
make
cp /usr/src/linux-source-2.6.31/drivers/char/nozomi.ko /lib/modules/YOUR-UBUNTU-KERNEL-VERSION/kernel/drivers/char/

Now wvdial will be working fine.

Release: Ubuntu Karmic 64bit, all updates
modemmanager 0.2.git.20091104t211123.74f679a-0ubuntu2~nmt1
network-manager 0.8~a~git.20091113t224013.f7d7b31-0ubuntu1~nmt1~karmic
network-manager-gnome 0.8~a~git.20091102t055646.67067af-0ubuntu2~nmt1
linux-image-2.6.31-15-generic 2.6.31-15.50

Today new update incoming
libnm-util1 (0.8~a~git.20091117t004859.1151ac2-0ubuntu1~nmt1~karmic)
libnm-glib2 (0.8~a~git.20091117t004859.1151ac2-0ubuntu1~nmt1~karmic)
network-manager (0.8~a~git.20091117t004859.1151ac2-0ubuntu1~nmt1~karmic)
network-manager-gnome (0.8~a~git.20091117t020011.ed23277-0ubuntu1~nmt1~karmic)

Still nothing.

Thank you for your hint GreDi,

compiled the older nozomi kernel modules for my karmic 32 bit version - but that did not help.
Have the same card - same connection timeout problems.

Kind regards,
Thorsten

So what we really need here is to get full logs with the latest daily packages like here: https://wiki.ubuntu.com/DebuggingModemmanager

its important that we get debug messages for pppd in the nm.log.txt. thats what the export NM_PPP_DEBUG=1 is there for in the instructions above.

Please also post the package versions in the same comment. Thanks!

GreDi, does NM also start working after your kernel fix?

@ Alexander: I just did the daily trunk updates and ran everything from https://wiki.ubuntu.com/DebuggingModemmanager.

Release 9.10 (karmic) 32 bit
Kernel Linux 2.6.31-16-generic
All updates 6 December 2009

Lastest daily trunk for :
modemmanager 0.2.git.20091201t192528.f715e0d-0ubuntu2~nmt1~karmic
network-manager 0.8~a~git.20091204t191022.96a61a9-0ubuntu1~nmt1~karmic

PCMCIA Card (lspci):
16:00.0 Network controller: Option N.V. Qualcomm MSM6275 UMTS chip

I installed the daily trunk updates (8 Dec) and still the same issue (that you can see on previous attachments)...

"modem-manager: Got failure code 100: Unknown error"

With
modemmanager 0.2.git.20091201t192528.f715e0d-0ubuntu2~nmt1~karmic
network-manager 0.8~a~git.20091207t231113.30ca263-0ubuntu1~nmt1~karmic
network-manager-gnome 0.8~a~git.20091205t184334.325ec4f-0ubuntu1~nmt1~karmic

I have similar issue, but my card is usually not shown in nm-applet also when card was inserted before boot (rarely it is shown, but connection fails always). Making connection with pppd from command line works without any problems (with the help of comgt utility to register the card with PIN before) so this is hard to belive that the problem could be coused by some nozomi bug as GrEdi suggested before.

One interesting thing is in syslog after inserting the card - modem-manager entries probing for /dev/nozomi appear first and kernel nozomi driver entries saying that device is ready appear later:

Dec 22 20:20:23 lap modem-manager: (noz0) opening serial device...
Dec 22 20:20:23 lap modem-manager: (noz3) opening serial device...
Dec 22 20:20:23 lap modem-manager: (noz1) opening serial device...
Dec 22 20:20:23 lap modem-manager: (noz2) opening serial device...
Dec 22 20:20:23 lap kernel: [ 1102.992174] nozomi 0000:16:00.2: Version of card: 3
Dec 22 20:20:23 lap kernel: [ 1102.992401] nozomi 0000:16:00.2: Initialization OK!
Dec 22 20:20:24 lap kernel: [ 1103.571538] nozomi 0000:16:00.2: Device READY!
Dec 22 20:21:27 lap modem-manager: Caught signal 15, shutting down...

It seems that modem-manager tries to access nozomi device when the device is not ready yet.

A workaround is to download and compile comgt utility, make proper configuration with pppconfig and than use comgt for registering the card and pon and poff commands to connect to internet.

Thanks Radoslaw for your help !!! It works...

I installed comgt to register the card with PIN.
Then I added my user to the "dip" group, and did "sudo pppconfig" to configure a connection to my provider(Orange Business France).
Now, I can use "pon" and "poff" to connect/disconnect to my provider ^^ (i'm actually using my 3G+ card to post this comment...)

It's not as well integrated as Network-manager but it's a temporary solution.

Yes, for me too, it works ok
(inpired by Edouard Orcel and http://www.crium.univ-metz.fr/docs/system/gprs.html )

TUTORIAL :

1) installed comgt, and run it
my results (no with no PIN)
$ comgt
Trying list of devices
SIM ready
Waiting for Registration..(120 sec max)
Registered on Home network: "Orange F",0
Signal Quality: 6,99

2) modified /etc/chatscripts/orange
# ispauth chat
# abortstring
ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO DIALTONE' ABORT 'NO ANSWER' ABORT DELAYED
# modeminit
'' ATZ
# Check SIM pin should return ready
OK-AT-OK "AT+CPIN?"
# Check the whether 3G or GPRS
OK-AT-OK "AT$NWRAT?"
# Set +CGEE to 2
OK-AT-OK "AT+CMEE=2"
# Setup PDP? in +CGDCONT
OK-AT-OK 'AT+CGDCONT=1,"IP","internet-entreprise"'
# Setup +CGEQREG
OK-AT-OK 'AT+CGEQREQ=3,3,64,384,0,0,2,0,"0E0","0E0",3,0,0'
# Attached to Orange network, will return 1
OK-AT-OK 'AT+CGATT?'
# ispnumber
OK-AT-OK 'ATD*99***1#'
#OK-AT-OK 'ATD*99#'
# ispconnect
CONNECT '\d\c'

3) modifed /etc/ppp/peers/orange
#
#
lcp-echo-failure 0
lcp-echo-interval 0
connect "/usr/sbin/chat -v -f /etc/chatscripts/orange"
debug
nodetach
/dev/noz0
115200
# Controle de flux materiel
crtscts
# Ignorer la detection de porteuse
local
noipdefault
ipcp-accept-local
defaultroute
replacedefaultroute
usepeerdns
novj
nobsdcomp
novjccomp
nopcomp
noaccomp
# le telephone ne necessite pas d'autentification
noauth
# username et password
# le username doit correspondre a celui du fichier /etc/ppp/chap-secret
# et/ou /etc/ppp/pap-secret
user "orange"
password "orange"
remotename orange
ipparam orange

4) Launch with $sudo pon orange

BTW, I'd prefer the Network-manager too (as simple as JJ would be great !)
Luc
Linux lprLaptop 2.6.31-16-generic-pae #53-Ubuntu SMP Tue Dec 8 05:20:21 UTC 2009 i686 GNU/Linux
with PCMCIA Globetrotter Orange Fr, business contract, Qualcomm MSM6275 UMTS chip, driver=nozomi

With the latest ppa repository providing modemmanager 0.2.git.20091223t101926.5eed83c-0ubuntu1~nmt1~karmic the part with recognizing the modem seems to be fixed - the modem is shown in nm-applet after inserting, thanks.

However you still are not able to connect to Internet. I attach debug log from connection attempt while I noticed there is sometimes different output than provided by Edouard Orcel on 2009-12-06. With first attempt the resoult was similiar to the Edouard's one, but when the card was removed and inserted again it seems that connection process went some further - see attached logs. I used a little modified debugging procedure, since the NM_PPP_DEBUG variable was not passed to sudo session:

sudo NetworkManager ...

replaced with:

sudo -i; export NM_PPP_DEBUG=1; NetworkManager ...

I attach also syslog output produced while nozomi driver was loaded with debug=1 option that might be helpful. The log contains some errors reported by the driver.

While this bug report is about recognizing of the modem by network-manager, I have created new bug report #505330 regarding the connection issue.

I confirm with 32bit version here.

This bug was fixed in the package modemmanager - 0.3-0ubuntu1

---------------
modemmanager (0.3-0ubuntu1) lucid; urgency=low

  * upstream snapshot: 2009-12-08 06:07:58 (GMT)
    + 07114d4f43c6e724d22294108b1e73785e7aab2a
    - release: bump version to 0.2.997
    - gsm: handle different +COPS response behavior
    - gsm: implement enable/connecting/disconnecting state handling
    - core: fix ordering of DISABLING and DISABLED states
    - cdma: reset previous state if disconnect failed
    - cdma: correctly handle state update after disconnection
    - cdma: handle interim enabling/disabling states better
    - cdma: update for new modem states and make connect actually work
    - mbm: update state after enabling the device
    - core: schedule enabled/disabled callbacks to avoid infinite recursion
    - cdma: set correct modem state on connect failure
    - build: require glib-2.0 >= 2.6.18 for g_set_error_literal()
    - zte: add missing ZTE device aux port tags
    - gsm: more complete parsing of PIN responses
    - gsm: fix unsolicited registration segfaults
    - hso: ensure authentication works again after auth errors
    - serial: don't run commands when there's already one in progress
    - hso: fix up connection issues and error ignorance
    - nozomi: fix detection (LP: #425312)
    - gsm: CGDCONT parsing fixes (bgo #602552)
    - core: don't allow double scheduled callbacks (fixes crash)
    - serial: handle arbitrary amounts of <CF><LF> padding in responses
    - gsm: make "X4 &C1" init arguments optional (LP: #455031)

  * upstream release 0.3
    - cdma: increase data call initiation timeout
    - core: fix mm_modem_check_removed() to return errors correctly
    - cdma: allow plugins to override AT+CSS? during registration checking (rh #547294)
    - anydata: add plugin for AnyData CDMA devices (rh #547294)
    - huawei-cdma: robustify SYSINFO parsing
    - sierra: prefer primary port for status
    - core: protect against modem removal in critical callbacks (rh #553953)
    - cdma: prefer primary port unless it's connected
    - probe: add CPIN request during the probing process (bgo #604369)
    - zte: ignore SIM Build Main Menu requests (rh #551376)
    - longcheer: new plugin for Longcheer (Alcatel etc) devices (bgo #606550)
    - gsm: correctly parse Nokia N80 +COPS response
    - gsm: split out +COPS response parsing and add testcases
    - serial: prevent "hangs" by limiting EAGAIN retries on serial writes
    - gsm: ensure registration state is reset when disabling the modem
    - core: implement a PropertiesChanged signal for the MMModem class
    - core: add Enabled property to org.freedesktop.ModemManager.Modem interface
    - sierra: fix CDMA registration detection in some cases
    - zte: handle unsolicited messages during probe
    - cdma: fix quality parsing if modem doesn't prepend +CSQ:
    - sierra: use at!pcstate on CDMA modems for power control
    - option: always pick the right data port
    - mbm: ensure various unsolicited responses are turned off when disabling
    - cdma: try +CSQ? if CSQ fails
    - cdma: accept SID 0 in some cases

  [ Tony Espy <email address hidden> ]
  * add get-snapshot-info target ...