"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."
This could be solved in different ways:
1) Remove "cdc_mbim.ko" from packages like linux-image-extra-3.8.0-XX-YY. Easy, but makes it harder for people to experiment with MBIM and add userspace support
2) Set the kernel parameter "prefer_mbim" to false for "cdc_ncm" module. This could be done by adding a file "/etc/modprobe.d/avoid-mbim.conf" with content:
options cdc_ncm prefer_mbim=N
This will allow people wanting to test MBIM easy access by removing or editing the file. Then the question is if this file should stay in modemmanager package or maybe in the kernel package?
The required code for this option to exist seems to be in Ubuntu Raring packages in commit 04188f3010f64ddf2c75c3f4953eee9bdb4f5cc1.
"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."
This could be solved in different ways:
1) Remove "cdc_mbim.ko" from packages like linux-image- extra-3. 8.0-XX- YY. Easy, but makes it harder for people to experiment with MBIM and add userspace support
2) Set the kernel parameter "prefer_mbim" to false for "cdc_ncm" module. This could be done by adding a file "/etc/modprobe. d/avoid- mbim.conf" with content:
options cdc_ncm prefer_mbim=N
This will allow people wanting to test MBIM easy access by removing or editing the file. Then the question is if this file should stay in modemmanager package or maybe in the kernel package?
The required code for this option to exist seems to be in Ubuntu Raring packages in commit 04188f3010f64dd f2c75c3f4953eee 9bdb4f5cc1.