Author Topic: [SOLVED] ZTE MF190 Pocket Modem and wvdial  (Read 1292 times)

Offline cjcboy2

  • Full Member
  • ***
  • Posts: 122
[SOLVED] ZTE MF190 Pocket Modem and wvdial
« on: December 11, 2012, 11:06:34 PM »
Hi there!

I hope you can help to configure this one.

Apparently I am using a dialer (wvdial) which I installed in my system. It works perfectly on my old stick which is Huawei E153 model.

When I changed my modem to ZTE one, it is not being detected anymore that I have this error:

===========================================
--> WvDial: Internet dialer version 1.61
--> Cannot open /dev/ttyUSB0: No such file or directory
--> Cannot open /dev/ttyUSB0: No such file or directory
--> Cannot open /dev/ttyUSB0: No such file or directory
===========================================

Using lsusb command, it showed:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 003: ID 04b3:3025 IBM Corp.
Bus 002 Device 004: ID 04ca:0061 Lite-On Technology Corp.
Bus 002 Device 015: ID 19d2:1216 ZTE WCDMA Technologies MSM
Bus 002 Device 008: ID 2006:0001  


and:


[root@localhost rules.d]#  dmesg | grep tty
console [tty0] enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
usb 1-1.4: GSM modem (1-port) converter now attached to ttyUSB0
usb 1-1.4: GSM modem (1-port) converter now attached to ttyUSB1
usb 1-1.4: GSM modem (1-port) converter now attached to ttyUSB2
usb 1-1.4: GSM modem (1-port) converter now attached to ttyUSB3
option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
cdc_acm 2-1.8:1.1: ttyACM0: USB ACM device
cdc_acm 2-1.8:1.3: ttyACM1: USB ACM device
cdc_acm 2-1.8:1.5: ttyACM2: USB ACM device
cdc_acm 2-1.8:1.7: ttyACM3: USB ACM device
cdc_acm 2-1.8:1.1: ttyACM0: USB ACM device
cdc_acm 2-1.8:1.3: ttyACM1: USB ACM device
cdc_acm 2-1.8:1.5: ttyACM2: USB ACM device
cdc_acm 2-1.8:1.7: ttyACM3: USB ACM device
usb 2-1.8: GSM modem (1-port) converter now attached to ttyUSB0
usb 2-1.8: GSM modem (1-port) converter now attached to ttyUSB1
usb 2-1.8: GSM modem (1-port) converter now attached to ttyUSB2
option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
cdc_acm 2-1.8:1.1: ttyACM0: USB ACM device
cdc_acm 2-1.8:1.3: ttyACM1: USB ACM device
cdc_acm 2-1.8:1.5: ttyACM2: USB ACM device
cdc_acm 2-1.8:1.7: ttyACM3: USB ACM device


My configs are as follows:

I have this file /etc/udev/rules/25-zte-mf622.rules that has this:

ACTION!="add", GOTO="End"
SUBSYSTEM=="usb", SYSFS{idProduct}=="2000",
SYSFS{idVendor}=="19d2", GOTO="ZeroCD"
SUBSYSTEM=="usb", SYSFS{idProduct}=="0001",
SYSFS{idVendor}=="19d2", GOTO="Modem"
LABEL="ZeroCD"
RUN+="/sbin/rmmod usb_storage"
LABEL="Modem"
RUN+="/sbin/modprobe usbserial vendor=0x19d2 product=0x0001",
MODE="660", GROUP="dialout"
LABEL="End"


and

/etc/providerConfigs.conf which is being called thru this command:

wvdial --config=/etc/providerConfigs.conf

that config is my provider's default for me to connect to their network


I am seeing that this might be hardware driver / device driver issue.

Hoping for you assistance

Regards

Jessie










« Last Edit: January 15, 2013, 04:47:25 PM by cjcboy2 »
..the depth of your passion is far more important than the height of your ambition...

Offline pupthai

  • Hero Member
  • *****
  • Posts: 1426
  • PCLinuxOS 2011 2 - KDE4
Re: ZTE MF190 Pocket Modem and wvdial
« Reply #1 on: December 12, 2012, 01:17:21 AM »
I had problems with the MF190 at first - some of your post looks the same as back then, but it works now.  All I had to do when I tried it again a few mouths and updates later was plug it in and in network manager follow the set-up as my provider was listed.  It was listed before when it didn't work too, but something changed and it works without any hassle to set up now. 

Did you follow this one yet?  It has some suggests about what needs to be installed and kernel level etc.
http://www.pclinuxos.com/forum/index.php/topic,92897.0.html
PCLinuxOS 2011 2 - KDE4
Intel 2 core duo @3.22gig, Asus P5G41/M, DDR2/1066 4gig, ENGT220 DDR3/1gig, 2x Seagate 250gig.

Offline cjcboy2

  • Full Member
  • ***
  • Posts: 122
Re: ZTE MF190 Pocket Modem and wvdial
« Reply #2 on: December 12, 2012, 01:30:06 AM »
Will go ahead and check this out. Will post update as soonest

Thanks
..the depth of your passion is far more important than the height of your ambition...

Offline cjcboy2

  • Full Member
  • ***
  • Posts: 122
Re: ZTE MF190 Pocket Modem and wvdial [Solved]
« Reply #3 on: December 12, 2012, 03:20:13 AM »
Great tip! It is working now.

Thanks a lot!

Regards
..the depth of your passion is far more important than the height of your ambition...

Offline cjcboy2

  • Full Member
  • ***
  • Posts: 122
Re: ZTE MF190 Pocket Modem and wvdial
« Reply #4 on: January 15, 2013, 04:30:15 PM »
Hi!

Just to add up here, been experimenting to make things work on my setup. Though admittedly, this was quite painful technically =D

I do have a dual boot system Windows 7 and PCLOS (Mini Me). This is both freshly installed systems on a Lenovo S400 laptop.

Since I needed this dongle to work on both, I didn't stopped reading tricks and workarounds to successfully connect to the internet.

I did noticed that ejecting the dongle, just makes my nix system hung and apparently rebooting it all the time is not an option so what I did was:

1.) booted my system to Windows 7 (just to detect the dongle and sync it with the provider)
2.) rebooted the system to PCLOS (leaves the dongle still synced)
3.) re-enabled the connection and presto I'm connected

The above mentioned is based on my experience and not saying that it can work on others setup.

Cheers!
..the depth of your passion is far more important than the height of your ambition...