Hi,
to be shure i removed usb_modeswitch from the last build and i added an
udev rule, that the bConfiguration switch happened before modemmanager
was started.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
usbcore: registered new interface driver uas
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver uss720
usbcore: registered new interface driver btusb
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbcore: registered new interface driver option
usbcore: registered new interface driver uvcvideo
usbcore: registered new interface driver cdc_ncm
usbcore: registered new interface driver cdc_wdm
usbcore: registered new interface driver cdc_mbim
usbcore: registered new interface driver usbhid
mbim is still not bound to the device
T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=02 Dev#= 3 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=02 Prot=01 MxPS=64 #Cfgs= 2
P: Vendor=03f0 ProdID=521d Rev=00.01
S: Manufacturer=Hewlett-Packard
S: Product=HP hs3110 HSPA+ Mobile Broadband Device
C: #Ifs= 3 Cfg#= 2 Atr=a0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=(none)
I: If#= 1 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=02 Driver=(none)
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=05 Driver=option
how does the mbim driver detects the mbim capabilities of a device?
On 19.09.2016 23:02, Dan Williams wrote:
On Mon, 2016-09-19 at 22:06 +0200, Harald Jung wrote:
At this point i have no idea why cdc_mbim doen't grab the device.
Just that it is loaded but i think it is just loaded by cdc_ncm
dependencies.
Check usb_modeswitch/usb_modeswitch_dispatcher. If you move them out
of the way, does that help? Older versions (like 2.4 and earlier) than
the most recently released one would force-bind interfaces to some
drivers which could interfere with kernel device matching.
I just had this issue today for a Franklin U600 which should use cdc-
acm on interfaces 0 & 1 and qcaux on 2-5. But the presence of
/usr/sbin/usb_modeswitch_dispatcher prevented cdc-acm from binding.
moving it out of the way fixed the issue, as would (I presume)
updating my usb_modeswitch version.
Dan
On 19.09.2016 22:03, Bjørn Mork wrote:
Harald Jung <harald.j...@ecos.de> writes:
echo "03f0 521d" > /sys/bus/usb/drivers/cdc_mbim/new_id
had no effect
And it should not. The driver will match the MBIM class.
usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0
usbcore: registered new interface driver cdc_ncm
usbcore: registered new interface driver cdc_wdm
usbcore: registered new interface driver cdc_mbim
T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=02 Dev#= 3 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=02 Prot=01 MxPS=64 #Cfgs= 2
P: Vendor=03f0 ProdID=521d Rev=00.01
S: Manufacturer=Hewlett-Packard
S: Product=HP hs3110 HSPA+ Mobile Broadband Device
C: #Ifs= 3 Cfg#= 2 Atr=a0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00
Driver=(none)
I: If#= 1 Alt= 0 #EPs= 0 Cls=0a(data ) Sub=00 Prot=02
Driver=(none)
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=05
Driver=option
The cdc_mbim driver should at least try to bind to the two first
interfaces. Don't you see any other messages from it in the log?
Bjørn
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
