On Aug 6, 2012 2:54 PM, "Aleksander Morgado" wrote:
>
>
> More or less, yes. You have the 'mmcli' utility in that branch,
though,
> so you can skip writing raw dbus-send commands and play with the cli
> instead, like this (assuming only one modem connected, so index 0):
>
> >>>
On Jul 31, 2012 10:03 AM, wrote:
>
> Hi,
>
> >
> > Looking at the patched code, the most likely cause I think is that I
have
> > disabled PIN check at the SIM card and then the patch code that hooks
into
> > the PIN dialog is never executed.
>
> [[GR]] That's right. As far as I see nm-applet will
I have a Pantech 290 that I'm determined to get working with the
qmi_wwan driver. I have the module, and it creates a wwan interface
when the modem is plugged in; now I'm looking at ModemManager. I
started compiling the qmi-support branch, but it looks like I'll have
to go get some dependencies. Be
On Aug 29, 2012 1:48 PM, "Shawn J. Goff" wrote:
>
> I have a Pantech 290 that I'm determined to get working with the
> qmi_wwan driver. I have the module, and it creates a wwan interface
> when the modem is plugged in; now I'm looking at ModemManager. I
> started compiling the qmi-support branch,
On Wed 29 Aug 2012 08:14:10 AM EDT, Marius Kotsbak wrote:
Maybe nobody have tried it yet. It would be useful to get the test
results to see it there are missing parts.
I'll get working on it, then.
Also, even though I had success using mmcli to connect semimaually, it
might be easier/better
>
>> Maybe nobody have tried it yet. It would be useful to get the test
>> results to see it there are missing parts.
>>
> I'll get working on it, then.
>
>> Also, even though I had success using mmcli to connect semimaually, it
>> might be easier/better to connect using libqmi support scripts.
>
>> More or less, yes. You have the 'mmcli' utility in that branch,
> though,
>> so you can skip writing raw dbus-send commands and play with the cli
>> instead, like this (assuming only one modem connected, so index 0):
>>
>> Show modem info and status:
>> $> mmcli
>> Attached is a patch which makes the after-sim-unlock step get run also
>> when PIN request is disabled. Could you give it a try with your use case
>> and a proper implementation of the modem_after_sim_unlock() callback? I
>> would actually try the ZTE way (running +CPMS? retries), as IIRC you
>
On 08/28/2012 07:36 PM, Tristan Stevens wrote:
> I'm now running 0.5.999 as downloaded
> from https://launchpad.net/ubuntu/quantal/amd64/modemmanager however am
> still seeing the same problem. Logs below:
>
> Aug 28 18:27:33 hostname-1 modem-manager[1065]:
> [mm-modem-huawei-gsm.c:712] handle_
On Tuesday, 21 August, 2012 10:10:11 cac...@quantum-sci.com wrote:
>
> Just had the failure again, and still no supplicant log.
>
>
> On Tuesday, 21 August, 2012 07:53:26 cac...@quantum-sci.com wrote:
> > On Monday, 20 August, 2012 09:54:13 you wrote:
> > > > Not enough of the log? I wonder wha
Hey everyone,
So, the 'qmi-support' was just merged to git master, which means that
you'll now need libqmi git master [1] to compile ModemManager. All new
QMI-related development will now go into git master directly.
Cheers!
[1] http://cgit.freedesktop.org/libqmi
--
Aleksander
Den 29. aug. 2012 15:52, skrev Aleksander Morgado:
I actually got the connection up now using the method above (mmcli +
ifup wwan0) so it seems to be close to functional now.
Regarding connectivity; QMI-powered MM is fully functional. Missing
things include messaging and location, which are sc
On a related note, since ModemManager already uses AT+CRSM to read
ICCID and operator name/ID, I wonder if it makes sense to
"AT+CRSM=176,28423,0,0,9" instead of AT+CIMI for reading IMSI, or use
it as a fallback solution if AT+CIMI fails or is not supported by a
modem.
At least on one modem I have
Aleksander Morgado writes:
> So, the 'qmi-support' was just merged to git master, which means that
> you'll now need libqmi git master [1] to compile ModemManager. All new
> QMI-related development will now go into git master directly.
Wow, great work!
I noticed that you even support multiple b
>>> I actually got the connection up now using the method above (mmcli +
>>> ifup wwan0) so it seems to be close to functional now.
>>>
>> Regarding connectivity; QMI-powered MM is fully functional. Missing
>> things include messaging and location, which are scheduled for next
>> weeks.
>
> Okay.
> On a related note, since ModemManager already uses AT+CRSM to read
> ICCID and operator name/ID, I wonder if it makes sense to
> "AT+CRSM=176,28423,0,0,9" instead of AT+CIMI for reading IMSI, or use
> it as a fallback solution if AT+CIMI fails or is not supported by a
> modem.
>
> At least on o
>> So, the 'qmi-support' was just merged to git master, which means that
>> you'll now need libqmi git master [1] to compile ModemManager. All new
>> QMI-related development will now go into git master directly.
>
> Wow, great work!
>
> I noticed that you even support multiple bearers now, allow
17 matches
Mail list logo
