From: Steven Walter <srwalter@yahoo.com>
To: Dana Lacoste <dana.lacoste@peregrine.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: actiontec PCI call waiting modem not responding with kernels 2.4.7+, 2.4.6 is ok though..
Date: Mon, 12 Aug 2002 17:43:50 -0500 [thread overview]
Message-ID: <20020812224350.GC25701@hapablap.dns2go.com> (raw)
In-Reply-To: <1029158509.31368.108.camel@dlacoste.ottawa.loran.com>
On Mon, Aug 12, 2002 at 09:21:49AM -0400, Dana Lacoste wrote:
> Another confirmed "working" report.
>
> If you're using devfs it's easy to tell if it's tts/4 or tts/2 or
> whatever, but assuming you're not using setserial and you're using
> the right ttyS it works fine (using the actiontec and IBM versions
> of the same card, based on the lucent venus chipset, with
> 2.4.everything)
That makes for 4 working reports to 2 non-working. Apparently, these 2
people are having a true hardware issue, not merely a configuration
problem.
Can you tell me how old your modem is? (i.e., about how long ago you
bought it?) My theory is that actiontec made a new revision of the
modem that has sacrificed pure 16550 UART emulation in order to expose
more of the call-waiting feature to the computer.
Additionally, even my modem occasionally ceases to work, requiring a
reboot. When this happens, dmesg contains the message "LSR safety check
failed."
Here's to getting this figured out!
--
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
-- George Orwell
This concept of "wuv" confuses and infuriates us!
-- Lrrr of Omicron Persei VIII
next prev parent reply other threads:[~2002-08-12 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-10 19:29 actiontec PCI call waiting modem not responding with kernels 2.4.7+, 2.4.6 is ok though Blaise
2002-08-11 5:31 ` Steven Walter
2002-08-12 13:21 ` Dana Lacoste
2002-08-12 22:43 ` Steven Walter [this message]
2002-08-12 22:36 ` Blaise
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020812224350.GC25701@hapablap.dns2go.com \
--to=srwalter@yahoo.com \
--cc=dana.lacoste@peregrine.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox