Huawei E620 - pppd dies after disconnecting monitor on /dev/ttyUSB2

[Inte]

Hi alltogether,
I use a Huawei E620 (ID: 12d1:1001) and monitor the signal quality with xfce4-cellmodem-plugin (also tried comgt & minicom). Everytime I close the application (connected to /dev/ttyUSB2) the pppd dies.

The PPP daemon has died: A modem hung up the phone (exit code = 16)

With enabled syslog debugging:

Mar 26 22:00:25 [pppd] Script /etc/ppp/ip-up started (pid 24146)
Mar 26 22:00:26 [pppd] rcvd [IPCP ConfReq id=0x28]

--> pppd dies

Mar 26 22:00:26 [pppd] Connect time 0.1 minutes.
Mar 26 22:00:26 [pppd] Sent 0 bytes, received 4 bytes.
Mar 26 22:00:26 [pppd] sent [IPCP ConfReq id=0x5 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
Mar 26 22:00:26 [pppd] sent [IPCP ConfNak id=0x28 <addr 0.0.0.0>]
Mar 26 22:00:26 [pppd] Modem hangup
Mar 26 22:00:26 [pppd] Connection terminated.
Mar 26 22:00:26 [pppd] Waiting for 1 child processes...
Mar 26 22:00:26 [pppd] script /etc/ppp/ip-up, pid 24146
Mar 26 22:00:31 [pppd] sending SIGTERM to process 24146
Mar 26 22:00:31 [pppd] Exit.

--> Automatic wvdial redial 

Mar 26 22:00:42 [pppd] pppd 2.4.4 started by tobias, uid 1000
Mar 26 22:00:42 [pppd] using channel 21
Mar 26 22:00:42 [pppd] Using interface ppp0
Mar 26 22:00:42 [pppd] Connect: ppp0 <--> /dev/ttyUSB0

Used drivers:
2.6.19-gentoo-r5
> CONFIG_USB_SERIAL=y
> CONFIG_USB_SERIAL_OPTION=y

I don't have a clue what causes the interfere of ttyUSB0 and ttyUSB2. Maybe you have.

Inte

[redarrow]

Just guessing here.. maybe it's caused by the app reseting the modem on disconnect?
Try quitting minicom with Ctrl+A, Q instead of the usual Ctrl+A, X... that'll quit without reseting the modem.. if it works then thats obviously your problem...

This is just a hunch though..
Reseting the modem does not terminate pppd with my E220..

[Inte]

Just guessing here.. maybe it's caused by the app reseting the modem on disconnect?

If it were so easy. I'm already in contact with the xfce4-cellmodem dev and he also has no clue what the reason is.

Try quitting minicom with Ctrl+A, Q instead of the usual Ctrl+A, X... that'll quit without reseting the modem.. if it works then thats obviously your problem...

It doesn't matter if I quit minicom by using 'Q' or 'X'.

[redarrow]

Eish..

Is there a reason you must connect to /dev/ttyUSB2 to check signal or whatever?
With my E220 I can connect to /dev/ttyUSB1 to check signal or other stuff whilst connected... not that I see how that could really make a huge difference though..

It's weird though..

[Inte]

Is there a reason you must connect to /dev/ttyUSB2 to check signal or whatever?

Yes, there is a reason. minicom for example connects to ttyUSB1, but isn't able to send any AT commands to the modem, as comgt and xfce4-cellmodem also can't.

[redarrow]

Yes, there is a reason. minicom for example connects to ttyUSB1, but isn't able to send any AT commands to the modem, as comgt and xfce4-cellmodem also can't.

I see...
In my case with my E220 it's the other way around ... ttyUSB2 can't seem to be used for anything...


Sorry, I'm out of ideas for now..

You'll have to wait for Tazz_Tux ... maybe he's got some ideas..

[Tazz_Tux]

I see...
In my case with my E220 it's the other way around ... ttyUSB2 can't seem to be used for anything...


Sorry, I'm out of ideas for now..

You'll have to wait for Tazz_Tux ... maybe he's got some ideas..

( Oh - I saw now that you have an e620 - I have one at the office, so try this tip below and if you don't have any luck, pm me and I will look at it )

Wow - nice one.....

Here is a few of mine ideas:

Normally, the cards work like this:

ttyUSB0 - GSM Interface
ttyUSB1 - Upgrade/prop. Interface
ttyUSB2 - Application Interface

(This is what I have gathered over time - not taken from a manual)

So, normally you would setup on ttyUSB0, and monitor via usb2. Now we have seen some very weird things with the e220 under linux (btw - I saw a changelog for the e220 somewhere on the usbserial driver dev group - so watch this space)

I suspect that the e220/linux assigns these ports as the hardware is ready since it doesn't really have a normal startup (It has that usbstorage as well)

So - the long and short is, try usb2 as the dialup and monitor on usb0 ?

[redarrow]

( Oh - I saw now that you have an e620 - I have one at the office, so try this tip below and if you don't have any luck, pm me and I will look at it )

Hmm.. no I don't? I have an E220.. Or are you reffering to Inte? - Just confused since you quoted me..

Wow - nice one.....

Here is a few of mine ideas:

Normally, the cards work like this:

ttyUSB0 - GSM Interface
ttyUSB1 - Upgrade/prop. Interface
ttyUSB2 - Application Interface

(This is what I have gathered over time - not taken from a manual)

So, normally you would setup on ttyUSB0, and monitor via usb2. Now we have seen some very weird things with the e220 under linux (btw - I saw a changelog for the e220 somewhere on the usbserial driver dev group - so watch this space)

I suspect that the e220/linux assigns these ports as the hardware is ready since it doesn't really have a normal startup (It has that usbstorage as well)

So - the long and short is, try usb2 as the dialup and monitor on usb0 ?

I tried this on my E220 out of curiosity...

My results:
I cannot connect using ttyUSB2 I just get: (the file /dev/ttyUSB2 does exist btw.. regardless of what wvdial seems to think)

--> WvDial: Internet dialer version 1.54.0
--> Cannot open /dev/ttyUSB2: No such file or directory
--> Cannot open /dev/ttyUSB2: No such file or directory
--> Cannot open /dev/ttyUSB2: No such file or directory

Trying to connect on ttyUSB1 has a strange result.. it starts attempting to connect but doesn't seem to manage:

--> Modem initialized.
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Sending: AT+CGDCONT=1,"IP","internet"
AT+CGDCONT=1,"IP","internet"
OK
--> Modem initialized.
--> Sending: ATDT*99***1#
--> Waiting for carrier.
ATDT*99***1#
^BOOT:37087801,0,0,0,6
^BOOT:37087801,0,0,0,6

Funny thing is after having tried to connect via ttyUSB1, then going back to ttyUSB0 I suddenly get:

--> WvDial: Internet dialer version 1.54.0
--> Cannot open /dev/ttyUSB1: No such file or directory
--> Cannot open /dev/ttyUSB1: No such file or directory
--> Cannot open /dev/ttyUSB1: No such file or directory

Which make me think that attempting to connect on ttyUSB1 messes up some sort of internal mode or something..? - I needed to unplug and replug after that to restore the device..

Anymore info on the speed of the E220 btw? My E220 totally maxes out at 496kbps.. - It will not budge above that.. but it sits so comfortably there that I doubt it's the signal strength in my case..