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
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
https://wi
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
https://bugs.launchpad.net/b
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 corr
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 modem
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
https://b
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 connection
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 this
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 am
** 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
https://bugs.launchpa
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
http://usa.dpeddi
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 b
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
https://bugs.launchp
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: Activation (ttyUSB1) starting
connection '3'
Nov 3 23:17:50 motin-xps NetworkManager: (ttyUSB1): device state
change: 3 -> 4
Nov 3 23:17:50 motin-xps NetworkManager:
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
EAP-
@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 http://launchpadlibrar
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 prote
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 received
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: Activation (ttyUSB1) starting
connection '3'
Nov 3 23:17:50 motin-xps NetworkManager: (ttyUSB1): device state
change: 3 -> 4
Nov 3 23:17:50 motin-xps NetworkManager:
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
EAP-
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 this
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 am
** 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
https://bugs.launchpa
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
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 modem
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 corr
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 received
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 b
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
https://bugs.launchp
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
https://b
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
http://usa.dpeddi
@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 http://launchpadlibrar
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 prote
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 connection
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
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 modem
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 corr
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
https://bugs.launchpad.net/b
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
https://wi
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
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
https://wi
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
https://bugs.launchpad.net/b
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
https://bugs.launchp
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: Activation (ttyUSB1) starting
connection '3'
Nov 3 23:17:50 motin-xps NetworkManager: (ttyUSB1): device state
change: 3 -> 4
Nov 3 23:17:50 motin-xps NetworkManager:
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
EAP-
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 this
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 am
** 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
https://bugs.launchpa
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
http://usa.dpeddi
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
https://b
@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 http://launchpadlibrar
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 prote
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 received
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 b
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 connection
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
https://bugs.launchp
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 modem
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 corr
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: Activation (ttyUSB1) starting
connection '3'
Nov 3 23:17:50 motin-xps NetworkManager: (ttyUSB1): device state
change: 3 -> 4
Nov 3 23:17:50 motin-xps NetworkManager:
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
EAP-
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 this
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 am
** 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
https://bugs.launchpa
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
http://usa.dpeddi
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
https://b
@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 http://launchpadlibrar
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 prote
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 received
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 b
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 connection
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
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
https://bugs.launchpad.net/b
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
https://wi
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
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
https://bugs.launchpad.net/b
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
https://wi
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: Activation (ttyUSB1) starting
connection '3'
Nov 3 23:17:50 motin-xps NetworkManager: (ttyUSB1): device state
change: 3 -> 4
Nov 3 23:17:50 motin-xps NetworkManager:
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
EAP-
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 this
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 am
** 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
https://bugs.launchpa
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
http://usa.dpeddi
@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 http://launchpadlibrar
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 prote
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 received
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 b
1 - 100 of 126 matches
Mail list logo
