[devdevdev]

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.

For some reason the modem device keeps "rebooting" now - if i set disableswitching=1 the devices stays as 05c6:f000

And everytime i run "sudo usb_modeswitch -W -v 05c6 -p f000 -K" the dongle reboots.

What am i doing wrong?

[devdevdev]

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.

Is there a reason why the usb dongle keeps rebooting when connecting it to ubuntu? It seems like usb-modeswitch is in a loop when on ubuntu. When running on openwrt it also happens but not like on ubuntu.

Also - i have read thas Ndiswrapper can be used to convert windows drivers to linux drivers. Is this also possible with 4g modem drivers or is it only for wifi drivers?

[LOM]

For some reason the modem device keeps "rebooting" now - if i set disableswitching=1 the devices stays as 05c6:f000

And everytime i run "sudo usb_modeswitch -W -v 05c6 -p f000 -K" the dongle reboots.

What am i doing wrong?

Automatic invoke of usb_modeswitch is disabled, the cmd you run manually will switch the device and usb_modeswitch will then exit, wWhatever happens afterwards has nothing to do with usb_modeswitch.
I guess that your usb port can not supply enough current to the modem so it resets itself.

[LOM]

Is there a reason why the usb dongle keeps rebooting when connecting it to ubuntu? It seems like usb-modeswitch is in a loop when on ubuntu. When running on openwrt it also happens but not like on ubuntu.

If the modem resets itself then it will return in initial mode and be detected by the kernel as new device arriving, it will then be switched again by usb_modreswitch. Exactly same effect as if you unplug and replug the modem.

Also - i have read thas Ndiswrapper can be used to convert windows drivers to linux drivers. Is this also possible with 4g modem drivers or is it only for wifi drivers?

I have no idea but why would you do that? linux has all the native drivers you need for this modem.

[devdevdev]

For some reason the modem device keeps "rebooting" now - if i set disableswitching=1 the devices stays as 05c6:f000

And everytime i run "sudo usb_modeswitch -W -v 05c6 -p f000 -K" the dongle reboots.

What am i doing wrong?

Automatic invoke of usb_modeswitch is disabled, the cmd you run manually will switch the device and usb_modeswitch will then exit, wWhatever happens afterwards has nothing to do with usb_modeswitch.
I guess that your usb port can not supply enough current to the modem so it resets itself.

Turns out Modemmanager was at fault. When uninstalling modemmanager the rebooting / resetting of the usb device stops.

I'm trying different software to find the best solution for this modem. But i'm starting to think i have to replaces the usb modem since i cannot get it to connect with LTE. I have only succeeded with 3g connection and it is very unstable since i often just stops transmitting data through the usb even thoug the LED indicates it i stil connected.

[devdevdev]

Is there a reason why the usb dongle keeps rebooting when connecting it to ubuntu? It seems like usb-modeswitch is in a loop when on ubuntu. When running on openwrt it also happens but not like on ubuntu.

If the modem resets itself then it will return in initial mode and be detected by the kernel as new device arriving, it will then be switched again by usb_modreswitch. Exactly same effect as if you unplug and replug the modem.

Like i wrote just before this reply it turned out that modemmanager was making the device loop reset/restart.

Also - i have read thas Ndiswrapper can be used to convert windows drivers to linux drivers. Is this also possible with 4g modem drivers or is it only for wifi drivers?

I have no idea but why would you do that? linux has all the native drivers you need for this modem.

Does it? Could you point me in the right direction of getting it to connect with LTE and stay connected?
I thought Ndiswrapper could help produce the correct drivers - guess that was a bad idea...

[LOM]

Could you point me in the right direction of getting it to connect with LTE and stay connected?

The type of connection is not driver dependent, the modem negotiates the best connection with the tower.
There are AT cmds for restricting connection type to 3G, GPRS, GSM but the default is to use the best available type.

If you've read this thread then you know that 05c6:6000 is USB Id used by many different modems so the USB interface composition and usage is not unique, the interface list I have for this USB Id is quite old and will most likely not match your modem.

I need the Windows .inf files from your card in order to tell you which linux drivers the card needs, those .inf files are available in the software you can find on the virtual cd-rom the modem presents (05c6:f000) before getting switched by usb_modeswitch.
You can also find them in the Windows system directory for drivers after installing the modem on a Windows computer, if unsure then look at the date column in the directory which shows the install date.
It would also be interesting to know what the USB Id of the modem is under Windows.

[knfevg]

Got the same type of modem. Trying to make it usable in Ubuntu 18.04

Attached the windows log:

ModemLog_RELINK USB Modem 6000.txt

(8.25 KiB) Downloaded 370 times

Here is the INF file:

oem146.inf

(49.67 KiB) Downloaded 352 times

After fixing the switch message to :555342431234567890ABCDEF80000671030000000000000000000000000000 I think it started switching properly:

usb_modeswitch.log

(4.31 KiB) Downloaded 353 times

After this WVDIAL "locates" the mode:

--> WvDial: Internet dialer version 1.61
--> Initializing modem.
--> Sending: ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Configuration does not specify a valid phone number.
--> Configuration does not specify a valid login name.
--> Configuration does not specify a valid password.

But Network manager in Ubuntu still doesnt see it....
I can use WVDIAL but thats kinda "ol'school".... any way to make Netowrk Manager see it correctly?

There is an issue, however, that for some reason the devices keeps disconnecting and reconnecting back to the USB... which is strange.. dont see any reason it happens and it doesnt sounds reasonable that it consumes more than 0.5A power and the Desktop (not even a laptop) cannot support it's power requirements

[LOM]

Got the same type of modem. Trying to make it usable in Ubuntu 18.04

Attached the windows log:
ModemLog_RELINK USB Modem 6000.txt

Here is the INF file:
oem146.inf

Only one .inf file? This one is for the modem interface but there are a couple of other serial interfaces which also should have one or more .inf files.
The modem .inf file is obviously "borrowed" from Longcheer (vendor id 1C9E) and has two Qualcomm vendor id's added in it.
This Longcheer .inf file version 2.0.0.0 is from somewhere around 2008-2009 so whoever "borrowed" it also changed the date to 2015 in order to make it look more recent.

After fixing the switch message to :555342431234567890ABCDEF80000671030000000000000000000000000000 I think it started switching properly:
usb_modeswitch.log

The bytes you changed in the switch message does not change switching success.

After this WVDIAL "locates" the mode:

--> WvDial: Internet dialer version 1.61
--> Initializing modem.
--> Sending: ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Configuration does not specify a valid phone number.
--> Configuration does not specify a valid login name.
--> Configuration does not specify a valid password.

But Network manager in Ubuntu still doesnt see it....
I can use WVDIAL but thats kinda "ol'school".... any way to make Netowrk Manager see it correctly?

Networkmanager can only see and work with linux net devices, in your case it would be ppp0 after it has been created.
ModemManager is the standard linux software that handles initialization of modems but you can probably also let wvdial do it.

[knfevg]

Ok, I'll try to use ModemManager. Do all 05c6:6000 work only as serial modems or do they have a mode for Network device?
And I also need to solve the things with the USB disconnects.

[LOM]

Ok, I'll try to use ModemManager. Do all 05c6:6000 work only as serial modems or do they have a mode for Network device?
And I also need to solve the things with the USB disconnects.

There are so many different type of mobile broadband dongles sold with the 05c6:f000/6000 id by chinese pedlars, some are only serial dialup modems, some have direct net interfaces.
The Windows .inf files which gets installed from the virtual cdrom in 05c6:f000 is the most reliable info for determining what device an interface is intended for. You can copy out the content of the virtual cd-rom and get the .inf files, if it contains a single .exe file then it can usually be unpacked with 7-zip.

[knfevg]

Here you go, fished these out....

[LOM]

Here you go, fished these out....

1 serial modem interface + 3 additional serial interfaces.
This is some very old snail speed device, I'd guess 3.6/0.38 Mbps

interface info here, matches your .inf files:
https://driverlookup.com/hardware-id/us ... 6&pid_6000

[knfevg]

Really? Strange, it's an LTE with WiFi....

[LOM]

Really? Strange, it's an LTE with WiFi....

A MiFi dongle with .inf files dated 2009 without .inf file for a net device..

I guess everything is possible when a chinese company buys dongles from Qualcomm, dongles preprogrammed during manufacturing with a default USB Id's and where it is intended that the buyer shall reprogram them using his own vendor id that he has paid much money to get from the USB-IF organization.
Oh, he hasn't, he just peddles them to the end user with the default USB Id intact and that is why there since 15 years back exists fiftyeleven different version of 05c6:6000 on the market..

Most MiFi dongles are NAT'ed routers where the LAN subnet is shared between the WiFi and a USB net device which a host computer can teether to and get an IP address from the LAN subnet.
Show me the output from lsusb -vd 05c6:6000 so I can see if the very old .inf files you submitted matches the actual device and if there are additional interfaces not covered by those two .inf files.
LTE speeds are much higher than what you can achieve over serial ppp dialup so they need a net interface, all LTE dongles I know of has one. Many of them does not have a serial ppp modem interface since it is basically useless for LTE.