Network-Manager not seeing broadband card

Same problem here with a Toshiba G450 HSPA modem (vendor=0x0930, product=0x0d45), which works flawlessly in 8.10.

Apr 24 22:42:55 dodo-mon nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/usb_device_930_d45_noserial_if0_serial_usb_0, iface: (null)): iface not found
Apr 24 22:42:55 dodo-mon NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)
Apr 24 22:42:55 dodo-mon NetworkManager: <info> (ttyUSB0): ignoring due to lack of probed mobile broadband capabilties
Apr 24 22:42:55 dodo-mon NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties
Apr 24 22:42:55 dodo-mon NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties

This is a show-stopper bug: the affected computer doesn't have any other network connection available.

Sierra Aircard 875 (PCMCIA, vendor 0x1199; ID 0x6820 ) showed same problem on Dell D630 when first inserted. (Device recognized as USB modem but did not appear in Network Manager menu) It was working in 8.10 but not in 9.04. But after unplugging and then reseating and then using the WIFI connection to connect to the Web and searching for other reports like this, it finally did get recognized! (Might have something to do with the modem registration on the 3G network?

(I have also have a Novatel MC950D (USB) which *does* work in both 8.10 and 9.04 once you "eject" the NVTL_AICD drive that it gets mounted initially as.)

Apr 26 07:45:53 psvan-03 kernel: [ 1195.164172] pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0
Apr 26 07:45:53 psvan-03 kernel: [ 1195.164261] pci 0000:04:00.0: reg 10 32bit mmio: [0x000000-0x000fff]
Apr 26 07:45:53 psvan-03 kernel: [ 1195.164367] pci 0000:04:00.0: supports D1 D2
Apr 26 07:45:53 psvan-03 kernel: [ 1195.164373] pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot
Apr 26 07:45:53 psvan-03 kernel: [ 1195.164384] pci 0000:04:00.0: PME# disabled
Apr 26 07:45:53 psvan-03 kernel: [ 1195.164474] pci 0000:04:00.1: reg 10 32bit mmio: [0x000000-0x000fff]
Apr 26 07:45:53 psvan-03 kernel: [ 1195.164578] pci 0000:04:00.1: supports D1 D2
Apr 26 07:45:53 psvan-03 kernel: [ 1195.164583] pci 0000:04:00.1: PME# supported from D0 D1 D2 D3hot
Apr 26 07:45:53 psvan-03 kernel: [ 1195.164594] pci 0000:04:00.1: PME# disabled
Apr 26 07:45:53 psvan-03 kernel: [ 1195.165364] ohci_hcd 0000:04:00.0: enabling device (0000 -> 0002)
Apr 26 07:45:53 psvan-03 kernel: [ 1195.165381] ohci_hcd 0000:04:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
Apr 26 07:45:53 psvan-03 kernel: [ 1195.165842] ohci_hcd 0000:04:00.0: setting latency timer to 64
Apr 26 07:45:53 psvan-03 kernel: [ 1195.165851] ohci_hcd 0000:04:00.0: OHCI Host Controller
Apr 26 07:45:53 psvan-03 kernel: [ 1195.166378] ohci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 8
Apr 26 07:45:53 psvan-03 kernel: [ 1195.166413] ohci_hcd 0000:04:00.0: irq 19, io mem 0x8c000000
Apr 26 07:45:54 psvan-03 kernel: [ 1195.250083] usb usb8: configuration #1 chosen from 1 choice
Apr 26 07:45:54 psvan-03 kernel: [ 1195.250162] hub 8-0:1.0: USB hub found
Apr 26 07:45:54 psvan-03 kernel: [ 1195.250187] hub 8-0:1.0: 1 port detected
Apr 26 07:45:54 psvan-03 kernel: [ 1195.250575] ohci_hcd 0000:04:00.1: enabling device (0000 -> 0002)
Apr 26 07:45:54 psvan-03 kernel: [ 1195.250592] ohci_hcd 0000:04:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
Apr 26 07:45:54 psvan-03 kernel: [ 1195.250659] ohci_hcd 0000:04:00.1: setting latency timer to 64
Apr 26 07:45:54 psvan-03 kernel: [ 1195.250667] ohci_hcd 0000:04:00.1: OHCI Host Controller
Apr 26 07:45:54 psvan-03 kernel: [ 1195.250819] ohci_hcd 0000:04:00.1: new USB bus registered, assigned bus number 9
Apr 26 07:45:54 psvan-03 kernel: [ 1195.250850] ohci_hcd 0000:04:00.1: irq 19, io mem 0x8c001000
Apr 26 07:45:54 psvan-03 kernel: [ 1195.334496] usb usb9: configuration #1 chosen from 1 choice
Apr 26 07:45:54 psvan-03 kernel: [ 1195.334806] hub 9-0:1.0: USB hub found
Apr 26 07:45:54 psvan-03 kernel: [ 1195.334830] hub 9-0:1...

Regarding the Toshiba G450, I forgot to say that it also works fine in Jaunty, if you make the ugly hack of adding the device/vendor ids as kernel parameters in /boot/grub/menu.lst (usbserial is not a module anymore!?) and use a dialer, such as wvdial. However, NetworkManager continues thinking there's no active network connection, so Firefox runs in offline mode... :S

I too have the same problem with a Sierra Wireless AC875 (PCMCIA) on a Lenovo T61. However, in my case running through the wizard does not allow the device to be seen to network manager. Worked on 8.10 out-of-the-box.

The kernel still recognizes it when plugged in, but I could not get wvdial or UTMSmon to work (so it is not the same as this bug: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/368457 - where the device shows up in NM but does not connect). On the exact same laptop, if I boot into Fedora 10 (which has Network Mangager 0.7.0.99) it works out-of-the-box as well (9.10 uses NM 0.7.0.100)

The following is the output from syslog, I don't know how to get the console information from Network Manager. Let me know if there's any other information I can provide, this is a big show stopping regression for me, I'd rather not revert to 8.10.

***
May 1 11:21:30 ubuntulaptoptest kernel: [ 5870.960217] USB Serial support registered for Sierra USB modem
May 1 11:21:30 ubuntulaptoptest kernel: [ 5870.960283] sierra 8-1:1.0: Sierra USB modem converter detected
May 1 11:21:30 ubuntulaptoptest kernel: [ 5870.963076] usb 8-1: Sierra USB modem converter now attached to ttyUSB0
May 1 11:21:30 ubuntulaptoptest kernel: [ 5870.963174] usb 8-1: Sierra USB modem converter now attached to ttyUSB1
May 1 11:21:30 ubuntulaptoptest kernel: [ 5870.963267] usb 8-1: Sierra USB modem converter now attached to ttyUSB2
May 1 11:21:30 ubuntulaptoptest kernel: [ 5870.963298] usbcore: registered new interface driver sierra
May 1 11:21:30 ubuntulaptoptest kernel: [ 5870.963304] sierra: v.1.3.2:USB Driver for Sierra Wireless USB modems

I just upgraded to the new version from 8.10. I have an AT&T USBConnect Quicksilver broadband device that Network Manager can not see! It shows up as a cd drive. I can not find a way to get Network Manager to see it.

i think this if fixed upstream.

please test the patch i will attach in a minute.

to test, download that patch to /tmp/ directory, then do:

1. sudo apt-get install build-essential
2. sudo apt-get build-dep network-manager
3. apt-get source network-manager
4. cd network-manager-*/
5. patch -p1 < /tmp/0030-core-only-match-serial-devices-when-filtering-on-or.patch
6. dpkg-buildpackage -rfakeroot -b
7. sudo dpkg -i ../*.deb

once that succeeds restart your system.

.patch text file moved to /tmp
step 1 initiated: gksudo apt-get install build-essential
step 1 completed
step 2 initiated: gksudo apt-get build-dep network manager
step 2 cont: Reading package lists... Done
step 2 cont: Building dependancy tree
step 2 cont: Reading state information... Done
step 2 cont: 0 upgraded, 121 newly installed, o to remove and 3 not upgraded.
step 2 cont: Need to get 34.9MB of archives.
step 2 cont: After this operation, 140 MB of additional disk space will be used.
step 2 cont: Do you want to continue [Y/n]? Y
step 2: # After 'Y' entered, terminal hangs.

I followed the instructions and installed the patch (the only missing piece was that I had to apt-get install fakeroot as well in order for the dpkg-buildpackage to succeed). Still doesn't recognize the Sierra AC875 wireless card in Network Manager.

Also, I updated Fedora 10 to the latest patch revision, and it broke there as well. I booted with older kernel versions (in both Ubuntu and Fedora) to verify that nothing had changed with the kernel driver to break this.

Let me know if there's additional troubleshooting information I can gather.

@rinosarus: Verify your network connection, I plugged in the ethernet adapter to make sure the connection was stable (rather than doing it over wireless), and had no problems downloading.

Josh,

Sorry, I should have clarified. I am running over ethernet. Both eth0 and wireless (WiFi) work fine. The Sierra Wireless 875 PCMCIA card (which "just worked" out the the box in 8.10 IS receiving power and drivers are present as per Sierra Wireless site. The status LED's show power good (blue) and 3G present (amber, present but not connected). The card does not show under network manager, and attempts to add the card manually via network manager show an entry under 'Mobile Broadband' (not an 'Auto' entry though). The entry is not available under the available connections as it was under 8.10. The wired and wireless do show under available connections (left-click network icon to the left of the date, clock, etc. in the upper right)

Quick Update:

Tried to launch 9.04 as LIVE, still no luck. I will attempt reload next.

No help - reloaded - still same behavior - only additions to raw load are Gnome Do and Tilde (quake style terminal)

Same problem with Jaunty UNR on an ASUS Eee 1000HA Netbook with MF627 Mobile broadband dongle connected. Dmesg shows the dongle is recognised. Using usb_modeswitch to switch to modem. The card is not displayed in Network-manager. I can no longer connect to a broadband network. What is going on here? This is critical for UNR and Netbook use in general.

From looking at the source code, we have a udev test and a HAL test.

The udev path looks for ID_NM_MODEM_GSM=1 in the capabilities.

On my system, my Sierra device has:

$ sudo /sbin/udevadm info --query=env --path=/sys/devices/pci0000:00/0000:00:1e.0/0000:03:01.0/0000:04:00.0/usb8/8-1/8-1:1.0
UDEV_LOG=3
DEVPATH=/devices/pci0000:00/0000:00:1e.0/0000:03:01.0/0000:04:00.0/usb8/8-1/8-1:1.0
DEVTYPE=usb_interface
DRIVER=sierra
DEVICE=/proc/bus/usb/008/002
PRODUCT=1199/6820/2
TYPE=0/0/0
INTERFACE=255/255/255
MODALIAS=usb:v1199p6820d0002dc00dsc00dp00icFFiscFFipFF

So no GSM string.

But in the HAL path, it looks for 'GSM-07.07' in modem.command_sets, which my system does have:

$ sudo lshal
[...]
udi = '/org/freedesktop/Hal/devices/usb_device_1199_6820_noserial_if0_serial_usb_0'
  access_control.file = '/dev/ttyUSB0' (string)
  access_control.type = 'modem' (string)
  info.callouts.add = {'hal-acl-tool --add-device'} (string list)
  info.callouts.remove = {'hal-acl-tool --remove-device'} (string list)
  info.capabilities = {'serial', 'modem', 'access_control'} (string list)
  info.category = 'serial' (string)
  info.parent = '/org/freedesktop/Hal/devices/usb_device_1199_6820_noserial_if0' (string)
  info.product = 'AC875 Device' (string)
  info.subsystem = 'tty' (string)
  info.udi = '/org/freedesktop/Hal/devices/usb_device_1199_6820_noserial_if0_serial_usb_0' (string)
  linux.device_file = '/dev/ttyUSB0' (string)
  linux.hotplug_type = 2 (0x2) (int)
  linux.subsystem = 'tty' (string)
  linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1e.0/0000:03:01.0/0000:04:00.0/usb8/8-1/8-1:1.0/ttyUSB0/tty/ttyUSB0' (string)
  modem.command_sets = {'GSM-07.07', 'GSM-07.05'} (string list)
  serial.device = '/dev/ttyUSB0' (string)
  serial.originating_device = '/org/freedesktop/Hal/devices/usb_device_1199_6820_noserial_if0' (string)
  serial.port = 0 (0x0) (int)
  serial.type = 'usb' (string)
[...]

Then the code says we trust udev over HAL...

        /* Case (c): HAL thinks it's a modem, but udev doesn't */
        nm_info ("(%s): ignoring due to lack of probed mobile broadband capabilties", ttyname);
        later = FALSE;

So I've got to make udev return that extra capability, which is obviously what Alexander's patches are about, but at least know I know why and how I might be able to help.

My ttyUSB0 sub-device has ID_MODEM_GSM=1

Should it be ID_MODEM_GSM or ID_NM_MODEM_GSM?

ttyUSB1 and ttyUSB2 do not have that capability listed.

$ sudo /sbin/udevadm info --query=env --path=/sys/devices/pci0000:00/0000:00:1e.0/0000:03:01.0/0000:04:00.0/usb8/8-1/8-1:1.0/ttyUSB0
UDEV_LOG=7
DEVPATH=/devices/pci0000:00/0000:00:1e.0/0000:03:01.0/0000:04:00.0/usb8/8-1/8-1:1.0/ttyUSB0
DRIVER=sierra

Sorry my feed back has been missing from this and I thank all of the folks who have had the same issue and have supplied the information needed to progress this bug.

The patch provided by Alex (https://bugs.launchpad.net/ubuntu/jaunty/+source/network-manager/+bug/360905/comments/8) has corrected the original bug in my case (sierra wireless 875U). Thank you Alex for your efforts as well.

Regards,

Can confirm same issue with Huawei Technologies Co., Ltd. E220 HSDPA Modem.

If inserted before booting, network manager recognises modem and starts connection. If inserted after boot, modem not recognised.

Worked flawlessly before upgrade to Jaunty.

I have the same problem, but with the KDE Network Manager Plasma Widget. The Card is definitely detected by Networkmanager and even by the widget itself (hovering over it shows "ttyUSB0 Not connected"), but "mobile broadband is greyed out and the card is not shown in the list of active devices.

This not related to https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager/+bug/334122 which was fixed.

Everything was fine, but then I upgraded to KDE 4.3 Beta 1.

With the Gnome network-manager applet used in KDE everything is fine. The reason why I am posting here is that I want to ask if the efforts of fixing this bug may have caused a breakage in KDE widget? I will post a separate Bug in the KDE bugtracker and in Launchpad, but if there is a relation it may be a useful for the KDE people to know.

I have found a related bug already in Launchpad:
https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager/+bug/352922
This suggests that the problem is related, the other bug may be a duplicate then.

I have tried the patch using the KDE-Network-Widget. It has no effect. I have an Option Geo 201 card.

Here my /var/log/daemon.log

Jun 3 10:27:22 penguin NetworkManager: <info> (ttyUSB0): found serial port (udev:GSM hal:)
Jun 3 10:27:22 penguin NetworkManager: <info> (ttyUSB0): deferring until all ports found
Jun 3 10:27:27 penguin NetworkManager: <info> Re-checking deferred serial ports
Jun 3 10:27:27 penguin NetworkManager: <info> (ttyUSB0): new Modem device (driver: 'usb')
Jun 3 10:27:27 penguin NetworkManager: <info> (ttyUSB0): exported as /org/freedesktop/Hal/devices/usb_device_af0_6701_Serial_Number_serial_usb_0
Jun 3 10:27:28 penguin NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties
Jun 3 10:27:28 penguin NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Jun 3 10:27:31 penguin NetworkManager: <info> (ttyUSB0): device state change: 1 -> 2
Jun 3 10:27:31 penguin NetworkManager: <info> (ttyUSB0): deactivating device (reason: 2).

Another daemon.log for E220:

Jun 3 20:22:44 loki NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Jun 3 20:22:46 loki ovpn-client[2669]: read UDPv4 [ECONNREFUSED]: Connection refused (code=111)
Jun 3 20:22:50 loki last message repeated 2 times
Jun 3 20:22:51 loki 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
Jun 3 20:22:51 loki NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)
Jun 3 20:22:51 loki NetworkManager: <info> (ttyUSB0): ignoring due to lack of probed mobile broadband capabilties
Jun 3 20:22:52 loki ovpn-client[2669]: read UDPv4 [ECONNREFUSED]: Connection refused (code=111)
Jun 3 20:23:25 loki last message repeated 15 times

and messages:

....
Jun 3 20:22:44 loki kernel: [34998.051168] USB Serial support registered for generic
Jun 3 20:22:44 loki kernel: [34998.051249] usbcore: registered new interface driver usbserial_generic
Jun 3 20:22:44 loki kernel: [34998.051253] usbserial: USB Serial Driver core
Jun 3 20:22:44 loki kernel: [34998.057619] USB Serial support registered for GSM modem (1-port)
Jun 3 20:22:44 loki kernel: [34998.057718] option 6-2:1.0: GSM modem (1-port) converter detected
Jun 3 20:22:44 loki kernel: [34998.057868] usb 6-2: GSM modem (1-port) converter now attached to ttyUSB0
Jun 3 20:22:44 loki kernel: [34998.057890] option 6-2:1.1: GSM modem (1-port) converter detected
Jun 3 20:22:44 loki kernel: [34998.057981] usb 6-2: GSM modem (1-port) converter now attached to ttyUSB1
Jun 3 20:22:44 loki kernel: [34998.058006] usbcore: registered new interface driver option
Jun 3 20:22:44 loki kernel: [34998.058010] option: v0.7.2:USB Driver for GSM modems

Andy was correct...

It worked great because I rebooted and works when the card is connected on boot. The card does not work on hotplug...\

Jun 3 08:30:23 james-laptop kernel: [ 1782.124093] usb 3-1: new full speed USB device using ohci_hcd and address 2
Jun 3 08:30:23 james-laptop kernel: [ 1782.292035] usb 3-1: configuration #1 chosen from 1 choice
Jun 3 08:30:23 james-laptop kernel: [ 1782.362872] USB Serial support registered for Sierra USB modem
Jun 3 08:30:23 james-laptop kernel: [ 1782.362943] sierra 3-1:1.0: Sierra USB modem converter detected
Jun 3 08:30:23 james-laptop kernel: [ 1782.364362] usb 3-1: Sierra USB modem converter now attached to ttyUSB0
Jun 3 08:30:23 james-laptop kernel: [ 1782.364468] usb 3-1: Sierra USB modem converter now attached to ttyUSB1
Jun 3 08:30:23 james-laptop kernel: [ 1782.364576] usb 3-1: Sierra USB modem converter now attached to ttyUSB2
Jun 3 08:30:23 james-laptop kernel: [ 1782.364615] usbcore: registered new interface driver sierra
Jun 3 08:30:23 james-laptop kernel: [ 1782.364622] sierra: v.1.3.2:USB Driver for Sierra Wireless USB modems
Jun 3 08:30:24 james-laptop NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties
Jun 3 08:30:29 james-laptop nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/usb_device_1199_6812_noserial_if0_serial_usb_0, iface: (null)): iface not found
Jun 3 08:30:29 james-laptop NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)
Jun 3 08:30:29 james-laptop NetworkManager: <info> (ttyUSB0): ignoring due to lack of probed mobile broadband capabilties
Jun 3 08:30:30 james-laptop NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties

I had only tried hotplugging it, so I recompiled/patched/installed the fix, and it still doesn't work for me, even if the card is inserted prior to boot. I know the other bug (which is not the same) says to update the firmware, I can try that and see if it has an effect, since I'm sure this still has the original firmware on it.

I get the same messages in the daemon.log (grep "ttyUSB" /var/log/daemon.log):
Jun 3 11:42:22 ubuntulaptoptest NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties
Jun 3 11:42:23 ubuntulaptoptest NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)
Jun 3 11:42:23 ubuntulaptoptest NetworkManager: <info> (ttyUSB0): ignoring due to lack of probed mobile broadband capabilties
Jun 3 11:42:24 ubuntulaptoptest NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties

I can attach the output of my lshal if someone would find that useful (I didn't see a nice way to grep out the relevant sections). For the moment, Ubuntu's Network Manager is still dead in the water for me and I'm using Fedora 10 with the older Network Manager.

Just to update, I updated to the latest firmware, and still no luck (it did have the original firmware from the factory, H1_0_0_6ACAP, which I upgraded to H1_1_8_3ACAP). I do have an AC875 (not an AC875U so maybe that explains the difference as to why mine doesn't work at all, whereas others have had some success).

Just received update for network-manager-gnome to 0.7.1-0ubuntu1~nm1~jaunty1 (repository update). Will monitor and report.

Update to network-manager-gnome 0.7.1 (as commented above) has not changed behaviour.

This may be a wider problem than just USB mobile broadband hot-plugging. I booted with my wireless network 'hard' switched off (on a Lenovo T500). When I switched it on, the network adapter was not recognised.

Looking for similar existing bug now.

I also am using and AC875 (PCMCIA). I reinstalled 8.10, and got full functionality "out of the box". I then tried upgrading (rather than clean install) via update manager to 9.04. Instantly lost the card in network manager. Card was installed during upgrade (and used for upgrade downloads), and has been in machine throughout.

@Andy

The hard switch didn't work in 8.10 either like that, so I think that's more of a feature request than a bug. FYI, if you accidentally had it hard switched off and booted that way, you can open a console and rmmod the driver and modprobe it back in. In my case (for the T61's intel wireless) the sequence is:
sudo rmmod iwlagn
sudo modprobe iwlagn
And then Network Manager will pick up the device after a few seconds and if you have an autoconnect profile, it will attempt to autoconnect.

@rinosarus

Were you able to follow the instructions above to test the patch?

Applied the patch, still doesn't work.

As previously stated, the issue appears to be in udev.

libudev: udev_device_new_from_syspath: device 0x865a400 has devpath '/devices/pnp0/00:09/tty/ttyS0'
libudev: udev_device_read_db: device 0x865a400 filled with db symlink data '/dev/ttyS0'
NetworkManager: <info> (ttyS0): ignoring due to lack of mobile broadband capabilties
libudev: udev_device_new_from_syspath: device 0x865a4b0 has devpath '/devices/pci0000:00/0000:00:1e.0/0000:03:01.0/0000:04:00.0/usb8/8-1/8-1:1.0/ttyUSB2/tty/ttyUSB2'
libudev: udev_device_read_db: device 0x865a4b0 filled with db file data
NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties
libudev: udev_device_new_from_syspath: device 0x865a400 has devpath '/devices/pci0000:00/0000:00:1e.0/0000:03:01.0/0000:04:00.0/usb8/8-1/8-1:1.0/ttyUSB1/tty/ttyUSB1'
libudev: udev_device_read_db: device 0x865a400 filled with db file data
NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
libudev: udev_device_new_from_syspath: device 0x865a400 has devpath '/devices/pci0000:00/0000:00:1e.0/0000:03:01.0/0000:04:00.0/usb8/8-1/8-1:1.0/ttyUSB0/tty/ttyUSB0'
libudev: udev_device_read_db: device 0x865a400 filled with db file data
NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)
NetworkManager: <info> (ttyUSB0): ignoring due to lack of probed mobile broadband capabilties

> Should it be ID_MODEM_GSM or ID_NM_MODEM_GSM?

the latter. maybe you have udev-extras installed? what do you get for ls /lib/udev/*probe* ?

> With the Gnome network-manager applet used in KDE everything is fine. The reason why
> I am posting here is that I want to ask if the efforts of fixing this bug may have caused a
> breakage in KDE widget?

unlikely. please file a bug against plasma network widget package.

> It worked great because I rebooted and works when the card is connected on boot.
> The card does not work on hotplug...\

please set udev in debugging mode like:

sudo udevadm control --log-priority=debug

then plug in your device and submit what you get as output in syslog.

> As previously stated, the issue appears to be in udev.

i dont see any invokation of nm-modem-probe in your log. which log priority did you use? please do the same with --log-priority=debug (see previous post).

Also please run:

nm-modem-probe --verbose --export /dev/ttyUSBx

for your ttyUSBx ports and see what you get.

Syslog with udev debug for hot-plugged Huawei E220 HSDPA Modem

Yes, udev-extras is installed.

ii udev-extras 0~-2~gite5fb9bd-1 additional rules and add-ons for udev

I think it was installed when installing the patched version you mentioned on May 6 (network-manager-0.7.1\~rc4.1.cf199a964).

$ ls /lib/udev/*probe*
/lib/udev/modem-probe /lib/udev/nm-modem-probe

Will do the debug udev probe stuff now.

andy@loki:~$ /lib/udev/nm-modem-probe --verbose --export /dev/ttyUSB0
L: main(): (/dev/ttyUSB0): usb-vid 0x0000 usb-pid 0x0000 usb-intf 0 driver '(null)'
L: main(): probing /dev/ttyUSB0
L: modem_send_command(): Sending: 'AT+GCAP
'
L: modem_wait_reply(): Got: 'AT+GCA'
L: modem_wait_reply(): Got: 'AT+GCAP'
L: modem_wait_reply(): Got: 'AT+GCAP
+GCAP: +CGSM,+FCLASS,+DS

OK
'
L: modem_probe_caps(): GCAP response: +GCAP: +CGSM,+FCLASS,+DS
ID_NM_MODEM_GSM=1
ID_NM_MODEM_PROBED=1
L: main(): /dev/ttyUSB0: caps (0x29) GSM

andy@loki:~$
andy@loki:~$ /lib/udev/nm-modem-probe --verbose --export /dev/ttyUSB1
L: main(): (/dev/ttyUSB1): usb-vid 0x0000 usb-pid 0x0000 usb-intf 0 driver '(null)'
L: main(): probing /dev/ttyUSB1
L: modem_send_command(): Sending: 'AT+GCAP
'
L: modem_wait_reply(): Got: '

^BOOT:75472591,0,0,0,6

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

^BOOT:75472591,0,0,0,6

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

^BOOT:75472591,0,0,0,6

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

^BOOT:75472591,0,0,0,6

T+GCAP
+GCAP: +CGSM,+FCLASS,+DS

OK
'
L: modem_probe_caps(): GCAP response: +GCAP: +CGSM,+FCLASS,+DS
ID_NM_MODEM_GSM=1
ID_NM_MODEM_PROBED=1
L: main(): /dev/ttyUSB1: caps (0x29) GSM

andy@loki:~$

Entries in /var/log/syslog after card was plugged in.

Same issue with a Motorola A910 phone. Here is syslog with debug priority:

Jun 15 15:37:55 chimera kernel: [118371.440119] usb 3-1: new full speed USB device using uhci_hcd and address 3
Jun 15 15:37:55 chimera udevd[7639]: seq 1923 queued, 'add' 'usb'
Jun 15 15:37:55 chimera udevd-event[21354]: device 0x7fc3532683e0 has devpath '/devices/pci0000:00/0000:00:1a.0/usb3/3-1'
Jun 15 15:37:55 chimera udevd-event[21354]: device 0x7fc353267ce0 has devpath '/devices/pci0000:00/0000:00:1a.0/usb3'
Jun 15 15:37:55 chimera udevd-event[21354]: device 0x7fc353268590 has devpath '/devices/pci0000:00/0000:00:1a.0'
Jun 15 15:37:55 chimera udevd-event[21354]: device 0x7fc353268990 has devpath '/devices/pci0000:00'
Jun 15 15:37:55 chimera udevd-event[21354]: LINK 'char/189:258' /lib/udev/rules.d/50-udev-default.rules:5
Jun 15 15:37:55 chimera udevd-event[21354]: MODE 0664 /lib/udev/rules.d/50-udev-default.rules:53
Jun 15 15:37:55 chimera udevd-event[21354]: NAME 'bus/usb/003/003' /lib/udev/rules.d/50-udev-default.rules:53
Jun 15 15:37:55 chimera udevd-event[21354]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2
Jun 15 15:37:55 chimera udevd-event[21354]: create db link (bus/usb/003/003 char/189:258)
Jun 15 15:37:55 chimera udevd-event[21354]: creating device node '/dev/bus/usb/003/003', devnum=189:258, mode=0664, uid=0, gid=0
Jun 15 15:37:55 chimera udevd-event[21354]: mknod(/dev/bus/usb/003/003, 020664, (189,258))
Jun 15 15:37:55 chimera udevd-event[21354]: chmod(/dev/bus/usb/003/003, 020664)
Jun 15 15:37:55 chimera udevd-event[21354]: chown(/dev/bus/usb/003/003, 0, 0)
Jun 15 15:37:55 chimera udevd-event[21354]: '/dev/char/189:258' with target '/dev/bus/usb/003/003' has the highest priority 0, create it
Jun 15 15:37:55 chimera udevd-event[21354]: creating symlink '/dev/char/189:258' to '../bus/usb/003/003'
Jun 15 15:37:55 chimera udevd-event[21354]: passed 321 bytes to monitor 0x7fc3532683e0
Jun 15 15:37:55 chimera udevd-event[21354]: passed -1 bytes to monitor 0x7fc353257670
Jun 15 15:37:55 chimera udevd-event[21354]: seq 1923 exit with 0
Jun 15 15:37:55 chimera udevd[7639]: seq 1923 forked, pid [21354], 'add' 'usb', 0 seconds old
Jun 15 15:37:55 chimera udevd[7639]: seq 1923 cleanup, pid [21354], status 0, 0 seconds old
Jun 15 15:37:55 chimera kernel: [118371.624561] usb 3-1: configuration #1 chosen from 1 choice
Jun 15 15:37:55 chimera kernel: [118371.630972] cdc_acm 3-1:1.0: ttyACM0: USB ACM device
Jun 15 15:37:55 chimera udevd[7639]: seq 1924 queued, 'add' 'usb'
Jun 15 15:37:55 chimera udevd-event[21355]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2
Jun 15 15:37:55 chimera udevd-event[21355]: passed 313 bytes to monitor 0x7fc353268f40
Jun 15 15:37:55 chimera udevd-event[21355]: passed -1 bytes to monitor 0x7fc353257670
Jun 15 15:37:55 chimera udevd-event[21355]: seq 1924 exit with 0
Jun 15 15:37:55 chimera udevd[7639]: seq 1924 forked, pid [21355], 'add' 'usb', 0 seconds old
Jun 15 15:37:55 chimera udevd[7639]: seq 1924 cleanup, pid [21355], status 0, 0 seconds old
Jun 15 15:37:55 chimera udevd[7639]: seq 1925 queued, 'add' 'tty'
Jun 15 15:37:55 chimera udevd-e...

USB0 is a modem
ID_NM_MODEM_GSM=1
ID_NM_MODEM_PROBED=1

USB1 is not a modem.

USB2 is not detected as a modem, but is responding to some AT commands.

On Mon, Jun 15, 2009 at 11:39:08PM -0000, Mikel Ward wrote:
> Yes, udev-extras is installed.
>
> ii udev-extras 0~-2~gite5fb9bd-1
> additional rules and add-ons for udev
>
> I think it was installed when installing the patched version you
> mentioned on May 6 (network-manager-0.7.1\~rc4.1.cf199a964).
>
> $ ls /lib/udev/*probe*
> /lib/udev/modem-probe /lib/udev/nm-modem-probe
>
> Will do the debug udev probe stuff now.

remove udev-extras package please. having two modem probers fighting
over your thing, doesnt sound promissing ;).

>

 - Alexander

On Tue, Jun 16, 2009 at 12:09:04AM -0000, Daniel Gimpelevich wrote:
>
> L: main(): (/dev/ttyACM0): usb-vid 0x0000 usb-pid 0x0000 usb-intf 0 driver '(null)'
> L: main(): probing /dev/ttyACM0
> L: modem_send_command(): Sending: 'AT+GCAP
>

Daniel, I think we should track your modem in a separate bug, as for
you even running the modem prober manually doesnt work. Please open a
new one, and drop the bug id here so we can followup there.

 - Alexander

Removed udev extras, but no difference. :-)

$ ls /lib/udev/*probe*
/lib/udev/nm-modem-probe

Jun 16 19:42:49 laptop NetworkManager: <info> (ttyS0): ignoring due to lack of mobile broadband capabilties
Jun 16 19:42:49 laptop NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties
Jun 16 19:42:49 laptop NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Jun 16 19:42:49 laptop NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)

On Tue, Jun 16, 2009 at 09:57:24AM -0000, Mikel Ward wrote:> Removed udev extras, but no difference. :-)
>
> $ ls /lib/udev/*probe*
> /lib/udev/nm-modem-probe
>
> Jun 16 19:42:49 laptop NetworkManager: <info> (ttyS0): ignoring due to lack of mobile broadband capabilties
> Jun 16 19:42:49 laptop NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties
> Jun 16 19:42:49 laptop NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
> Jun 16 19:42:49 laptop NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)
>

Hmm.. please set your udev to debug again, and replug your
system. also do the same after a fresh restart and attach both parts
from syslog.

Also you can see a nm-modem-probe command in the syslog, try to use
that with the /dev/ttyUSB0 and see if that works.

 - Alexander

udev debug syslog output after removing udev-extras

This one?

$ sudo /lib/udev/nm-modem-probe --vid 0x1199 --pid 0x6820 --usb-interface 00 --driver sierra --delay 3000 --export /dev/.tmp-char-188:0
open(/dev/.tmp-char-188:0) failed: 2

Sorry, obviously you meant this:
$ sudo /lib/udev/nm-modem-probe --vid 0x1199 --pid 0x6820 --usb-interface 00 --driver sierra --delay 3000 --export /dev/ttyUSB0
ID_NM_MODEM_GSM=1
ID_NM_MODEM_PROBED=1

FYI, I had a similar problem. After many hours I got my 3g card working.

For those of you using usbserial driver, there is a udev rule that prevents nm-modem-probe being executed to add ID_NM_MODEM_GSM=1
ID_NM_MODEM_PROBED=1
to your ttyUSB device info.

I got around this by modifying the rule to remove the checks based on driver. For some reason usbserial isn't in the list.

/lib/udev/rules.d/77-nm-probe-modem-capabilities.rules

Could you be a bit more specific about what has to be changed in this file so that I can test it?

syslog attached...

***********************
modem probe ttyUSB0
***********************

L: main(): (/dev/ttyUSB0): usb-vid 0x0000 usb-pid 0x0000 usb-intf 0 driver '(null)'
L: main(): probing /dev/ttyUSB0
L: modem_send_command(): Sending: 'AT+GMM
'
L: modem_wait_reply(): Got: 'AT'
L: modem_wait_reply(): Got: 'AT+'
L: modem_wait_reply(): Got: 'AT+G'
L: modem_wait_reply(): Got: 'AT+GM'
L: modem_wait_reply(): Got: 'AT+GMM
ERROR
'
ID_NM_MODEM_PROBED=1
L: main(): /dev/ttyUSB0: caps (0x0)

***********************
modem probe ttyUSB1
***********************

L: main(): (/dev/ttyUSB1): usb-vid 0x0000 usb-pid 0x0000 usb-intf 0 driver '(null)'
L: main(): probing /dev/ttyUSB1
L: modem_send_command(): Sending: 'AT+GCAP
'
L: modem_probe_caps(): timed out waiting for GCAP reply (idx -2, term_idx -1)
L: modem_send_command(): Sending: 'AT+GCAP
'
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)

***********************
modem probe ttyUSB2
***********************

L: main(): (/dev/ttyUSB2): usb-vid 0x0000 usb-pid 0x0000 usb-intf 0 driver '(null)'
L: main(): probing /dev/ttyUSB2
L: modem_send_command(): Sending: 'AT+GCAP
'
L: modem_wait_reply(): Got: '
OK
'
L: modem_probe_caps(): GCAP failed, trying ATI...
L: modem_send_command(): Sending: 'ATI
'
L: modem_wait_reply(): Got: 'Sierra Wireless, Inc.
MC8775
APP1
'
L: modem_wait_reply(): Got: 'Sierra Wireless, Inc.
MC8775
APP1

OK
'
L: modem_send_command(): Sending: 'AT+GMM
'
L: modem_wait_reply(): Got: '
OK
'
ID_NM_MODEM_PROBED=1
L: main(): /dev/ttyUSB2: caps (0x0)

What's all this stuff by the way?

Adding --log /var/log/nmprobe.log to the udev rules prints all this:

**** Started: Thu Jun 18 12:43:12 2009

E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5

But no mention of any ID_NM stuff (usage message says --log <file> logs ALL output, is that correct?).

I wrote a wrapper script around nm-modem-probe.

It turns out it works only if you probe the modem twice!

I tried sleeping for 3, 5, 8, 10 seconds and then probing once, but that didn't work.

I could probe using /dev/.tmp-char-188:0 the first time and /dev/ttyUSB0 the second time, the other way around, or the same device twice.

The only thing that mattered was that I probed the device twice.

3975 13:30:47 nm-modem-probe /dev/.tmp-char-188:0:
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
E: error writing command: 5
ID_NM_MODEM_PROBED=1
3975 13:30:53 nm-modem-probe /dev/ttyUSB0:
ID_NM_MODEM_GSM=1
ID_NM_MODEM_PROBED=1

Adding another entry to /lib/udev/rules.d/77-nm-probe-modem-capabilities.rules without the GOTO made NetworkManager see it. :-)

Working rules file attached.

After that, I connected. The link light went blue, but NetworkManager gave me no DNS servers (it came up in Automatic PPP addresses only mode and an empty address list - I can't remember how it was set in Ubuntu 8.10, but it worked there).

I changed it to Automatic PPP so it would use the default DNS servers, then tried reconnecting, at which point my whole system hung.

After a hard reset, it seems to be working.

On Wed, Jun 17, 2009 at 05:56:05PM -0000, James wrote:
>
> OK
> '
> L: modem_send_command(): Sending: 'AT+GMM

Could you minicom against this device and check if AT+CGMM gives
you a better result?

 - Alexander

On Thu, Jun 18, 2009 at 03:57:42AM -0000, Mikel Ward wrote:
> I wrote a wrapper script around nm-modem-probe.
>
> It turns out it works only if you probe the modem twice!
>
> I tried sleeping for 3, 5, 8, 10 seconds and then probing once, but that
> didn't work.

There is a --delay argument in the udev rules file. can you see if
tweaking that helps? Also when observing the log you posted, do those
multiple E: error writing ... lines just flush out at once, or is
there some wait in between?

 - Alexander

On Thu, Jun 18, 2009 at 04:15:32AM -0000, Mikel Ward wrote:
> After that, I connected. The link light went blue, but NetworkManager
> gave me no DNS servers (it came up in Automatic PPP addresses only mode
> and an empty address list - I can't remember how it was set in Ubuntu
> 8.10, but it worked there).

There is a bug in ppp which makes the dns servers you get
unreliable. Instead use the broadband wizard and select your provider,
which fills in the right nameserver.

 - Alexander

There is some wait in between.

Inserted modem at :20.
Blue power light at :25.
Amber 3G signal light at :30.

Thu Jun 18 23:42:20 EST 2009
Thu Jun 18 23:42:21 EST 2009
Thu Jun 18 23:42:22 EST 2009
Thu Jun 18 23:42:23 EST 2009
Thu Jun 18 23:42:24 EST 2009
Thu Jun 18 23:42:25 EST 2009
tail: 0.out: file truncated
Thu Jun 18 23:42:26 EST 2009
error writing command: 5
error writing command: 5
Thu Jun 18 23:42:26 EST 2009
error writing command: 5
Thu Jun 18 23:42:27 EST 2009
error writing command: 5
error writing command: 5
Thu Jun 18 23:42:27 EST 2009
error writing command: 5
Thu Jun 18 23:42:28 EST 2009
error writing command: 5
error writing command: 5
error writing command: 5
Thu Jun 18 23:42:28 EST 2009
error writing command: 5
Thu Jun 18 23:42:29 EST 2009
error writing command: 5
error writing command: 5
Thu Jun 18 23:42:29 EST 2009
error writing command: 5
Thu Jun 18 23:42:30 EST 2009
error writing command: 5
error writing command: 5
Thu Jun 18 23:42:30 EST 2009
error writing command: 5
Thu Jun 18 23:42:31 EST 2009
error writing command: 5
error writing command: 5
error writing command: 5
Thu Jun 18 23:42:31 EST 2009
error writing command: 5
11897 23:42:32 ls -l /dev/.tmp-char-188:0:
crw------- 1 root root 188, 0 Jun 18 23:42 /dev/.tmp-char-188:0
11897 23:42:32 ls -l /dev/ttyUSB0:
ls: cannot access /dev/ttyUSB0: No such file or directory
Thu Jun 18 23:42:32 EST 2009
Thu Jun 18 23:42:33 EST 2009

With the duplicate (required?) entries, delay of 1000 msec for both works, delay of 100 msec for both fails with:
Jun 18 23:48:23 laptop NetworkManager: <info> (ttyUSB0): found serial port (udev:GSM hal:)
Jun 18 23:48:23 laptop NetworkManager: <info> (ttyUSB0): deferring until all ports found

Obviously anything higher than 3000 (I tried 6000) will fail, since max delay is 3000.

On Thu, Jun 18, 2009 at 01:50:32PM -0000, Mikel Ward wrote:
> With the duplicate (required?) entries, delay of 1000 msec for both works, delay of 100 msec for both fails with:

Sorry. not sure i understand what you mean with duplicate entries
here. Please use the "default" udev rules shipped by our NM package to
test what i suggest.

 - Alexander

The duplicate SUBSYSTEM=="tty"... IMPORT{program}="nm-modem-probe" entries as described earlier today.

I tried reverting that change, and setting the delay to 100, 200, 500, 1000, 2000, and 3000, and none of them caused NM to report a GSM modem on ttyUSB0, but it didn't seem likely it would.

Actually, the rules file is from 0.7.1~rc4.1.cf199a964-0ubuntu2, so if there's a different version you'd like me to try, can you please attach it here?

ok, can you please test this patch? assuming you save it as /tmp/lp360905_try_longer_eagain.patch you can build a package and install it, like:

-1. sudo apt-get install build-essential fakeroot
0. sudo apt-get build-dep network-manager
1. apt-get source network-manager
2. cd network-manager-0*/
3. cp /tmp/lp360905_try_longer_eagain.patch debian/patches/
4. echo lp360905_try_longer_eagain.patch >> debian/patches/series
5. dpkg-buildpackage -rfakeroot -b
6. sudo dpkg -i ../*.deb

After patch: #67

Jun 18 10:26:54 james-laptop kernel: [ 383.668055] usb 3-1: new full speed USB device using ohci_hcd and address 4
Jun 18 10:26:54 james-laptop kernel: [ 383.835953] usb 3-1: configuration #1 chosen from 1 choice
Jun 18 10:26:54 james-laptop kernel: [ 383.838259] sierra 3-1:1.0: Sierra USB modem converter detected
Jun 18 10:26:54 james-laptop kernel: [ 383.839572] usb 3-1: Sierra USB modem converter now attached to ttyUSB0
Jun 18 10:26:54 james-laptop kernel: [ 383.839917] usb 3-1: Sierra USB modem converter now attached to ttyUSB1
Jun 18 10:26:54 james-laptop kernel: [ 383.840269] usb 3-1: Sierra USB modem converter now attached to ttyUSB2
Jun 18 10:26:55 james-laptop lt-NetworkManager: <info> (ttyUSB2): ignoring due to lack of mobile broadband capabilties
Jun 18 10:27:00 james-laptop nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/usb_device_1199_6812_noserial_if0_serial_usb_0, iface: (null)): iface not found
Jun 18 10:27:00 james-laptop lt-NetworkManager: <info> (ttyUSB0): found serial port (udev: hal:GSM)
Jun 18 10:27:00 james-laptop lt-NetworkManager: <info> (ttyUSB0): ignoring due to lack of probed mobile broadband capabilties
Jun 18 10:27:01 james-laptop lt-NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties

Hi

I have the same problem with a Huawei ETS 2258 wireless telefone with TI 3410 modem chip
jaunty, nm is actual as per above;
/dev/ttyUSB0 is created but not recognized with nm

best regards

EM

Still doesn't work.
Jun 19 11:10:47 laptop NetworkManager: <info> (ttyUSB0): found serial
port (udev: hal:GSM)
Jun 19 11:10:47 laptop NetworkManager: <info> (ttyUSB0): ignoring due
to lack of probed mobile broadband capabilties

In fact I can't see any difference
9666 11:16:32 nm-modem-probe /dev/.tmp-char-188:0:
error writing command: 5
error writing command: 5
Fri Jun 19 11:16:33 EST 2009
Fri Jun 19 11:16:34 EST 2009
error writing command: 5
error writing command: 5
error writing command: 5
Fri Jun 19 11:16:34 EST 2009
error writing command: 5
Fri Jun 19 11:16:35 EST 2009
error writing command: 5
error writing command: 5
error writing command: 5
Fri Jun 19 11:16:35 EST 2009
Fri Jun 19 11:16:36 EST 2009
error writing command: 5
error writing command: 5
error writing command: 5
Fri Jun 19 11:16:36 EST 2009
Fri Jun 19 11:16:37 EST 2009
error writing command: 5
error writing command: 5
error writing command: 5
Fri Jun 19 11:16:37 EST 2009
error writing command: 5
Fri Jun 19 11:16:38 EST 2009
error writing command: 5
error writing command: 5
error writing command: 5
Fri Jun 19 11:16:38 EST 2009
Fri Jun 19 11:16:39 EST 2009

Intrepid amd64 -- Suddenly lost wireless (and wired) networking, via NM.

I upgraded to Jaunty, hoping that that would fix the issue, but no such luck.

I'm attaching my networking info -- lshw, lspci, ifconfig, iwconfig.

Below is what happened when I attempted to configure the wireless/WEP interface manually:

$ ifconfig wlan0 down

$ dhclient -r wlan0
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:1d:e0:9a:c6:ed
Sending on LPF/wlan0/00:1d:e0:9a:c6:ed
Sending on Socket/fallback

$ ifconfig wlan0 up

$ iwconfig wlan0 essid "mySSID"
Error for wireless request "Set ESSID" (8B1A) :
    SET failed on device wlan0 ; Resource temporarily unavailable.

I've been able to fix this, I believe, by installing the latest stable compat-wireless drivers: http://wireless.kernel.org/en/users/Download/stable/

Aslam,

The problem is with broadband cards NOT wifi can you explain your logic? I am willing to try it but don't want to needlessly compile so I would rather only build an individual module rather than the whole mess..

Thanks,

James

James,

I think my problem may not be the same as the one described in this bug -- I wondered about this after posting, since I saw the same behavior with NM as well as WICD.

Yes, my problem was with the wireless driver (iwlagn). I thought this bug had to do with it because my wireless access point was not getting recognized. Further research led me to the following bugs, which are more relevant -- I learned of the compat-wireless drivers from this comment: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/313854/comments/6

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/348275
https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.24/+bug/193970

HTH.

--aslam

Any updates? I expected this issue to be fixed by now.

Hi!,

I'll buy a Toshiba G450 (yoygo - Spain) and I like that this bug should will be fixed...

Please!, what do you need for fix this problem?

Hello!

I managed to make my AirCard 875 PCMCI modem work with Jaunty somehow.

I used instructions from “/etc/udev/rules.d/README” and post #57 to change probing rules. I put the file from post #57 to “/etc/udev/rules.d/” directory. I renamed the file to “40-nm-probe-modem-capabilities.rules”.

Therefore, NetworkManager (version 0.7.0.100) easily establishes connection after modem hotplugging as well as on system boot or waking up. I did not suffer problems described in post #58.

anyone tried my patch from https://bugs.edge.launchpad.net/ubuntu/+source/network-manager/+bug/360905/comments/67 ?

I tried the patch but I still experience the problem.

I have a Novatel MC950D and I'm running Jaunty on an ASUS 1000 eee PC. If I boot with the stick plugged in, the nm-applet will connect. If I remove the stick and re-plug it, the connection is not re-established. If I don't boot with the stick plugged in Network Manager applet never detects the stick.

This used to work in previous versions.

Alexander, both James and I tried your patch and it didn't work, as stated above.

SUBSYSTEM=="tty", SUBSYSTEMS=="usb", ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="?*", IMPORT{program}="nm-modem-probe --vid 0x$attr{idVendor} --pid 0x$attr{idProduct} --usb-interface $env{NM_MODEM_USB_INTERFACE_NUMBER} --driver $env{NM_MODEM_DRIVER} --delay 5000 --export $tempnode", GOTO="nm_modem_probe_end"

please add that line before the other one with the nm-modem-probe ... this should give your modems more time.

sorry ...use 0x1199 as the idVendor there

sorry2: just 1199 ;)

I had already tried delays of up to 6000 msec, but that didn't work, and wouldn't be expected to, since the maximum delay is 3000.

$ /lib/udev/nm-modem-probe --help
Usage: probe-modem [options] <device>
 --export export key/value pairs
 --delay <ms> delay before probing (1 to 3000 ms inclusive)
...

But I'll try again anyway.

Does not work, as expected.

Further, it works with two 1000 msec probes, but not one 3000 msec one (and obviously 5000 is out, since it's not supported by nm-modem-probe).

still an issue in todays dailes? https://edge.launchpad.net/~network-manager/+archive/trunk ... we had some aircard landings ... so maybe that helps.

booting in to the 9.10 Live CD my card works again. I am doing a dist
upgrade now will know in a few hours if it works after upgrade.

On Wed, Oct 14, 2009 at 8:54 AM, Alexander Sack <email address hidden> wrote:

> still an issue in todays dailes? https://edge.launchpad.net/~network-
> manager/+archive/trunk<https://edge.launchpad.net/%7Enetwork-%0Amanager/+archive/trunk>... we had some aircard landings ... so maybe
> that helps.
>
> --
> Network-Manager not seeing broadband card
> https://bugs.launchpad.net/bugs/360905
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
James Finstrom
http://dontcallmyboss.com/projects
http://blog.dontcallmyboss.com
http://twitter.com/geek3point0

I have done a dist-upgrade to 9.10 and my card now hot plugs and shows up

On 10/14/09, JAMES FINSTROM <email address hidden> wrote:
> booting in to the 9.10 Live CD my card works again. I am doing a dist
> upgrade now will know in a few hours if it works after upgrade.
>
> On Wed, Oct 14, 2009 at 8:54 AM, Alexander Sack <email address hidden> wrote:
>
>> still an issue in todays dailes? https://edge.launchpad.net/~network-
>> manager/+archive/trunk<https://edge.launchpad.net/%7Enetwork-%0Amanager/+archive/trunk>...
>> we had some aircard landings ... so maybe
>> that helps.
>>
>> --
>> Network-Manager not seeing broadband card
>> https://bugs.launchpad.net/bugs/360905
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>
>
> --
> James Finstrom
> http://dontcallmyboss.com/projects
> http://blog.dontcallmyboss.com
> http://twitter.com/geek3point0
>

--
James Finstrom
http://dontcallmyboss.com/projects
http://blog.dontcallmyboss.com
http://twitter.com/geek3point0

thx ... not sure what to do for jaunty task. resetting to triaged.

Hello,

My Sierra Wireless modem worked fine in 8.10 but disappeared in 9.04. The patch procedure at https://bugs.launchpad.net/ubuntu/jaunty/+source/network-manager/+bug/360905/comments/8 repaired this issue. I wish the fix were distriibuted to 8.10 users without requiring a manual patch.

Sincerely,
-daniel

Jaunty reached end-of-life on 23 October 2010, so this bug won't be fixed in that version of Ubuntu. The bug is fixed in later versions.