UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
this is hard to believe. i had dapper on my system and had no problem dialing up. now with edgy i cannot dialup, i've tried pppconfig,wvdial and system-adminstration-networking. all to no avail.i have a diamond supra ext. serial modem connected to ttyS0. someone shed some light on this?
i did as you said. i uninstalled wvdial and reinstalled it. i also created a symbolic link. but wvdial is still writing to /dev/null. when i uninstalled wvdial, maybe i should have deleted the wvdial.conf files? also edgy will not let me edit /etc/ppp/peers, which might help.still no dialup.
I did not suggest you reinstall wvdial, I suggested you run sudo wvdialconf ... did you do this? I also asked you to post your wvdial.conf file here - you have not done this.
How can I help you if you will not follow advise?
Please reread my previous post carefully and follow all the instructions.
Last edited by Simon Bridge; 04-08-2007 at 11:53 PM.
this is what i get when i do a sudo wvdialconf /etc/wvdial.conf:Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- OK
ttyS0<*1>: ATQ0 V1 E1 Z -- OK
ttyS0<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyS0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyS0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyS0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyS0<*1>: Modem Identifier: ATI -- 56000
ttyS0<*1>: Speed 4800: AT -- OK
ttyS0<*1>: Speed 9600: AT -- OK
ttyS0<*1>: Speed 19200: AT -- OK
ttyS0<*1>: Speed 38400: AT -- OK
ttyS0<*1>: Speed 57600: AT -- OK
ttyS0<*1>: Speed 115200: AT -- OK
ttyS0<*1>: Max speed is 115200; that should be safe.
ttyS0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S2 S3
Found a modem on /dev/ttyS0.
Modem configuration written to /etc/wvdial.conf.
ttyS0<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0"
... good, you have followed one part of my advise successfully. This means that everything went just fine. But what about the other parts of my advise?
I am getting tired of repeating myself - perhaps I am not being clear? If you do not understand something, please let me know and I will rephrase it.
Just to make things very clear, I've divided the advice into three (3) parts. Please complete all three parts before replying. Keep a record of what happens in each part. Your reply should include a record of what you did and what happened in the form of copied terminal input and output. If, for any reason, you are unable to complete all three parts, please explain. Otherwise I will know I am wasting my time and I will bother you no more. Thank you - the three parts follow...
Part 1:
Open a terminal and enter
cat /etc/wvdial.conf
You will get a lot of output that looks kinda like this
Part 2:
To make this conf file work, you need to change the last three lines. So, in terminal again, enter the following:
sudo gedit /etc/wvdial.conf
Using the editor, you need to remove the semi-colon ( from the start of those last three lines. Also remove everything in the chevrons (< >) as well as the chevrons. Replace all that with your details... i.e. instead of <Target Phone Number> you write in the phone number for your ISP, instead of <Password> you write your ISP account password, instead of <Your Login Name> you write the name of your account (eg. if you are normally joebloggs@yourisp.com, then your login name is "joebloggs").
Save the file, and exit.
Part 3:
In the terminal again, enter
wvdial
... copy the output and paste here.
Last edited by Simon Bridge; 04-10-2007 at 12:55 AM.
this is hard to believe. i had dapper on my system and had no problem dialing up. now with edgy i cannot dialup, i've tried pppconfig,wvdial and system-adminstration-networking. all to no avail.i have a diamond supra ext. serial modem connected to ttyS0. someone shed some light on this?
Yes it doesn't work. It is a fault which Ubuntu should have seen before sending out edgy. Kppp doesn't work either.
I have not used earlier versions but my friends went back to Windoze because of this most basic of bugs.
heres it is[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = Analog Modem
ISDN = 0
New PPPD = yes
stupidmode = on
Phone = *702156874676
Modem = /dev/ttyS0
Username = my user name
Password = my password
Baud = 115200
i know what you are talking about. i have been using ubuntu since warty. thanks for your help.
here it is: -> WvDial: Internet dialer version 1.56
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT*702156874676
--> Waiting for carrier.
ATDT*702156874676
CONNECT 115200
--> Carrier detected. Waiting for prompt.
--> Connected, but carrier signal lost! Retrying...
--> Sending: ATDT*702156874676
--> Waiting for carrier.
Level 3 Comm nas14.phi1 UQKT2
Username:/login:/Login:
Username:/login:/Login:
Username:/login:/Login:
Username:/login:/Login:ATDT*702156874676
Password:
after i enter the password, a message comes up saying, idle timeout
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.