LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Ubuntu (https://www.linuxquestions.org/questions/ubuntu-63/)
-   -   dialup in edgy (https://www.linuxquestions.org/questions/ubuntu-63/dialup-in-edgy-543992/)

unisol 04-07-2007 05:37 AM

dialup in edgy
 
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?

Simon Bridge 04-07-2007 06:09 AM

Check /dev/modem is present and pointing to /dev/ttyS0

Have you tried dialing the modem direct like this:

sudo echo "atdt 5551234" > /dev/ttyS0

... watch for the modem lights.

Have you tried: system > administration > networking -- modem, and configuring from there?

unisol 04-07-2007 06:20 AM

dialup in edgy
 
i've tried the networking app. ill try the other things you said. thank you.

unisol 04-07-2007 10:06 AM

dialup in edgy
 
ubuntu says there is not such directory as /dev/modem. also wvdial is writitng to /dev/null.

Simon Bridge 04-07-2007 06:01 PM

Well, that explains it. /dev/null is called the "bitbucket". It is where you write to when you want nothing to happen.

You want to create a symlink

ln -s /dev/ttyS0 /dev/modem

(This is a common convention, not essential but can simplify things.)

In terminal enter:

sudo wvdialconf (copy and paste output and command here)

cat /etc/wvdial.conf (copy and paste output with command here)

sudo gedit /etc/wvdial.conf (fill in your isp details)

wvdial (everything should go)

unisol 04-08-2007 08:49 AM

dialup in edgy
 
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.

Simon Bridge 04-08-2007 11:48 PM

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.

unisol 04-09-2007 09:33 AM

dialup in edgy
 
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"

Simon Bridge 04-10-2007 12:53 AM

Quote:

Modem configuration written to /etc/wvdial.conf.
... 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
Code:

simon@errata:~$ cat /etc/wvdial.conf

[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = Analog Modem
Baud = 115200
New PPPD = yes
Modem = /dev/ttyS0
ISDN = 0
; Phone = <Target Phone Number>
; Password = <Your Password>
; Username = <Your Login Name>

... you copy your version and paste it here.

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.

barrythai 04-10-2007 10:32 AM

Quote:

Originally Posted by unisol
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.

:Pengy: :Pengy: :Pengy:

unisol 04-10-2007 01:35 PM

dialup in edgy
 
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.

Simon Bridge 04-11-2007 06:21 AM

Quote:

Originally Posted by barrythai
Yes it [dialup in edgy] doesn't work. It is a fault which Ubuntu should have seen before sending out edgy. Kppp doesn't work either.

My dialup is fine with Edgy. You are calling this a bug - do you have a reference for this?

AFAIK: The only thing not going seems to be the modem monitor applet.

Unisol:
Part 1 and 2 have been completed. Awaiting the rest of part 3.

unisol 04-11-2007 08:51 AM

dialup in edgy
 
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

Simon Bridge 04-11-2007 05:03 PM

In your wvdial.conf, remove the line "stupidmode = on" and add a line "Stupid Mode = 1". Retry.

The initial dropped carrier, though, wasn't wvdial or anything linux related. It is your telephone line.

unisol 04-11-2007 05:15 PM

dialup in edgy
 
thanks. tell me something. how come dialup works in debian(etch) and windows?

Simon Bridge 04-11-2007 06:13 PM

Did adding the "stupid mode" line work?

Quote:

thanks. tell me something. how come dialup works in debian(etch) and windows?
I have no indication that dailup does not work in Ubuntu Edgy.

Note: dialup seldom works in windows unless you install the driver that came with the modem (in '03 I had to load the drivers for intel chipset modems - internal and external - before windows could use them, all linuxes to date have recognised the external one with no problem). Similarily, I found that RH9 autodetected and configured an internal ISA modem for me which windows 98se claimed did not exist.

If you look at the list of bundled modem drivers in windows, you'll see seperate drivers for modems with identical chipsets - requiring only one driver in linux.

Basically, windows uses stupid mode all the time :)

With Debian Etch, it depends how you set it up. also, different distribution have different setup systems. These systems will work to different effect with different devices - so devices that get autodetected and configured in one distro may give errors in another. This is also the sort of thing that can change between version in a distro - especially when one method is being depreciated in favour of a more promising one.

I suspect the GUI issues in modem setup are due to the emergence of the wvdialconf script. (and the prevalance of broadband use amongst developers.)


All times are GMT -5. The time now is 05:24 AM.