Subject: Re: detecting a WaveLAN card
To: Brook Milligan <firstname.lastname@example.org>
From: Charles M. Hannum <email@example.com>
Date: 02/21/2001 08:39:32
On Wed, Feb 21, 2001 at 08:32:21AM -0700, Brook Milligan wrote:
> This is generally because the memory is not mapped correctly -- typically
> due to a conflict with some other device. For example, there may be
> another device at the same address, and there are known problems on some
> PCs when trying to use both 8-bit and 16-bit mappings in the same 128k
> range in the `I/O hole'.
> Thanks for the info, but I'm not exactly sure what to do about that.
> Can I control how the memory is mapped in any way (i.e., via kernel or
> BIOS configuration options)? Can I figure out what the conflicts are?
The `I/O hole' refers to the region 0xa0000-0xeffff, traditionally
used for talking to addin devices through memory space. (Some parts
of it are now commonly used for things like VGA extension BIOSes.)
You can try configuring the pcic to use a different region.