Re: 03f0:521d Hewlett-Packard again
Harald Jung writes: > may I miss something? > dmesg shows nothing,too > ThinClient,initial:root:~ $ echo "7 7 7 7" > /proc/sys/kernel/printk > ThinClient,initial:root:~ $ echo "module cdc_ncm +fp" >>/sys/kernel/debug/dynamic_debug/control > ThinClient,initial:root:~ $ echo "module cdc_mbim +fp" >>/sys/kernel/debug/dynamic_debug/control > ThinClient,initial:root:~ $ echo -n "1-3:2.0" > > /sys/bus/usb/drivers/cdc_mbim/bind > bash: echo: write error: No such device Looks like I'm missing something. I don't see where the probe is failing. Unlessyou did echo "03f0 521d" > /sys/bus/usb/drivers/cdc_mbim/new_id previously. Is that still active? If so, then remove it. I believe it will make usbnet_probe see the device as blacklisted. If that's not it, then I guess you have to start adding debug printk's to see where it is failing. I don't know what else to do. Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: 03f0:521d Hewlett-Packard again
may I miss something? dmesg shows nothing,too ThinClient,initial:root:~ $ echo "7 7 7 7" > /proc/sys/kernel/printk ThinClient,initial:root:~ $ echo "module cdc_ncm +fp" >/sys/kernel/debug/dynamic_debug/control ThinClient,initial:root:~ $ echo "module cdc_mbim +fp" >/sys/kernel/debug/dynamic_debug/control ThinClient,initial:root:~ $ echo -n "1-3:2.0" > /sys/bus/usb/drivers/cdc_mbim/bind bash: echo: write error: No such device Harald On 20.09.2016 19:55, Bjørn Mork wrote: Harald Jung writes: Hi, no idea what I'm doing wrong here: cat /sys/bus/usb/devices/1-3/product HP hs3110 HSPA+ Mobile Broadband Device ls /sys/bus/usb/devices/ |grep 1-3 1-3 1-3:2.0 1-3:2.1 1-3:2.2 echo -n "1-3:2.0" > /sys/bus/usb/drivers/cdc_mbim/bind bash: echo: write error: No such device You're not doing anything wrong. That error is consistent with the probing failure. Do you have dynamic debugging enabled? If so, then mount debugfs, do echo module cdc_ncm +fp >/sys/kernel/debug/dynamic_debug/control and then repeat the manual bind. Hoping this will produce a more specific debug message. Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: 03f0:521d Hewlett-Packard again
Harald Jung writes: > Hi, > > no idea what I'm doing wrong here: > > cat /sys/bus/usb/devices/1-3/product > HP hs3110 HSPA+ Mobile Broadband Device > ls /sys/bus/usb/devices/ |grep 1-3 > 1-3 > 1-3:2.0 > 1-3:2.1 > 1-3:2.2 > echo -n "1-3:2.0" > /sys/bus/usb/drivers/cdc_mbim/bind > bash: echo: write error: No such device You're not doing anything wrong. That error is consistent with the probing failure. Do you have dynamic debugging enabled? If so, then mount debugfs, do echo module cdc_ncm +fp >/sys/kernel/debug/dynamic_debug/control and then repeat the manual bind. Hoping this will produce a more specific debug message. Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: 03f0:521d Hewlett-Packard again
Hi, no idea what I'm doing wrong here: cat /sys/bus/usb/devices/1-3/product HP hs3110 HSPA+ Mobile Broadband Device ls /sys/bus/usb/devices/ |grep 1-3 1-3 1-3:2.0 1-3:2.1 1-3:2.2 echo -n "1-3:2.0" > /sys/bus/usb/drivers/cdc_mbim/bind bash: echo: write error: No such device On 20.09.2016 13:06, Bjørn Mork wrote: Harald Jung writes: 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? The USB core will see "Cls=02(commc) Sub=0e Prot=00'" and match it against the cdc_mbim device list. The core runs the cdc_mbim probe function, which is responsible for verifying that the device is a supported MBIM device. It does that by parsing and verifying all the CDC class descriptors (which look fine AFAICS), and then it does a couple of NCM (or MBIM) specific control requests to confgure the remaining parts. You can try to force a manual bind and see if that returns some error code. The "x-y" part must be replaced with the proper bus+port numbers: echo x-y:2.0 >/sys/bus/usb/drivers/cdc_mbim/bind Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: 03f0:521d Hewlett-Packard again
Harald Jung writes: > 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? The USB core will see "Cls=02(commc) Sub=0e Prot=00'" and match it against the cdc_mbim device list. The core runs the cdc_mbim probe function, which is responsible for verifying that the device is a supported MBIM device. It does that by parsing and verifying all the CDC class descriptors (which look fine AFAICS), and then it does a couple of NCM (or MBIM) specific control requests to confgure the remaining parts. You can try to force a manual bind and see if that returns some error code. The "x-y" part must be replaced with the proper bus+port numbers: echo x-y:2.0 >/sys/bus/usb/drivers/cdc_mbim/bind Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: 03f0:521d Hewlett-Packard again
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 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
Re: 03f0:521d Hewlett-Packard again
I was able to switch it to Configuration 2 but the mbim driver didn't
grab the device.
On 20.09.2016 04:26, Sebastian Sjoholm wrote:
I use following for Huawei ME936 to force it to MBIM;
ACTION=="add|change", SUBSYSTEM=="usb", \
ENV{DEVTYPE}=="usb_device", \
ATTR{idVendor}=="12d1", ATTR{idProduct}=="15bb", \
ATTR{bNumConfigurations}=="3", ATTR{bConfigurationValue}!="3" \
ATTR{bConfigurationValue}=“3"
And it seems to work pretty well.
-Sebastian
___
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
Re: 03f0:521d Hewlett-Packard again
> On Sep 19, 2016, at 23:14 , Harald Jung wrote:
>
> I don't think that this device is triggered by any udev rule, so
> usb_modeswitch won't be triggered
>
> grep 03f0 40-usb_modeswitch.rules *
> 40-usb_modeswitch.rules:ATTR{idVendor}=="03f0", ATTR{idProduct}=="002a",
> RUN+="usb_modeswitch '%b/%k'"
> 40-usb_modeswitch.rules:ATTR{idVendor}=="03f0", ATTR{idProduct}=="002a",
> RUN+="usb_modeswitch '%b/%k'"
> 77-mm-ericsson-mbm.rules:ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="271d",
> ENV{ID_MM_ERICSSON_MBM}="1"
> 77-mm-ericsson-mbm.rules:ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="261d",
> ENV{ID_MM_ERICSSON_MBM}="1"
> 77-mm-ericsson-mbm.rules:ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="3a1d",
> ENV{ID_MM_ERICSSON_MBM}="1"
> 77-mm-ericsson-mbm.rules:ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="3d1d",
> ENV{.MM_USBIFNUM}=="09", ENV{ID_MM_ERICSSON_MBM_GPS_PORT}="1"
> 77-mm-ericsson-mbm.rules:ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="3d1d",
> ENV{ID_MM_ERICSSON_MBM}="1"
> 77-mm-ericsson-mbm.rules:ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="301d",
> ENV{ID_MM_ERICSSON_MBM}="1"
> 77-mm-ericsson-mbm.rules:ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="2f1d",
> ENV{ID_MM_ERICSSON_MBM}="1"
> 77-mm-fix-unexpected.rules:ATTRS{idVendor}=="03f0", ATTRS{idProduct}=="9d1d",
> RUN+="fix-unexpected"
> 77-mm-usb-device-blacklist.rules:ATTRS{idVendor}=="03f0",
> ATTRS{idProduct}=="1f0a", ENV{ID_MM_DEVICE_IGNORE}="1"
>
> Would it help to revert the option patch?
>
>
I use following for Huawei ME936 to force it to MBIM;
ACTION=="add|change", SUBSYSTEM=="usb", \
ENV{DEVTYPE}=="usb_device", \
ATTR{idVendor}=="12d1", ATTR{idProduct}=="15bb", \
ATTR{bNumConfigurations}=="3", ATTR{bConfigurationValue}!="3" \
ATTR{bConfigurationValue}=“3"
And it seems to work pretty well.
-Sebastian
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Re: 03f0:521d Hewlett-Packard again
I don't think that this device is triggered by any udev rule, so
usb_modeswitch won't be triggered
grep 03f0 40-usb_modeswitch.rules *
40-usb_modeswitch.rules:ATTR{idVendor}=="03f0", ATTR{idProduct}=="002a",
RUN+="usb_modeswitch '%b/%k'"
40-usb_modeswitch.rules:ATTR{idVendor}=="03f0", ATTR{idProduct}=="002a",
RUN+="usb_modeswitch '%b/%k'"
77-mm-ericsson-mbm.rules:ATTRS{idVendor}=="03f0",
ATTRS{idProduct}=="271d", ENV{ID_MM_ERICSSON_MBM}="1"
77-mm-ericsson-mbm.rules:ATTRS{idVendor}=="03f0",
ATTRS{idProduct}=="261d", ENV{ID_MM_ERICSSON_MBM}="1"
77-mm-ericsson-mbm.rules:ATTRS{idVendor}=="03f0",
ATTRS{idProduct}=="3a1d", ENV{ID_MM_ERICSSON_MBM}="1"
77-mm-ericsson-mbm.rules:ATTRS{idVendor}=="03f0",
ATTRS{idProduct}=="3d1d", ENV{.MM_USBIFNUM}=="09",
ENV{ID_MM_ERICSSON_MBM_GPS_PORT}="1"
77-mm-ericsson-mbm.rules:ATTRS{idVendor}=="03f0",
ATTRS{idProduct}=="3d1d", ENV{ID_MM_ERICSSON_MBM}="1"
77-mm-ericsson-mbm.rules:ATTRS{idVendor}=="03f0",
ATTRS{idProduct}=="301d", ENV{ID_MM_ERICSSON_MBM}="1"
77-mm-ericsson-mbm.rules:ATTRS{idVendor}=="03f0",
ATTRS{idProduct}=="2f1d", ENV{ID_MM_ERICSSON_MBM}="1"
77-mm-fix-unexpected.rules:ATTRS{idVendor}=="03f0",
ATTRS{idProduct}=="9d1d", RUN+="fix-unexpected"
77-mm-usb-device-blacklist.rules:ATTRS{idVendor}=="03f0",
ATTRS{idProduct}=="1f0a", ENV{ID_MM_DEVICE_IGNORE}="1"
Would it help to revert the option patch?
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 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
Re: 03f0:521d Hewlett-Packard again
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 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
Re: 03f0:521d Hewlett-Packard again
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. On 19.09.2016 22:03, Bjørn Mork wrote: Harald Jung 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
Re: 03f0:521d Hewlett-Packard again
Harald Jung 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
Re: 03f0:521d Hewlett-Packard again
Hi, echo "03f0 521d" > /sys/bus/usb/drivers/cdc_mbim/new_id had no effect 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 Bus 001 Device 003: ID 03f0:521d Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 bDeviceSubClass 2 bDeviceProtocol 1 bMaxPacketSize064 idVendor 0x03f0 idProduct 0x521d bcdDevice0.01 iManufacturer 5 Hewlett-Packard iProduct4 HP hs3110 HSPA+ Mobile Broadband Device iSerial 0 bNumConfigurations 2 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 253 bNumInterfaces 5 bConfigurationValue 1 iConfiguration 2 configuration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 bInterfaceSubClass 2 bInterfaceProtocol 1 iInterface 0 ** UNRECOGNIZED: 05 24 00 10 01 ** UNRECOGNIZED: 04 24 02 03 ** UNRECOGNIZED: 05 24 01 00 00 ** UNRECOGNIZED: 05 24 06 00 00 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 bInterfaceSubClass 2 bInterfaceProtocol 2 iInterface 0 ** UNRECOGNIZED: 05 24 00 10 01 ** UNRECOGNIZED: 04 24 02 02 ** UNRECOGNIZED: 05 24 01 00 01 ** UNRECOGNIZED: 05 24 06 01 01 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 bInterfaceSubClass 2 bInterfaceProtocol 3 iInterface 0 ** UNRECOGNIZED: 05 24 00 10 01 ** UNRECOGNIZED: 04 24 02 02 ** UNRECOGNIZED: 05 24 01 00 02 ** UNRECOGNIZED: 05 24 06 02 02 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpo
Re: 03f0:521d Hewlett-Packard again
Harald Jung writes: > Hi, > > two years ago we had some trouble with the HP hs3110 HSPA+ > > https://lists.freedesktop.org/archives/modemmanager-devel/2014-September/001553.html > > The last time the job was done to patch the option driver, this doesn' > work with the variant of the moden i have in another HP notebook. > My last test was to patch the huawei_cdc driver (because its a jungo > device), but it seems the problem is on the AT port. > > I've tested to switch to the other bConfiguration value, but it seems > the device doesn't speek mbim nor qmi. This looks like MBIM to me. Doesn't it work?: > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 137 > bNumInterfaces 3 > bConfigurationValue 2 > iConfiguration 3 configuration 1 > bmAttributes 0xa0 > (Bus Powered) > Remote Wakeup > MaxPower 500mA > Interface Association: > bLength 8 > bDescriptorType11 > bFirstInterface 0 > bInterfaceCount 2 > bFunctionClass 2 > bFunctionSubClass 14 > bFunctionProtocol 0 > iFunction 0 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 2 > bInterfaceSubClass 14 > bInterfaceProtocol 0 > iInterface 0 > CDC Header: > bcdCDC 1.10 > CDC MBIM: > bcdMBIMVersion 1.00 > wMaxControlMessage 1024 > bNumberFilters 32 > bMaxFilterSize 128 > wMaxSegmentSize 1500 > bmNetworkCapabilities 0x20 > 8-byte ntb input size > CDC MBIM Extended: > bcdMBIMExtendedVersion 1.00 > bMaxOutstandingCommandMessages 16 > wMTU 1500 > 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= 5 Cfg#= 1 Atr=a0 MxPwr=500mA > I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=01 Driver=option > I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=02 Driver=option > I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=03 Driver=option > I: If#= 3 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=02 Prot=07 Driver=huawei_ether > I: If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=02 Prot=05 Driver=option The "huawei_ether" is a vendor specific driver? FWIW, I believe that is the correct driver for this function. It is probably resembling a standard CDC ECM device, except that it has merged all 3 endpoints in one USB interface. And it might support an AT command channel similar to the huawei_cdc_ncm type functions. But I'm only guessing. Never actually tested one of these. You might be able to trick qmi_wwan into supporting the function for testing purposes (exporting the assumed AT channel over the /dev/cdc-wdm0 device), but I don't want to do that by default. It will confuse the hell out of both users and software if qmi_wwan started driving non-QMI functions.. I still recommend MBIM for these devices, if at all possible. So please: Test configuration #2. Bjørn ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
