Hey,
Thanks Olaf, that's exactly what I've done and it's working perfectly well.
Bests,
E.
Le 25/09/2013 16:40, Olaf Schulz a écrit :
Hi,
I found another option to avoid the problem you observed on
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1169117:
...by adding a file
On 02/10/13 17:05, Kenneth Berland wrote:
NM moves along well until it errors-out with these lines (I think):
Oct 2 07:35:50 ken-x230 ModemManager[1811]: info error: couldn't
start network: QMI protocol error (14): 'CallFailed'
Oct 2 07:35:50 ken-x230 ModemManager[1811]: info call end
Kenneth Berland k...@hero.com writes:
apn=wap.cingular
I don't know anything about ATT services, but Google sent me to this
page: http://www.wireless.att.com/support_static_files/KB/KB41477.html
where wap.cingular is documented as Does not allow tethering (using
phone as a modem) of a handset
On 03/10/13 10:15, Bjørn Mork wrote:
Could very well be that they forbid using that APN with a Sierra
Wireless IMEI.
Really? Why would they do that?
--
Aleksander
___
networkmanager-list mailing list
networkmanager-list@gnome.org
Aleksander Morgado aleksan...@lanedo.com writes:
On 03/10/13 10:15, Bjørn Mork wrote:
Could very well be that they forbid using that APN with a Sierra
Wireless IMEI.
Really? Why would they do that?
To force the APN to be used exclusively with handsets, because the
provided services aren't
That was it: wrong APN. Perhaps MM or NM could be a bit more descriptive
about the problem? I can patch it. Are there any other error you know of
that provide a more verbose reason when encountered? I can follow the
existing pattern, if there is one and add a message regarding the APN.
On Wednesday 25 of September 2013 17:18:35 Jiri Pirko wrote:
Wed, Sep 25, 2013 at 04:46:48PM CEST, d...@gnome.org wrote:
On 09/16/2013 03:28 AM, Jiri Pirko wrote:
Hi, any comments please? I discussed this with jklimes and he seems
happy with it.
Sorry for the delay. Mostly good, and I see
