Created attachment 748737 [details]
dmesg

Created attachment 748738 [details]
nm debug

Created attachment 748755 [details]
journalctl

there are only two patches to the mbim driver between 3.8 and 3.9
One looks like a cleanup, and the other is this..

commit 1e8bbe6cd02fc300c88bd48244ce61ad9c7d1776
Author: Bjørn Mork <bjorn>
Date:   Thu Mar 14 01:05:13 2013 +0000

    net: cdc_ncm, cdc_mbim: allow user to prefer NCM for backwards compatibility
    
    commit bd329e1 ("net: cdc_ncm: do not bind to NCM compatible MBIM devices")
    introduced a new policy, preferring MBIM for dual NCM/MBIM functions if
    the cdc_mbim driver was enabled.  This caused a regression for users
    wanting to use NCM.
    
    Devices implementing NCM backwards compatibility according to section
    3.2 of the MBIM v1.0 specification allow either NCM or MBIM on a single
    USB function, using different altsettings.  The cdc_ncm and cdc_mbim
    drivers will both probe such functions, and must agree on a common
    policy for selecting either MBIM or NCM.  Until now, this policy has
    been set at build time based on CONFIG_USB_NET_CDC_MBIM.
    
    Use a module parameter to set the system policy at runtime, allowing the
    user to prefer NCM on systems with the cdc_mbim driver.



Can you try that module parameter ? 'prefer_mbim'

hi dave, the problem exist since kernel 3.8. It should be something between 3.7.9 - 3.8.x

I tried echo "options cdc_ncm prefer_mbim=Y" > /etc/modprobe.d/cdc_ncm.conf but the problem still exist

argh echo "options cdc_ncm prefer_mbim=N" > /etc/modprobe.d/cdc_ncm.conf and the Mobile broadband modem works, thanks dave

The reason things fail is that ModemManager in Fedora <= 19 doesn't have the bits to handle MBIM yet, that's only landing in F20.  And when the Ericsson device is driven by MBIM but set up by AT commands (as is the case when you don't have native MBIM support in userspace) then the eth port simply won't work.

The 5321 is capable of using MBIM or NCM, but we shouldn't have userspace programs trying to unbind one driver and rebind the other based on what they support.  We have two options:

1) blacklist the 5321 (and maybe other dual NCM/MBIM devices) from the MBIM driver until userspace catches up and then revert this

2) make userspace catch up

We aren't shipping ModemManager 0.8 (which can do MBIM) in Fedora 19 because it's an API break and KDE hasn't caught up yet.  What we should probably do for Fedora < 20 is a modprobe option that forces a preference for NCM instead of MBIM, and anyone who really wants to use MBIM can remove that.

Dan, I'll merge this patch from debian that reverts the 'do mbim by default' part.

http://anonscm.debian.org/viewvc/kernel/dists/trunk/linux/debian/patches/debian/cdc_ncm-cdc_mbim-use-ncm-by-default.patch?revision=19955&view=markup

sound good ?

Had the same problem with a DW5560.
Workaround echo "options cdc_ncm prefer_mbim=N" > /etc/modprobe.d/cdc_ncm.conf did work for me too.

Dan, see comment #9.  Is userspace in all of Fedora now ready for MBIM, or should we carry the patch Dave pointed to?

(In reply to mrmx1 from comment #10)
> Had the same problem with a DW5560.
> Workaround echo "options cdc_ncm prefer_mbim=N" >
> /etc/modprobe.d/cdc_ncm.conf did work for me too.

Sorry, forgot to add config info
Fedora 18 i386
kernel-PAE-3.10.11-100.fc18.i686
NetworkManager-0.9.8.2-1.fc18.i686
ModemManager-0.6.2.0-1.fc18.i686.rpm

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs.

Fedora 18 has now been rebased to 3.11.4-101.fc18.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19.

If you experience different issues, please open a new bug report for those.

Hi All,

I have F19 64-bit with Lenovo x230 with same H5321gw and I am experiencing exactly the same problems. It sends dhcp requests but not able to make connection. I have tried the above fixed but still no joy...:)

Is there a known fix for this same problem for F19 64-bit?

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Retested after upgrade to FC20.
Removed /etc/modprobe.d/cdc_ncm.conf, which was the workaround for FC18, and now my DW5560 WWAN card is able to connect.

Fedora 20 i386
kernel-PAE-3.12.5-302.fc20.i686
NetworkManager-0.9.9.0-22.git20131003.fc20.i686
ModemManager-1.1.0-2.git20130913.fc20.i686

Thanks for letting us know.