For version 6.00b15 and later, the actions mentioned below should NOT be necessary
as they have been written into the installation scripts.
However this file is being retained as a tutorial on the devfs (DEvice File System)
0) Check whether systen has devfs support. If there is an acting Device File System with
# ls -l /dev/.devfsd
crw------- 1 root root 8, 0 Dec 31 1969 /dev/.devfsd
or else the following is not relevant.
If you have done a ltmodem install procedure, their should be:
# ls -l /dev/ttyLTO
and you are under the classical support for device nodes
Quit here.
But proceeding:
1) Check for preexisting /dev/modem link
# ls -l /dev/modem
lr-xr-xr-x 1 root root 7 Dec 29 02:30 /dev/modem -> tts/LT0
is expected for Lucent support when all else is done LATER
But if there is something like:
# ls -l /dev/modem
lr-xr-xr-x 1 root root 7 Dec 29 02:30 /dev/modem -> tts/0 or 1 or 2 or 3
This is INTERFERENCE. Unless you have a non Lucent modem functioning, remove the Symbolic link, as Root:
# rm /dev/modem
2) Check for ltmodem support lines installed in /etc/modules.conf,
selectively displated by using "grep" filtration by lt_
# grep lt_ /etc/modules.conf
# lt_drivers: autoloading and insertion parameter usage
alias char-major-62 lt_serial
alias /dev/tts/LT0 lt_serial
alias /dev/modem lt_serial
# The next line is a syntax example, rarely needed, to automate parameter usage during lt_drivers insertion. See documentation for details
# options lt_modem vendor_id=0x115d device_id=0x0420 Forced=3,0x130,0x2f8
# section for lt_drivers ends
This was put in place by during the ltmodem installation software
and mediates autoloading of the modem drivers
The /dev/tts/LT0 is the replacement under the Device File System for /dev/ttyLT0
3a) Maintenance of /dev/tts/LT0 is called for by lines in
/etc/devfsd.conf (in Mandrake, but it /etc/devfs/conf.d/ltmodem under Debian)
# grep LT0 /etc/devfsd.conf
# maintenance of symbolic links /dev/modem to /dev/tts/LT0
REGISTER ^tts/LT0$ CFUNCTION GLOBAL symlink $devname modem
UNREGISTER ^tts/LT0$ CFUNCTION GLOBAL unlink modem
These lines should either be within
/etc/devfsd.conf
as for example in Mandrake 8.1, or alternatively within
/etc/devfs/conf.d/ltmodem
as for example Debian Linux.
3b) Should your system already have a none-Lucent modem whose
functionality you wish to maintain, then change:
modem --> modem1
within
i) /etc/devfsd.conf (or /etc/devfs/conf.d/ltmodem under Debian)
ii) the line of /etc/modules.conf: alias /dev/modem lt_serial
iii) the Systems ppp dialup scripts
iv) For all subsequent steps below, replace "modem" by "modem1".
4) Inform your System of this new entry with:
# killall -HUP devfsd
If all else is well the modem should be functional NOW.
======================================
Let's see how this works in practice.
To keep display simpler, changing to the /dev/ folder
[root@localhost /root]# cd /dev
Let's look at properties of the serial like devices.
[root@localhost /dev]# ls /dev/ttyLT0
ls: /dev/ttyLT0: No such file or directory
This is expected under the Device File System!
Lets look for the standard serial ports.
[root@localhost /dev]# ls -l ttyS* tts
lr-xr-xr-x 1 root root 5 Dec 23 08:51 ttyS0 -> tts/0
lr-xr-xr-x 1 root root 5 Dec 23 08:51 ttyS1 -> tts/1
tts:
total 0
crw------- 1 root root 4, 64 Dec 31 1969 0
crw------- 1 root root 4, 65 Dec 31 1969 1
These are the replacements for the old /dev/ttyS0 and /dev/ttyS1
The ltmodem drivers are NOT loaded yet
[root@localhost /dev]# lsmod
Module Size Used by
ymfpci 39392 0
ac97_codec 9248 0 [ymfpci]
usb-ohci 17440 0 (unused)
usbcore 52000 1 [usb-ohci]
unix 13728 127 (autoclean)
To save space I'll use hereafter use the filter: grep lt_
[root@localhost /dev]# lsmod | grep lt_
just again shows that the lt_* drivers are not loaded
Now calling for driver loading with:
[root@localhost /dev]# modprobe lt_serial
The kernel messages relate
[root@localhost /dev]# tail /var/log/messages
Dec 23 17:38:42 localhost kernel: Loading Lucent Modem Controller driver version 6.00
Dec 23 17:38:42 localhost kernel: Detected Parameters Irq=12 BaseAddress=0xb400 ComAddress=0xb800
Dec 23 17:38:42 localhost kernel: Lucent Modem Interface driver version 6.00 (2001-01-26) with SHARE_IRQ enabled
Dec 23 17:38:42 localhost kernel: ttyLT00 at 0xb400 (irq = 12) is a Lucent Modem
and thereis confirmation
[root@localhost /dev]# lsmod | grep lt_
lt_serial 20144 0 (unused)
lt_modem 314464 0 [lt_serial]
Looking at serial devices again:
[root@localhost /dev]# ls -l ttyS* tts
lr-xr-xr-x 1 root root 5 Dec 23 08:51 ttyS0 -> tts/0
lr-xr-xr-x 1 root root 5 Dec 23 08:51 ttyS1 -> tts/1
lr-xr-xr-x 1 root root 7 Dec 23 17:38 ttySLT0 -> tts/LT0
tts:
total 0
crw------- 1 root root 4, 64 Dec 31 1969 0
crw------- 1 root root 4, 65 Dec 31 1969 1
crw-r--r-- 1 root root 62, 64 Dec 23 14:34 LT0
MAGIC!!! of the devfs, with one of its Economic motivations.
The /dev/tts/LT0 has only been CREATED when needed
along with a useful symbolic link to it: /dev/ttySLT0
To illustrate the reverse, unloading the modem drivers:
[root@localhost /dev]# modprobe -r lt_serial
With kernel messages
[root@localhost /dev]# tail /var/log/messages
Dec 23 17:40:00 localhost CROND[1629]: (root) CMD ( /sbin/rmmod -as)
Dec 23 17:45:23 localhost kernel: Unloading Lucent Modem Interface driver: version 6.00
Dec 23 17:45:23 localhost kernel: Unloading Lucent Modem Controller driver: version 6.00
and they are indeed removed
[root@localhost /dev]# lsmod | grep lt_
TOGETHER with the device that served them
[root@localhost /dev]# ls -l ttyS* tts
lr-xr-xr-x 1 root root 5 Dec 23 08:51 ttyS0 -> tts/0
lr-xr-xr-x 1 root root 5 Dec 23 08:51 ttyS1 -> tts/1
tts:
total 0
crw------- 1 root root 4, 64 Dec 31 1969 0
crw------- 1 root root 4, 65 Dec 31 1969 1
Another way of loading the drivers is to start a ppp session
or EVEN just by quering the symbolic /dev/modem
[root@localhost /dev]# ls -l /dev/modem
lr-xr-xr-x 1 root root 7 Dec 23 19:25 /dev/modem -> tts/LT0
Confirming:
[root@localhost /dev]# lsmod | grep lt_
lt_serial 20144 0 (autoclean) (unused)
lt_modem 314464 0 (autoclean) [lt_serial]
Checking devices too, LT0 is back.
[root@localhost /dev]# ls -l ttyS* tts*
lr-xr-xr-x 1 root root 5 Dec 23 08:51 ttyS0 -> tts/0
lr-xr-xr-x 1 root root 5 Dec 23 08:51 ttyS1 -> tts/1
lr-xr-xr-x 1 root root 7 Dec 23 18:26 ttySLT0 -> tts/LT0
tts:
total 0
crw------- 1 root root 4, 64 Dec 23 18:24 0
crw------- 1 root root 4, 65 Dec 23 18:24 1
crw-r--r-- 1 root root 62, 64 Dec 23 14:34 LT0
Enough games, on to COMMUNICATE
The wvdial setup utility only scans for ports with name /etc/ttyS* , as mentioned in DOCs/wvdial.txt
But /dev/ttySLT0 should suffice.
So testing:
[root@localhost /dev]# wvdialconf /etc/wvdial.conf
Scanning your serial ports for a modem.
ttyS0<*1>: ATQ0 V1 E1 -- ATQ0 V1 E1 -- ATQ0 V1 E1 -- nothing.
ttyS1<*1>: ATQ0 V1 E1 -- ATQ0 V1 E1 -- ATQ0 V1 E1 -- nothing.
ttySLT0<*1>: ATQ0 V1 E1 -- OK
ttySLT0<*1>: ATQ0 V1 E1 Z -- OK
ttySLT0<*1>: ATQ0 V1 E1 S0=0 -- OK
ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 -- OK
ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 -- OK
ttySLT0<*1>: Modem Identifier: ATI -- LT V.90 Data+Fax Modem Version 6.00
ttySLT0<*1>: Speed 2400: AT -- OK
ttySLT0<*1>: Speed 4800: AT -- OK
ttySLT0<*1>: Speed 9600: AT -- OK
ttySLT0<*1>: Speed 19200: AT -- OK
ttySLT0<*1>: Speed 38400: AT -- OK
ttySLT0<*1>: Speed 57600: AT -- OK
ttySLT0<*1>: Speed 115200: AT -- OK
ttySLT0<*1>: Max speed is 115200; that should be safe.
ttySLT0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 -- OK
Found a modem on /dev/ttySLT0.
ttySLT0<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0"
Thus was created a defualt file:
[root@localhost /etc]# cat wvdial.conf
[Dialer Defaults]
Modem = /dev/ttySLT0
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>
Which after editing to:[Dialer Defaults]
Modem = /dev/ttySLT0
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
Phone = 3019178111
Username = stodolsk
Password = XXXXXX
Supports a dialout:
[root@localhost /etc]# wvdial
--> WvDial: Internet dialer version 1.42
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATDT 3019178111
--> Waiting for carrier.
ATDT 3019178111
CONNECT 53333 V42bis
--> Carrier detected. Waiting for prompt.
** APX2.LNH.MD.RCN.NET Terminal Server **
Login:
--> Looks like a login prompt.
--> Sending: stodolsk
stodolsk
Password:
--> Looks like a password prompt.
--> Sending: (password)
Entering PPP Session.
IP address is 66.44.14.23
MTU is 1006.
Etc. of course I had other ppp items previously configured.
==============================================================================
Fall back issues.
The above illustrates the simplest situation when there are no resource conflicts.
1) Should there be a failure of:
$ modprobe lt_serial
First let's cleanup
[root@localhost /dev]# modprobe -r lt_serial
[root@localhost /dev]# lsmod | grep lt_
[root@localhost /dev]# ls -l ttyS* tts
lr-xr-xr-x 1 root root 5 Dec 23 08:51 ttyS0 -> tts/0
lr-xr-xr-x 1 root root 5 Dec 23 08:51 ttyS1 -> tts/1
tts:
total 0
crw------- 1 root root 4, 64 Dec 23 19:13 0
crw------- 1 root root 4, 65 Dec 23 19:13 1
Now trying only
[root@localhost /dev]# modprobe lt_modem
This driver alone was loaded
[root@localhost /dev]# lsmod | grep lt_
Module Size Used by
lt_modem 314464 0 (unused)
But will also be soon unloaded, for lack of contact with the hardware
[root@localhost /dev]# tail /var/log/messages
Dec 23 19:22:17 localhost kernel: Loading Lucent Modem Controller driver version 6.00
Dec 23 19:22:17 localhost kernel: Detected Parameters Irq=12 BaseAddress=0xb400 ComAddress=0xb800
Dec 23 19:22:17 localhost kernel: Lucent Modem Interface driver version 6.00 (2001-01-26) with SHARE_IRQ enabled
Dec 23 19:22:17 localhost kernel: ttyLT00 at 0xb400 (irq = 12) is a Lucent Modem
Dec 23 19:30:00 localhost CROND[1855]: (root) CMD ( /sbin/rmmod -as)
Dec 23 19:35:50 localhost kernel: Unloading Lucent Modem Interface driver: version 6.00
Dec 23 19:35:50 localhost kernel: Unloading Lucent Modem Controller driver: version 6.00
Dec 23 19:37:32 localhost kernel: Loading Lucent Modem Controller driver version 6.00
Dec 23 19:40:00 localhost CROND[1864]: (root) CMD ( /sbin/rmmod -as)
[root@localhost /dev]#
Courtesy of the periodic
Dec 23 19:30:00 localhost CROND[1855]: (root) CMD ( /sbin/rmmod -as)
The lt_modem driver will load in the presence of a variety of modem hardware including the
AMR Lucent
ESS something or the other
A failure of the lt_serial to load could mean either
Incompatibel modem hardware
Resource conflicts
Procedures for addressing the resouce conflict situation are in DOCs/ltmodem
with Successes listed in DOCs/Ltmodem.html
Download Driver Pack
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.