[ale] Oddly Slow Internal Modem
Matt Smith
msmith at risklabs.com
Mon Oct 28 15:03:35 EST 2002
I've experienced a similar phenomenon when there was an IRQ conflict. Any
chance there are still some ISA peripherals that might be conflicting? Or
perhaps COM1 isn't truly disabled?
--Matt
-----Original Message-----
From: Jeff Hubbs [mailto:hbbs at attbi.com]
To: ale at ale.org
Sent: Monday, October 28, 2002 2:53 PM
To: Atlanta Linux Enthusiasts
Subject: [ale] Oddly Slow Internal Modem
I have a Gentoo 1.4rc1 P/100 machine set up here with an ISA-bus US
faxmodem inside. When I run minicom, I can talk to the modem and it
talks back, but at an excruciatingly slow speed. For example, when
minicom fires up, it puts up its "Initializing Modem" box, that goes
away like normal, then it lands in its comm mode. Minicom then tries to
send the modem the string
AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
It takes about 15 seconds for the first half of that string to echo back
and another 15 for most of the rest of it, then another 10 or so for it
to complete with a carriage return. I don't seem to get an "OK" back
from that, but if I type something in like "at+fclass=?" it takes about
15 seconds to get an echo and another 15 to get a response.
I looked through dmesg and found that ttyS00 (COM1) and ttyS02 (COM3,
the modem) appeared to both be set to IRQ 4, so, in the interest of
simplicity, I simply disabled COM1 in the BIOS. However, this didn't
solve the problem of the unusual lag .
Any ideas as to what's going on here?
- Jeff
---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be
sent to listmaster at ale dot org.
-----
Confidential Information
The information in this e-mail message (including any attachments) is
privileged and confidential information intended only for the use of the
individual or entity named above. If the reader of this message is not the
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this communication is strictly prohibited.
---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be
sent to listmaster at ale dot org.
More information about the Ale
mailing list