Puppy Linux Discussion Forum

[rerwin]

potong,
Thanks for spelling out how to use 4.3.1 for wireless modems. You are exactly right, except that step 5 is unnecessary. And if the name of that button is not the same as the currently selected/detected port, you could get a surprising result. Pupdial would try the other port and either select it or leave the same selection. That is for unusual situations. Obviously, in your case it does no harm.
Richard

[potong]

rerwin:

Out of interest, does the dev# on the T: line of /proc/bus/usb/devices refer to ttyUSBn?

In my case dev#=3, therefore starting from zero would mean ttyUSB2, correct?

I ask because I repeated the steps in my howto and sometimes the port is not detected at all or detected incorrectly i.e. ziltch or ttyUSB1.
When the port was detected as ttyUSB1 the button was correctly identified as ttyUSB2.
I guess my first attempts must have been lucky.

When this happened I re-probed until the port and the button were both the same i.e. ttyUSB2.
Then everything was hunky dory.

Can one manually (via the command line) get puppy to re-probe the usb devices?

Potong

[bignono1]

Installed all 5 pets ,probed modem and it was detected
input all numbers.
Trying connect i get: voice line detected .Trying again.
sending : ATDT*99# (tried *99***#1 but no luck).
waiting for carrier.
ATDT*99#
ERROR
If i type wvdial in terminal i get:
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.
Please help.

[bignono1]

Changed user name ,password and APN , all pps
now i get : Bad init string .

[rerwin]

bignono1

[bignono1]

Thank you Richard, the file is attached.

[rerwin]

bignono1,
Thanks for the diag file. I see that you are not setting "stupid mode", which apparently is essential. Then, you may need to set the APN (which I don't see). Other that those, everything looks normal.

If that still does not work, please do not disconnect when you see the problem, but bring up a console and enter "pmodemdiag" (w/o quotes) to get a diag file. That way I can see the pupdial log that you see. When pmodemdiag completes, only then you should disconnect and exit pupdial.
Richard

[bignono1]

Thank you Richard ,
I did try stupid mode many times since i am good only in stupid modes put even those did outputed stupid and helpless,
so please keep up the good spirit and ignore my stupidness and see it as my only good advantage , sometimes being stupid is better than being mean.
Thanks again mate , you and this forum and all the puppians here are great .

[jemimah]

I just bought a new modem because my husband dropped the old one and wrecked it. I got the Sierra Shockwave (USB 308). I've owned two other sierra modems, and they worked without usb_modeswitch. This one however, is either different, or newer than kernel 2.6.35.7.

I ran pmodemdiag and saw the the device id was not recognized by usb_modeswitch. So I copied the config file from another device id and tried to modify it - but that didn't work.

This is on Puppeee4.4Beta4 which I added the latest patches.

Any ideas?

[cthisbear]

" Any ideas? "

Shoot husband???

Chris.

[jemimah]

Heh - being without internet for a few hours is punishment enough for him.

Further research suggest the sierra_net module is supposed to work with this modem. But it doesn't. I'm rebuilding the kernel now to see if I can fix it.

[jemimah]

WhhoooHooo! My kernel patch worked! I just added the pci id to sierra.c.

So nevermind.

[rerwin]

bignono1,
I have been googling for clues on things to try regarding the "bad init string" problem. I found some ideas to try one at a time.

1. Some solutions simply insert more commands into the Init3 string, adding S7=60 S30=0, resulting in:
ATQ0 V1 E1 S0=0 S7=60 S30=0 &C1 &D2 +FCLASS=0

2. Keying off of your APN of "pps", I found a web page where you can get modem setup information, but it requires your "subscriber code", so I cannoot read it. But you can: http://www.kw.zain.com/kw/af/services/main/OTASettings/OTASettings.do?channelId=-9325&selectedChannels=-9325,-8159,-8155,-8153&lang=en

3. The modems usually need to be "initialized" in a Windows system, then removed before exiting the initialization program. Be sure yours has been initialized.

4. Many users disable the requirement for a SIM PIN code. Otherwise, you need to enter one in pupdial. If you are uncertain about the SIM PIN, you can find out its status this way:
- add a command to the Init2 string, to make it:
ATZ +CPIN?
- Connect and view the response in the log window, for examples.
+CPIN: SIM PIN <==== modem requires sim pin
+CPIN: READY <======shows the modem is now ready

5. The logon and password given for your provider is "pps" for both (w/o quotes).

That's what I found. Apparently many people have trouble with ZTE modems. Maybe that is because there are so many out there. Or not. I hope these help you along.

If not, can you install wary 0.9.8 and try your modem with it. It has the most recent developments for modems and might help.
Richard

[bignono1]

Gooooood news :I am on line using my USB modem after more than 4 months .
Here is what i did finally:
1.Connected the modem to a win xp machine .
2.Unpluged the modem while still on line.
3.Removed the pps from APN.
4.Phone no. *99***1#
The modem switch WAS changed to ttyUSB1, I DID NOT CHANGE IT


Thank you Richard , you are great.
And here is the pmodemdiag again for the record.
Thank you again Richard , i am really happy because of you.

[bignono1]

Hi,
Same modem on lucid puppy 5.0.1
Just inputed pps in APN field.
The diag file is attached.