Linmodems Mailing list Archives


Return-Path: <>
Mailing-List: contact; run by ezmlm
Delivered-To: mailing list
Received: (qmail 13572 invoked from network); 4 Mar 2001 04:49:06 -0000
Received: from (
  by with SMTP; 4 Mar 2001 04:49:06 -0000
Received: from ([]
	by with esmtp (Exim 3.16 #5)
	id 14ZQRd-0001ya-00 
	for; Sat, 03 Mar 2001 23:48:33 -0500
Sender: marv
Message-ID: <>
Date: Sat, 03 Mar 2001 23:48:09 -0500
From: Marvin Stodolsky <>
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: LinModems <>
Subject: Resource Conflicts, Compaq 1500c Re: Lucent Winmodem
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

The good question Carlos poses below is:
While out Compaq 1500c Armada laptops are near identical,
why did only he encounter an IRQ conflict with the PCMCIA system and the
IRQ 3 of the isa Lucent modem.

The answer can only be guessed at, but way well be representative of
recurring problems reported to the List.  We can assume that PC
assemblers will want to use every last(aging) component in their
inventories.  Probably initial large PC runs are well conceived and
designed.  But when it comes to left over components, they way well be
kludged together with minimal flexibilty, just enough that they will
boot WinSwish when sold at YourComputerChain.

My Compaq was part of a large Company buy, with service reliability
contracts, making it Compaq's benefit not to cut any corners.  But  all
buyers may not get such "royal" hardware, and may have to fight it a bit
more to get implementation under Linux.

Microsoft has spent Many millions on software development to ameliorate
resource conflicts.  Under Linux, things are definitly improving fast,
much owing to the fact that our Folks with strong technical background
have access to the code, and can rapidly turn around improvements. But
there is still clearly much to be done in automating resource conflict
resolution, as contrasted to the sometimes Heroic efforts/contributions
reported to this List

-------- Original Message --------
Subject: Re: [Fwd: Conflicts, Compaq 1500c Re: Lucent Winmodem]]
Date: Fri, 02 Mar 2001 18:03:14 -0300
From: Carlos Menezes <>
To: Marvin Stodolsky <>

Your suggestion was OK! I simply excluded IRQ 3 at config.opts file and
the conflict disappeared. Only a couple of
-If you have a notebook equal than mine, why you didn't have to exclude
IRQ 3 of config.opts?
-Wvdial didn't recognize a busy line signal. What is happening?


Carlos Menezes.

Marvin Stodolsky wrote:

> -------- Original Message --------
> Subject: Conflicts, Compaq 1500c Re: Lucent Winmodem]
> Date: Thu, 01 Mar 2001 16:44:54 -0500
> From: Marvin Stodolsky <>
> To: LinModems <>
> Every Linux installation should have a file (somewhere) like that below,
> within which IRQs to be avoided by PCMCIA can be set,
> to leave the IRQ free, for say ltmodem.o
> MarvS
> #/etc/pcmcia/config.opts
> #
> # Local PCMCIA Configuration File
> #
> #----------------------------------------------------------------------
> # System resources available for PCMCIA devices
> include port 0x100-0x4ff, port 0x800-0x8ff, port 0xc00-0xcff
> include memory 0xc0000-0xfffff
> include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff
> # High port numbers do not always work...
> # include port 0x1000-0x17ff
> # Extra port range for IBM Token Ring
> include port 0xa00-0xaff
> # Resources we should not use, even if they appear to be available
> # First built-in serial port
> exclude irq 4
> # Second built-in serial port
> #exclude irq 3
> # First built-in parallel port
> exclude irq 7
> # marv LANBUS test
> # exclude irq 11
> #-------------

Webmaster: Russell Nelson
Last modified: Wed Jul 30 11:02:43 EDT 2003