[freddieventura]

Dear Community,


First of all thanks for this tool, I'm looking forward setting up my 4GLTE device, and it wouldn't be possible without the kind developers, as always guys my biggest "Domo Arigato".

So I happen to have one of these Chinese 4G LTE Wifi Modem that I saw some people having problems with
I'm willing to set up a solution if you guys can guide me a bit through the process, so I will document the case and sniff the usb if you guys are able to guide me how (I have wireshark and been fiddeling with that a bit)


$lsusb

Code: Select all

Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp.
Bus 001 Device 003: ID 0bda:57cb Realtek Semiconductor Corp.
Bus 001 Device 033: ID 05c6:6000 Qualcomm, Inc. Siemens SG75   -------------------> Target Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ sudo lsusb -v -d 05c6:6000

Code: Select all

Bus 001 Device 033: ID 05c6:6000 Qualcomm, Inc. Siemens SG75
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x05c6 Qualcomm, Inc.
  idProduct          0x6000 Siemens SG75
  bcdDevice            0.00
  iManufacturer           3 Qualcomm, Incorporated
  iProduct                2 Qualcomm CDMA Technologies MSM
  iSerial                 4 1234567890ABCDEF
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0083
    bNumInterfaces          5
    bConfigurationValue     1
    iConfiguration          1 Qualcomm Configuration
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               5
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        4
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      1
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0000
  (Bus Powered)

dmesg -T --follow

Code: Select all

[Wed Dec  2 10:18:31 2020] usb 1-2: new high-speed USB device number 108 using xhci_hcd
[Wed Dec  2 10:18:31 2020] usb 1-2: New USB device found, idVendor=05c6, idProduct=f000, bcdDevice= 0.00
[Wed Dec  2 10:18:31 2020] usb 1-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[Wed Dec  2 10:18:31 2020] usb 1-2: Product: Qualcomm CDMA Technologies MSM
[Wed Dec  2 10:18:31 2020] usb 1-2: Manufacturer: Qualcomm, Incorporated
[Wed Dec  2 10:18:31 2020] usb 1-2: SerialNumber: 1234567890ABCDEF
[Wed Dec  2 10:18:31 2020] usb-storage 1-2:1.0: USB Mass Storage device detected
[Wed Dec  2 10:18:31 2020] scsi host2: usb-storage 1-2:1.0
[Wed Dec  2 10:18:31 2020] usb 1-2: USB disconnect, device number 108
[Wed Dec  2 10:18:32 2020] usb 1-2: new high-speed USB device number 109 using xhci_hcd
[Wed Dec  2 10:18:32 2020] usb 1-2: New USB device found, idVendor=05c6, idProduct=6000, bcdDevice= 0.00
[Wed Dec  2 10:18:32 2020] usb 1-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[Wed Dec  2 10:18:32 2020] usb 1-2: Product: Qualcomm CDMA Technologies MSM
[Wed Dec  2 10:18:32 2020] usb 1-2: Manufacturer: Qualcomm, Incorporated
[Wed Dec  2 10:18:32 2020] usb 1-2: SerialNumber: 1234567890ABCDEF
[Wed Dec  2 10:18:32 2020] option 1-2:1.0: GSM modem (1-port) converter detected
[Wed Dec  2 10:18:32 2020] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0
[Wed Dec  2 10:18:32 2020] option 1-2:1.1: GSM modem (1-port) converter detected
[Wed Dec  2 10:18:32 2020] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1
[Wed Dec  2 10:18:32 2020] option 1-2:1.2: GSM modem (1-port) converter detected
[Wed Dec  2 10:18:32 2020] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2
[Wed Dec  2 10:18:32 2020] option 1-2:1.3: GSM modem (1-port) converter detected
[Wed Dec  2 10:18:32 2020] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB3
[Wed Dec  2 10:18:32 2020] usb-storage 1-2:1.4: USB Mass Storage device detected
[Wed Dec  2 10:18:32 2020] scsi host2: usb-storage 1-2:1.4
[Wed Dec  2 10:18:33 2020] scsi 2:0:0:0: Direct-Access     4G       MMC Storage      2.31 PQ: 0 ANSI: 2
[Wed Dec  2 10:18:33 2020] sd 2:0:0:0: Attached scsi generic sg1 type 0
[Wed Dec  2 10:18:33 2020] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[Wed Dec  2 10:18:51 2020] usb 1-2: USB disconnect, device number 109
[Wed Dec  2 10:18:51 2020] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[Wed Dec  2 10:18:51 2020] option 1-2:1.0: device disconnected
[Wed Dec  2 10:18:51 2020] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[Wed Dec  2 10:18:51 2020] option 1-2:1.1: device disconnected
[Wed Dec  2 10:18:51 2020] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[Wed Dec  2 10:18:51 2020] option 1-2:1.2: device disconnected
[Wed Dec  2 10:18:51 2020] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[Wed Dec  2 10:18:51 2020] option 1-2:1.3: device disconnected
[Wed Dec  2 10:18:56 2020] usb 1-2: new high-speed USB device number 110 using xhci_hcd
[Wed Dec  2 10:18:56 2020] usb 1-2: New USB device found, idVendor=05c6, idProduct=f000, bcdDevice= 0.00
[Wed Dec  2 10:18:56 2020] usb 1-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[Wed Dec  2 10:18:56 2020] usb 1-2: Product: Qualcomm CDMA Technologies MSM
[Wed Dec  2 10:18:56 2020] usb 1-2: Manufacturer: Qualcomm, Incorporated
[Wed Dec  2 10:18:56 2020] usb 1-2: SerialNumber: 1234567890ABCDEF
[Wed Dec  2 10:18:56 2020] usb-storage 1-2:1.0: USB Mass Storage device detected
[Wed Dec  2 10:18:56 2020] scsi host2: usb-storage 1-2:1.0
[Wed Dec  2 10:18:56 2020] usb 1-2: USB disconnect, device number 110
[Wed Dec  2 10:18:57 2020] usb 1-2: new high-speed USB device number 111 using xhci_hcd
[Wed Dec  2 10:18:57 2020] usb 1-2: New USB device found, idVendor=05c6, idProduct=6000, bcdDevice= 0.00
[Wed Dec  2 10:18:57 2020] usb 1-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[Wed Dec  2 10:18:57 2020] usb 1-2: Product: Qualcomm CDMA Technologies MSM
[Wed Dec  2 10:18:57 2020] usb 1-2: Manufacturer: Qualcomm, Incorporated
[Wed Dec  2 10:18:57 2020] usb 1-2: SerialNumber: 1234567890ABCDEF
[Wed Dec  2 10:18:57 2020] option 1-2:1.0: GSM modem (1-port) converter detected
[Wed Dec  2 10:18:57 2020] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0
[Wed Dec  2 10:18:57 2020] option 1-2:1.1: GSM modem (1-port) converter detected
[Wed Dec  2 10:18:57 2020] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1
[Wed Dec  2 10:18:57 2020] option 1-2:1.2: GSM modem (1-port) converter detected
[Wed Dec  2 10:18:57 2020] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2
[Wed Dec  2 10:18:57 2020] option 1-2:1.3: GSM modem (1-port) converter detected
[Wed Dec  2 10:18:57 2020] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB3
[Wed Dec  2 10:18:57 2020] usb-storage 1-2:1.4: USB Mass Storage device detected
[Wed Dec  2 10:18:57 2020] scsi host2: usb-storage 1-2:1.4
[Wed Dec  2 10:18:58 2020] scsi 2:0:0:0: Direct-Access     4G       MMC Storage      2.31 PQ: 0 ANSI: 2
[Wed Dec  2 10:18:58 2020] sd 2:0:0:0: Attached scsi generic sg1 type 0
[Wed Dec  2 10:18:58 2020] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[Wed Dec  2 10:19:17 2020] usb 1-2: USB disconnect, device number 111
[Wed Dec  2 10:19:17 2020] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[Wed Dec  2 10:19:17 2020] option 1-2:1.0: device disconnected
[Wed Dec  2 10:19:17 2020] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[Wed Dec  2 10:19:17 2020] option 1-2:1.1: device disconnected
[Wed Dec  2 10:19:17 2020] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[Wed Dec  2 10:19:17 2020] option 1-2:1.2: device disconnected
[Wed Dec  2 10:19:17 2020] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[Wed Dec  2 10:19:17 2020] option 1-2:1.3: device disconnected
[Wed Dec  2 10:19:22 2020] usb 1-2: new high-speed USB device number 112 using xhci_hcd
[Wed Dec  2 10:19:22 2020] usb 1-2: New USB device found, idVendor=05c6, idProduct=f000, bcdDevice= 0.00
[Wed Dec  2 10:19:22 2020] usb 1-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[Wed Dec  2 10:19:22 2020] usb 1-2: Product: Qualcomm CDMA Technologies MSM
[Wed Dec  2 10:19:22 2020] usb 1-2: Manufacturer: Qualcomm, Incorporated
[Wed Dec  2 10:19:22 2020] usb 1-2: SerialNumber: 1234567890ABCDEF
[Wed Dec  2 10:19:22 2020] usb-storage 1-2:1.0: USB Mass Storage device detected
[Wed Dec  2 10:19:22 2020] scsi host2: usb-storage 1-2:1.0
[Wed Dec  2 10:19:22 2020] usb 1-2: USB disconnect, device number 112
[Wed Dec  2 10:19:23 2020] usb 1-2: new high-speed USB device number 113 using xhci_hcd
[Wed Dec  2 10:19:23 2020] usb 1-2: New USB device found, idVendor=05c6, idProduct=6000, bcdDevice= 0.00
[Wed Dec  2 10:19:23 2020] usb 1-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[Wed Dec  2 10:19:23 2020] usb 1-2: Product: Qualcomm CDMA Technologies MSM
[Wed Dec  2 10:19:23 2020] usb 1-2: Manufacturer: Qualcomm, Incorporated
[Wed Dec  2 10:19:23 2020] usb 1-2: SerialNumber: 1234567890ABCDEF
[Wed Dec  2 10:19:23 2020] option 1-2:1.0: GSM modem (1-port) converter detected
[Wed Dec  2 10:19:23 2020] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB0
[Wed Dec  2 10:19:23 2020] option 1-2:1.1: GSM modem (1-port) converter detected
[Wed Dec  2 10:19:23 2020] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB1
[Wed Dec  2 10:19:23 2020] option 1-2:1.2: GSM modem (1-port) converter detected
[Wed Dec  2 10:19:23 2020] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB2
[Wed Dec  2 10:19:23 2020] option 1-2:1.3: GSM modem (1-port) converter detected
[Wed Dec  2 10:19:23 2020] usb 1-2: GSM modem (1-port) converter now attached to ttyUSB3
[Wed Dec  2 10:19:23 2020] usb-storage 1-2:1.4: USB Mass Storage device detected
[Wed Dec  2 10:19:23 2020] scsi host2: usb-storage 1-2:1.4
[Wed Dec  2 10:19:24 2020] scsi 2:0:0:0: Direct-Access     4G       MMC Storage      2.31 PQ: 0 ANSI: 2
[Wed Dec  2 10:19:24 2020] sd 2:0:0:0: Attached scsi generic sg1 type 0
[Wed Dec  2 10:19:24 2020] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[Wed Dec  2 10:19:44 2020] usb 1-2: USB disconnect, device number 113
[Wed Dec  2 10:19:44 2020] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[Wed Dec  2 10:19:44 2020] option 1-2:1.0: device disconnected
[Wed Dec  2 10:19:44 2020] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[Wed Dec  2 10:19:44 2020] option 1-2:1.1: device disconnected
[Wed Dec  2 10:19:44 2020] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[Wed Dec  2 10:19:44 2020] option 1-2:1.2: device disconnected
[Wed Dec  2 10:19:44 2020] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[Wed Dec  2 10:19:44 2020] option 1-2:1.3: device disconnected

The usb is not listed on the tar-ball with known devices

/usr/share/usb_modeswitch$ tar tf configPack.tar.gz | grep 05c6

Code: Select all

05c6:0010
05c6:1000:sVe=GT
05c6:1000:sVe=Option
05c6:1000:uMa=AnyDATA
05c6:1000:uMa=CELOT
05c6:1000:uMa=Co.,Ltd
05c6:1000:uMa=DGT
05c6:1000:uMa=Option
05c6:1000:uMa=SAMSUNG
05c6:1000:uMa=SSE
05c6:1000:uMa=StrongRising
05c6:1000:uMa=Vertex
05c6:2000
05c6:2001
05c6:6503
05c6:9024
05c6:98ff
05c6:f000

Plus I didnt find any rules existent for a device such as 05c6:6000
:/lib/udev/rules.d$ sudo vim 40-usb_modeswitch.rules

I try adding the following to the usb_modeswitch.conf in order to make it initiate
Probiding the data I've got from previous outputs I can fill the following

Code: Select all

DefaultVendor= 0x05c6
DefaultProduct= 0x6000
TargetVendor= 0x05c6
TargetProduct= 0x6000

I lack of the MessageContent though, so I google it and find the following
https://myopenhab.wordpress.com/2017/06 ... odeswitch/

Code: Select all

usb_modeswitch -v 05c6 -p 1000-V 05c6 -P 6000 -M 55534243123456780000000000000011060000000000000000000000000000

I take that number right after the M as the Message content

Code: Select all

MessageContent="55534243123456780000000000000011060000000000000000000000000000"

I try to proceed then with usb_modeswitch now and


$ sudo usb_modeswitch -c /etc/usb_modeswitch.conf

Code: Select all

Look for target devices ...
 Found devices in target mode or class (1)
Look for default devices ...
 Found devices in default mode (1)
Access device 033 on bus 001
Get the current device configuration ...
Current configuration number is 1
Use interface number 0
 with class 255
Error: can't use storage command in MessageContent with interface 0; interface class is 255, expected 8. Abort

I don't know what I am missing in here , but any information leading me to sth would be highly appreciated

B.R.

[LOM]

Your device, when it is in default mode, has the USB Id 05c6:f000 and that Id is supported for switching by usb_modeswitch then it gets the Id 05cf6:6000 after being switched.
Trying to switch 05c6:6000 is futile and trying to switch a USB Id you do not have (05c6:1000) is equally futile.

Your dmesg shows successful switchings, USB serial drivers binding and creating ttyUSB's, but the dongle falls off the USB bus and returns in default mode, if it isn't you plugging/unplugging the dongle multiples time then it is probably your USB port that can not provide enough power to the dongle.

Are you sure that your dongle also has wifi built-in? The interface layout looks like it is an old-fashion dial-up modem without wifi (which most of the 05c6:6000 are)

[freddieventura]

Well it should have wifi , according to the specs.
Though I don't mind not being able to use the Wifi cause I don't essentially need it (though it would be fine if it works)
(See pics https://imgur.com/a/uz4B1i3 )
According to the Powering , is weird, I also noticed that (the plug in and unplug straightaway), I'm using a laptop USB port , so it should be fine I guess.
I'm gonna try though checking on a Desktop with Windows 10 Installed to see if it works or its faulty.

[LOM]

Ok, the print on the casing says it has wifi. Can you see it transmitting the SSID? Can you connect to it?

[freddieventura]

Yes , I can actually see the SSID: Das Kapital 4G . So the previous owner changed the default SSID , also the password.
(yes is a second hand 4G LTE). I've just contacted the guy and he told me that he forgot his password (probably he doesn't want to hand it over to me or sth). He is guiding me that with the drivers I will be able to set this Wifi Hotspot back.
So I'm going to check this with a Windows 10 computer and will get to you back with more findings.
Thanks!

[AtomX]

I think it's usb-modeswitch problem because it suspends the USB Dongle for several minutes. And can't configure properly dual mode (WiFi and Cellular data) USB Dongle.

[LOM]

I think it's usb-modeswitch problem because it suspends the USB Dongle for several minutes. And can't configure properly dual mode (WiFi and Cellular data) USB Dongle.

usb_modeswitch will only switch the dongle from its initial mode 05c6:f000 into 05c6:6000, after that it leaves the arena.
Whatever happens thereafter has nothing to do with usb_modeswitch.

05c6:6000 is an indistinguishable USB Id, it and its companion initial id 05c6:f000 are "transport Id's" generated by Qualcomm so that a vendor can easily test the received batches before programming them with the vendors own Id (VID and PID).
It is not intended that a vendor should resell a device without changing the Id but some careless vendor do, mainly because it is expensive to register for a unique VID.
The 05c6:6000 Id has been used for at least 15 years and covers device from old CDMA-only dongles up to modern LTE devices and MiFi devices like yours.
The interfaces has different usage between these ancient, old, and recent devices so when linux is using the option driver then it is correct for old devices but probably not for new LTE devices.
I don't expect an LTE device to be an old fashion slow speed serial ppp modem, there ought to be a direct net interface in them instead but the problem is that linux can not distinguish between one 05c6:6000 device and another.

You would not had been in this situation if you had bought your dongle from a known brand manufacturer instead of from some obscure Chinese reseller.

[AtomX]

I think it's usb-modeswitch problem because it suspends the USB Dongle for several minutes. And can't configure properly dual mode (WiFi and Cellular data) USB Dongle.

usb_modeswitch will only switch the dongle from its initial mode 05c6:f000 into 05c6:6000, after that it leaves the arena.
Whatever happens thereafter has nothing to do with usb_modeswitch.

I don't know for sure, but the moment I disabled usb-modeswitch my device's WiFi worked (Though keeps switching between 4G to 3G...) But it's working. And that doesn't explain why all USB Dongle I've used on Ubuntu are suspended for several minutes before working.

Chinese guys maybe be little shady, but they know how to do the job right. They are the most reliable people for buying and manufacturing things for reasonable price.

[LOM]

I don't know for sure, but the moment I disabled usb-modeswitch my device's WiFi worked (Though keeps switching between 4G to 3G...) But it's working. And that doesn't explain why all USB Dongle I've used on Ubuntu are suspended for several minutes before working.

You must be hit by bad luck, I have around 30 dongles and also 35-40 3G pci cards and all of them starts up almost immediately on the 4 flavors of linux distros I have installed (Ubuntu is one of them).
These Mobile Broadband dongles/cards are all from well known vendors.

Chinese guys maybe be little shady, but they know how to do the job right. They are the most reliable people for buying and manufacturing things for reasonable price.

Almost all Mobile Broadband dongles/cards are manufactured in China, that is not the problem, the Chinese vendors knowledge and the support they can give you is what makes a huge difference between them.

Did you get a Users Manual with your dongle? Can your vendor send you one if you request it?
An AT-cmd manual?
Does he know how to switch your device can he give you the USB switch message to do it?
Does he know how the USB tethering is supposed to work?

I guess the answer to all those questions is a No and that is because you have bought your dongle from a sales company that is mainly interested in selling them to MS Windows users for which there is drivers and a connection manager with built in switch utility on the virtual cd-rom which appears in the dongles initial mode before being switched.
Your seller is not interested in linux, may not even know what it is, and can definitely not give you any help in getting the device work in linux.

Linux support for Mobile Broadband devices is what I and a bunch of other people has to figure out mostly without any help from the manufacturers but instead based on collected info from users after a device appears on the market.
Don't blame us, don't blame linux when your not satisfied with the working of your device, blame the manufacturers who are not interested in linux support, who doesn't lift a finger to get their devices linux supported before they start to sell them and who expect that someone at some time voluntarily will add linux support for them.

[LOM]

(Though keeps switching between 4G to 3G...)

That is what Mobile Broadband devices do when the antenna signal varies, it has nothing todo with USB, usb_modeswitch, or linux.

[AtomX]

I don't know for sure, but the moment I disabled usb-modeswitch my device's WiFi worked (Though keeps switching between 4G to 3G...) But it's working. And that doesn't explain why all USB Dongle I've used on Ubuntu are suspended for several minutes before working.

You must be hit by bad luck, I have around 30 dongles and also 35-40 3G pci cards and all of them starts up almost immediately on the 4 flavors of linux distros I have installed (Ubuntu is one of them).
These Mobile Broadband dongles/cards are all from well known vendors.

Chinese guys maybe be little shady, but they know how to do the job right. They are the most reliable people for buying and manufacturing things for reasonable price.

Almost all Mobile Broadband dongles/cards are manufactured in China, that is not the problem, the Chinese vendors knowledge and the support they can give you is what makes a huge difference between them.

Did you get a Users Manual with your dongle? Can your vendor send you one if you request it?
An AT-cmd manual?
Does he know how to switch your device can he give you the USB switch message to do it?
Does he know how the USB tethering is supposed to work?

I guess the answer to all those questions is a No and that is because you have bought your dongle from a sales company that is mainly interested in selling them to MS Windows users for which there is drivers and a connection manager with built in switch utility on the virtual cd-rom which appears in the dongles initial mode before being switched.
Your seller is not interested in linux, may not even know what it is, and can definitely not give you any help in getting the device work in linux.

Some of them indeed had Ubuntu (proprietary) support packages and UI Wizard for installation. I have one from ZTE, nearly same thing happens... And that doesn't explain why my USB ports power, which I attach mobile broadband, are suspended for long time... And the vendors said it was supposed to 'just work' like on macOS. Both macOS and Linux has implicit support.

About user manual, the dongle box came with it, but it was Windows's centric. It still is on warranty timeline, I think I'll ask refund. They lied to me, when they said it'd 'just work' well on Ubuntu.

I'm talking about recently manufactured mobile broadband, from explicit to implicit support is nearly same thing.

My ports are USB 3.1 all of them.

[AtomX]

(Though keeps switching between 4G to 3G...)

That is what Mobile Broadband devices do when the antenna signal varies, it has nothing todo with USB, usb_modeswitch, or linux.

It seems. I didn't try mobile broadband connection yet, but I'll check it out.

[AtomX]

I don't know for sure, but the moment I disabled usb-modeswitch my device's WiFi worked (Though keeps switching between 4G to 3G...) But it's working. And that doesn't explain why all USB Dongle I've used on Ubuntu are suspended for several minutes before working.

You must be hit by bad luck, I have around 30 dongles and also 35-40 3G pci cards and all of them starts up almost immediately on the 4 flavors of linux distros I have installed (Ubuntu is one of them).
These Mobile Broadband dongles/cards are all from well known vendors.

Chinese guys maybe be little shady, but they know how to do the job right. They are the most reliable people for buying and manufacturing things for reasonable price.

Almost all Mobile Broadband dongles/cards are manufactured in China, that is not the problem, the Chinese vendors knowledge and the support they can give you is what makes a huge difference between them.

Did you get a Users Manual with your dongle? Can your vendor send you one if you request it?
An AT-cmd manual?
Does he know how to switch your device can he give you the USB switch message to do it?
Does he know how the USB tethering is supposed to work?

I guess the answer to all those questions is a No and that is because you have bought your dongle from a sales company that is mainly interested in selling them to MS Windows users for which there is drivers and a connection manager with built in switch utility on the virtual cd-rom which appears in the dongles initial mode before being switched.
Your seller is not interested in linux, may not even know what it is, and can definitely not give you any help in getting the device work in linux.

Some of them indeed had Ubuntu (proprietary) support packages and UI Wizard for installation. I have one from ZTE, nearly same thing happens... And that doesn't explain why my USB ports power, which I attach mobile broadband, are suspended for long time... And the vendors said it was supposed to 'just work' like on macOS. Both macOS and Linux has implicit support.

I'm talking about recently manufactured mobile broadband, from explicit to implicit support is nearly same thing.

My ports are USB 3.1 all of them.

Irony of life is that most of computer systems components are meant for Windows, but Linux community is well known for it's magical art in 'reverse engineering'. Believe or not, they all can work well on Linux, in some rare cases, even little better than in Windows.

[devdevdev]

Hi everybody.
I'm so happy to find this thread.
Quick dislaimer. I'm not as experienced in linux as you guys seem to be. I love the linux enviorement but i'm really a beginner. I do know my way around code in generel and i do kinda know my way around the linux terminal. So i appoligize in advance for any n00b moves and apprechiate any kind of help and knowledge sharring.

https://www.av-cables.dk/3g-usb-modem/4 ... -hvid.html
I just bought a couple of this model thinking it would work on my Rasp pi running linux. I have other 4g usb dongle which work fine. The model of this topic though has the "wifi dongle" feauture which i'm not interested in. I need the usb device to function as a usb 4g dongle - without the wifi part.

Plugging the dongle in to a win10 machine reveals this is possible but you have to install the UI and then switch to usb mode from the setting. If needed i can provide screenshots of this.

There is also the possibility of connecting to the SSID the device creates on boot but it is not possible to switch from wifi mode to usb mode from here.

Novice as i am, i tried installing the software via wine. The software installs fine but the drivers don't install.

This is where i hope you guys can help?

@freddyventura - Your last comment indicated you had trouble accessing the wifi http setup page. Did you get access? I have acces to mine if you need anything from there.

Basicly i'm hoping to find some kind of driver for the device for ubuntu or, even better, a way to switch the device to usb mode from termial. Is this a possible?

Best regards.


This is my output:
$ sudo usb_modeswitch -W -v 05c6 -p 6000 -K
Take all parameters from the command line


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

! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor= 0x05c6
DefaultProduct= 0x6000

StandardEject=1

Look for default devices ...
found USB ID 05c6:6000
vendor ID matched
product ID matched
found USB ID 1d6b:0002
found USB ID 80ee:0021
found USB ID 1d6b:0001
Found devices in default mode (1)
Access device 005 on bus 001
Get the current device configuration ...
Current configuration number is 1
Use interface number 0
with class 255
Error: can't use storage command in MessageContent with interface 0; interface class is 255, expected 8. Abort

[LOM]

Error: can't use storage command in MessageContent with interface 0; interface class is 255, expected 8. Abort

This tells us that the dongle is not in initial mode, it has already been switched and is ready to be used.