Thanks to all who replied to my plea. I am writing this response from
Linux. I have no sound, no USB support, and no printer, but I am at least
connected. First things first, right? The problem was indeed an IRQ
conflict.
--Chase
-Original Message-
From: Chase Brady [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Wed, 23 May 2001 10:06:24 -0400
Subject: [newbie] Actiontec Internal Call Waiting modem setup
I am trying to configure an Actiontec Internal Call Waiting modem on
Mandrake 8.0. This is a hardware modem advertised as compatible with
Linux.
I have looked through the archives, and apparently some have had
success
with it. I got the configuration instructions from Actiontec's web
site
(also in the archives). After getting the IO address using a cat
/proc/pci command, I type the following
# setserial /dev/ttyS3 port 0xbc00 spd_vhi skip_test auto_irq
autoconfig
At this point, the system hangs. I get no prompt, no message, and no
response to keys or mouse. Kind of like Windows. I've tried this from
the
Gnome terminal, from the regular terminal under KDE, and from failsafe.
I
tried it with ttyS4, and I tried disabling the onboard sound, which
changed
the modem's IRQ from 11 to 10, and changed the IO address. Same result
every time. I deleted Mandrake and reinstalled. Same thing.
I could well have an IRQ conflict here, since it appears that all my
peripherals are trying to use IRQs 10 and 11. Before I start
disassembling
my system trying to find a way to get it working, I thought I'd ask.
Is it
normal for the system to hang in response to an IRQ conflict here, or
is
there a deeper problem?
My system: Soyo K7VTA motherboard with 750mHz Duron, 128M PC133 ram, 5G
and
20G Maxtor drives (Mandrake on 2nd drive), Diamond Speedstar A55,
Adaptec
AVA 1505 driving Smart Friendly CDR 4012, D-Link ethernet (not
currently
in use), Ensoniq AudioPCI and Hoontech Soundtrack 4ch sound cards. Any
help
would be appreciated.
--Chase
