Draisberghof | Software | USB_ModeSwitch | ModeSwitchForum

FAQ Search LoginRegister

Author Message
< Everything Coding ~ Multiple interfaces are not created using option driver
venkat
PostPosted: Thu Oct 03, 2013 12:46 pm Reply with quote
Posts: 2
Joined: Thu Oct 03, 2013 12:17 pm
Hi All,
In my system udev is not supported and I enabled the usb-serial and option drive
r in the kernel to talk to my ZTE dongle.
Also created three device files from ttyUSB[0-2].
I have cross compiled the usb_modeswitch utility according to my platform and ra
n the utility by passing the required vendor and product id.
It actually detached the driver (usb-storage). When I checked in the proc/bus/us
b/devices, I see the driver is assigned as none. I manually bind the option driv
er to my device using below command. This time I see only 1 interface got detect
ed.
echo "12d1 1505" > /sys/bus/usb-serial/drivers/option1/new_id
I believe that 4 interfaces should be created, where 3 interfaces should contain
the option driver and 1 interface should have usb-storage. Also the product id
should change to some different value other than the original product id.
I am currently using kernel version 2.6.23. Could some help me with the below po
ints.
1: What is the minimum kernel version (with respect to option driver and usb-ser
ial) required for usb_modeswitch to work correctly.
2: Is there any issue with the driver (option and usb-serial) verison what i am
using?.
3: Manual binding of driver using the above method followed is the correct way?.
4: Why only one interface is created instead of 4 interfaces?.
Appreciate if some one can give me clue in where I am doing wrong?.
Thanks,
Venkat
Top
Offline Profile
LOM
PostPosted: Thu Oct 03, 2013 3:00 pm
Reply with quote
Posts: 900
Location: Koh Samui, TH
Joined: Wed Jul 11, 2012 3:14 pm
The most obvious error is that the vendor id for ZTE is 19d2, 12d1 is Huawei so
your echo command will not work.
What is the ZTE product name of your dongle?
What is its USB Id (vendor:product)?
Your system log should contain a line showing the USB Id when the dongle gets de
tected on the USB bus.

Top
Offline Profile
venkat
PostPosted: Thu Oct 03, 2013 3:41 pm
Posts: 2
Joined: Thu Oct 03, 2013 12:17 pm
Hi,

Reply with quote

Thanks for your reply. The answers are embedded in the below mail.
LOM wrote:
The most obvious error is that the vendor id for ZTE is 19d2, 12d1 is Huawei so
your echo command will not work.
[Venkat]: I am actually using both Huawei and ZTE dongle. In the above case for
testing, I am using Huwaei dongle.
What is the ZTE product name of your dongle?
What is its USB Id (vendor:product)?
[Venkat]: (12d1:1505)
Your system log should contain a line showing the USB Id when the dongle gets de
tected on the USB bus.
[Venkat]: When I bind the driver using the below command
echo "12d1 1505" > /sys/bus/usb-serial/drivers/option1/new_id
The system logs shows the below message.
USB Serial support registered for GSM modem (1-port)
option 1-1.4:1.0: GSM modem (1-port) converter detected
usb 1-1.4: GSM modem (1-port) converter now attached to ttyUSB0
When I check in the /proc/bus/usb/devices, I am seeing only one interface and dr
iver is attached to option.
But I am actually expecting 4 interfaces with attaching the option driver to thr
ee interfaces and one to usb-storage.
Could you please help me the below questions?.
1: What is the minimum kernel version (with respect to option driver and usb-ser
ial) required for usb_modeswitch to work correctly.
2: Is there any issue with the driver (option and usb-serial) verison what i am
using?.
3: Manual binding of driver using the above method followed is the correct way?.
4: Why only one interface is created instead of 4 interfaces?.
Thanks,
Venkat
Top
Offline Profile
LOM
PostPosted: Thu Oct 03, 2013 5:49 pm
Reply with quote
Posts: 900
Location: Koh Samui, TH
Joined: Wed Jul 11, 2012 3:14 pm
12d1:1505 is a Huawei Id, not a ZTE Id so what you have is a Huawei modem.

It is furthermore the initial Id when the modem is in Windows install mode where
it only has 1 interface which is for the virtual cd-rom where the Windows drive
rs and Windows Connection Manager are stored.
USB_ModeSwitch, when correctly installed, will work on kernel 2.6.23 and will sw
itch it into modem mode where it will get a different USB Id.
It is of no use trying to bind the driver to the initial Id, the driver must be
bound to the switched Id so your first step should be to get it to switch.
You need to install the complete usb_modeswitch , not only the executable but al
so the data package with udev rules.
Top
Offline Profile
Display posts from previous: Sort by:
Go
Print view All times are UTC + 1 hour [ DST ]
Previous topic | Next topic
Board index ~ Everything Coding Page 1 of 1
4 posts
Users browsing this forum: No registered users and 4 guests
Search for:
Go
Post new topic Reply to topic
Jump to: Go
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum
cron
Powered by phpBB // Template by Mike Lothar
3.x port by CiC and will_hough // GC