I have a Lucent Microelectronics Venus based modem, the Actiontec
Internal Call Waiting modem. I have been trying to get it working well
with Linux 2.4 for some time now. Theodore Ts'o, the maintainer of
the Linux serial driver, and I have talked quite a bit on the subject.
We both suspect that the Venus chipset is broken.
I have some code available at http://www.flyn.org related to this issue.
First, I have an ugly patch that adds support for the Actiontec Internal
Call Waiting modem to Theodore's serial driver version 5.05. Second,
I have a simple kernel module that seems to demonstrate that the Venus
chipset has something wrong with it. The module code should be self
explanatory. To summarize, writing a value, call it foo, to, for example,
the modem's interrupt enable register and then immediately reading the
register's value does not always return foo.
If you have or have access to a Linux box with a Venus-based modem,
answering any of these questions would be very helpful:
o Does your modem work flawlessly with Linux 2.4?
o Could you run my test kernel module? If so, what are the results on
your computer?
I have been lobbying both Lucent and Actiontec to help me with this issue.
Up to this point neither has provided substantial help. However, there
is promise and I am not ready to give up yet.
Thanks!
--
W. Michael Petullo
:wq
On Fri, 9 Mar 2001, W. Michael Petullo wrote:
> If you have or have access to a Linux box with a Venus-based modem,
> answering any of these questions would be very helpful:
>
Well, I'm not absolutely sure if we are talking about the same thing: what
I have is a re-labeled PC-Card modem which identifies according to
cardctl ident:
product info: "LUCENT-VENUS", "PCMCIA 56K DataFax"
manfid: 0x0200, 0x0001
function: 2 (serial)
ATI:
Venus K56FLEX V.90 kfav163 PCMCIA p52198
> o Does your modem work flawlessly with Linux 2.4?
Yes, for me it does - with the standard serial.c driver (and
PCMCIA's serial_cs of course) under Linux 2.0/2.2/2.4.
HTH.
Martin