On Wed, Mar 12, 2014 at 8:30 AM, Marko Myllynen <[email protected]> wrote:
> On 2014-03-10 21:51, Aleksander Morgado wrote:
>> On Mon, Mar 10, 2014 at 7:12 PM, Dan Williams <[email protected]> wrote:
>>>> I've been trying to get a ZTE MF60 3G modem working with MM/NM but even
>>>> though recent updates have provided some progress it's still quite not
>>>> working. It's not explicitly listed in the page of Supported Devices [1]
>>>> so I'm not sure whether there is some fundamental problem with the
>>>> device or is this merely a fixable issue somewhere in the stack.
>>>
>>> Posted an update to the bug, at the moment it looks like the device
>>> simply doesn't respond to the StartNetwork request via QMI.  Some of the
>>> early hotspots are known not to implement QMI well, but I think we'll
>>> want to test with a Gobi 1K (which is also NAS 1.0 and very early QMI)
>>> just to make sure that still works.
>>
>> Yeah, known issue. The MF60 doesn't play well with the WDS service in QMI; 
>> see
>> http://lists.freedesktop.org/archives/libqmi-devel/2012-July/000098.html
>>
>> Quoting Bjørn:
>> "3G connection management is done using the built-in web server.  Does
>> not look like it can be managed by QMI.  But many QMI_NAS and QMI_DMS
>> commands are supported."
>>
>> Anyway, I actually delayed QMI support in the ZTE plugin just because
>> of this device. MM 1.2 now allows QMI for ZTE devices, but we should
>> probably setup that blacklist that we talked about some months ago,
>> for devices like this one.
>
> ok, thanks for the pointer and background information, it looks like
> this is much more "fundamental problem with the device" than "merely a
> fixable issue" then.


Does the modem expose a tty as well? The fallback of course is to make
it use AT+PPP instead of QMI; which is the purpose of the blacklist
suggested here.

-- 
Aleksander
https://aleksander.es
_______________________________________________
networkmanager-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/networkmanager-list

Reply via email to