3 thoughts on “HE910 mini PCIe USB initialization problem (EDITED)”
I have an HE910 mini PCIe board with SIM holder (LOT: 0813, IC: 5131A-HE910) that doesn’t initialize properly on USB in two different laptops running Ubuntu Linux 12.04:
– in the first laptop (Acer Inspire 1830T), the device seems to simply be absent from USB (lsusb shows nothing)
– in the second laptop (Lenovo W520), only the Infineon (bootloader?) device shows, but it continuously disconnect and reconnects:
[ 676.950760] usb 2-1.4: new high-speed USB device number 87 using ehci_hcd
[ 677.044078] usb 2-1.4: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 255, changing to 11
[ 677.044928] cdc_acm 2-1.4:1.0: This device cannot do calls on its own. It is not a modem.
[ 677.045041] cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device
[ 678.054051] usb 2-1.4: USB disconnect, device number 87
[ 678.994489] usb 2-1.4: new high-speed USB device number 88 using ehci_hcd
[ 679.087806] usb 2-1.4: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 255, changing to 11
[ 679.088683] cdc_acm 2-1.4:1.0: This device cannot do calls on its own. It is not a modem.
[ 679.088797] cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device
[ 680.097676] usb 2-1.4: USB disconnect, device number 88
[ 681.038245] usb 2-1.4: new high-speed USB device number 89 using ehci_hcd
[ 681.131687] usb 2-1.4: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 255, changing to 11
[ 681.132552] cdc_acm 2-1.4:1.0: This device cannot do calls on its own. It is not a modem.
[ 681.132666] cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device
[ 682.141544] usb 2-1.4: USB disconnect, device number 89
[ 683.082149] usb 2-1.4: new high-speed USB device number 90 using ehci_hcd
[ 683.175579] usb 2-1.4: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 255, changing to 11
[ 683.176421] cdc_acm 2-1.4:1.0: This device cannot do calls on its own. It is not a modem.
[ 683.176532] cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device
[ 684.185364] usb 2-1.4: USB disconnect, device number 90
[ 685.125704] usb 2-1.4: new high-speed USB device number 91 using ehci_hcd
[ 685.219323] usb 2-1.4: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 255, changing to 11
[ 685.220151] cdc_acm 2-1.4:1.0: This device cannot do calls on its own. It is not a modem.
[ 685.220263] cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device
Any ideas what be wrong here?
There is a doc "HE-GE Linux USB Driver – User Guide" saying the following – maybe thekernel module isn’t present at least in one installation, or not loaded?
Loading the driver Linux OS includes a generic USB driver for modems supporting the CDC ACM specification in the form of a kernel module (called cdc-acm): this driver works well without customization for HE-GE module.
Most recent Linux distributions do not require any user action in order to load this driver: it is enough to simply plug the USB cable.
If the modem is recognized by the operating system seven devices will be created:
/dev/ttyACM0 /dev/ttyACM1 /dev/ttyACM2 1
/dev/ttyACM3 1
/dev/ttyACM4 1
/dev/ttyACM5 1
/dev/ttyACM6 1
Of those only the following devices can be used: generic port for AT commands
/dev/ttyACM0: data port for PPP connections and AT commands /dev/ttyACM3 2 : generic port for AT commands
If no devices are created in your system check for the existence of the kernel module:
# lsmod | grep cdc_acm
If no entries are found, load the kernel module, with root privileges:
# modprobe cdc-acm
If an error response is returned, such as:
# FATAL: Module cdc-acm not found
this means that the kernel module is not present in your system and it should be built. Refer to the next paragraph for generic instructions.
Actually, cdc-acm is present on all instalations.
But the problem is that only the bootloader USB device (058b:0041) is briefly present on the USB bus – each time followed by a disconnection. So this doesn’t even get to the point where cdc-acm could pick up.
I have in the mean time tried to same module in a desktop via a PCIe-to-MiniPCIe adapter and it works there.
So I suspect this has somehow to do with the electrical level initialization off the various MiniPCI-e lines? The laptops must be doing something different that the module doesn’t like?
I’d really appreciate some help as I’m planning to test this in a laptop for mobility – but so far could not get it to work.
I have an HE910 mini PCIe board with SIM holder (LOT: 0813, IC: 5131A-HE910) that doesn’t initialize properly on USB in two different laptops running Ubuntu Linux 12.04:
– in the first laptop (Acer Inspire 1830T), the device seems to simply be absent from USB (lsusb shows nothing)
– in the second laptop (Lenovo W520), only the Infineon (bootloader?) device shows, but it continuously disconnect and reconnects:
[ 676.950760] usb 2-1.4: new high-speed USB device number 87 using ehci_hcd
[ 677.044078] usb 2-1.4: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 255, changing to 11
[ 677.044928] cdc_acm 2-1.4:1.0: This device cannot do calls on its own. It is not a modem.
[ 677.045041] cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device
[ 678.054051] usb 2-1.4: USB disconnect, device number 87
[ 678.994489] usb 2-1.4: new high-speed USB device number 88 using ehci_hcd
[ 679.087806] usb 2-1.4: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 255, changing to 11
[ 679.088683] cdc_acm 2-1.4:1.0: This device cannot do calls on its own. It is not a modem.
[ 679.088797] cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device
[ 680.097676] usb 2-1.4: USB disconnect, device number 88
[ 681.038245] usb 2-1.4: new high-speed USB device number 89 using ehci_hcd
[ 681.131687] usb 2-1.4: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 255, changing to 11
[ 681.132552] cdc_acm 2-1.4:1.0: This device cannot do calls on its own. It is not a modem.
[ 681.132666] cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device
[ 682.141544] usb 2-1.4: USB disconnect, device number 89
[ 683.082149] usb 2-1.4: new high-speed USB device number 90 using ehci_hcd
[ 683.175579] usb 2-1.4: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 255, changing to 11
[ 683.176421] cdc_acm 2-1.4:1.0: This device cannot do calls on its own. It is not a modem.
[ 683.176532] cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device
[ 684.185364] usb 2-1.4: USB disconnect, device number 90
[ 685.125704] usb 2-1.4: new high-speed USB device number 91 using ehci_hcd
[ 685.219323] usb 2-1.4: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 255, changing to 11
[ 685.220151] cdc_acm 2-1.4:1.0: This device cannot do calls on its own. It is not a modem.
[ 685.220263] cdc_acm 2-1.4:1.0: ttyACM0: USB ACM device
Any ideas what be wrong here?
There is a doc "HE-GE Linux USB Driver – User Guide" saying the following – maybe thekernel module isn’t present at least in one installation, or not loaded?
Actually, cdc-acm is present on all instalations.
But the problem is that only the bootloader USB device (058b:0041) is briefly present on the USB bus – each time followed by a disconnection. So this doesn’t even get to the point where cdc-acm could pick up.
I have in the mean time tried to same module in a desktop via a PCIe-to-MiniPCIe adapter and it works there.
So I suspect this has somehow to do with the electrical level initialization off the various MiniPCI-e lines? The laptops must be doing something different that the module doesn’t like?
I’d really appreciate some help as I’m planning to test this in a laptop for mobility – but so far could not get it to work.