Subject: Re: fxp - unable to map device registers
To: Adam Glass <adam@clarity.net>
From: Manuel Bouyer <bouyer@antioche.eu.org>
List: port-i386
Date: 04/15/2003 22:12:20
On Tue, Apr 15, 2003 at 01:36:34AM -0700, Adam Glass wrote:
> I have an Intel 845 chipset-based system with two fxp interfaces. I
> just compiled two kernels from the same ~4/12/03 1.6 sources: GENERIC
> and a customized/stripped-down kernel ("CUSTOM"). CUSTOM is only able
> to deal with the first of the fxp interfaces. Here's what the
> relevant dmesg output looks like when I boot under CUSTOM:
>
> fxp0 at pci2 dev 6 function 0: i82559 Ethernet, rev 8
> fxp0: interrupting at irq 12
> fxp0: Ethernet address 00:30:48:51:e4:68
> inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
> fxp1 at pci2 dev 7 function 0: unable to map device registers
>
> Note the last line. Here's what GENERIC sees (this is correct):
>
> fxp0 at pci2 dev 6 function 0: i82559 Ethernet, rev 8
> fxp0: interrupting at irq 12
> fxp0: Ethernet address 00:30:48:51:e4:68
> inphy0 at fxp0 phy 1: i82555 10/100 media interface, rev. 4
> fxp1 at pci2 dev 7 function 0: i82559 Ethernet, rev 8
> fxp1: interrupting at irq 10
> fxp1: Ethernet address 00:30:48:51:e4:69
> inphy1 at fxp1 phy 1: i82555 10/100 media interface, rev. 4
Can you post the diffs between GENERIC and CUSTOM ?
--
Manuel Bouyer <bouyer@antioche.eu.org>
NetBSD: 24 ans d'experience feront toujours la difference
--