After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 632022 - Japanese E-mobile D26HW (carrier customized Huawei UMTS modem) fails to connect
Japanese E-mobile D26HW (carrier customized Huawei UMTS modem) fails to connect
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: API
0.8.x
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2010-10-13 01:09 UTC by Rolf Leggewie
Modified: 2010-12-05 03:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
debug log (11.96 KB, text/plain)
2010-10-15 05:40 UTC, Rolf Leggewie
Details

Description Rolf Leggewie 2010-10-13 01:09:23 UTC
https://bugs.launchpad.net/bugs/574192

Lucid introduced a regression either in gnome-ppp, wvdial or one of the packages that these two use for dialing. I have a D26HW USB which is a carrier-customized CDMA USB modem (incorrectly identified by lsubs as E220). Mine works with the Japanese CDMA network from emobile.jp.

current status:
gnome-ppp works
network-manager still doesn't

Some people suggested this may be a problem in hal-info but a provided patch did not resolve the issue.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-ppp 0.3.23-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Mon May 3 07:08:47 2010
EcryptfsInUse: Yes
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LC_MESSAGES=C
 LANG=de_DE.utf8
 LANGUAGE=en_US:en:de_DE
SourcePackage: gnome-ppp
Comment 1 Rolf Leggewie 2010-10-13 01:15:50 UTC
My apologies.  This bug has a history that evolved over time.  Gnome-ppp used to work fine in Karmic.  Initially neither gnome-ppp nor network-manager worked in lucid.  The current situation is that gnome-ppp again successfully establishes a connection, but NM still doesn't.

proposed patch: https://bugs.launchpad.net/ubuntu/+source/gnome-ppp/+bug/574192/comments/11
NM failure log: https://bugs.launchpad.net/ubuntu/+source/gnome-ppp/+bug/574192/comments/10
Comment 2 Rolf Leggewie 2010-10-13 01:23:40 UTC
I think this is the relevant entry from lshal.  I hope you can decipher it ;-)

udi = '/org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial'
  info.linux.driver = 'usb'  (string)
  info.parent = '/org/freedesktop/Hal/devices/usb_device_1d6b_2_0000_00_1d_7'  (string)
  info.product = 'E220 HSDPA Modem / E270 HSDPA/HSUPA Modem'  (string)
  info.subsystem = 'usb_device'  (string)
  info.udi = '/org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial'  (string)
  info.vendor = 'Huawei Technologies Co., Ltd.'  (string)
  linux.device_file = '/dev/bus/usb/001/017'  (string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'usb'  (string)
  linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3'  (string)
  usb_device.bus_number = 1  (0x1)  (int)
  usb_device.can_wake_up = true  (bool)
  usb_device.configuration = 'Huawei   Configuration'  (string)
  usb_device.configuration_value = 1  (0x1)  (int)
  usb_device.device_class = 0  (0x0)  (int)
  usb_device.device_protocol = 0  (0x0)  (int)
  usb_device.device_revision_bcd = 0  (0x0)  (int)
  usb_device.device_subclass = 0  (0x0)  (int)
  usb_device.is_self_powered = true  (bool)
  usb_device.linux.device_number = 17  (0x11)  (int)
  usb_device.linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3'  (string)
  usb_device.max_power = 500  (0x1f4)  (int)
  usb_device.num_configurations = 1  (0x1)  (int)
  usb_device.num_interfaces = 3  (0x3)  (int)
  usb_device.num_ports = 0  (0x0)  (int)
  usb_device.product = 'E220 HSDPA Modem / E270 HSDPA/HSUPA Modem'  (string)
  usb_device.product_id = 4099  (0x1003)  (int)
  usb_device.speed = 480.0 (480) (double)
  usb_device.vendor = 'Huawei Technologies Co., Ltd.'  (string)
  usb_device.vendor_id = 4817  (0x12d1)  (int)
  usb_device.version = 2.0 (2) (double)
Comment 3 Dan Williams 2010-10-15 03:12:27 UTC
The suggested fix isn't applicable because it's for HAL-based systems, which was NetworkManager 0.7.  Most of the time NM uses udev probing for the device.  Given that the logs in that bug report talk about ModemManager, the commenter there is using NM 0.8.

So, we need to get the ModemManager debug logs.  To do that:

1) stop NetworkManager
2) killall -TERM modem-manager
3) unplug the 3G stick
4) /usr/sbin/modem-manager --debug
5) in another terminal, start NetworkManager again
6) plug the 3G stick in and try to connect
7) then attach the modem-manager debug output to this bug

and we'll diagnose what the issue is.  Thanks!
Comment 4 Rolf Leggewie 2010-10-15 05:40:10 UTC
Created attachment 172407 [details]
debug log

here is the requested information
Comment 5 Rolf Leggewie 2010-10-23 17:41:26 UTC
This stick now works correctly in Maverick.  I tried backporting the maverick modemmanager package to lucid to see if that would enable the stick in lucid as well.  Unfortunately, it didn't.  Somebody more knowledgeable than me please help in finding out what needs to be backported to lucid for this to work.
Comment 6 Rolf Leggewie 2010-12-05 03:25:55 UTC
https://bugs.launchpad.net/ubuntu/+source/gnome-ppp/+bug/574192/comments/18

I updated both the modemmanager and the usb-modeswitch package to the maverick versions and now the stick works even in lucid.

Thanks, guys.
Comment 7 Rolf Leggewie 2010-12-05 03:26:48 UTC
FWIW, the stick works OOTB in Maverick