Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Huawei 3131 with idVendor=12d1, idProduct=14fe
Date: Tue, 12 Jan 2016 10:52:23 -0600	[thread overview]
Message-ID: <56952F47.5070904@gmail.com> (raw)
In-Reply-To: <CADnUhn2vxkMDZrBkTL98BryyOmzPUM=ivceK1ekcV+uLHgKZcQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

Hi Matti,

On 01/12/2016 10:46 AM, matti kaasinen wrote:
>
> Hi Denis,
> 2016-01-12 18:30 GMT+02:00 Denis Kenzior <denkenz@gmail.com
> <mailto:denkenz@gmail.com>>:
>
>
>         activate-context
>         =>
>         Error activating /huawei_0/context1: org.ofono.Error.NotImplemented:
>         Implementation not provided
>
>
>     There is no gprs context driver provided or it failed to setup.  Do
>     you have TUN/TAP in the kernel or kernel module?
>
> It was not loaded, but I modprobed it now manually and got different
> error message:
> Error activating /huawei_1/context1: org.ofono.Error.Failed: Operation
> failed

Please provide the AT command trace.

>
>
>     Please note, that there are two different versions of the Huawei
>     cards supported by oFono.  One uses the "gobi" driver (these are
>     Qualcomm chips).  While the more traditional one uses PPP & the
>     "huawei" driver.
>
>
> I suppose I should edit setup_gobi() and vendor_list() as before in case
> it's "gobi"?

Its a bit more subtle.  Check the logic in udevng.c setup_huawei()

Regards,
-Denis

  reply	other threads:[~2016-01-12 16:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADnUhn1efXRB7fZGkSfsToHH5gxd-tK4OxJxF9MhP334P1Pvcw@mail.gmail.com>
2016-01-11 15:02 ` Huawei 3131 with idVendor=12d1, idProduct=14fe matti kaasinen
2016-01-11 17:18   ` Denis Kenzior
2016-01-11 17:52     ` matti kaasinen
2016-01-12  8:38       ` matti kaasinen
2016-01-12  8:47         ` matti kaasinen
2016-01-12  9:40           ` matti kaasinen
2016-01-12 10:04             ` matti kaasinen
2016-01-12 16:30         ` Denis Kenzior
2016-01-12 16:46           ` matti kaasinen
2016-01-12 16:52             ` Denis Kenzior [this message]
2016-01-12 16:56             ` matti kaasinen
2016-01-12 17:20               ` Denis Kenzior
2016-01-13 10:40                 ` matti kaasinen
2016-01-13 16:04                   ` Denis Kenzior
2016-01-14 10:19                     ` matti kaasinen
2016-01-14 15:32                       ` Denis Kenzior
2016-01-14 15:53                         ` matti kaasinen
2016-01-14 15:55                           ` Denis Kenzior
2016-01-15 10:14                         ` matti kaasinen
2016-01-20 14:47                           ` matti kaasinen
2016-01-20 15:25                             ` =?unknown-8bit?q?Bj=C3=B8rn?= Mork
2016-01-20 17:20                               ` matti kaasinen
2016-01-21  8:05                                 ` matti kaasinen
2016-01-23 20:32                                   ` CedrIc Jehasse
2016-02-24 14:49                                     ` matti kaasinen
2016-01-21 12:56                                 ` matti kaasinen
2016-01-12 19:08             ` =?unknown-8bit?q?Bj=C3=B8rn?= Mork
2016-01-13 16:08               ` Denis Kenzior
2015-12-30 10:31 matti kaasinen
2015-12-31  8:39 ` matti kaasinen
2016-01-04 16:18 ` Denis Kenzior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56952F47.5070904@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox