Subject: Re: "can't map i/o space"
To: Bob Bernstein <>
From: Jared D. McNeill <>
List: current-users
Date: 06/03/2006 08:21:43
On 2-Jun-06, at 3:17 PM, Bob Bernstein wrote:

> I have a build of current (i386 as of two days ago) on an old Gateway
> Celeron box that sets up my Intel NIC, but not the Realtek one. Nor  
> does it
> configure the Ensoniq sound chip.
> I shouldn't really make this a "current" issue because 3.0 stable  
> displayed
> the same behaviour before I moved to current.
> A search of the list archives suggested that perhaps some of the  
> pci-related
> kernel Options need to be turned on, but I am at a loss to know  
> which ones.
> Any guidance would be greatly appreciated. dmesg starts below:

Do you have any BIOS options named similar to the following?:
	PnP Aware OS
	Running Windows 95

May be a variation of either 'Windows 95' or 'PnP OS'. Anyway, if you  
can, toggle this value and try booting once more. I've found this to  
be the cause of the majority of 'can't map i/o space' problems on