NetworkManager 0.7 cannot use E220 anymore

Bug #278890 reported by Elmit
6
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: network-manager

I use Ubuntu 8.04 on an EeePC.
In order to use ALSO the 3G modem E220 I switched to NetworkManager 0.7.
Several problems were corrected/re-introduced with several updates.

Latest version (updated around Oct 4):
1. can connect to wireless using the wireless key. IT REMEMBERS THE KEY AGAIN! (hurray!)
2. it can connect via ethernet as well
3. when connected I can also OPEN APPLICATIONS again! (hurray!)
4. if I try to connect via E220, the connection times out and I have no connection (coming back to hit connect)
I tried to use at the same location the internal Xandros and it connects immediately, means there is no network problem.

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

how did you create your 3g connection setting? Did you use the new connection wizard? Consider to try that (e.g. open connection editor and create a new mobile broadband connection after taking care that libmbca0 package is installed).

also please attach your complete lshal output as well as:

  hal-find-by-capability --capability modem

and

  lshal -u `hal-find-by-capability --capability modem`

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Elmit (ronald-elmit) wrote :

I just upgraded to the latest version (downloaded and installed at 0:30 GMT Oct. 7) and it works again!

HOWEVER, it only works if the E220 is plugged in when booting.

If I plug in later, the device will be detected (left mouse click shows me 3 Auto GSM networks with E220, but none can connect)

BTW, how do I know which version I have installed? (rather then pointing to the time I got it)
How can I go back to this version, if the next version is not working?

Below are these two commands, after I rebooted with the E220 attached during boot time and connected with it to the Internet:
hal-find-by-capability --capability modem
/org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0

lshal -u `hal-find-by-capability --capability modem`
udi = '/org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0'
  info.capabilities = {'serial', 'modem'} (string list)
  info.category = 'serial' (string)
  info.parent = '/org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0' (string)
  info.product = 'E220 HSDPA Modem' (string)
  info.udi = '/org/freedesktop/Hal/devices/usb_device_12d1_1003_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:1d.0/usb1/1-2/1-2: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_12d1_1003_noserial_if0' (string)
  serial.port = 0 (0x0) (int)
  serial.type = 'usb' (string)

Revision history for this message
Elmit (ronald-elmit) wrote :

I just installed the newest version (2008 October 10 @ 3:00 am GMT), and I cannot use the E220 anymore, neither during boot time plugged in nor later plugged in.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

could you try to check this with intrepid or jaunty?

Changed in network-manager:
importance: Undecided → Low
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in network-manager:
status: Incomplete → Invalid
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.