Sierra Wireless EM7355
dcbw at redhat.com
Wed Jun 18 06:14:18 PDT 2014
On Wed, 2014-06-18 at 10:38 +0200, Bjørn Mork wrote:
> Erinn Looney-Triggs <erinn.looneytriggs at gmail.com> writes:
> > On 06/17/2014 04:24 PM, Dan Williams wrote:
> >> On Tue, 2014-06-17 at 13:42 -0600, Erinn Looney-Triggs wrote:
> >>> I am having trouble getting this device to work under Fedora 20.
> >>> It is detected on first boot, though in a dual boot environment
> >>> after booting into windows, it is still detected, though not
> >>> configured. However, that is another issue.
> >> Until Bjorn drops some righteous knowledge on us...
> >> Bjorn posted some driver patches for the 7355 which just hit the
> >> 3.14 stable kernel two weeks ago:
> >> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-3.14.y&id=d2c3d4f3bcfd826546cabcc1850b1a14ab2b4749
> >> so make sure you're using the 3.14.5 or later kernel, which is
> >> available in Fedora updates since early June. Can you confirm that
> >> you are using the 3.14.5 or later kernel, and if not, try it after
> >> updating?
> >> Dan
> > Dan,
> > Thanks for the suggestion, I am running against 3.14.7 right now, so
> > no luck there.
> No, that patch doesn't really matter here. It is for qmi_wwan which you
> won't use unless you choose to switch the modem to cfg #1. MBIM is
> supported by the class driver and does not depend on device IDs being
So it's got two configurations, the first one (presumably) for QMI and
the second for MBIM, is that correct? For future reference, from
looking at the lsusb output, how do we know which one is active? Or
does the kernel have code to bind the class driver before specific
drivers, so that it always matches MBIM before qmi_wwan?
More information about the ModemManager-devel