** Changed in: network-manager
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/290177
Title:
[huawei/option] NM 0.7: GSM connections won't work with PIN code
** Changed in: network-manager
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/290177
Title:
[huawei/option] NM 0.7: GSM connections won't work with PIN code
ZTE MF628 3G modem doesn't connect from network-manager applet until I disable
PIN code in SIM card.
Network manager applet doesn't ask PIN code at all :(
** Also affects: baltix
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
This only affect sticks where the stick won't respond to AT commands
(identifying itself as a GSM modem) before a PIN has been supplied. In
that case network-manager doesn't detect there is a GSM modem connected
(modem-manager send AT commands to check if it is a GSM modem and
doesn't get the
Seems like this affects all Sticks? Got the same issue with 2 3G usb
sticks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/290177
Title:
[huawei/option] NM 0.7: GSM connections won't work with PIN
** Tags added: patch-needs-work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/290177
Title:
[huawei/option] NM 0.7: GSM connections won't work with PIN code
protected modems - despite having
Hello.
I got a Huawei E620 and using Natty '11.04', and I still got this issue
:(
modem-manager[5728]: info [1296952772.346647] [mm-serial-port.c:702]
mm_serial_port_open(): (ttyUSB0) opening serial port...
modem-manager[5728]: debug [1296952772.349365] [mm-serial-port.c:764]
** Bug watch added: GNOME Bug Tracker #641637
https://bugzilla.gnome.org/show_bug.cgi?id=641637
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=641637
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Changed in: network-manager
Status: Unknown = New
** Changed in: network-manager
Importance: Unknown = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/290177
Title:
[huawei/option]
I just did so (see https://bugs.launchpad.net/bugs/368325).
Thank you for your advice.
gabriela
--
[huawei/option] NM 0.7: GSM connections won't work with PIN code protected
modems - despite having supplied the correct PIN for the connection in
nm-connection-editor
Gabriela, Thank you for your comment, but according to your log, your
modem uses the hso driver, while as this bug is for huawei/option based
modems.
To get your issue reported, you will need to open a new bug report. For
clarity's sake, please also include a serial log, as described in
I'm using an Asus EeePC 1000H and am trying to use my Option Icon 225
stick (got this by Orange Switzerland). I seem to encounter the same
problems, but on a brand new installed and completely updated Jaunty
Jackalope (9.04).
When I first connect the stick, some kind of wizard appears, which lets
Alexander,
Please can you create a different PPA repository for people with this
issue?
We will never know if this patch may stop working other modem if it
won't be released.
--
[huawei/option] NM 0.7: GSM connections won't work with PIN code protected
modems - despite having supplied the
The patch is not good enough as it add tweaks for specific modems to
code used for all modems. risk that other modems break is also there.
Unlikely we can fix that in intrepid, but once we have modemmanager in
jaunty i can provide backports aka PPA builds for that. modemmanager
allows to use
ok. i moved martin's issue to bug 303142 3G [Option] some modems take a
while time to register on network (CREG)
--
[huawei/option] NM 0.7: GSM connections won't work with PIN code protected
modems - despite having supplied the correct PIN for the connection in
nm-connection-editor
Can this patch be proposed to hardy-updates for testing? Or become
available in a ppa so that more can test it out and see if it breaks
other dongles?
--
[huawei/option] NM 0.7: GSM connections won't work with PIN code protected
modems - despite having supplied the correct PIN for the
Eddi: The patch works fine on my 32 bit computer.
--
[huawei/option] NM 0.7: GSM connections won't work with PIN code protected
modems - despite having supplied the correct PIN for the connection in
nm-connection-editor
https://bugs.launchpad.net/bugs/290177
You received this bug notification
The problem now isn't with our dongle.
Other dongle that worked before, may stop working after my patch.
--
[huawei/option] NM 0.7: GSM connections won't work with PIN code protected
modems - despite having supplied the correct PIN for the connection in
nm-connection-editor
Alexander,
do you think my patch can be incorporated into your ppa tree?
--
[huawei/option] NM 0.7: GSM connections won't work with PIN code protected
modems - despite having supplied the correct PIN for the connection in
nm-connection-editor
https://bugs.launchpad.net/bugs/290177
You
I'd really prefer not to build it myself, as I'm using NM on an Asus EEE
with limited disk space. If this patch is solving the problem, when can
it be incorporated in a new build/package that I can download through
apt-get?
--
[huawei/option] NM 0.7: GSM connections won't work with PIN code
@Eddi: I'd love to try your packages, but I'm running 32-bit... Mind to
share how you built them after applying the patch (which I have
done...)? Thanks!
@Martin: The bug you are experiencing seem not to be the same as the one
that Eddi and I are experiencing. Could you please file a separate bug
I don't know how to build package for 32bit under 64 bit architecture...
however you can build them yourself
terminal
# sudo apt-get build-dep network-manager
# mkdir src
# cd src
# apt-get source network-manager
# cd network-manager-0.7~~svn20081018t105859/
# cd src
# wget
** Attachment added: nm-serial-fail.txt
http://launchpadlibrarian.net/19428788/nm-serial-fail.txt
--
[huawei/option] NM 0.7: GSM connections won't work with PIN code protected
modems - despite having supplied the correct PIN for the connection in
nm-connection-editor
sorry for duble post... this is my log...
the success happened after:
gcom -d /dev/ttyUSB1
I haven't tested yet the supplied patch. But it shouldn't solve:
minicom
AT
OK
ATZ E0 V1 X4 C1 +FCLASS=0
ERROR
ATZ E0
ERROR
AT V1
ERROR
AT X4
ERROR
AT C1
ERROR
AT +FCLASS0
ERROR
ATZ
OK
AT+CPIN=1234
OK
I've prepared a patch for my problem, but it needs regressions with
other gsm modem.
For amd64 binary package
http://usa.dpeddi.com/nm/libnm-glib0_0.7~~svn20081018t105859-0ubuntu2~nm4_amd64.deb
http://usa.dpeddi.com/nm/libnm-util-dev_0.7~~svn20081018t105859-0ubuntu2~nm4_amd64.deb
please dont post anything here without trying the patch. Thanks!
--
[huawei/option] NM 0.7: GSM connections won't work with PIN code protected
modems - despite having supplied the correct PIN for the connection in
nm-connection-editor
https://bugs.launchpad.net/bugs/290177
You received
Sorry, Alexander, but as you can see from our serial debug logs, me and
Martin are not experiencing the same problem, and I highly doubt that a
patch to schedule_automatic_registration_again() would affect me, since
I am not even coming that far.
Of course, I'll still try the patch - although I
given that the patch worked for martin i tentatively start the SRU
procedure on this bug.
** Changed in: network-manager (Ubuntu)
Importance: High = Undecided
** Changed in: network-manager (Ubuntu)
Importance: Undecided = High
** Changed in: network-manager (Ubuntu)
Importance: High =
For me, network manager doesn't even seem to detect that a PIN secret is
needed:
Nov 3 23:17:50 motin-xps NetworkManager: info Activation (ttyUSB1) starting
connection '3'
Nov 3 23:17:50 motin-xps NetworkManager: info (ttyUSB1): device state
change: 3 - 4
Nov 3 23:17:50 motin-xps
For me it bails out on the first ATZ command if no PIN has been
supplied. Could we just switch the order at which ATZ and AT+CPIN is
sent to the device?
Using 'option' driver with the following device btw: 413c:8138 Dell
Computer Corp. Wireless 5520 Voda I Mobile Broadband (3G HSDPA) Minicard
30 matches
Mail list logo
