sony-vaio-z-series team mailing list archive

[vick <weasalandme@xxxxxxxxx>]

>>Thanks for the response. Yes, I can modprobe qcserial without compiling a new module, however, none of the ttyUSB devices seem to work. By the way the ttyUSB0, ttyUSB1, ttyUSB2, and ttyUSB3, are created at boot without the qcserial module loaded. Also, it looks like 
>>
>>
>>usb_wwan               19863  1 option
>>usbserial              42302  2 option,usb_wwan
>>
>>are loaded as well. 
>>
>>
>>dmesg output from modprobe qcserial
>>[  893.577556] usbcore: registered new interface driver qcserial
>>[  893.577574] USB Serial support registered for Qualcomm USB 
>>



I take it you don't see anything like this in dmesg

[20710.154030] qcserial 3-1.4:1.1: Qualcomm USB modem converter detected
[20710.154228] usb 3-1.4: Qualcomm USB modem converter now attached to ttyUSB0
[20710.155006] qcserial 3-1.4:1.2: Qualcomm USB modem converter detected
[20710.155194] usb 3-1.4: Qualcomm USB modem converter now attached to ttyUSB1
[20710.155728] qcserial 3-1.4:1.3: Qualcomm USB modem converter detected
[20710.155908] usb 3-1.4: Qualcomm USB modem converter now attached to ttyUSB2


ttyUSB1 is the interface that works for me. I assume you have network-manager installed, do you have modemmanager package as well? It looks like rfkill is seeing the device and is not blocking it so it should be on and processed by qcserial. 
The modules look funny though, I don't have the option module and I suspect it might be blocking the ttyUSB devices so try to blacklist it and let qcserial use the usbserial module. I see this:

qcserial               12466  0 
usb_wwan               17278  1 qcserial
usbserial              28139  2 qcserial,usb_wwan