[hunters1094]

Hi,

I'm running in Centos 7 with Mobily Quanta 1K3M Device

This is the log of Quanta 0408:ea25 when run usb_modeswitch:

GNU nano 2.3.1 File: usb_modeswitch_1-1.3

--------------------------------

Read long config from command line

* usb_modeswitch: handle USB devices with multiple modes
* Version 2.5.1 (C) Josua Dietze 2017
* Based on libusb1/libusbx

! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor= 0x0408
DefaultProduct= 0xea25
TargetVendor= 0x0408
TargetProduct= 0xea26
QuantaMode=1
System integration mode enabled

Use given bus/device number: 001/005 ...
Look for default devices ...
bus/device number matched
found USB ID 0408:ea25
vendor ID matched
product ID matched
Found devices in default mode (1)
Get the current device configuration ...
Use interface number 0
with class 8

USB description data (for identification)
-------------------------
Manufacturer: Qualcomm, Incorporated
Product: Qualcomm CDMA Technologies MSM
Serial No.: 352593051104832
-------------------------
Send Quanta control message ...
Error: Quanta control message failed (error -7). Abort
--------------------------------
(end of usb_modeswitch output)


Core program reported switching failure. Exit


How can I check more detail or fix it? Thank you.

[LOM]

The error reported by libusb is probably not a real error, which usb id does lsusb show for the device after "switching failure"?

[hunters1094]

Hi LOM

The USB show by lsusb:
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 006: ID 0408:ea26 Quanta Computer, Inc.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsusb -t:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
|__ Port 2: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
|__ Port 3: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 480M
|__ Port 3: Dev 6, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 3: Dev 6, If 2, Class=Vendor Specific Class, Driver=, 480M
|__ Port 3: Dev 6, If 3, Class=Vendor Specific Class, Driver=, 480M
|__ Port 3: Dev 6, If 4, Class=Mass Storage, Driver=usb-storage, 480M


Log when modeswitch run (unplug and plug usb):
May 18 15:50:20 localhost kernel: usb 1-1.3: USB disconnect, device number 4
May 18 15:50:28 localhost kernel: usb 1-1.3: new high-speed USB device number 5 using ehci-pci
May 18 15:50:28 localhost kernel: usb 1-1.3: New USB device found, idVendor=0408, idProduct=ea25, bcdDevice= 0.00
May 18 15:50:28 localhost kernel: usb 1-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=4
May 18 15:50:28 localhost kernel: usb 1-1.3: Product: Qualcomm CDMA Technologies MSM
May 18 15:50:28 localhost kernel: usb 1-1.3: Manufacturer: Qualcomm, Incorporated
May 18 15:50:28 localhost kernel: usb 1-1.3: SerialNumber: 352593051104832
May 18 15:50:28 localhost kernel: usb-storage 1-1.3:1.0: USB Mass Storage device detected
May 18 15:50:28 localhost kernel: scsi host7: usb-storage 1-1.3:1.0
May 18 15:50:28 localhost mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3"
May 18 15:50:28 localhost mtp-probe: bus: 1, device: 5 was not an MTP device
May 18 15:50:28 localhost systemd: Created slice system-usb_modeswitch.slice.
May 18 15:50:28 localhost systemd: Starting USB_ModeSwitch_1-1.3...
May 18 15:50:29 localhost usb_modeswitch: switch device 0408:ea25 on 001/005
May 18 15:50:30 localhost kernel: scsi 7:0:0:0: CD-ROM Qualcomm MMC Storage 2.31 PQ: 0 ANSI: 2
May 18 15:50:30 localhost kernel: scsi 7:0:0:1: Direct-Access Qualcomm MMC Storage 2.31 PQ: 0 ANSI: 2
May 18 15:50:30 localhost kernel: sr 7:0:0:0: [sr1] scsi-1 drive
May 18 15:50:30 localhost kernel: sr 7:0:0:0: Attached scsi generic sg3 type 5
May 18 15:50:30 localhost kernel: sd 7:0:0:1: Attached scsi generic sg4 type 0
May 18 15:50:30 localhost kernel: sd 7:0:0:1: [sdc] Attached SCSI removable disk
May 18 15:50:30 localhost systemd: Started USB_ModeSwitch_1-1.3.
May 18 15:50:32 localhost kernel: usb 1-1.3: USB disconnect, device number 5
May 18 15:50:37 localhost kernel: usb 1-1.3: new high-speed USB device number 6 using ehci-pci
May 18 15:50:37 localhost kernel: usb 1-1.3: New USB device found, idVendor=0408, idProduct=ea26, bcdDevice= 0.00
May 18 15:50:37 localhost kernel: usb 1-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=0
May 18 15:50:37 localhost kernel: usb 1-1.3: Product: Qualcomm CDMA Technologies MSM
May 18 15:50:37 localhost kernel: usb 1-1.3: Manufacturer: Qualcomm, Incorporated
May 18 15:50:37 localhost kernel: usb-storage 1-1.3:1.4: USB Mass Storage device detected
May 18 15:50:37 localhost kernel: scsi host8: usb-storage 1-1.3:1.4
May 18 15:50:37 localhost mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3"
May 18 15:50:37 localhost mtp-probe: bus: 1, device: 6 was not an MTP device
May 18 15:50:38 localhost kernel: scsi 8:0:0:0: Direct-Access Qualcomm MMC Storage 2.31 PQ: 0 ANSI: 2
May 18 15:50:38 localhost kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
May 18 15:50:38 localhost kernel: sd 8:0:0:0: [sdc] Attached SCSI removable disk


Modeswitch can change device ID to 0408:ea26, but the usb is still storage.

[LOM]

Modeswitch can change device ID to 0408:ea26, but the usb is still storage.

Not the same storage device as in 0408:ea25 which created a sr device ie a virtual cd-rom.
0408:ea26 created a sd device ie a disk device which is for the TF/SD card in the dongle.

Why did you cut the log at that point?
There should be both a serial usb driver binding and a net usb driver binding creating linux ttyUSB devices and a linux net device.
Your log should show that.

[hunters1094]

Modeswitch can change device ID to 0408:ea26, but the usb is still storage.

Not the same storage device as in 0408:ea25 which created a sr device ie a virtual cd-rom.
0408:ea26 created a sd device ie a disk device which is for the TF/SD card in the dongle.

Why did you cut the log at that point?
There should be both a serial usb driver binding and a net usb driver binding creating linux ttyUSB devices and a linux net device.
Your log should show that.

Hi LOM

There is no more log for serial binding or net usb binding and no ttyUSB device.
These are all the lines of log for switch.

Which command can I show you more?

[Josh]

If you don't see a driver binding to the modem after the switch, then there is

1. either the "option" driver module missing on your system
2. or the "option" module is there but the kernel is so old that the USB ID of your modem is not yet built into it

The second possibility means that the driver does not 'know' your modem and does not bind to it automatically.

You can check this by loading and binding that module manually (as root or with sudo):

Code: Select all

# modprobe -v option
# echo "0408 ea26" > /sys/bus/usb-serial/drivers/option1/new_id

Then look at the output of "dmesg" again.

[LOM]

Looking at the linux drivers I see that there is no support for Quanta 1K3M yet so adding temporarily support for it by echoing the device id to the new_id function as Josh suggested will get part of the dongle working.
It is not a good longtime solution though and it will only give you a serial ppp dialup ttyUSB linux device and not a high speed net device.
Are you able to edit the source for two linux drivers and compile them afterwards?
If so, are you also willing to send in patches to the linux driver maintainers so the dongle gets linux support?

[hunters1094]

Thanks for your help. Really appreciated