03f0:521d Hewlett-Packard again
Bjørn Mork
bjorn at mork.no
Tue Sep 20 23:38:35 UTC 2016
Harald Jung <harald.jung at ecos.de> 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. Unless....you 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
More information about the ModemManager-devel
mailing list