Payment to anyone who can help me get my U.S. Robotics Modem
model 00568603 Sportster dial-up external dial-up modem running on
RedHat
Linux 7.3 (2.4.18 kernel) in under 1/2 hour. It seems that the modem
is not being detected. And possibly RH 7.3 lacks a driver for this
modem. Let me
know when a good time for you to work on this is if you need to
troubleshoot.
-> What I've Done So Far:
On my Slackware 4.x Linux in '99, this modem worked just fine.
'ifconfig' only shows loopback. I have tried cycling the power on the
modem, as one newsgroup posting recommended. I've looked at the links
from /dev/ttySx and tried varying device targets with the GUI set-up
dialogues. I've tried both GNOME and KDE GUI wizards. GNOME's
hardware profiler does not show the modem. I've searched for a driver
kit for this modem on Linux on the web but haven't found one. |
Request for Question Clarification by
googleexpert-ga
on
06 Mar 2003 13:08 PST
have you checked out:
http://www.linuxquestions.org/questions/history/39949 ?
|
Clarification of Question by
gardens_of_now-ga
on
06 Mar 2003 14:05 PST
I just checked out the entire thread at
http://www.linuxquestions.org/questions/history/39949
and there was no resolution of the problem there.
|
Request for Question Clarification by
maniac-ga
on
06 Mar 2003 16:09 PST
Hello Gardens_of_now,
Hmm. Based on my experience with Red Hat, I would be surprised if an
external modem would be detected by a hardware scan (usually done by
scanning the PCI bus). A few questions / comments
- During the original install of Red Hat, was this device present and
if so, did you attempt to configure (to establish your network
interface)? I assume you don't want to reinstall Linux, but this would
be helpful to know.
- At GMU, they have a pretty detailed "mini-how-to" for their
specific set up.
http://cpe.gmu.edu/linux.htm
This mentions both the Sportster external and internal modem. The
network settings would be different, but perhaps this would give you a
pointer to the steps involved.
- If there are any specific error messages in /var/log/messages
related to the modem, please include them in a clarification request.
--Maniac
|
Clarification of Question by
gardens_of_now-ga
on
06 Mar 2003 17:15 PST
The external modem was turned off during the original install of RH
7.3 Linux.
The error message I get from the KDE's KPP GUI utility is "Modem is
busy". The RedHat "neat" GUI utility hangs sometimes when I try to
use the modem. I will get the /var/log messages when I get a chance.
The GMU page mentioned deals with an internal one, and does not
discuss problems with detection.
Is there a detection utility that I can run?
I would think that there would be a way to check ttyS0 and ttyS1,
etc., to see if they actually are pointing to any hardware or not.
|
Request for Question Clarification by
maniac-ga
on
06 Mar 2003 19:24 PST
Hello Gardens_of_now,
It appears that the "modem is busy" message is a generic phrase to
indicate that KDE was not able to connect with the port(s) it expects
to use. One user ended up adding a link from /dev/ttyS3 to the real
port where the modem is connected to get it to work. Most other times,
it is because the user had a winmodem (not your problem).
Search phrase: "modem is busy" KDE "external modem"
The Modem-HOWTO at
http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/ps/Modem-HOWTO.ps.gz
http://www.ibiblio.org/mdw/HOWTO/Modem-HOWTO.html
or the Serial-HOWTO at
http://www.ibiblio.org/mdw/HOWTO/Serial-HOWTO.html
has some additional suggestions including
- use zmodem or kermit to talk to the port directly. Type AT and see
if you get OK as a response to confirm the port connection. (you
should have one or both already installed)
- use wvdialconf to "find" the modem and save settings for it. This
is part of the "wvdial" RPM
http://www.rpmfind.net/linux/rpm2html/search.php?query=wvdial&submit=Search+...&system=&arch=
for locations which have this.
The other possibility (unlikely) is that the serial line is in use.
You can set up a Linux box to allow logins on the serial ports. If so,
look for getty (or similar names) as a job running - mingetty is the
one for the virtual consoles (ctrl-alt-F1, thru -F6; ctrl-alt-F7 for
your X display); don't kill those. If so, I can walk you through
changing the configuration for those.
--Maniac
|
Clarification of Question by
gardens_of_now-ga
on
11 Mar 2003 00:14 PST
Thanks, I will try these approaches. Using 'wvdial' seems like it
might work, but would it really do more than the KDE GUI utility?
How can I check to see if the serial line is really in use (the
unlikely possibility)? (I have nothing networkish plugged into the
box besides the modem cable).
|
Request for Question Clarification by
maniac-ga
on
11 Mar 2003 05:25 PST
Hello Gardens_of_now,
About your follow up questions -
Q: Would it [wvdial] really do more than the KDE GUI utility?
A: Not until it is configured properly. That is why I mentioned
"wvdialconf" which is supposed to try several possible interfaces to
"find" the modem. Once you are sure of the connection to the modem -
the appropriate settings to the KDE utilities should get them to work
as well.
Q: How can I check to see if the serial line is really in use (the
unlikely possibility)?
A: As I mentioned, there would be a job running connected to that
line. If you did
ps -fe
you may see a number of mingetty jobs - those are connected to the
virtual consoles and won't use the serial lines. There may also be a
copy of agetty (or similarly named application) running as well. The
purpose of agetty and similar programs is to give you a login prompt
for a serial line (e.g, for dial-in to your computer). The Red Hat
install doesn't do this - so it would have to have been something set
up by a root user on your system.
--Maniac
|
