Courier v everything freezes on Mepis3.4.1 new install

hi, maybe try turning off your ethernet connection first to avoid conflicts...

MEPIS OS Center > System Config > Network Interfaces > click "Stop eth0"

then for your USR modem, in Kppp under Modem Commands use AT&F1 for your initilization string.

Of course double-check you have the phone no., username/password, and ISP domain entered correctly in Kppp Accounts.

Modem device = /dev/ttySO
Flow control = Hardware [CRTSCTS]
Line termination = CR
Connection speed = 115200
Init string = AT&F1

~good luck

I did as you suggested and the responce changed slightly:

Turning off eth0 seemed to have no effect but it did get me further into understanding Mepis and where to look.

Adding the command AT&F1 had the effect of making the modem hang at "Modem Ready". It did not proceed to "Initialization" as before.

I can clearly communicate with the modem. The lights flash before "modem ready" and if I set the speaker volume to "high" under Modem Commands I get the message that it is adjusting volume after it tries to initialise. This only works if I do not have the AT&F1 string inserted which appears to cause it to hang at the start of the modem commands.

Any further thoughts?

Sorry it didn't work. I had a USR external but it wasn't the Courier model as you have. I found this site

http://www.modemhelp.org/inits/usrobotics.html

that has other strings you can try -- you might have to experiment a little. If you have the modem documentation, it might have the recommended one there.

In KPPP get to terminal mode and see if you can manually control the modem with ATH0 and ATDT phone number to dial
see if your modem actually responses to you and will
connect to your isp

Let us know here...

I think you have hit on something. If I switch to terminal mode I get no response. I cannot type any commands even though it says "Modem Ready"

However if I put ATDT and my isp number into "Initialisation string 1" in Modem commands I can dial and get through to my ISP when I go into terminal mode and it starts to initialize. I connect but cannot log on as the user name and password are missing. This seems to indicate that the modem is ok and I am making contact.

I put an aztech initialization string into modem commands by mistake and found that the terminal screen replied with ok and I was able to use it with all the at commands that I tried. Not sure what the significance of this is but it might help in understanding. String is AT&FE1Q

I will continue to try. Thanks for your help and please feel free to comment and add advice.

Has anyone got a Courier v-everything 56kmodem to work with Mepis3.4.1

I have spent a lot of time trying to find out how to make this work without success. I can manually use AT commands and dial up etc but the modem will not work automatically.

I loaded Mepis 3.3.1 today and the moden worked fine. The only changes I made from default setup was to set flow control to "software" and connection speed to 57000 It connected at about 45000 and I was able to go on the internet.

I noticed that the "Modem command" page under 3.3.1 was full of responses but under 3.4.1 this page was blank. I then rebooted to 3.4.1 and put these responses into the Modem command page. I then tried the "terminal screen and got the resoponse ATZ OK I could then use AT commands. However KPPP would not connect from the "connect" command on the start up screen

Am I doing something wrong or is there a fault with 3.4.1. I like 3.4.1 and just want to use it. I do not want to become an expert in rebuilding operating systems.

Manually using terminal mode
Completely login and get a browser up and working....

Revisit with a magnifying glass the automatic
settings....

Check Chap/Pap setting...

let us know...

Courier v-everything now working.

The final problem was as follows:

I successfully tried various commands in terminal mode under KPPP. I then checked the modem by using the "Query Modem" command. All seemed to be ok. However if I then moved to the KPPP front screen and clicked "connect" the modem hung on Initializing. I went round this loop making changes many times. I then found that if I opened the terminal window after running "Query Modem" the modem worked on "connect". The terminal window sends the command ATZ to the modem which seems to reset nvram.

I have powered the system down several times, rebooted and it now runs as expected. Now I can get down to the real business of getting to know Linux and use the computer at a location which still cannot get broadband.

Many thanks to all those who helped. Your comments kept me going and heading in the right direction.