Trouble with Alcatel X220D
Running OpenWRT backfire firmware in D-Link DIR-320 router.
usb_modeswich version 1.1.4
usb_modeswitch-data version 20100826
These are included with the OpenWRT firmware.
usb_modeswitch detects the Alcatel and switches it to modem mode;
root@OpenWrt:~# lsusb
Bus 002 Device 002: ID 1bbb:0017 T & A Mobile Phones
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@OpenWrt:~#
However there are no entries for ttyUSB0->5 in /dev
Someone at OpenWRT had me add echo "1bbb 0017" > /sys/bus/usb-serial/drivers/option1/new_id to /etc/rc.local and now I have the /dev entries.
I see that the contents of /etc/usb_modeswitch.d/1bbb:0017 is :
########################################################
# Alcatel X200/X060S
DefaultVendor= 0x1bbb
DefaultProduct=0xf000
TargetVendor= 0x1bbb
TargetProduct= 0x0000
CheckSuccess=20
MessageContent="55534243123456788000000080000606f50402527000000000000000000000"
does not specifically identify this model.
In version usb_modeswitch-data-20110227 this files content are:
########################################################
# Alcatel X200/X200L/X060S
DefaultVendor= 0x1bbb
DefaultProduct=0xf000
TargetVendor= 0x1bbb
TargetProductList="0000,0017"
CheckSuccess=20
MessageContent="55534243123456788000000080000606f50402527000000000000000000000"
Will updating the OpenWRT version of usb_modeswitch correct my problem or is there something else causing this?
Because several modems are lumped together is there some ambiguity that cause this behavior?
Thanks,
Perazim
Sorry, I must have missed your post somehow ...
Yes, an update to the config file (or the whole package) would definitely help solving your issue.
Regarding the target IDs, there is no ambiguity because the USB ID before switching is identical for both models. This is what counts.
The target ID is useful for any steps which may follow the switching, like success checking and binding the driver to the newly "created" modem device.
Yes, an update to the config file (or the whole package) would definitely help solving your issue.
Regarding the target IDs, there is no ambiguity because the USB ID before switching is identical for both models. This is what counts.
The target ID is useful for any steps which may follow the switching, like success checking and binding the driver to the newly "created" modem device.