does not recognize modem "GBC PL 68 Chinese bird" mobile broadband network

Bug #490800 reported by Zico Rafael
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
modemmanager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubuntuone-client

tigo modem "GBC PL 68" recognizes it as USB memory, but not detected as a modem. as I do to configure, so you can explore the Internet with this device?.

I have little knowledge about programming, try installing the files "wvdial.conf and usb_modeswitch.conf" in / etc and "binary file and the file usb_modeswitch initmodem.sh in" in / sbin / usr but failed. (web: http://luisalvarado.blogspot.com/2009/04/configurando-el-modem-tigo-gbc-en.html)

en la terminal, con el comando lsusb, sigue apareciendo "Bus 001 Device 003: ID 1c9e:f000 "

It is for the mobile broadband network TIGO Bolivia (HPDSA, UMTS, EDGE, GPRS). help

ProblemType: Bug
.home.pc..cache.ubuntuone.log.syncdaemon.exceptions.log:

.home.pc..config.ubuntuone.ubuntuone.client.conf:
 [ubuntuone]
 bookmarked = True
 connected = True
 connect = 1
 show_applet = 1
Architecture: i386
CheckboxSubmission: 7954c5b6b43e807f210e07f90851d336
CheckboxSystem: b62ae224500b03a9fc2c9b6caf3feb14
Date: Tue Dec 1 07:55:52 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
Package: ubuntuone-client 1.0.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: ubuntuone-client
Tags: ubuntu-unr
Uname: Linux 2.6.31-15-generic i686
XsessionErrors:
 (gnome-settings-daemon:1968): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2068): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2106): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Zico Rafael (zlc-ken) wrote :
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
visibility: private → public
Revision history for this message
Joshua Hoover (joshuahoover) wrote :

Hi Zico,

This doesn't appear to be an Ubuntu One related bug. I'm going to set it to a more appropriate package where I think you might get better help.

Thank you,

Joshua

Changed in ubuntuone-client (Ubuntu):
status: New → Invalid
Revision history for this message
Josua Dietze (digidietze) wrote :

Zico,

if your device did not switch to modem mode, it's not ModemManager's fault. This is rather an "udev" issue. In Ubuntu, there is not yet a straightforward way to handle the various (and quickly multiplying) switching devices.

To get your modem switched, you need to adapt the "/etc/usb_modeswitch.conf" file. In fact, you can delete everything else from it and just add these lines:
-snip-----------------------------
DefaultVendor= 0x1c9e
DefaultProduct= 0xf000

TargetVendor= 0x1c9e
TargetProduct= 0x9603

MessageContent="55534243123456788000000080000606f50402527000000000000000000000"
-snip-----------------------------

You'll find this entry in the current version of the config file on
http://www.draisberghof.de/usb_modeswitch

Revision history for this message
Dan Williams (dcbw) wrote :

Please email me the contents of the fake driver CD *before* you use usb_modeswitch to switch the device to modem mode. I need the Windows driver to extract the .INF files and make sure that the correct serial port is used for communication. Please email to:

dcbw at redhat dot com

(replace the "at" and "dot" with @ and . of course)

Revision history for this message
Josua Dietze (digidietze) wrote :

In all cases that I encountered so far, the correct serial port - after switching - is the one that is assigned to an interface with an endpoint that provides the "interrupt transfer" type.

This is rather easy to check in usbfs or with libusb.

Until there is no case to falsify that empirical deduction, it's probably easier to rely on this than maintaining an array of modem models with their respective communication port.

no longer affects: ubuntuone-client (Ubuntu)
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.