Author Message

<  Setup Discussion  ~  Generic HSDPA USB modem on Pi

PostPosted: Sat Sep 09, 2017 4:46 am Reply with quote
Posts: 1 Joined: Sat Sep 09, 2017 2:53 am
I am new to the forum so please forgive any poor formatting etc.

I hope someone with experience with usb_modeswitch can help and I thank those in advance that that time to consider this post.

I have set up a number of new an old 3G and 4G USB modems on a raspberry pi based system with complete success. But I am just completely stuck with a generic HSDPA form that I would like to use going forward (so I can use any network provider).

The Generic HSPDA modem can be purchased from multiple vendors on Ebay etc.

It powers on as a QUALCOMM 05c6:1000.

I can switch it to 05c6:6000 with multiple commands found on these pages (using the standard Eject sequence in usb_modeswitch or special switching codes like MessageContent="5553424312345678000000000000061b000000020000000000000000000000".)

All looks fine at this stage. 4 ttys_USB devices are created but no gsmmodem device. But that is not important (as I understand). I can run wvdial through ttyUSB0 (and interestingly through ttypUSB1 with slightly different results) and it finds the dial tone and logs on, but does not complete with a wan address or working internet access.

Also importantly usb_modesswitch does not result in a wwano being configured by Dhcpcd as shown by ifconfig. This will probably be the reason wvdial does not create a ip connection successfully. The switching does however result in the correct usbserial kernel modules being loaded (wwan0).

Looking closely, usb-modeswitch seems to execute with error messages that does indicate a problem.

FYI the modeswitch output that results in "seeming" correct switching to 05c6:6000 is:

/Looking for default devices ...
product ID matched
Found device 005 on bus 001
Access device 005 on bus 001
Current configuration number is 1
User Interface 0
Use endpoint 0x01 (out) and 0x81 (in)

USB description data (for identification)
Manufacturer: Qualcomm, Incorporated
Product: Qualcomm CMDA Technologies MSM
Serial No.:35160200025260
Sending Standard EJECT Sequence
Looking for active driver . . .
OK, driver detached
Set up Interface 0
Use endpoint 0x01 for message sending . . .
Trying to send message 1 to endpoint 0x01 . . .
OK, message successfully sent
Read response to message to message 1 (CSW) . . .
Response successfully read (13 bytes)
Trying to send message 2 to endpoint 0x01 . . .
OK, message successfully sent
Read response to message to message 1 (CSW) . . .
Response reading failed (error -1)
Device is gone. skip further commands
-> Run lsusb to note any changes. Bye!

After usb_modeswitch, the lsmod command reveals two relevant loaded modules. This seems correct. But as I said no wwan0 is visible to Dhcpcd using ifconfig:

Module Size Used by
usb_wan 9084. option
usbserial 29996 option, usb_wan

Has anyone experienced this and know the solution? It would seem to me that during the running of modeswitch another module is interfering with the process. But I can't seem to find what is going on.

PostPosted: Mon Sep 11, 2017 8:31 am Reply with quote
Posts: 1175 Joined: Wed Jul 11, 2012 3:14 pm Location: Koh Samui, TH
I don't think your problem is related to usb_modeswitch, it switches the modem from what I can see and you have even loaded the serial driver which binds to the modem and creates ttyUSB devices in the system.

What remains for you to do now is configuring your dialing program.


Display posts from previous:  Sort by:

All times are UTC+02:00
Page 1 of 1
2 posts
Users browsing this forum: No registered users and 2 guests
Search for:
Jump to:  
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