Thanks for your advice gargamel.

As I've encountered file access problems in the past when running as a non-root user, I always make a point of running my scripts as root when attempting a device configuration (functional modem in this case), and then worry about file permissions when trying to activate the configured device as a non-root user.

I've given up on the ltmodem package and have decided to investigate the slmodem package as this seems to install and run without a problem on my FC4 system, though I still can't get beyond the 'NO DIALTONE' error of wvdial after it successfully sends various initialization strings to the modem:

wvdial damodem
--> WvDial: Internet dialer version 1.54.0
--> 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
--> Sending: ATM1L2
ATM1L2
OK
--> Modem initialized.
--> Sending: ATDT<my-dialout-number>
--> Waiting for carrier.
ATDT<my-dialout-number>
NO DIALTONE
--> No dial tone.
--> Disconnecting at Mon Dec 12 16:32:20 2005


The 'NO DIALTONE' error seems quite common with other slmodem users - but I've yet to find a solution.

-

The soft modem drivers are not interchangeable. LTmodem for Lucent/Agere, SLmodem for Smartlink modems. Conexant modems take a different two other drivers depending on the version of the modem. IBM had an mwave modem in it's older laptops.

Post the output of "lspci" if you have any trouble identifying the needed driver.

Is the file that isn't found by make/gcc actually there, then?
Hmmm. If so, I can only think of a udev problem: Could it be that the missing device is only created when the softmodem is connected to the phone line? Easy to check: Just plug the phone line into your modem port and run

#modprobe ltserial

again.

I think in your case it is vital to find out what causes the GCC warnings. So, do you have a file ltserial.ko somewhere on your machine? If so: Is it in the right place? If yes: Why doesn't GCC/Make see it?

We'll have to track this down in order to solve your problem, I guess.

gargamel

I hope the following helps gargamel -

output from /sbin/lspci:

00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01)
02:00.0 CardBus bridge: Texas Instruments PCI1510 PC card Cardbus Controller
02:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
02:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (MOB) Ethernet Controller (rev 81)


When phone line is plugged into modem port:

/sbin/modprobe ltserial
FATAL: Error inserting ltserial (/lib/modules/2.6.11-1.1369_FC4/other/ltserial.ko): No such device


Does ltserial.ko exist?

locate ltserial.ko
/lib/modules/2.6.11-1.1369_FC4/other/ltserial.ko

locate ltmodem.ko
/lib/modules/2.6.11-1.1369_FC4/other/ltmodem.ko


The command '/sbin/modprobe ltmodem' returns to a command prompt without producing any errors.


/sbin/lsmod shows that the 'ltmodem' module is loaded:

Module Size Used by
ltmodem 557520 0



I'm afraid I don't know what to do next.

-

Update:

I've just been told by somebody who inspected my ModemData.txt file that the modem on my laptop uses a Conexant CODEC, and that slmodem and ltmodem simply won't work.

I was then advised to use the linuxant HSF driver in an effort to get my conexant internal modem working.

Unfortunately, this is not the solution I wanted if it means I need to pay linuxant for a driver that cannot be ported to a new laptop if I decide to upgrade my system (determined after sending them several e-mails).

I visited the conexant web site to try to find a free driver to download - they provide free downloads for windows users, but their link for linux users goes directly to linuxant (pay for a driver). Perhaps not an agreeable state of affairs, but understandable given the nature of the beast.

Anyway, thanks to gargamel and others who offered insightful suggestions. Very much appreciated.

John

-

Thank you, John.

Just for completeness:
- Make sure that you have the right driver for your modem. ltmodem is for Agere/Lucent, and only for that.
- Hope you find a good, free solution.
- If you only find proprietary stuff for which you would have to pay you might want to consider purchasing a good external faxmodem, instead. Disadvantage: You have to carry an additional device with you when you travel. Advantage: Usually much more reliable than *any* softmodem based solution (although my Agere/Lucent works just fine with ltmodem.ko, so far). If the external modem is cheaper than the softmodem driver, then it's probably the hardware solution is to be preferred...
But don't buy the cheapest modem you can find, get a good one instead. Recommended: Acer Modem 56 Surf. Not recommended: USR/3Com. The latter are very good in data mode, but they are a nightmare when you want to use them for sending and receiving fax with standard compliant software like Hylafax. The Acer works like a charm right out of the box with any software I have used, so far. My old USR/3Com did not.

Ok, it might not be relevant anymore, but I looked at your logs.

The warning said that make was looking here:

/lib/modules/2.6.11-1.1369_FC4/kernel/drivers/misc/ltserial.ko

Compare this to the results of locate:

/lib/modules/2.6.11-1.1369_FC4/other/ltserial.ko

So if you your softmodem was an Agere/Lucent the next step would be to check the scripts and configuration files for LTmodem in order to find the reason for the different paths. The question we had to answer would be:

Why does make look at the wrong location?

But first of all, check again, what type of modem you actually have.

Good luck,

gargamel

It looks like you have an intel modem. I have never worked with those but recall that intel did provide linux drivers for the 2.4 kernel. Newer intel modems would work with the smartlink modem driver.

Try googling for intel linux modem. You should be able to get it running albeit with an older kernel.

Also the Hardware compatiblilty list here has a lot of info on intel modems
http://www.linuxquestions.org/hcl/showcat.php/cat/168


You lspci looks like the output from a laptop so you will not have the luxury of changing the modem although lucent LTmodems were available in pcmcia cards.