wvdial.txt Driver File Contents (AGERE_MODEM_Chip_1648c-tv5_Model_No._IC56A_made_by_Stratitec.zip)

THis is HowTo to set  up WVDIAL for usage with winmodems.
The guidance here is for ltmodem hardware & drivers.
But the process will be substantially the same for any winmodem.
All steps should be run as Root, as an ordinary User may get a
"driver or resource busy" error. 

1) First check that your drivers in fact have been added to the running kernel:
$ 	modprobe lt_serial
$	lsmod
among modules displayed there should be:
lt_serial              21008   
lt_modem              314752   [lt_serial]

2) wvdialconf scans ONLY for ports with generic serial port names: /dev/ttyS* 
The ports corresponding to PCMCIA modem cards should have such a
designation. But a symbolic link is needed to support scanning for other
types of Lucent modem cards: ISA, PCI or unknown types of some laptops. 
First verify that there is present a real node needed by your winmodem.
For the case of ltmodems it is:
$ 	ls -l /dev/ttyLT0
crw-rw----    1 root     dialout   62,  64 Jun  2 13:32 /dev/ttyLT0

which should have been made earlier by  
	./autoload 
Next make the TEMPORARY symbolic link using the "local/experimental" port
reservation space, S14 or S15:
$	ln -sf /dev/ttyLT0 /dev/ttyS14
Verify success with:
$	# ls -l  /dev/ttyS14
lrwxrwxrwx    1 root     root      11 Jun  2 13:16 /dev/ttyS14 -> /dev/ttyLT0

AFTER your setups below are completed, BE SURE to: 
$	rm -f /dev/ttyS14
as for a Very-Small-Minority of Systems having resource conflicts,
retention of /dev/ttyS14 could cause a CRASH during bootup.

3) Now run the configuration test with command:
$	wvdialconf /etc/wvdial.conf
There should be output like:
-----
Scanning your serial ports for a modem.

ttyS0<*1>: ATQ0 V1 E1 -- ATQ0 V1 E1 -- ATQ0 V1 E1 -- nothing.
Port Scan<*1>: S1   S2   S3   
ttyS14<*1>: ATQ0 V1 E1 -- OK
ttyS14<*1>: ATQ0 V1 E1 Z -- OK
ttyS14<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyS14<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyS14<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyS14<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 -- OK
ttyS14<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 -- OK
ttyS14<*1>: Modem Identifier: ATI -- LT V.90 Data+Fax Modem Version 5.99
ttyS14<*1>: Speed 2400: AT -- OK 
ttyS14<*1>: Speed 4800: AT -- OK 
ttyS14<*1>: Speed 9600: AT -- OK  
ttyS14<*1>: Speed 19200: AT -- OK
ttyS14<*1>: Speed 38400: AT -- OK
ttyS14<*1>: Speed 57600: AT -- OK
ttyS14<*1>: Speed 115200: AT -- OK
ttyS14<*1>: Max speed is 115200; that should be safe.
ttyS14<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 -- OK  
--------
and there will be written a file /etc/wvdial.conf:

[Dialer Defaults]
Modem = /dev/ttyS14
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
; Phone = <Target Phone Number>
; Username = <Your Login Name>
; Password = <Your Password >

---------
The following should next be done:
1) Edit 
   /dev/ttyS14 ---> /dev/ttyLT0
2) Edit the lines beginning with ; including deletion of ;
3) Your modem May or May Not be set with an appropriate Country Code.
If in doubt, edit per below:

[Dialer Defaults]
Modem = /dev/ttyLT0
Baud = 115200
Init1 = ATZ  
Init2 = AT+GCI=HexadecimalNumber
Init3 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
Phone = Target_Phone_Number
Username = Your_Login_Name 
Password = Your_Password

-------
HexadecimalNumber should be chosen from the list in DOCs/CountryCodes.

That is the essense. 
You should be able to dialout simple with:
$	wvdial
and terminate a session with:
$	Ctrl-C

For ltmodem users a liner within /etc/modules.conf
   alias char-major-62 lt_serial

enables demand loading of drivers, upon start up of PPP.
--------------------------------------------------

Happily note that Wvdial supports Many Useful configuration variants
Do read the documentation suppled with the wvdial package.
Below is one of mine:

======================
[Dialer Defaults]
Modem = /dev/ttyLT0
Baud = 115200
Init1 = ATZ
# Init2 = AT+GCI=b5, country code usage when traveling
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0

# Phone = 17574238738
Phone = 3019178111
Username = stodolsk
Password = xxxxxxx

[Dialer daughter]
phone=4301146
Username = xxxxxxxx
Password = YYYYYYY

[Dialer lake]
Phone = 17574238738

[Dialer hotel]
Phone = 8,1,9252189607

# for verbose report
#  wvdial >/var/log/wvdial.log 2>&1 &

# Jacques advice.
# This last thing has rescued me from something looking like your new problem:
#  pppd waited for a prompt and the ISP waited for a request. 
# StupidMode = yes
# With StupidMode on using wvdial, 
#  pppd starts trying to establish a connection and everything works fine.
===============
For example, to use my daughter's IP when visiting, it suffices to:

$	wvdial daughter

Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web2, load: 1.24