Re: Chris Sparnicht, USA kernel 2.6.26-2-686

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Chris,

I do not wish to start a useless thread on the virtues and problems of Linux.

wvdial is distributed with the man files and even if some link in there is missing, they do answer any question- which

I however you almost never need to ask.

I had not noticed that the link to the original wvdial page is bad. I have corrected for that, and added a few tips, in

http://linmodems.technion.ac.il/wvdial.html which I had written very long ago.

Sometimes, some programs are good, so the fast appearance of new versions is not necessarily a proof of software quality.

If you have suggestions to improve http://linmodems.technion.ac.il/wvdial.html , please write them to the list, I will consider them and accordingly improve the file.


Jacques


chris@xxxxxxxxxxx wrote:

Hi Jacques,

Thanks for your reply. 'man' can be a great tool - I agree.
Unfortunately all too often, the resultant man pages are unintentionally
more cryptic to end-users than their creators may imagine,
even for those who have a modicum of bash experience.

Further, with time, faqs and web references within the man page
change, become 404, are sometimes even misleading,
or become no longer entirely relevant.

Unfortunately, this seems to be the case with wvdial's man page.
The web-referenced FAQ and other urls are no longer available.

One can google endless references to wvdial - especially various
versions of the man page, but the actual home page is now
hosting a cyber-squatter waiting for original owner to buy
back the domain for what is likely to be a ridiculous ransom,
and wikipedia suggests that no new releases
have been made since July, 2007 - almost two years ago.

I know that there are proprietary portions of the software that have to be
compiled by the user, but I seem to remember installing a couple earlier
linux distros and using the modem without problems, without the "make
dance" or configuration. Unfortunately none of those distros seemed mature
enough to hand over to a total noob and expect it to recover itself when
something goes kerflooey. Jaunty and Lenny both seem to recover quickly.

From a 'sour-grapes' point of view, I begin to suspect modem emulation
might take enough of a toll on cpu crunch-time to seriously hamper a
reasonable dialup web-surfing experience on an 800MHz PIII.

Perhaps at this point, perhaps I should see if I can find a used
non-winmodem-style PCI modem.

I greatly appreciate your response and Marvin's bending over backward to
help me.

Chris



Jacques Goldberg wrote:
As always in Linux pratice,   man wvdial   answers your questions.

The name of the command, man , is short for manual, easy to remember.


You can learn there how to use any other file name that you may want, as
long as wvdialconf first creates a file with the same name.
But why make things more complicated than needed?


sudo wvdialconf /etc/wvdial.conf

sudo nano /etc/wvdial.conf

   adjust parameters

sudo wvdial


will succeed or fail independently of the name of the file used for the
contents of default name /etc/wvdial.conf
Jacques

chris@xxxxxxxxxxx wrote:

Hi Marvin,
Your directions have been very clear.
I'd properly edited wvdial.conf too.
I'm sorry for neglecting to say.
from the below terminal results:
Found a modem on /dev/ttySpctel.
Modem configuration written to /etc/wvdial.conf.
ttySpctel<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2
+FCLASS=0"
rod@rod-desktop:~$ nano /etc/wvdial.conf
rod@rod-desktop:~$ sudo !!
sudo nano /etc/wvdial.conf
Is wvdial using /etc/wvdial.conf or is it using a .conf somewhere else?
I'm beginning to wonder if there are further options.
Any ideas?
Chris
Marvin Stodolsky wrote:
Chris
These three initial lines in /etc/wvdial.conf
; Phone = <Target Phone Number>
; Password = <Your Password>
; Username = <Your Login Name>
should  be edited to format
Phone = xxxyyyzzz
Username =  loginName
Password =   LoginPassWord
MarvS
On Thu, May 7, 2009 at 10:29 PM,  <chris@xxxxxxxxxxx> wrote:
Marvin,
Well, I think we're closer - thanks again.
I followed your suggestions and tried a number of different things. I
added the correct phone, user and pass in the wvdial.conf.
I changed the path to /dev/537 in Gnome PPP.
More screen results below.
===== terminal results =====
rod@rod-desktop:~$ sudo ln -s /dev/537 Â /dev/ttySpctel
[sudo] password for rod:
rod@rod-desktop:~$ sudo wvdialconf
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
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.
ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS3<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS3<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS3<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttySpctel<*1>: ATQ0 V1 E1 -- OK
ttySpctel<*1>: ATQ0 V1 E1 Z -- OK
ttySpctel<*1>: ATQ0 V1 E1 S0=0 -- OK
ttySpctel<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttySpctel<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttySpctel<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
ttySpctel<*1>: Modem Identifier: ATI -- OK
ttySpctel<*1>: Speed 4800: AT -- OK
ttySpctel<*1>: Speed 9600: AT -- OK
ttySpctel<*1>: Speed 19200: AT -- OK
ttySpctel<*1>: Speed 38400: AT -- OK
ttySpctel<*1>: Speed 57600: AT -- OK
ttySpctel<*1>: Speed 115200: AT -- OK
ttySpctel<*1>: Speed 230400: AT -- OK
ttySpctel<*1>: Speed 460800: AT -- OK
ttySpctel<*1>: Max speed is 460800; that should be safe.
ttySpctel<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK
Found a modem on /dev/ttySpctel.
Modem configuration written to /etc/wvdial.conf.
ttySpctel<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2
+FCLASS=0"
rod@rod-desktop:~$ nano /etc/wvdial.conf
rod@rod-desktop:~$ sudo !!
sudo nano /etc/wvdial.conf
rod@rod-desktop:~$ man wvdial
rod@rod-desktop:~$ poff
/usr/bin/poff: No pppd is running. Â None stopped.
rod@rod-desktop:~$ wvdial stop
--> WvDial: Internet dialer version 1.60
--> Warning: section [Dialer stop] does not exist in wvdial.conf. -->
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.
--> Configuration does not specify a valid phone number.
--> Configuration does not specify a valid login name.
--> Configuration does not specify a valid password.
rod@rod-desktop:~$ wvdial
--> WvDial: Internet dialer version 1.60
--> 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.
--> Configuration does not specify a valid phone number.
--> Configuration does not specify a valid login name.
--> Configuration does not specify a valid password.
rod@rod-desktop:~$
===== gnome log =====
--> Ignoring malformed input line: ";Do NOT edit this file by hand!"
--> WvDial: Internet dialer version 1.60
--> 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: ATM1L3DT(###) 621-4801
--> Waiting for carrier.
ATM1L3DT(###) 621-4801
NO DIALTONE
--> No dial tone.
--> Disconnecting at Thu May  7 22:17:34 2009
Marvin Stodolsky wrote:
Chris,
Evidently your wvdialconf is not testing /dev/modem
So set a symbolic link
$ sudo ln -s /dev/537 Â /dev/ttySpctel
Then again try
$ sudo wvdialconf
If the modem is found:
$ sudo gedit  /etc/wvdial.conf
entering your personal info and removing the symbols ; < >
Also if either the configuration tools for KPPP or  gnomeppp while
allow you to specify /dev/537 as the port, you can likely use them
too.
MarvS
On Thu, May 7, 2009 at 8:41 PM, Â <chris@xxxxxxxxxxx> wrote:
Marvin,
Hi, and thanks once more.
See 'results - wvdial.conf' below.
It appears there was already a symlink from /dev/537 to /dev/modem.
The wiki referred to in the results is no longer there.
Attempts with Gnome PPP also give odd results, even though
everything
has
been set properly as far as I can tell. See 'results - Gnome PPP'
below.
Gnome PPP also has a nasty habit of freezing the desktop. I have to
reboot. Bummer.
Chris
===== results - wvdial.conf =====
rod@rod-desktop:~$ sudo wvdialconf
[sudo] password for rod:
Editing `/etc/wvdial.conf'.
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200
baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
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.
ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200
baud
ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS3<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS3<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200
baud
ttyS3<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Sorry, no modem was detected! Â Is it in use by another program?
Did you configure it properly with setserial?
Please read the FAQ at http://open.nit.ca/wiki/?WvDial
===== results - Gnome PPP =====
--> Ignoring malformed input line: ";Do NOT edit this file by
hand!"
--> WvDial: Internet dialer version 1.60
--> 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.
--> Please enter password (or empty password to stop):






[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux