I am working on a custom embedded linux solution, with a down-device Sierra Wireless EM9293 cellular modem on the carrier board.
My linux kernel sees the modem on the USB bus, but I see no new /dev/ devices, and no new network interfaces. Can someone tell me if there are particular tools and/or kernel options that are required for me to be able to use this device?
Here is the dmesg output of my board:
[ 35.400923] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd
[ 35.425414] usb 2-1: LPM exit latency is zeroed, disabling LPM.
[ 35.432631] usb 2-1: config 1 has an invalid interface number: 4 but max is 3
[ 35.439798] usb 2-1: config 1 has no interface number 2
[ 35.445540] usb 2-1: New USB device found, idVendor=1199, idProduct=90e3, bcdDevice= 0.06
[ 35.453856] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 35.461018] usb 2-1: Product: Sierra Wireless EM9293
[ 35.466006] usb 2-1: Manufacturer: Sierra Wireless, Incorporated
[ 35.472029] usb 2-1: SerialNumber: EG4464920401B117
I have no Sierra devices attached via USB, but I have worked with another manufacturers modems. In that case, the device exposed numerous serial devices as well as a network device. I could enumerate which functions were available using lsusb -vvv ... to get very verbose information. Maybe that will be helpful, but I have no idea if it is or not.
When we used this module on our project, we used the Sierra drivers, the MBPL drivers. Compiled them and the module interfaces were recognized. Have tried the MBPL drivers?
Thanks all, I was able to get it resolved by adding some kernel modules (particularly CONFIG_USB_NET_CDC_MBIM=m and CONFIG_USB_SERIAL_QUALCOMM=y … for some reason, cdc_mbim compiled monolithically did NOT work…)
with that new kernel and modules, the mbim net interface was automatically discovered. I still needed to run