0.7 "New" 3G config dialogue broke my Huawei E220 support

[Peter]

Binary package hint: network-manager

EDIT: Been able to get networkmanager to work now, error lies in pppd access rights for non-admin users, i.e. non-root users are unable to start a pppd connection on this build of ubuntu. Problem solved by chmod o+rx /usr/sbin/pppd and /etc/ppp/*

Been testing ut intrepid 8.10 on my asus eee, and just last week got networkmanager to work with my huawei e220.
The new version has a popup dialogue asking for national operator. (Netcom in Norway, in my case)
After selecting NetCom I am no longer able to get online with the E220 adapter. Trying to connect only returns "Connection terminated" after a few seconds.

I've tried to delete the netcom profile generated, make a new one, remove all settings etc, but it just doesn't connect any more.

Now using:

Ubuntu 8.10 with all updates as of oct 27.

NetworkManager
Installed: 0.7~~svn20081018t105859-0ubuntu1

[Alexander Sack (asac)]

we need your complete syslog taken after reproducing the failed connect attempt. please attach here.

[Peter (piroco)]

Here is my syslog from the failed connection attempts yesterday.

Oct 27 01:04:28 eeepeter NetworkManager: <info> Activation (ttyUSB0) starting connection 'Netcom'
Oct 27 01:04:28 eeepeter NetworkManager: <info> (ttyUSB0): device state change: 3 -> 4
Oct 27 01:04:28 eeepeter NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 27 01:04:28 eeepeter NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Oct 27 01:04:28 eeepeter NetworkManager: <debug> [1225065868.468136] nm_serial_device_open(): (ttyUSB0) opening device...
Oct 27 01:04:28 eeepeter NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Oct 27 01:04:39 eeepeter NetworkManager: <WARN> init_done(): Modem initialization failed
Oct 27 01:04:39 eeepeter NetworkManager: <info> (ttyUSB0): device state change: 4 -> 9
Oct 27 01:04:39 eeepeter NetworkManager: <debug> [1225065879.011993] nm_serial_device_close(): Closing device 'ttyUSB0'
Oct 27 01:04:39 eeepeter NetworkManager: <info> Marking connection 'Netcom' invalid.
Oct 27 01:04:39 eeepeter NetworkManager: <info> Activation (ttyUSB0) failed.
Oct 27 01:04:39 eeepeter NetworkManager: <info> (ttyUSB0): device state change: 9 -> 3
Oct 27 01:04:39 eeepeter NetworkManager: <info> (ttyUSB0): deactivating device (reason: 0).
Oct 27 01:04:39 eeepeter NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Oct 27 01:04:39 eeepeter NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed
Oct 27 01:05:20 eeepeter NetworkManager: <info> Activation (ttyUSB0) starting connection 'Netcom'
Oct 27 01:05:20 eeepeter NetworkManager: <info> (ttyUSB0): device state change: 3 -> 4
Oct 27 01:05:20 eeepeter NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 27 01:05:20 eeepeter NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Oct 27 01:05:20 eeepeter NetworkManager: <debug> [1225065920.528351] nm_serial_device_open(): (ttyUSB0) opening device...
Oct 27 01:05:20 eeepeter NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Oct 27 01:05:31 eeepeter NetworkManager: <WARN> init_done(): Modem initialization failed
Oct 27 01:05:31 eeepeter NetworkManager: <info> (ttyUSB0): device state change: 4 -> 9
Oct 27 01:05:31 eeepeter NetworkManager: <debug> [1225065931.001953] nm_serial_device_close(): Closing device 'ttyUSB0'
Oct 27 01:05:31 eeepeter NetworkManager: <info> Marking connection 'Netcom' invalid.
Oct 27 01:05:31 eeepeter NetworkManager: <info> Activation (ttyUSB0) failed.
Oct 27 01:05:31 eeepeter NetworkManager: <info> (ttyUSB0): device state change: 9 -> 3
Oct 27 01:05:31 eeepeter NetworkManager: <info> (ttyUSB0): deactivating device (reason: 0).
Oct 27 01:05:31 eeepeter NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Oct 27 01:05:31 eeepeter NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed
Oct 27 01:05:35 eeepeter NetworkManager: <info> Activation (ttyUSB0) ...

[Alexander Sack (asac)]

did you try to fill in your pin etc. in the connection editor? If that doesn't help, please remove the current connection from connection editor, then remove the libmbca0 package and plug in your device again.

Now there should be a "auto GSM" connection in the network-manager tray applet. Try that. Does that work better?

[Peter (piroco)]

I tried to fill in my PIN, but there seems to be two problems with it:

1) If connection is a "System setting" (i.e. system-wide) network-manager refuses to remember PIN.

2) If connection is NOT "system setting", network-manager remembers PIN but is unable to unlock device (E220)

I can now get NM to work, but only after using wvdial first to unlock PIN. If I use wvdial to pin-unlock, I can then go on to connect via networkmanager and get a 3G connection running.

I have tried repeatedly to remove and re-install the network profile completely, to no avail.

[Alexander Sack (asac)]

ok, please try:

1. remove device
2. remove libmbca0 package
3. remove your current connection in connection-editor
4. restart
5. plugin your device and use the use the "auto connection" for your mobile device.

Does that work better?

[Peter (piroco)]

OK, tried removing libmbca0, delete the Netcom profile and reboot - made no difference.

Able to connect with auto connection profile, but only after I unlock PIN via wvdial first. Seems NM still is not able to unlock my E220 PIN on its own.

[Alexander Sack (asac)]

please stop NM:

sudo /etc/init.d/NetworkManager stop

then start it on the terminal like:

NM_SERIAL_DEBUG=1 sudo NetworkManager --no-daemon

please reproduce and attach the output here.

[Peter (piroco)]

OK

Here is the output after just connecting E220 without unlocking PIN first, trying to connect:

NetworkManager: <info> ttyUSB0: driver is 'option'.
NetworkManager: <debug> [1225549631.683082] setup_monitor_device(): No monitoring udi provided
NetworkManager: <info> Found new Modem device 'ttyUSB0'.
NetworkManager: <info> (ttyUSB0): exported as /org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0
NetworkManager: <info> (ttyUSB0): device state change: 1 -> 2
NetworkManager: <info> (ttyUSB0): deactivating device (reason: 2).
NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed
NetworkManager: <info> (ttyUSB0): device state change: 2 -> 3
NetworkManager: <info> Activation (ttyUSB0) starting connection 'Auto Mobile Broadband (GSM) connection'
NetworkManager: <info> (ttyUSB0): device state change: 3 -> 4
NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <debug> [1225549635.879568] nm_serial_device_open(): (ttyUSB0) opening device...
NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <WARN> init_done(): Modem initialization failed
NetworkManager: <info> (ttyUSB0): device state change: 4 -> 9
NetworkManager: <debug> [1225549647.004562] nm_serial_device_close(): Closing device 'ttyUSB0'
NetworkManager: <info> Marking connection 'Auto Mobile Broadband (GSM) connection' invalid.
NetworkManager: <info> Activation (ttyUSB0) failed.
NetworkManager: <info> (ttyUSB0): device state change: 9 -> 3
NetworkManager: <info> (ttyUSB0): deactivating device (reason: 0).
NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed

Doing a wvdial pin - to unlock PIN. Trying to connect again:

NetworkManager: <info> Activation (ttyUSB0) starting connection 'Auto Mobile Broadband (GSM) connection'
NetworkManager: <info> (ttyUSB0): device state change: 3 -> 4
NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
NetworkManager: <debug> [1225549678.328756] nm_serial_device_open(): (ttyUSB0) opening device...
NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
NetworkManager: <WARN> init_done(): Modem initialization failed
NetworkManager: <info> (ttyUSB0): device state change: 4 -> 9
NetworkManager: <debug> [1225549689.004746] nm_serial_device_close(): Closing device 'ttyUSB0'
NetworkManager: <info> Marking connection 'Auto Mobile Broadband (GSM) connection' invalid.
NetworkManager: <info> Activation (ttyUSB0) failed.
NetworkManager: <info> (ttyUSB0): device state change: 9 -> 3
NetworkManager: <info> (ttyUSB0): deactivating device (reason: 0).
NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion...

[Alexander Sack (asac)]

hmm .. somehow the serial debug didnt work. wierd. there should be more stuff from modem communication.

[Alexander Sack (asac)]

ok, please do this instead:

# become root
sudo su

#now run like above:
NM_SERIAL_DEBUG=1 NetworkManager --no-daemon 2>&1 | tee /tmp/nm-serial.txt

then attach the nm-serial.txt (there should be quite a bunch more output when trying to dial).

[Peter (piroco)]

OK.

Here is the nm-serial.txt

Tried first to connect E220 and login, did not work. Then deleted auto gsm profile and created a new one, wrote PIN code in the profile and tried to connect. Didn't work. Then did wvdial pin to unlock pin and tried to connect, worked on second attempt. (First fail may be due to slightly poor coverage indoors where I am now)

[Alexander Sack (asac)]

so what command does wvdial send when you do the pin stuff there?

[Peter (piroco)]

the command 'wvdial pin' simply unlocks the device, this is the command used: (my pin replaced with nnnn)

[Dialer pin]
Modem = /dev/ttyUSB0
Baud = 460800
Init1 =AT+Cpin=nnnn

[lesve (just-bug1)]

It is possible to run the above "wvdial pin" through udev. It works for me.

The udev rule should look like: (Called /etc/udev/rules.d/86-telia.rules)

ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="1001", RUN+="/usr/bin/wvdial pin"

Maybe idVendor and/or idProduct has to be changed

                      Regards

[Peter (piroco)]

Thanks for the tip. I'll give it a try. It doesn't solve the underlying problem though, namely that NM 0.7 still seems to have some quirks that needs ironing out in PIN handling. I can get online so it's just a minor annoyance, I'll try your tip in the mean time.

[HenrikAn (henrikan)]

I can confirm Peter:s problem with the PIN code. And judging from the amount of questions about network manager and 3G on the swedish forum I know we are not the only ones.
But I don't know if it has anything to do with the original access right problems? Maybe it should be a separate bug?

[Alexander Sack (asac)]

looking at the log this seems to be a dupe of bug 290177 ... i attached a patch for that issue there. Please test.