Netgear 340u

[Noah Taber]

I don't think I am able to communicate through the serial interfaces of the
340u for some reason, thus I don't think I can issue ATi commands.

I have tried minicom and gcom (or comgt now) to ttyUSB0, ttyUSB1 and
ttyUSB2.  None of the tty interfaces respond.  There is no output with
minicom.  Below is the output with comgt:

$ sudo comgt -d /dev/ttyUSB2
 ***SIM ERROR***
Check device port configuration.
Check SIM is inserted
Test SIM in a mobile phone?

What are your thoughts regarding this?


On Sun, Apr 27, 2014 at 8:38 PM, Bjørn Mork <bjorn at mork.no> wrote:

> Noah Taber <noahtaber at gmail.com> writes:
>
> > I will try the command later tonight.
> >
> > I'm not sure if this is clear, but the device I'm trying to make this
> work
> > on is a raspberry pi, if that matters.  Do you think that will make a
> > difference?
>
> No, that won't make any difference.  The device config is presented by
> the device firmware.  But if you have a Linux PC around, then
> replicating the problem on that would be an easy and somewhat useful
> test.  There *are* issues with the raspberry pi usb host controller
> driver.  I don't think this should matter (you are obviously talking
> just fine to the modem), but it wouldn't hurt to completely eliminate
> the possibility.
>
> Regarding the "missing" second config: All these modern Sierra devices
> can be configured for a number of different device layouts, using 1 or 2
> configurations. Such changes are non-volatile. I agree that it is
> surprising to see such a new device without any MBIM configuration by
> default, but this is really the choice of whoever you bought this device
> from.  Maybe they didn't want Windows8 support?
>
> Anyway, none of this should conflict with QMI support.  And are
> definitely talking QMI to the modem.  The modem auto-connecting looks
> like the most likely explanation so far, and your
>  "qmi-network /dev/cdc-wdm0 status"
> test shows that it is in fact already connected.
>
> So what we have to figure out is why it doesn't respond to DHCP. It
> would have been interesting to see the output of a QMI_WDS "Get Current
> Settings" request, but unfortunately that isn't implemented in the
> qmicli yet...
>
>
>
> Bjørn
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/libqmi-devel/attachments/20140427/61cf7cb3/attachment.html>