[stav13]

Hi,

I have successfully installed gammu and got it sending SMS via scripts from my monitoring program, however after around 24 hours it start getting errors of;


[root@********** ~]# gammu --identify
No response in specified timeout. Probably phone not connected.

However I can see the device;

[root@********** ~]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 12d1:1464 Huawei Technologies Co., Ltd.
Bus 006 Device 002: ID 03f0:7029 Hewlett-Packard


If i go and reboot the machine or even unplug the Huawei and run the below commands it works again;

usb_modeswitch -v 0x12d1 -p 0x1521 -M 55534243123456780000000000000011060000000000000000000000000000
modprobe usbserial vendor=0x12d1 product=0x1464

The Huawei status light is blinking green showing it has signal and this doesnt change, just looks like the host cannot communicate with the Huawei anymore.

Im currently running this on Centos 6.5 (final)

Many thanks

[LOM]

Probably a dongle firmware crash or a usb driver problem, for sure not a usb_modeswitch problem since it has left the scene immediately after switching the device into 12d1:1464.

Your usage of the usbserial driver is just wrong, the K4505 has direct ethernet interfaces which a serial driver should not bind to but usbserial has no knowledge of that and will bind to any interface.
Use the option.ko driver, it has the net interfaces of K4505 blacklisted so will not bind to those and it it is also a generally much better driver than usbserial.

[stav13]

Hi LOM,

Thanks for getting back to me. Im a bit unsure how to use the option.ko drive, is it as simple as the below;

# modprobe -v option
# echo " 12d1 1464" > /sys/bus/usb-serial/drivers/option1/new_id


After that do I need to add these commands to run on boot in the /etc/rc.local file ?

Many Thanks

[LOM]

12d1:1464 is already defined in the option driver (unless you use an extremely old one) so no need to use the new_id function.
Just modprobe these 3 drivers in dependency order:

modprobe usbserial
modprobe usb_wwan (it needs one function exported from usb_serial)
modprobe option (it needs many functions exported by usb_wwan)

You will now get the correct number of ttyUSB devices, 2 less (the direct ethernet interfaces) than you got when using usbserial with vendor/product.