"can't map i/o space"

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:

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002,
2003, 2004, 2005, 2006
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights
reserved.

NetBSD 3.99.20 (GENERIC) #0: Wed May 31 23:12:46 EDT 2006
	rootnbsdboy.legomenon.org:/usr/obj/sys/arch/i386/compile/
GENERIC
total memory = 255 MB
avail memory = 242 MB
BIOS32 rev. 0 found at 0xfd7b0
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel Celeron (Mendocino) (686-class), 365.04 MHz, id
0x660
cpu0: features
183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR>
cpu0: features 183f9ff<PGE,MCA,CMOV,PAT,PSE36,MMX>
cpu0: features 183f9ff<FXSR>
cpu0: I-cache 16 KB 32B/line 4-way, D-cache 16 KB 32B/line
4-way
cpu0: L2 cache 128 KB 32B/line 4-way
cpu0: ITLB 32 4 KB entries 4-way, 2 4 MB entries fully
associative
cpu0: DTLB 64 4 KB entries 4-way, 8 4 MB entries 4-way
cpu0: 8 page colors
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult,
wr/inv ok
pchb0 at pci0 dev 0 function 0
pchb0: Intel 82443LX PCI AGP Controller (rev. 0x03)
agp0 at pchb0: aperture at 0xf8000000, size 0x4000000
ppb0 at pci0 dev 1 function 0: Intel 82443LX AGP Interface
(rev. 0x03)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled
vga1 at pci1 dev 0 function 0: ATI Technologies 3D Rage Pro
(AGP) (rev. 0x5c)
wsdisplay0 at vga1 kbdmux 1: console (80x25, vt100
emulation)
wsmux1: connecting to wsdisplay0
pcib0 at pci0 dev 7 function 0
pcib0: Intel 82371AB (PIIX4) PCI-ISA Bridge (rev. 0x02)
piixide0 at pci0 dev 7 function 1
piixide0: Intel 82371AB IDE controller (PIIX4) (rev. 0x01)
piixide0: bus-master DMA support present
piixide0: primary channel wired to compatibility mode
piixide0: primary channel interrupting at irq 14
atabus0 at piixide0 channel 0
piixide0: secondary channel wired to compatibility mode
piixide0: secondary channel interrupting at irq 15
atabus1 at piixide0 channel 1
uhci0 at pci0 dev 7 function 2: Intel 82371AB (PIIX4) USB
Host Controller (rev. 0x01)
uhci0: interrupting at irq 9
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
piixpm0 at pci0 dev 7 function 3: SMI
iic0 at piixpm0: I2C bus
eap0 at pci0 dev 12 function 0: Ensoniq AudioPCI 97 (rev.
0x02)
eap0: can't map i/o space
fxp0 at pci0 dev 13 function 0: i82559 Ethernet, rev 8
fxp0: interrupting at irq 11
fxp0: Ethernet address 00:90:27:94:da:e3
inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rtk0 at pci0 dev 14 function 0: Accton MPX 5030/5038
10/100BaseTX
rtk0: can't map i/o space
isa0 at pcib0
lpt0 at isa0 port 0x378-0x37b irq 7
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
attimer0 at isa0 port 0x40-0x43: AT Timer
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
npx0 at isa0 port 0xf0-0xff
npx0: using exception 16
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
pcppi0: attached to attimer0
isapnp0: no ISA Plug 'n Play devices found
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
Kernelized RAIDframe activated
wd0 at atabus0 drive 0: <QUANTUM FIREBALL EX6.4A>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 6149 MB, 13328 cyl, 15 head, 63 sec, 512 bytes/sect x
12594960 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2
(Ultra/33)
wd0(piixide0:0:0): using PIO mode 4, Ultra-DMA mode 2
(Ultra/33) (using DMA)
atapibus0 at atabus1: 2 targets
cd0 at atapibus0 drive 0: <GCR-8521B, , 1.00> cdrom
removable
cd0: 32-bit data port
cd0: drive supports PIO mode 4, DMA mode 2
wd1 at atabus1 drive 1: <FUJITSU MPE3084AE>
wd1: drive supports 16-sector PIO transfers, LBA addressing
wd1: 8063 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x
16514064 sectors
wd1: 32-bit data port
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4
(Ultra/66)
cd0(piixide0:1:0): using PIO mode 4, DMA mode 2 (using DMA)
wd1(piixide0:1:1): using PIO mode 4, Ultra-DMA mode 2
(Ultra/33) (using DMA)
boot device: wd0
root on wd0a dumps on wd0b
root file system type: ffs
wsdisplay0: screen 1 added (80x25, vt100 emulation)
wsdisplay0: screen 2 added (80x25, vt100 emulation)
wsdisplay0: screen 3 added (80x25, vt100 emulation)
wsdisplay0: screen 4 added (80x25, vt100 emulation)


Best regards,

-- 
Bob Bernstein

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

> rtk0 at pci0 dev 14 function 0: Accton MPX 5030/5038
10/100BaseTX
> rtk0: can't map i/o space

Please post the pcictl dump output for this device ( try
pcictl pci0 
dump -d 14 )
Might need a quirks entry or something like that, some
vendors like to 
play shuffle-the-BARs with their chips.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRICJLcpnzkX8Yg2nAQIpMAf/bYWOdYJ0wNTTTTJYstUDgr/R2/5b
x0Eq
q5icNSP2YawISLAZ0Raw7JtnR+r2PBOrJ0DYSusi7EmYB8lTaSMcPcdvTTiM
MNch
4JSR/OnRWCK3qjjDoh2hVcUdsUw2C0BrutTzSIyvedlZdjOkvjpRfxY2srRs
qbk6
3KPG/YRj3nlB0VHY2joDRkNDaTQf5/aNi1pf2Wh3DDy1IWOBaqI7GjH5jkdy
YdGC
pGUJJ8ZAdrDcgg3BMyLhXm8nreSZ6i40xdr+acmUdGxS3lZIAR/j1g4oT7P9
1weV
iZd2K/khYHTSji8xYYdmAI0kMk0Km5qjI4glsDnfCoMeIcloIb8fXA==
=m2Qq
-----END PGP SIGNATURE-----

On 02Jun2006 02:53PM (-0400), Michael Lorenz wrote:

> Please post the pcictl dump output for this device (
try pcictl pci0 
> dump -d 14 )

voila:

PCI configuration registers:
  Common header:
    0x00: 0x12111113 0x02900104 0x02000010 0x00004000

    Vendor Name: Accton Technology (0x1113)
    Device Name: MPX 5030/5038 Ethernet (0x1211)
    Command register: 0x0104
      I/O space accesses: off
      Memory space accesses: off
      Bus mastering: on
      Special cycles: off
      MWI transactions: off
      Palette snooping: off
      Parity error checking: off
      Address/data stepping: off
      System error (SERR): on
      Fast back-to-back transactions: off
    Status register: 0x0290
      Capability List support: on
      66 MHz capable: off
      User Definable Features (UDF) support: off
      Fast back-to-back capable: on
      Data parity error detected: off
      DEVSEL timing: medium (0x1)
      Slave signaled Target Abort: off
      Master received Target Abort: off
      Master received Master Abort: off
      Asserted System Error (SERR): off
      Parity error detected: off
    Class Name: network (0x02)
    Subclass Name: ethernet (0x00)
    Interface: 0x00
    Revision ID: 0x10
    BIST: 0x00
    Header Type: 0x00 (0x00)
    Latency Timer: 0x40
    Cache Line Size: 0x00

  Type 0 ("normal" device) header:
    0x10: 0x00001401 0xf4101000 0x00000000 0x00000000
    0x20: 0x00000000 0x00000000 0x00000000 0x12111113
    0x30: 0x00000000 0x00000050 0x00000000 0x40200105

    Base address register at 0x10
      type: i/o
      base: 0x00001400, not sized
    Base address register at 0x14
      type: 32-bit nonprefetchable memory
      base: 0xf4101000, not sized
    Base address register at 0x18
      not implemented(?)
    Base address register at 0x1c
      not implemented(?)
    Base address register at 0x20
      not implemented(?)
    Base address register at 0x24
      not implemented(?)
    Cardbus CIS Pointer: 0x00000000
    Subsystem vendor ID: 0x1113
    Subsystem ID: 0x1211
    Expansion ROM Base Address: 0x00000000
    Capability list pointer: 0x50
    Reserved  0x38: 0x00000000
    Maximum Latency: 0x40
    Minimum Grant: 0x20
    Interrupt pin: 0x01 (pin A)
    Interrupt line: 0x05

  Capability register at 0x50
    type: 0x01 (Power Management, rev. 1.0)

  Device-dependent header:
    0x40: 0x00000000 0x00000000 0x00000000 0x00000000
    0x50: 0x76010001 0x00000100 0x00000000 0x00000000
    0x60: 0x00000000 0x00000000 0x00000000 0x00000000
    0x70: 0x00000000 0x00000000 0x00000000 0x00000000
    0x80: 0x00000000 0x00000000 0x00000000 0x00000000
    0x90: 0x00000000 0x00000000 0x00000000 0x00000000
    0xa0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xb0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xc0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xd0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xe0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xf0: 0x00000000 0x00000000 0x00000000 0x00000000



Best regards,

-- 
Bob Bernstein

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

>       I/O space accesses: off
>       Memory space accesses: off

This should NOT happen. Of course we can't access i/o space
when it's 
not enabled. I wonder why it's disabled.

>     Base address register at 0x10
>       type: i/o
>       base: 0x00001400, not sized
>     Base address register at 0x14
>       type: 32-bit nonprefetchable memory
>       base: 0xf4101000, not sized

These look ok though.

Are you familiar with pcitweak?
If so please use it to enable i/o and memory access on this
card, cross 
fingers and reboot. ( to do that set the lower two bit in
the command 
register which is at offset 0x4 ) Hopefully it stays
enabled. I'm not 
at all familiar with the rtk driver but enabling i/o and
memory access 
there is trivial.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRICW9MpnzkX8Yg2nAQIe3wgAnXB3SBeH4cpp8emgUalIBunIC7l/
ui3a
sRz9w/YN1uWQqEVa20sQVG3RoREWjz+QDZblfjuMRDw0f4n+/8EZSU8EHDmy
C8vJ
1f71QCmRtFgNfv4bQlqeOxvMp43onUcOVvEBdo6TOu8IKqvpiIQTtwJCaaB8
xMZ1
WBr9Z7PLNtc1x8GGkVsVVNYyFHycI7uZKDEd7dNX9Yfy6HAYhL9EMy64o7c6
iGo+
tFzJfb3y3N7Pf8x4zaxYY2l5CKlNgnk0XECWEXvkdd2AW/2/dX46LQvB1+TH
kLgI
10xG0FJx0QB0idlWnvnLTL6e5+J1fUXfJBzKbVfDjbDu4NCqdVkBgw==
=qceQ
-----END PGP SIGNATURE-----

On 02Jun2006 03:52PM (-0400), Michael Lorenz wrote:

> >      I/O space accesses: off
> >      Memory space accesses: off
 
> This should NOT happen. Of course we can't access i/o
space when it's 
> not enabled. I wonder why it's disabled.

All I can attest to is that the card (and the sound chip)
functioned ok when
<ahem> another OS (penguin-related) was on the
machine. <g>

> Are you familiar with pcitweak?

No, but I'll give her a whirl, as they say!


Thanks,

-- 
Bob Bernstein

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

>>>      I/O space accesses: off
>>>      Memory space accesses: off
>
>> This should NOT happen. Of course we can't access
i/o space when it's
>> not enabled. I wonder why it's disabled.
>
> All I can attest to is that the card (and the sound
chip) functioned 
> ok when
> <ahem> another OS (penguin-related) was on the
machine. <g>

They probably just enable i/o access in the driver ( and so
should we, 
probably, although that's really the firmware's job )

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRIDHCspnzkX8Yg2nAQIVuAf/VTbhfPjBE6dZB5n4TA7GK0TUg29B
BkNK
iVECDhHPM0Z9A5mfv6Il5SVDtfjovTfir/eoYZRFFn9E8L9pAfRZ+VkJ7EXM
pjEJ
YEMq00xybVDoAzEkuby0nBF+sQ6syY/stYoZp0MSV/mqZlvfT690ht1h60Jz
Om2Y
lli1gb0bpdN5EkLDB45ayGtErGVMLa+l5xB5Iy6gueNQYygrQ+Ap2nbjJUTK
mawa
4guabp6tSDsNuNMxcKU+RxL3XzpIZDA8oQCFJ1kaI5vaJ4qgQoE8e/9uaut7
YH9I
BCI6TXyqyeGjPBJ/rGM1US2Id1sVaeAjmqYJYoUapvr7KX3j/4pF4Q==
=VbUm
-----END PGP SIGNATURE-----

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  
NetBSD.

Cheers,
Jared 

On 03Jun2006 08:21AM (-0300), Jared D. McNeill wrote:

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

Yup. Making that value "No" did the trick, for
the rtk NIC, and the sound
chip.

Thanks much,

-- 
Bob Bernstein