Re: Modem configuration:
From: Rob (sa92003_at_yahoo.com)
Date: 07/15/03
- Next message: Rob: "Re: Modem configuration:"
- Previous message: Peter Klein: "Sound Driver Problem (2.6.0-test1, 8233)"
- In reply to: Dances With Crows: "Re: Modem configuration:"
- Next in thread: Markku Kolkka: "Re: Modem configuration:"
- Reply: Markku Kolkka: "Re: Modem configuration:"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 15 Jul 2003 10:00:16 -0700
> When following up to an article, include context so people know what the
> hell you're talking about!
I believed the context was preéstablished by the reasonably detailed
conversation of the shallow-nested thread in which it was contained.
Very rarely, there are those times when, like that, I feel that is
more representational to duplicate the terminal verbatim and just
leave it at that. Mixed with frustration at the time, maybe it wasn't
the best decision.
> And don't post the same message twice.
I had some control over that. For that I apologize.
> [...but its automatic installation script failed midway through
> because /dev/modem already existed. His attempt to rpm -Uvh it
> again after removing /dev/modem failed, because the RPM database
> thought the package was already installed. ]
I am utterly unqualified to make those assumptions, Crows.
All I can say is that a few days ago, I did this:
---
# rpm -i ltmodem-kv_2.4.20_6-8.26a9-1.athlon.rpm
---
(...and not this:
---
# rpm -Uvh ltmodem-kv_2.4.20_6-8.26a9-1.athlon.rpm
---)
After cat[ing] for the port and irq settings of the modem, I wrote
this:
---
setserial /dev/ttyS2 irq 11 port 0x24b0 autoconfig
---
...and then I followed the apparent success (Linux returned a prompt)
of that up with this:
---
ln -sf /dev/ttyS2 /dev/modem
---
It is possible that I may have set those conditions in the same
session as when I went to install the driver package. Maybe not.
Later, under your advisement I went to remove that failed
installation, and I didn't know how to utilize your information (i.e.,
I didn't know that "ltmodem" was not likely the name of what I needed
to remove, and that the full name
ltmodem-kv_2.4.20_6-8.26a9-1.athlon.rpm was definitely not). Thank
you (and thank you Alex) for providing me with the rpm -qa | grep
ltmodem script. (A piped routine is technically a script right? I'm
a Doze user. :-)
In any event, throughout all of this I have found that if I leave the
inturrupt set at the same number as what cat reports, I get only
"Modem cannot be found." or "Modem is busy." (I forget which.) But I
definitely don't get to "---
"Modem Ready."
"Initializing modem..."
...as I do after I've reset the inturrupt:
---
setserial /dev/ttyS2 irq 11 port 0x24b0 autoconfig
---
Here is the latest transaction. While not necessarily the best for
the occasion, my commands to Linux are self explanatory:
---
[rob@localhost dirwhatever]$ rpm -qa | grep ltmodem
ltmodem-kv_2.4.20_6-8.26a9-1
[rob@localhost dirwhatever]$ su
Password:
[root@localhost dirwhatever]# rpm -e ltmodem-kv_2.4.20_6-8.26a9-1
Finished device node cleanup.
[root@localhost dirwhatever]# rm /dev/modem
rm: cannot lstat `/dev/modem': No such file or directory
[root@localhost dirwhatever]# rm /dev/modem2
rm: cannot lstat `/dev/modem2': No such file or directory
[root@localhost dirwhatever]# ln -s /dev/ttyS2 /dev/modem2
[root@localhost dirwhatever]# rpm -Uvh
ltmodem-kv_2.4.20_6-8.26a9-1.athlon.rpm
Preparing...
########################################### [100%]
1:ltmodem-kv_2.4.20_6
########################################### [100%]
Diagnostic information is being written to
/usr/share/doc/ltmodem-kv_2.4.20_6-8.26a9/LTinstall.txt
A supported Lucent/Agere DSP chipset modem is identified:
PCI_ID=11c1:0442
VENDOR 0x11c1 DEVICE 0x0442
ID are within the serviced ranges for Lucent/Agere DSP modems:
------------------------------------------
LUCENT 0x11c1 0x0440-0x045c
XIRCOM 0x115d 0x0000-0x000F
XIRCOM 0x115d 0x0440-0x045c
XIRCOM 0x115d 0x0010-0x03ff
-------------------------------------------
Drivers and their compiler kits are available at:
http://www.heby.de/ltmodem/
For more details read the Recording file.
redhat
Usage: lspci [<switches>]
-v Be verbose
-n Show numeric ID's
-b Bus-centric view (PCI addresses and IRQ's instead of
those seen
by the CPU)
-x Show hex-dump of config space
-s [[<bus>]:][<slot>][.[<func>]] Show only devices in selected
slots
-d [<vendor>]:[<device>] Show only selected devices
-t Show bus tree
-m Produce machine-readable output
-i <file> Use specified ID database instead of
/usr/share/hwdata/pci.ids
-M Enable `bus mapping' mode (dangerous; root only)
-P <dir> Use specified directory instead of /proc/bus/pci
-H <mode> Use direct hardware access (<mode> = 1 or 2)
-F <file> Read configuration data from given file
-G Enable PCI access debugging
scanmodem finished, proceeding with autoload section
The system motherboard has class CPU=i686
while these drivers were targeted for a CPU=athlon
Often a ranking System_CPU > Target_CPU will be problem free,
but vice versa could be a problem!
Test and assess functionality.
There is always the option of compiling perfectly matched drivers
with the ltmodem-8.26a9.tar.gz at http://www.heby.de/ltmodemq
Made modem device node /dev/ttyLT0
group ownership set to uucp
with symbolic link /dev/modem --> /dev/ttyLT0
Writing modules autoloading lines to /etc/modules.conf:
Using /sbin/depmod
Updating with: /sbin/depmod -a
Capturing output to /tmp/ltmodem/tmpfile and parsing.
Your system is lacking Default lines in /etc/modules.conf
which are usually needed to support the modem communications protocol
PPP.
Some modem installations replace these Defaults
with lines specific to particular modem hardware.
There may be problems using the Lucent/Agere modem without these
Default lines. The suspect lines are:
------------------------------
cat /tmp/ltmodem/tmpfile
------------------------------
and are being inserted in
/usr/share/doc/ltmodem-kv_2.4.20_6-8.26a9/LTinstall.txt for your
judgement.
Should you insert them in /etc/modules.conf, inform the System with
/sbin/depmod -a
The modem drivers dependencies are properly resolved.
A folder has been installed in your Systems documentation,
/usr/share/doc/ltmodem-kv_2.4.20_6-8.26a9
containing much useful guidance and uilities. Updates can be
downloaded from http://www.heby.de/ltmodem/ as DOCs.tgz
To get online, the Port to be specified in your dialout scripts is:
/dev/ttyLT0 or its symbolic, /dev/modem
A summary of installation actions with Advice is contained in:
/usr/share/doc/ltmodem-kv_2.4.20_6-8.26a9/LTinstall.txt
Browse DOCs/Ltmodem.html for issues that may be relevant to your
system and useful URLs
Also see DOCs/LastAdvice
Some dialer utilities including KPPP require that Each User set up a
configuration,
as there could be diverse configurations on multi-User systems.
Read DOCs/wvdial.txt for aid in configuring the smart dialup
utility, WVDIAL
Otherwise, get Online and Enjoy
Relate problems to discuss@linmodems.org
Gratitude too, to discuss@linmodems.org
If not familar with the ltmodem drivers, run the interactive CHECKOUT
utility by executing:
/usr/share/doc/ltmodem-kv_2.4.20_6-8.26a9/utils/checkout
[root@localhost Files_2003]#
---
Suffice it to say I still get idled on "Initializing modem...".
I've also instructed the OS to:
---
ln -s /dev/ttyLT0 /dev/modem
---
...and its command line reply is:
"No such device."
Thanks again.
-Rob
- Next message: Rob: "Re: Modem configuration:"
- Previous message: Peter Klein: "Sound Driver Problem (2.6.0-test1, 8233)"
- In reply to: Dances With Crows: "Re: Modem configuration:"
- Next in thread: Markku Kolkka: "Re: Modem configuration:"
- Reply: Markku Kolkka: "Re: Modem configuration:"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
Loading
