I have an Actiontec PCIV9212-01CW modem that is Linux compatible (I bought it specifically for that reason). I used it with Mandrake 8.0, but recently upgraded to Mandrake 8.1. Now my modem doesn't work, and the procedure to make it work in 8.0 does not work in 8.1. Does anyone have any suggestions? I have been to www.linmodems.org, and have double checked that this is a compatible modem. Any help is very appeciated!!

Ok, first things first. This is a Winmodem, right? Does it have a lucent/agere chipset? if so, you should be able to download a .rpm file that should be available on this website: http://www.physcip.uni-stuttgart.de/...ists/mandrake/

Note: the version numbers are the version of the drivers, not of mandrake.

Here's the information from the readme file on that page.

This is a minor update of previous instructions for Mandrake 8.1 with the Lucent modem,
following working through a problem online.

MAIN NEW POINT - Check for a pre-existing symbolic link /dev/modem ---> /dev/ttySomething
as if blocks needed actions. Thus

0) Check whether your device 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 and /dev/ttySLT0 --> /dev/tts/LT0
REGISTER ^tts/LT0$ CFUNCTION GLOBAL symlink $devname modem
UNREGISTER ^tts/LT0$ CFUNCTION GLOBAL unlink modem

if these lines are not within /etc/devfsd.conf , DO edit them in.
This will be automated in the next release.

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

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




(see next post for the rest of the file.)

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








I have never touched a Mandrake system, but I would strongly advise you to take that modem back and exchange it for a true HARDWARE modem, because a Winmodem is a Hardware/Software modem, and you'll more than likely have nothing but problems with it anyway. After I got my drivers successfully installed under slackware I couldn't properly connect to my ISP, so I have given up until I get a hardware modem. It is possible to get it to work, but it can be very time consuming. (It looks like under 'drake that it's relatively simple to install the modem, so I wish you the best of luck)

wow... lotta typing justice ... BUT...

if the modem was working out-of-the-box with Mandrake 8.0, then the chances that it was a winmodem are pretty slim. it's much more likely that it's a different problem.

generally, i highly recommend AGAINST upgrading distros - it's really unreliable, but fresh installs, esp from mandrake 8.1, are usually pretty good.

what program have you been using to dial-out?

No, just a little cut and paste... but alot of PCI modems now days are Winmodems...and seeing as she checked linmodems.org I assumed the worst.

I did do a clean install-after a disastrous 'upgrade' experience!! I don't know where is a good place to get a hardware modem that won't rip me off????

Oh, by the way, justice, thanks for all the info, even if it was mostly cut and paste!!!! This newbie is totally lost, but I am trying to figure it all out!!

well... how did you get it working before? we could help a lot more if we had a bit more info. did you download an rpm to get it working in 8.0? ect...

i've found that salespeople at computer stores tend to be pretty clueless about which modems will and won't work in linux. most of the time, they don't even know what a winmodem is. when i was replacing my winmodem, i bought four different modems, all of which i was assured would absolutely work under linux, and only one did. and it had "linux-compatible" on the box. (US Robotics, by the way )

general rule tho, if it's $20, it's not going to work.

I hope that it will be of some help...

Nope, this modem was $85.00, and says on box, Linux compatible . As for how I got it to work:This is exact information I gave MandrakeExpert:::

I have a Linux compatible modem-actiontec 56K call waiting that is a Lucent venus chipset-(used it with 8.0). Now I cannot get it to work. With 8.0, I had to 'su' and get information from cat /proc/pci and then make the entry 'setserial /dev/ttyS3 port 0xc000 irq 9 UART 16550A', then to enter the same line in /etc/rc.d/rc.setserial. When doing this now, it tells me ttyS3 doesn't exist (it doesn't that I can find in 8.1) and I have no idea how to make this one work-most online documentation on modem configuration is for other versions and distros. In Actiontec's documentation, they use the same configuration information that 8.0 used. Any help or a point in the right direction is appreciated.


So far the only replies I get are that I need to find the serial port it is attached to (I have tried every setting to no avail!). I am not sure where to turn or what to do at this point......

forgot to add-my dial out is kppp

Slack will pick up mine (Lucent venus chipset from Zoom) with the binary modules I compiled into the Kernel, but Kppp acts very strange when I dial out, sometimes I can connect, but then I get weird errors, or the system totally freezes. I think that installing the modules on the page I linked to earlier should at least help Kppp to detect your modem again. When you try to query the modem do you get this message?

Sorry, the modem is busy.

If you get that message it's reading from wherever you pointed it to, but since it's a winmodem (hardware+software), it cannot communicate with it properly because the commands it sends it aren't properly processed by your modem. The kernel modules should, but I only say they should because there are so many different system configurations that could cause unpredictable results, resolve your problem with being able to communicate with the modem, and hopefully you'll be able to get your modem to connect to your ISP. OH, Did I mention that that readme is for Mandrake 8.1 that should help you resolve your probs by doing the first couple of steps, but since I don't have mandrake I can't honestly say if it will work or not.

If you have window installed, check which com port it's installed to. I beleve (don't hold me to this since it's been quite a while since I have setup a modem or soundcard in linux!) ttys0 corresponds with Com 1, ttys1 with com 2, ttys2 with com 3 and ttys3 with com 4. That could obviously be the problem, but more than likely it isn't, and I'm sure you've already done that check anyway, but this is for reference for anyone else that is having a similar problem...If you do install the binary kernel modules the modem will be automatacally placed on a symlink for dev/modem, but where that corresponds with I have no idea...I think that the install program finds where your modem is...