This is interesting…I came across another thread with a suggestion that the driver just isn’t recognizing the device and a workaround was needed. So I thought I’d give it a go.
As soon as I saved the VID/PID 1199/9091 to the new_id file in /sys/bus/usb-serial/drivers/generic, I got the ttyUSBx assignments.
usbserial_generic 2-1:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 2-1:1.0: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 2-1:1.0: generic converter detected
usb 2-1: generic converter now attached to ttyUSB0
usbserial_generic 2-1:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserialusbserial_generic 2-1:1.2: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 2-1:1.2: generic converter detected
usb 2-1: generic converter now attached to ttyUSB1
usbserial_generic 2-1:1.3: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 2-1:1.3: Tell linux-usb@vger.kernel.org to add your device to a proper driver.types.
usbserial_generic 2-1:1.3: generic converter detected
usb 2-1: generic converter now attached to ttyUSB2
usbserial_generic 2-1:1.8: The "generic" usb-serial driver is only for testing and one-off prototypes.
usbserial_generic 2-1:1.8: Tell linux-usb@vger.kernel.org to add your device to a proper driver.
usbserial_generic 2-1:1.8: generic converter detected
usb 2-1: generic converter now attached to ttyUSB3
pwm-backlight backlight: backlight supply power not found, using dummy regulator
I had gone through the files qcserial.c, usb_wwan.c, and qmi_wwan.c to make sure that PID/VID for device I’m using was listed and it is. So why would I need to add the PID/VID to the new_id file? I don’t understand that one.