[mwsa]

I can't get the drivers to work. Is this the place I should ask? Is there some simple thing I should do to fix this?


I have a ZTE MF668A Revision: T03.

Running on ubuntu 14.04
Linux host 3.13.0-55-generic #92-Ubuntu SMP Sun Jun 14 18:32:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux


It loads OK and usb_modeswitch switches it and creates a /dev. The dongle, then connects up to the GSM network OK (the light turns blue). I can send SMS messages if I use screen to talk to the modem directly.

If I try gsmsemdsms I get:

Code: Select all

 gsmsendsms -d /dev/ttyUSB2 <my number>  "test 2"
gsmsendsms[ERROR]: ME/TA error 'invalid PDU mode parameter' (code 304)

If I use gsmctl I get this:

Code: Select all

 gsmctl -d /dev/ttyUSB2 ALL                     
<ME0>  Manufacturer: ZTE INCORPORATED
<ME1>  Model: MF668A
<ME2>  Revision: T03
<ME3>  Serial Number: 864851006400411
<FUN>  Functionality Level: unsupported
gsmctl[ERROR]: expected number (at position 2 of std::string '(2,"Telstra Mobile","Telstra","50501",2) .........

/var/log/usb_modeswitch.log

Has:

Code: Select all

(end of usb_modeswitch output)
Check success of mode switch for max. 20 seconds ... Read attributes ...
USB dir exists: /sys/bus/usb/devices/2-1
 All attributes matched
Mode switching was successful, found 19d2:0031 (ZTE,Incorporated: ZTE WCDMA Technologies MSM)Now check for bound driver ...
 no driver has bound to interface 0 yet
Device not in "bind_list" yet, bind it now
Module loader is /sbin/modprobe
Module is active already
Try to add ID to driver "option"
 ID added to driver; check for new devices in /dev
 driver binding failed
Check for AVOID_RESET_QUIRK kernel attribute
 AVOID_RESET_QUIRK activated

All done, exit

/var/log/syslog contains:

Code: Select all

Jun 29 14:46:58 sms-test usb_modeswitch[12621]: usb_modeswitch: switched to 19d2:0031 on 2/29
Jun 29 14:46:59 sms-test usb_modeswitch[12621]: usb_modeswitch: add device ID 19d2:0031 to driver option
Jun 29 14:46:59 sms-test usb_modeswitch[12621]: usb_modeswitch: please report the device ID to the Linux USB developers!

[LOM]

I can't get the drivers to work. Is this the place I should ask?

No, the serial drivers are not maintained here and I don't even think there is any problem with them.
gsmctl can communicate on ttyUSB2 so driver is loaded and working, I'd guess the problem lies in gsmsendsms or that you have choosen the ppp modem device (ttyUSB2) for sending SMS.
ttyUSB1 ought to be the device to use.

[Josh]

It's strange though that the driver shouldn't bind automatically - this is an OLD modem ID ...

Code: Select all

Mode switching was successful, found 19d2:0031
Now check for bound driver ...
 no driver has bound to interface 0 yet

[LOM]

It's strange though that the driver shouldn't bind automatically - this is an OLD modem ID ...

Code: Select all

Mode switching was successful, found 19d2:0031
Now check for bound driver ...
 no driver has bound to interface 0 yet

Yes I saw that but ignored it - he has a ttyUSB2 which must come from a successful driver loading even if usb_modeswitch couldn't see that.

[mwsa]

It's strange though that the driver shouldn't bind automatically - this is an OLD modem ID ...

Yes, it is.

Code: Select all

Mode switching was successful, found 19d2:0031
Now check for bound driver ...
 no driver has bound to interface 0 yet

So where do the drivers come from?

[mwsa]

I can't get the drivers to work. Is this the place I should ask?

I'd guess the problem lies in gsmsendsms or that you have choosen the ppp modem device (ttyUSB2) for sending SMS.
ttyUSB1 ought to be the device to use.

Code: Select all

root@sms-test:~  
# gsmsendsms -d /dev/ttyUSB0 <phone> "test 2"
gsmsendsms[ERROR]: clearing DTR failed (errno: 22/Invalid argument)
root@sms-test:~ 1 
# gsmsendsms -d /dev/ttyUSB1 <phone>  "test 2"
gsmsendsms[ERROR]: clearing DTR failed (errno: 22/Invalid argument)
root@sms-test:~ 1 
# gsmsendsms -d /dev/ttyUSB2 <phone> "test 2"
gsmsendsms[ERROR]: ME/TA error 'invalid PDU mode parameter' (code 304)
root@sms-test:~ 1 
#

I did try ttyUSB1 but it looked like some kind of storage device to me. On googling it appears that the gsm send error is related to the fact that something doesn't know the Functionalities of the dongle. That line comes up when I use gsmctl ALL :

Code: Select all

<FUN>  Functionality Level: unsupported

gsmsend won't try to put the phone into PDU mode or something.

[Josh]

So where do the drivers come from?

You misunderstand. The driver (its name is "option") is available and ready on your system. It just does not bind to your modem - which it should.
However, it has an interface where it can be told to bind to a specific USB ID - which is what usb_modeswitch does.