MASTER - modems not detected - udev prober broken (Was: Huawei e169 doesn't connect + Globetrotter 3G+ card not recognized anymore)

Bug #346835 reported by Peter Makowski
26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Critical
Alexander Sack
Jaunty
Fix Released
Critical
Alexander Sack
udev (Ubuntu)
Invalid
High
Unassigned
Jaunty
Invalid
High
Unassigned

Bug Description

Binary package hint: network-manager

My modem Huawei e169 was working great under Ubuntu 8.10 but in the newest Ubuntu 9.04 it cannot connect with my internet provider. When I try to do this than I have to disconnect the modem or I have a bug like this in MS Windows: modem seems to be damaged.

Revision history for this message
lanzen (lanzen) wrote :

Well I have this, but Hauwei e169 (seen as Hauwei E220) is still working as always in Intrepid and I have not noted any damage to the modem itself.

It was working fine in Jaunty, though there have been sporadic hesitations, but then stopped working after thursday's updates. Actually dmesg sees it and finds its driver, but then the connection doesn't show up under broadband any more.

I also tested my Nokia N70 and that brings up ttyAM0, shows up and works.

Revision history for this message
lanzen (lanzen) wrote :

And from /var/log/messages

Revision history for this message
Alexander Sack (asac) wrote :

please your complete syslog after reproducing the problem. Thanks!

Changed in network-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
lanzen (lanzen) wrote :

Ok, so I stopped my router and started a new session. Once the machine was ready, I've inserted the Hauwei e169 and here is syslog.

BTW, I've noticed that /var/log still contains syslogs from the time the modem was still working. Let me know if you need those, too. Or anything else for that matter. There's quite a few owners of e169 that are going to be affected.

One more thing. As can be noticed in lsusb, the modem was recognized ad E620 and not as E220 as I said in my previous post.

Thank you Alexander.

Revision history for this message
lanzen (lanzen) wrote :

I forgot to mention that I'm testing Ubuntu, Kubuntu and Xubuntu on different partitions on a usb HD. The hauwei modem stopped working on all 'buntu flavours at the very same time. Maybe bug #334122 could be related to this one (I'm using the nm plasmoid on kubuntu), as well as other 3G recent bugs.

Revision history for this message
lanzen (lanzen) wrote :

Well, I tried to downgrade to the older network-manager_0.7.1~rc3-0ubuntu1_i386.deb and network-manager and network-manager-gnome_0.7.1~rc3-0ubuntu1_i386.deb and my broadband connection reappeared, but, all the same, could not get connected, so I upgraded again and also applied all the new updates and, after reboot, my connection is again listed, but it's not working.

Right now I am using wvdial and this time, at this very moment, I am connected.

Alexander Sack (asac)
summary: - [9.04 regression] Huawei e169 doesn't connect
+ MASTER - modems not detected - udev prober broken (Was: Huawei e169
+ doesn't connect + Globetrotter 3G+ card not recognized anymore)
Changed in network-manager (Ubuntu):
assignee: nobody → asac
importance: Undecided → Critical
status: Incomplete → In Progress
Revision history for this message
Alexander Sack (asac) wrote :

this seems to be caused by NM udev modem prober getting bad parameters passed for product id and vendor id: e.g. $attr{idProduct} and $attr{idVendor} in /lib/udev/rules.d/77-nm-probe-modem-capabilities.rules are empty.

Changed in udev (Ubuntu):
importance: Undecided → High
status: New → Triaged
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Use $attr{../idProduct} - $attr{} only matches the event device, or the device matched by the previous DRIVERS. Since idProduct and idVendor come from the parent device of that device, you should use .. to find them.

Tracking the udev documentation issue at bug #348513

Changed in udev (Ubuntu Jaunty):
status: Triaged → Invalid
Revision history for this message
Alexander Sack (asac) wrote :

not a udev bug

Revision history for this message
lanzen (lanzen) wrote :

I don't have the technical background to help you with code, but if you need any testing, just let me know.

Revision history for this message
Alexander Sack (asac) wrote :

try to replace /lib/udev/rules.d/77-nm-probe-modem-capabilities.rules with this file and restart your system. thanks.

Revision history for this message
lanzen (lanzen) wrote :

No luck. It stays unchanged.

This is the relevant bit of syslog as the modem gets mounted:
Mar 26 00:50:33 test1 kernel: [ 150.928093] usb 3-2: new full speed USB device using uhci_hcd and address 3
Mar 26 00:50:33 test1 kernel: [ 151.090463] usb 3-2: configuration #1 chosen from 1 choice
Mar 26 00:50:33 test1 kernel: [ 151.125503] usb-storage: probe of 3-2:1.0 failed with error -1
Mar 26 00:50:33 test1 kernel: [ 151.127246] usb 3-2: USB disconnect, address 3
Mar 26 00:50:33 test1 pulseaudio[3112]: module-hal-detect.c: Error getting capability: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/Hal/devices/usb_device_12d1_1001_____________________if0
Mar 26 00:50:34 test1 kernel: [ 151.920111] usb 3-2: new full speed USB device using uhci_hcd and address 4
Mar 26 00:50:34 test1 kernel: [ 152.083441] usb 3-2: configuration #1 chosen from 1 choice
Mar 26 00:50:34 test1 kernel: [ 152.088251] usb-storage: probe of 3-2:1.0 failed with error -5
Mar 26 00:50:34 test1 kernel: [ 152.108343] usb-storage: probe of 3-2:1.1 failed with error -5
Mar 26 00:50:34 test1 kernel: [ 152.129441] usb-storage: probe of 3-2:1.2 failed with error -5
Mar 26 00:50:34 test1 kernel: [ 152.142520] usb-storage: probe of 3-2:1.3 failed with error -1
Mar 26 00:50:34 test1 kernel: [ 152.204065] USB Serial support registered for GSM modem (1-port)
Mar 26 00:50:34 test1 kernel: [ 152.204194] option 3-2:1.0: GSM modem (1-port) converter detected
Mar 26 00:50:34 test1 kernel: [ 152.204392] usb 3-2: GSM modem (1-port) converter now attached to ttyUSB0
Mar 26 00:50:34 test1 kernel: [ 152.204425] option 3-2:1.1: GSM modem (1-port) converter detected
Mar 26 00:50:34 test1 kernel: [ 152.204564] usb 3-2: GSM modem (1-port) converter now attached to ttyUSB1
Mar 26 00:50:34 test1 kernel: [ 152.204591] option 3-2:1.2: GSM modem (1-port) converter detected
Mar 26 00:50:34 test1 kernel: [ 152.204732] usb 3-2: GSM modem (1-port) converter now attached to ttyUSB2
Mar 26 00:50:34 test1 kernel: [ 152.204784] usbcore: registered new interface driver option
Mar 26 00:50:34 test1 kernel: [ 152.204792] option: v0.7.2:USB Driver for GSM modems
Mar 26 00:50:34 test1 nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/usb_device_12d1_1001_____________________if0_serial_usb_0, iface: (null)): iface not found
Mar 26 00:50:34 test1 NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties
Mar 26 00:50:34 test1 NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)
Mar 26 00:50:34 test1 NetworkManager: <info> (ttyUSB0): ignoring due to lack of probed mobile broadband capabilties
Mar 26 00:50:35 test1 NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Mar 26 00:50:59 test1 kernel: [ 176.513108] ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 361

Revision history for this message
lanzen (lanzen) wrote :

Sorry, sorry, sorry. Good news and bad news.

Last night I got home after a quite bad day and my mind wasn't so clear.

I decided to test it again this morning and suddenly remembered that, in order to use my my old hardy wvdial.conf, I disabled pin request and did the same in Broadband GUI configuration so that I could test without having to resort to my cell to switch pin on/off all the time. Unfortunately I did re-enabled it to use it in Intrepid and last night I forgot Jaunty was doing without.

Back to business:

1. The modified 77-nm-probe-modem-capabilities.rules does not work and does not list any Broadband connection.

2. The old one does. Now it shows two identical connections as it did when it was still working and after a session log-out/log-in or an extraction/insertion of the modem stick and when, then, only the second listed was working. Now the first one appears as using /dev/ttyUSB2 while the second listed uses /dev/ttyUSB0. This time the second does not work, but the first one does.

3. Though the good new are "it works", the bad news are: It does not disconnect and to do so I have to halt the system.

4. Attached is the latest syslog that to you surely speaks louder than my explanations.

Revision history for this message
lanzen (lanzen) wrote :

Sorry, the last phrase at point 3 should read:

Now the first one appears as using /dev/ttyUSB0 while the second listed uses /dev/ttyUSB2. This time the second does not work, but the first one does.

Revision history for this message
Alexander Sack (asac) wrote :

you are really confusing. Can you go back to square one, use the new rules file i attached with the latest network-manager and properly restart your system and plug in your 3G device?

Then please attach the output of /var/log/syslog (without trying to connect). Thanks!

Revision history for this message
Alexander Sack (asac) wrote :

above you said that you downgraded. please dont do that for this test. upgrade to really the latest before you do what i said in https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/346835/comments/15

Revision history for this message
Kazade (kazade) wrote :

This issue has got a bit confusing... I'll try to decipher it. The main issue of the bug report is that the wireless broadband just doesn't work, I'm experiencing the same problem as Lanzen.

Lanzen said that the 77-nm-probe-modem-capabilities.rules file from Intrepid fixes the problem, the one posted above my Alexander doesn't.

The double entry bug that Lanzen mentioned here: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/346835/comments/14 is a different bug ( https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/339926 ).

Alexander, the syslog you requested (https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/346835/comments/15) is the one here ( https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/346835/comments/4 ) - I'm receiving identical messages in mine, but I can't post it because my laptop battery just died.

Phew.. I'll try to post my syslog tonight if I have time.

Revision history for this message
Alexander Sack (asac) wrote :

ok, first. please lets use this bug only for the issue that the modem isn't detected at all. If there are other bugs that make it not work lets track it elsewhere.

The problem that modems are not detected was introduced in the last jaunty upload (0.7.1~rc3.1.git4cf2da146-0ubuntu1) because the .rules file we ship there seems to be bogus. The symptoms are that you don't see _any_ 3G connection in the applet; this is because you see something like:

Mar 23 09:44:34 test1 NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)
Mar 23 09:44:34 test1 NetworkManager: <info> (ttyUSB0): ignoring due to lack of probed mobile broadband capabilties
Mar 23 09:44:34 test1 NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Mar 23 09:44:34 test1 NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties
Mar

in syslog.

Revision history for this message
Alexander Sack (asac) wrote :
Revision history for this message
Feddar (ubuntu-bugs-biazzi) wrote :
Download full text (3.6 KiB)

Hi folks, I'm new to launchpad and sorry for my poor english, please!
Now, I've a Netbook and a Huawei E156g HSDPA Modem. I upgraded from Ubuntu 8.10 to Ubuntu 9.04.
Now Huawei doesn't go anymore. Same error as Lanzen:
-------- SYSLOG -----------
Mar 26 20:40:34 ubuntone kernel: [ 3012.663108] usb 1-2: new high speed USB device using ehci_hcd and address 11
Mar 26 20:40:34 ubuntone kernel: [ 3012.789614] usb 1-2: configuration #1 chosen from 1 choice
Mar 26 20:40:34 ubuntone kernel: [ 3012.793513] usb-storage: probe of 1-2:1.0 failed with error -1
Mar 26 20:40:34 ubuntone kernel: [ 3012.793571] usbserial_generic 1-2:1.0: generic converter detected
Mar 26 20:40:34 ubuntone kernel: [ 3012.793871] usb 1-2: generic converter now attached to ttyUSB0
Mar 26 20:40:34 ubuntone kernel: [ 3012.794737] usb 1-2: USB disconnect, address 11
Mar 26 20:40:34 ubuntone kernel: [ 3012.795735] generic ttyUSB0: generic converter now disconnected from ttyUSB0
Mar 26 20:40:34 ubuntone kernel: [ 3012.795807] usbserial_generic 1-2:1.0: device disconnected
Mar 26 20:40:34 ubuntone pulseaudio[3684]: module-hal-detect.c: Error getting capability: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/Hal/devices/usb_device_ffffffff_ffffffff_noserial_0_serial_usb_0
Mar 26 20:40:40 ubuntone kernel: [ 3019.191120] usb 1-2: new high speed USB device using ehci_hcd and address 12
Mar 26 20:40:40 ubuntone kernel: [ 3019.317618] usb 1-2: configuration #1 chosen from 1 choice
Mar 26 20:40:40 ubuntone kernel: [ 3019.330523] usb-storage: probe of 1-2:1.0 failed with error -5
Mar 26 20:40:40 ubuntone kernel: [ 3019.330588] usbserial_generic 1-2:1.0: generic converter detected
Mar 26 20:40:40 ubuntone kernel: [ 3019.333993] usb 1-2: generic converter now attached to ttyUSB0
Mar 26 20:40:40 ubuntone kernel: [ 3019.341545] usb-storage: probe of 1-2:1.1 failed with error -5
Mar 26 20:40:40 ubuntone kernel: [ 3019.341603] usbserial_generic 1-2:1.1: generic converter detected
Mar 26 20:40:40 ubuntone kernel: [ 3019.341907] usb 1-2: generic converter now attached to ttyUSB1
Mar 26 20:40:40 ubuntone kernel: [ 3019.351362] usb-storage: probe of 1-2:1.2 failed with error -1
Mar 26 20:40:40 ubuntone kernel: [ 3019.351428] usbserial_generic 1-2:1.2: generic converter detected
Mar 26 20:40:40 ubuntone kernel: [ 3019.351772] usb 1-2: generic converter now attached to ttyUSB2
Mar 26 20:40:40 ubuntone kernel: [ 3019.362396] usb-storage: probe of 1-2:1.3 failed with error -1
Mar 26 20:40:40 ubuntone kernel: [ 3019.362462] usbserial_generic 1-2:1.3: generic converter detected
Mar 26 20:40:40 ubuntone kernel: [ 3019.362806] usb 1-2: generic converter now attached to ttyUSB3
Mar 26 20:40:41 ubuntone NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Mar 26 20:40:41 ubuntone nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0, iface: (null)): iface not found
Mar 26 20:40:41 ubuntone NetworkManager: <info> (ttyUSB3): ignoring due to lack of mobile broadband capabilties
Mar 26 20:40:41 ubuntone NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)
Ma...

Read more...

Revision history for this message
Alexander Sack (asac) wrote :
Revision history for this message
Feddar (ubuntu-bugs-biazzi) wrote :
Download full text (6.4 KiB)

Alexander, tried your first file (replaced), rebooted, inserted Huawei, no result. Here the log:
-------- SYSLOG first file --------
Mar 26 22:48:22 ubuntone kernel: [ 76.604083] usb 1-3: new high speed USB device using ehci_hcd and address 3
Mar 26 22:48:22 ubuntone kernel: [ 76.730663] usb 1-3: configuration #1 chosen from 1 choice
Mar 26 22:48:22 ubuntone kernel: [ 76.748333] usb-storage: probe of 1-3:1.0 failed with error -1
Mar 26 22:48:22 ubuntone kernel: [ 76.748375] usbserial_generic 1-3:1.0: generic converter detected
Mar 26 22:48:22 ubuntone kernel: [ 76.749061] usb 1-3: generic converter now attached to ttyUSB0
Mar 26 22:48:22 ubuntone kernel: [ 76.752611] usb 1-3: USB disconnect, address 3
Mar 26 22:48:22 ubuntone kernel: [ 76.753014] generic ttyUSB0: generic converter now disconnected from ttyUSB0
Mar 26 22:48:22 ubuntone kernel: [ 76.753055] usbserial_generic 1-3:1.0: device disconnected
Mar 26 22:48:28 ubuntone kernel: [ 83.133081] usb 1-3: new high speed USB device using ehci_hcd and address 4
Mar 26 22:48:28 ubuntone kernel: [ 83.260106] usb 1-3: configuration #1 chosen from 1 choice
Mar 26 22:48:28 ubuntone kernel: [ 83.265619] usb-storage: probe of 1-3:1.0 failed with error -5
Mar 26 22:48:28 ubuntone kernel: [ 83.265653] usbserial_generic 1-3:1.0: generic converter detected
Mar 26 22:48:28 ubuntone kernel: [ 83.267377] usb 1-3: generic converter now attached to ttyUSB0
Mar 26 22:48:28 ubuntone kernel: [ 83.271265] usb-storage: probe of 1-3:1.1 failed with error -5
Mar 26 22:48:28 ubuntone kernel: [ 83.271307] usbserial_generic 1-3:1.1: generic converter detected
Mar 26 22:48:28 ubuntone kernel: [ 83.271510] usb 1-3: generic converter now attached to ttyUSB1
Mar 26 22:48:28 ubuntone kernel: [ 83.293407] usb-storage: probe of 1-3:1.2 failed with error -1
Mar 26 22:48:28 ubuntone kernel: [ 83.293447] usbserial_generic 1-3:1.2: generic converter detected
Mar 26 22:48:28 ubuntone kernel: [ 83.295309] usb 1-3: generic converter now attached to ttyUSB2
Mar 26 22:48:28 ubuntone kernel: [ 83.301378] usb-storage: probe of 1-3:1.3 failed with error -1
Mar 26 22:48:28 ubuntone kernel: [ 83.301417] usbserial_generic 1-3:1.3: generic converter detected
Mar 26 22:48:28 ubuntone kernel: [ 83.301615] usb 1-3: generic converter now attached to ttyUSB3
Mar 26 22:48:29 ubuntone nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0, iface: (null)): iface not found
Mar 26 22:48:29 ubuntone NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Mar 26 22:48:29 ubuntone NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)
Mar 26 22:48:29 ubuntone NetworkManager: <info> (ttyUSB0): ignoring due to lack of probed mobile broadband capabilties
Mar 26 22:48:29 ubuntone NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties
Mar 26 22:48:29 ubuntone NetworkManager: <info> (ttyUSB3): ignoring due to lack of mobile broadband capabilties
------- END ---------

Then tried your second file (replaced), rebooted, inserted Huawei, no result. Here th...

Read more...

Revision history for this message
Alexander Sack (asac) wrote :

please keep the file replaced:

then please run the modem prober manually:

 sudo /lib/udev/nm-modem-probe --verbose --export /dev/ttyUSB0

(repeat that for ttyUSB1, 2... and so on).

Attach the output please.

Revision history for this message
Fabien Tassin (fta) wrote :

The rules file from comment #11 works for me.
That's with network-manager 0.7.1~rc3.1.git4cf2da146-0ubuntu1.nm1.

Revision history for this message
lanzen (lanzen) wrote :

As I said at comment #13, as far as I'm concerned, this bug is solved.

Attached is the 77-nm-probe-modem-capabilities.rules as it is in /lib/udev/rules.d

Revision history for this message
Feddar (ubuntu-bugs-biazzi) wrote :
Download full text (3.3 KiB)

Alexander, with first file on comment 21 I got this:
/lib/udev/nm-modem-probe --verbose --export /dev/ttyUSB0
L: main(): probing /dev/ttyUSB0
L: modem_send_command(): Sending: 'AT+GCAP
'
L: modem_wait_reply(): Got: 'AT+GCA'
': modem_wait_reply(): Got: 'AT+GCAP
L: modem_wait_reply(): Got: 'AT+GCAP
+CME ERROR: SIM PIN required
'
L: modem_probe_caps(): timed out waiting for GCAP reply (idx -2, term_idx -1)
L: modem_send_command(): Sending: 'AT+GCAP
'
L: modem_wait_reply(): Got: 'AT+GCA'
': modem_wait_reply(): Got: 'AT+GCAP
L: modem_wait_reply(): Got: 'AT+GCAP
+CME ERROR: SIM PIN required
'
L: modem_probe_caps(): timed out waiting for GCAP reply (idx -2, term_idx -1)
ID_NM_MODEM_PROBED=1
L: main(): /dev/ttyUSB0: caps (0x0)
--------------------------------------------------------------------------------------------------------

/lib/udev/nm-modem-probe --verbose --export /dev/ttyUSB1
L: main(): probing /dev/ttyUSB1
L: modem_send_command(): Sending: 'AT+GCAP
'
L: modem_wait_reply(): Got: '

^BOOT:22607671,0,0,0,86

T+GCA'
L: modem_wait_reply(): Got: '

^BOOT:22607671,0,0,0,86

'+GCAP
L: modem_wait_reply(): Got: '

^BOOT:22607671,0,0,0,86

T+GCAP
+CME ERROR: SIM PIN required
'
L: modem_probe_caps(): timed out waiting for GCAP reply (idx -2, term_idx -1)
L: modem_send_command(): Sending: 'AT+GCAP
'
L: modem_wait_reply(): Got: 'AT+GCA'
': modem_wait_reply(): Got: 'AT+GCAP
L: modem_wait_reply(): Got: 'AT+GCAP
+CME ERROR: SIM PIN required
'
L: modem_probe_caps(): timed out waiting for GCAP reply (idx -2, term_idx -1)
ID_NM_MODEM_PROBED=1
L: main(): /dev/ttyUSB1: caps (0x0)
--------------------------------------------------------------------------------

With second file I got this:
/lib/udev/nm-modem-probe --verbose --export /dev/ttyUSB0
L: main(): probing /dev/ttyUSB0
L: modem_send_command(): Sending: 'AT+GCAP
'
L: modem_wait_reply(): Got: 'AT+GCA'
': modem_wait_reply(): Got: 'AT+GCAP
L: modem_wait_reply(): Got: 'AT+GCAP
+CME ERROR: SIM PIN required
'
L: modem_probe_caps(): timed out waiting for GCAP reply (idx -2, term_idx -1)
L: modem_send_command(): Sending: 'AT+GCAP
'
L: modem_wait_reply(): Got: 'AT+GCAP'
': modem_wait_reply(): Got: 'AT+GCAP
L: modem_wait_reply(): Got: 'AT+GCAP
+CME ERROR: SIM PIN required
'
L: modem_probe_caps(): timed out waiting for GCAP reply (idx -2, term_idx -1)
ID_NM_MODEM_PROBED=1
L: main(): /dev/ttyUSB0: caps (0x0)
---------------------------------------------------------------

/lib/udev/nm-modem-probe --verbose --export /dev/ttyUSB1
L: main(): probing /dev/ttyUSB1
L: modem_send_command(): Sending: 'AT+GCAP
'
L: modem_wait_reply(): Got: '

^BOOT:22607671,0,0,0,86

T+GCAP'
L: modem_wait_reply(): Got: '

^BOOT:22607671,0,0,0,86

'+GCAP
L: modem_wait_reply(): Got: '

^BOOT:22607671,0,0,0,86

T+GCAP
+CME ERROR: SIM PIN required
'
L: modem_probe_caps(): timed out waiting for GCAP reply (idx -2, term_idx -1)
L: modem_send_command(): Sending: 'AT+GCAP
'
L: modem_wait_reply(): Got: 'AT+GCA'
': modem_wait_reply(): Got: 'AT+GCAP
L: modem_wait_reply(): Got: 'AT+GCAP
+CME ERROR: SIM PIN required
'
L: modem_probe_caps(): timed out waiting for GCAP reply (idx -2, term_idx -1)
ID_NM_MODEM_PROBED=1
L: main(): /dev/ttyUSB1: caps (0x0)
---...

Read more...

Revision history for this message
lanzen (lanzen) wrote :

Kazade in https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/346835/comments/17
said:
[quote]Lanzen said that the 77-nm-probe-modem-capabilities.rules file from Intrepid fixes the problem [...] [/quote]

No, Kazade. I meant that wherever I managed to connect, the original Jaunty file was used. I never had a successful connection with the one Alexander suggested.

The two packages (network-manager and network-manager-gnome) I tried on my own initiative were not from Intrepid, but earlier jaunty version from the times all was working as expected. My experiment was unsuccessful.

And referring to previous comments from Alexander:
all testing I've done has been done after upgrading to the latest upgrade all the time in a clean Ubuntu Jaunty.

Last but not least, as I reported again in bug #339926, I only manage to successfully connect _if_ two entries for my broadband provider are listed in the applet. That was the situation when I sent comment https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/346835/comments/25.

Since then I logged out to log in later and on this new login _only_ _one_ entry was showing and could not get again connect.

I hope this sweps away a bit of confusion.

Revision history for this message
lanzen (lanzen) wrote :

@ Feddar

You could maybe place your sim card in a cellular phone and disable pin request for the time being.

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

This bug was fixed in the package network-manager - 0.7.1~rc3.2.gitb8fc83a7-0ubuntu1

---------------
network-manager (0.7.1~rc3.2.gitb8fc83a7-0ubuntu1) jaunty; urgency=low

  * upstream 0.7.1 rc3 + gitb8fc83a7 (Thu Mar 26 17:05:41 2009 -0400)
    + http://git.freedesktop.org/NetworkManager/NetworkManager/
    + NETWORKMANAGER_0_7 (branch)
    + fix broken udev-prober for 3G modems (LP: #346835)
  * fix LP: #348521 - network-manager sould depend on ppp
    - update control
  * update diverged patches
    - update patches/60_NULL_info_linux_driver.patch

 -- Alexander Sack <email address hidden> Fri, 27 Mar 2009 14:37:33 +0100

Changed in network-manager:
status: In Progress → Fix Released
Revision history for this message
Feddar (ubuntu-bugs-biazzi) wrote :

Ok, thank you very much. It will be released in ubuntu repository? What about 77-nm-probe-modem-capabilities.rules ? I have to replace original? Thanks

Revision history for this message
Alexander Sack (asac) wrote :

try to upgrade every couple of hours ... bits are built on i386 (amd64 seems will take a bit still) so its just a matter of time until it gets to your mirror.

And no, you dont need to change anything. the package will overwrite your current rules.

Revision history for this message
Alexander Sack (asac) wrote :

so the fix uploaded covers two things closely related to this bug:

 a) fix rules to be the one i posted in comment 11
 b) fix modem prober to fallback to another approach when the modem sends +CME ERROR: SIM PIN required like in https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/346835/comments/26

So both issues should be fixed.

@Lanzen: your rules file might work but its not good enough for a bunch of modems; hence we use the one from comment 11 - which works for most. If you get issues again, open a new bug and drop that bug number here. Thanks!

Revision history for this message
lanzen (lanzen) wrote :

@ Alexander

No need for further bugs reports on this issue from my part. I've just updated to the very latest bit and it works. Nice job, thank you.

Revision history for this message
Feddar (ubuntu-bugs-biazzi) wrote :

@ Alexander

Hi, yes, great job! Thank you very much. Latest update solved the problem. Have a nice day!

Revision history for this message
Dario Gallucci (dario-gallucci) wrote :

Network manager is still failing in my case:

I have a pcmcia card using "nozomi" driver. The driver creates /dev/noz# from 0 to 3 interfaces.

I tried to patch 77-nm-probe-modem-capabilities.rules without any success. Can someone please give me an hint?

Revision history for this message
Dario Gallucci (dario-gallucci) wrote :

The problem still exists for nozomi GSM modem...

Changed in network-manager:
status: Fix Released → In Progress
Revision history for this message
Alexander Sack (asac) wrote :

please open new bugs, don't reopen this one.

Changed in network-manager (Ubuntu Jaunty):
status: In Progress → Fix Released
Revision history for this message
emam (mohd-emam) wrote :

Hi,
I have a bandrich C100 3G USB modem, and I try to install on Ubuntu 9.04 on Asus EeePC 904HA. The ttyUSB0 has never been detected. I implemented your update on /lib/udev/rules.d/77-nm-probe-modem-capabilities.rules

With no luck.

An

Revision history for this message
emam (mohd-emam) wrote :

Hi,

I am also attaching the syslog before and after the USB connection, looks like it is still seen as a CDROM, see last line in the file @13:08

Regards,
M Emam

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.