[regression jaunty nozomi] NetworkManager does not recognise an Option Globetrotter 3G pcmcia modem

[kasade]

Binary package hint: network-manager

Ubuntu 9.04 beta
network-manager 0.7.1~rc3.2gitb8fc83a7-0ubuntu1

Option Globetrotter 3G is recognised by Ubuntu, but not by the network-manager. It does not appear in the network list.
On ubuntu 8.10 everything works fine.

lspci shows:

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

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: network-manager 0.7.1~rc3.2.gitb8fc83a7-0ubuntu1
ProcEnviron:
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
Uname: Linux 2.6.28-11-generic i686

[Dennis (dennis.guse)]

Me too.

NM does ignore the Option G cause he believes it isn't a mobile modem:

"/var/log/daemon.log":

Apr 1 09:00:56 x90 NetworkManager: <info> (noz0): found serial port (udev: hal:GSM)
Apr 1 09:00:56 x90 NetworkManager: <info> (noz0): ignoring due to lack of probed mobile broadband capabilties
Apr 1 09:00:56 x90 NetworkManager: <info> (noz1): ignoring due to lack of mobile broadband capabilties
Apr 1 09:00:56 x90 NetworkManager: <info> (noz3): ignoring due to lack of mobile broadband capabilties
Apr 1 09:00:56 x90 NetworkManager: <info> (noz2): ignoring due to lack of mobile broadband capabilties

Entry's are also present in the previous posted dmesg.txt...

[Alexander Sack (asac)]

please attach output of lshal, lsusb

also run /lib/udev/nm-modem-probe --export --verbose /dev/noz0 and attach the output.

[Alexander Sack (asac)]

we also want the output of lspci on top of what i asked for in https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/351803/comments/3

Would be great if you could come up with that asap as our time to fix things for jaunty is counting. Thanks!

[Franz Dietzmann (tdk-le)]

I can also confirm this. Output of commands is similar to what has been posted already, so I won't post it again.

[Alexander Sack (asac)]

can you try to change in /lib/udev/rules.d/77-nm-probe-modem-capabilities.rules to DRIVERS=="serial_cs|nozomi" ... ?

[Alexander Sack (asac)]

so: DRIVERS=="serial_cs|nozomi", IMPORT{program}="nm-modem-probe --delay 3000 --export $tempnode", GOTO="nm_modem_probe_end"

[kasade (kasade)]

Done. But there's no effect.
Output of /lib/udev/nm-modem-probe --export --verbose /dev/noz0 attached below

[Franz Dietzmann (tdk-le)]

The change doesn't work here either.

I don't know if it helps, but I just tried the card in a Jaunty Alpha 5 Live CD session I still had lying around and it is recognized by NM there.

[Dan Williams (dcbw)]

After making the change Alexander suggested in https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/351803/comments/11 can you unplug the card and replug the card, then grab the last 100 or so lines of /var/log/daemon.log (or wherever NM's syslog output goes) and attach it to this bug?

[Franz Dietzmann (tdk-le)]

Only the last 8 lines are generated after unplugging and replugging, but I attached the larger amount.

[Franz Dietzmann (tdk-le)]

Output of kern.log after same procedure.

[kasade (kasade)]

Same output here.

[Launchpad Janitor (janitor)]

This bug was fixed in the package network-manager - 0.7.1~rc4-0ubuntu1

---------------
network-manager (0.7.1~rc4-0ubuntu1) jaunty; urgency=low

  * upstream release 0.7.1 rc4
    + http://git.freedesktop.org/NetworkManager/NetworkManager/
    + NETWORKMANAGER_0_7 (branch)
      - dont send AT commands to serial consoles that are not using a modem driver
      - nozomi probing (LP: #351803)
      - allow users with polkit authorization to view/edit secrets for system connections
      - fix crash that might be LP: #319918
  * allow connection sharing out of the box; we add dnsmasq-base to Recommends:
    - update control

 -- Alexander Sack <email address hidden> Mon, 06 Apr 2009 12:43:31 +0200

[Franz Dietzmann (tdk-le)]

after today's update to network -manager, the card is still not found for me. output of relevant logs is still the same as posted before.

[Alexander Sack (asac)]

at best someone with the card would figure how to poke the udev rules to match your driver/card.

[Alexander Sack (asac)]

Franz, can you confirm that your driver is nozomi? (that part is not in the logs posted). Please attach complete syslog after reboot again.

[Dario Gallucci (dario-gallucci)]

I can confirm that 0.7.1_rc4 did not solve the issue.

Can someone please suggest a way to obtain more meaningful debug output from 77-nm-probe-modem-capabilities.rules?

[Dario Gallucci (dario-gallucci)]

I have realized that nozomi matches this line:

KERNEL!="tty*", GOTO="nm_modem_probe_end"

and replaced with:

KERNEL!="noz*", GOTO="nm_modem_probe_end"

but it didn't work. (I rebooted of course). Any other idea?

I have attached udevadm info output.

[Alexander Sack (asac)]

please use udevadm control --log-priority=debug

and then replug.

[Alexander Sack (asac)]

reopening bug: see https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/351803/comments/22 and https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/351803/comments/23

[Alexander Sack (asac)]

Dario, could you also get the udevadm info for the other ttys for us? (e.g. nzo1 nzo2)?

[Alexander Sack (asac)]

on top of what i asked above, please also run:

udevadm test --action=add /class/tty/noz0

and give us the output

[Alexander Sack (asac)]

(all as root user obviously)

[Franz Dietzmann (tdk-le)]

Attached the complete syslog of last reboot. (I hope it's the right thing, this is my first time contributing to a bug report, so I'm not fully sure it is.)
I will run the udevadm now and post results.

I am sure the card uses the nozomi driver, I'm running it using wvdial for the moment, which works fine.

[Alexander Sack (asac)]

Franz, I wanted to see those after the udev rules tweakage of the KERNEL line like Dario suggested. Maybe drop it completely for that.

[Alexander Sack (asac)]

see: https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/351803/comments/23

[Franz Dietzmann (tdk-le)]

Just so I get right this time, what do you mean by dropping it completely? Delete the whole line? Sorry I'm slow here..

[Franz Dietzmann (tdk-le)]

I had some time, so I did both. First set of files is with noz replacing tty.

[Franz Dietzmann (tdk-le)]

following are with the KERNEL line deleted

[Alexander Sack (asac)]

ok so with the KERNEL line removed the prober gets actually run. with that state, please replug/reboot and attach your complete syslog.

[Franz Dietzmann (tdk-le)]

syslog after reboot, plugged in the card after desktop was ready.

[Alexander Sack (asac)]

ok. still keep the KERNEL line removed and run:

sudo udevadm info --query=env --path=/sys/class/tty/noz0

[Franz Dietzmann (tdk-le)]

outout is just:

UDEV_LOG=3
DEVPATH=/devices/pci0000:00/0000:00:14.4/0000:02:04.0/0000:03:00.2/tty/noz0
MAJOR=249
MINOR=0
DEVNAME=/dev/noz0
DEVLINKS=/dev/char/249:0

[Alexander Sack (asac)]

ok, so still _without_ that KERNEL line in the rules, we need another log:

1. please set udev to debug mode like:

  udevadm control --log-priority=debug

2. run

  tail -n0 -f /var/log/syslog | tee /tmp/syslog.txt

3. replug your card; wait a bit and attach the syslog.txt here. Thanks!

[Franz Dietzmann (tdk-le)]

here you go. You're very welcome.

[Alexander Sack (asac)]

right now uploading network-manager_0.7.1~rc4.1.cf199a964-0ubuntu1_source.changes which hopefully fixes this. Please check this asap.

[Launchpad Janitor (janitor)]

This bug was fixed in the package network-manager - 0.7.1~rc4.1.cf199a964-0ubuntu1

---------------
network-manager (0.7.1~rc4.1.cf199a964-0ubuntu1) jaunty; urgency=low

  * upstream release 0.7.1 final candidate 1 (Wed Apr 8 06:38:37 2009 -0400)
    + http://git.freedesktop.org/NetworkManager/NetworkManager/
    + NETWORKMANAGER_0_7 (branch)
      - modem-probe: retry opening the serial port if --delay is used (LP: #351803)
        (Up to --delay milliseconds.)
      - core: ignore DHCP-sent MTUs less than 577 (LP: #352779)
      - core: update FSF address (bgo #577949)
      - modem-probe: don't restrict probing on tty device name (LP: #351803)

 -- Alexander Sack <email address hidden> Wed, 08 Apr 2009 12:53:41 +0200

[Franz Dietzmann (tdk-le)]

Works great now! Thanks alot!

[kasade (kasade)]

Yes, everything is working fine now :) Thank you :)

[Robert Hrovat (robi-hipnos)]

Will there be a fix for Karmic too?

[Zsolt Présing (presingzs)]

doesn't work in Karmic

[Alexander Sack (asac)]

for karmic, please try the trunk builds fom ppa on debugging page: https://wiki.ubuntu.com/DebuggingModemmanager

if that does not help, please use those instructions to get proper logs and open a new bug. drop the new bug id here, so we can follow up there.

Thanks!

[kasade (kasade)]

I've already filled a new bug ( Bug #437766 ), but it was marked as a duplicate of Bug #417389, which has a "Fix Committed" status, but for me nothing has changed and it still does not work! I don't know what to do...
You can find my logs here: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/417389/comments/30