[aiamuzz]

Hi,

back again ... just wanted to get some info ...
My device is running fine after installing network-manager-gnome and connecting my device through the same. However my OS Deepin 15.4.1 still lacks native support as this device still fails to populate in the OS's network device list.

However my OS uses the 'wwp0s26u1u5i6' interface instead of 'wwan' ... Initially my device used to connect as wwp0s26u1u5i6 interface, this let me monitor traffic/bandwidth through a combination of 'vnstat' & a great conky script.

All of a sudden, since the last few days, vnstat has stopped recording the wwp0s26u1u5i6 interface ... my conky stopped displaying network info as a result.

My Mobile Broadband continues to work however and i am writing this post through the same connection.
Deepin's native 'network details' settings shows this device's interface as 'ttyUSB0' ... i guess that explains 'vnstat' and conky network info dysfunctional.

Is it possible to manually switch to 'wwp0s26u1u5i6' interface instead of the current 'ttyUSB0' interface ?

usb-devices

Code: Select all

T:  Bus=03 Lev=02 Prnt=02 Port=04 Cnt=02 Dev#=  4 Spd=480 MxCh= 0
D:  Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=03f0 ProdID=421d Rev=00.00
S:  Manufacturer=Novatel Wireless, Inc.
S:  Product=HP lt2523 Mobile Broadband Device
S:  SerialNumber=359789040033051
C:  #Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I:  If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I:  If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I:  If#= 6 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=qmi_wwan
I:  If#= 7 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=qmi_wwan

thanks.

[Josh]

The device name has nothing to do with the mode switching. It is assigned by the kernel alone.

However, you can change the name to what you like, by using "udev rules". Once your rule is in place, the originally assigned kernel name will be changed automatically.

You will find plenty of information about how to do this. Just google "udev rules kernel name".

[aiamuzz]

i have no issue with interface names 'wwan' to 'wwp0s26u1u5i6' ... both of them are fine ... my concern is how do i get the 'ttyUSB0' change to either 'wwan or 'wwp0s26u1u5i6' ... can this too be done by the udev method you are suggesting ?

[Josh]

Yes, it can.

ttyUSB is the underlying device, wwan etc. is a configured network device that is based on ttyUSB. So you don't have to worry about ttyUSB at all.

[aiamuzz]

no worries as such ... just want the interface to work as 'wwan' or 'wwp0s26u1u5i6' as if its either of the 2 then 'vnstat' records traffic/bandwith used and as a result i'll have my conky graphs up and working ... that is all ...

[aiamuzz]

Hi,

I am back ... this forum helped me to get my card up and running ... since then i have moved away from ubuntu and currently using Deepin OS, (4.15.0-29deepin-generic x86_64) ... this card has worked without issues out of the box ...

but off late may be since the last few updates ... i have seen that its getting loaded as

Code: Select all

cdc_wdm0

the device does shows up in the nm-applet as Mobile Broadband ... and the command 'usb-devices' throws up the following ... seems the binding is correct ...

Code: Select all

Bus=01 Lev=02 Prnt=02 Port=04 Cnt=02 Dev#=  4 Spd=480 MxCh= 0
Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs=  1
Vendor=03f0 ProdID=421d Rev=00.00
Manufacturer=Novatel Wireless, Inc.
Product=HP lt2523 Mobile Broadband Device
SerialNumber=359789040033051
#Ifs= 7 Cfg#= 1 Atr=e0 MxPwr=500mA
If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
If#= 4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
If#= 6 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=00 Driver=qmi_wwan
If#= 7 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=qmi_wwan

but the Modem Manager GUI shows as the attached device is 'cdc_wdm0' ... snapshot below ...

cdc_wdm0

DeepinScreenshot_modem-manager-gui_20190107200107.png (28.79 KiB) Viewed 13798 times

when its loaded as ... cdc_wdm0 ... i am unable to connect to the data ... sms works through 'Modem Manager GUI' application ...


I am able to connect only when its loaded as

Code: Select all

ttyUSB0

... like how its connected here ...

BB Issue - DeepinScreenshot_modem-manager-gui_20190107152119.png (28.44 KiB) Viewed 13798 times

...

I was actually lost completely with my data no longer connecting ... i was just lucky that i had an older version of this OS on my system as the 4th OS ... when i booted into that i found that 'ttyUSB0' was attached and data worked ... and when i restarted from this older version OS into the current one ... then the current one attached corrrectly as 'ttyUSB0' ... Please note that if i boot after shutting down into the current version of the OS it attaches as 'cdc_wdm' ... the only way i can get the current version of OS to attach correctly as 'ttyUSB0' is only if i boot into the older version of the OS and reboot from that into the current version OS !!!

Can you please help me on how i can detach 'cdc_wdm0' and reattach as 'ttyUSB0' ?
I can't keep booting into the older version OS every time and boot into the current version from there to get my data working !

thanks.

[aiamuzz]

@josh ... @bmork ... @survient ... anybody active on the forum ?

a way i can switch cdc-wdm0 to ttyUSB0 would be most appreciated !

[Josh]

This looks like an issue in the distribution.

The network manager should detect the cdc driver that has bound to the modem.
It should also know what to do with QMI modems.

If you can't get a bugfix for the problem by the maintainers, try to manually (scripted) connect. There are tools like "qmicli", or maybe you can find a more comfortable tool/script that works on the command line.

Once the connection works, it's likely a bit faster and with less latency than when using pppd over a serial port.

[aiamuzz]

This looks like an issue in the distribution.

thanks for the reply josh ...
the distribution team is not very proactive when it comes to WWAN modules and supporting them as its a new distro ... and their priorities are different currently. I have raised the ticket ... but don't expect a quick response though. In fact their network settings don't even detect this card ... I am using nm-applet to manage this device.

The network manager should detect the cdc driver that has bound to the modem.
It should also know what to do with QMI modems.

If you can't get a bugfix for the problem by the maintainers,

Once the connection works, it's likely a bit faster and with less latency than when using pppd over a serial port.
try to manually (scripted) connect. There are tools like "qmicli", or maybe you can find a more comfortable tool/script that works on the command line.

I am a non-techy ... so you may have to give me a step-by-step guide on how i can successfully connect to data ... currently only ttyUSB0 on pppoe works ... i am concerned only with a consistent working data connection.

So if you could help me get one by any means and a way out of situations like this ... i am content with it.

thanks

[Josh]

I have googled and found this:
https://github.com/penguin2716/qmi_setup

Just make sure you can run the command line program "qmicli" on your computer.
If it's not available, look for a package that has "libqmi" in its name.

[aiamuzz]

I have googled and found this:
https://github.com/penguin2716/qmi_setup

Just make sure you can run the command line program "qmicli" on your computer.
If it's not available, look for a package that has "libqmi" in its name.

which one ...

Code: Select all

sudo apt-get install libqmi-
libqmi-glib1      libqmi-glib1-dbg  libqmi-glib5      libqmi-glib-dev   libqmi-glib-doc   libqmi-proxy      libqmi-utils

[aiamuzz]

further it says ...

You have to prepare the kernel modules
qmi_wwan (CONFIG_USB_NET_QMI_WWAN)
qcserial (CONFIG_USB_SERIAL_QUALCOMM)

how do you prepare 'qcserial' and load it ?

[Josh]

You don't need to do all that because you already see the cdc_wdm0 port. That means the driver has bound to the modem.

Any reasonably current kernel should know what to do with this modem.

[aiamuzz]

You don't need to do all that because you already see the cdc_wdm0 port. That means the driver has bound to the modem.

Any reasonably current kernel should know what to do with this modem.

what about 'libqmi' package ... even that isn't needed to be installed ?
if it is then which one 'glib1' or 'glib5'

[Josh]

I would install "libqmi-utils" and any dependencies (which should come automatically).