Re: tlp0: unable to map device registers

["Jonathan A. Kollasch" <jakllsch%kollasch.net@localhost>]

On Wed, Sep 10, 2008 at 09:35:59PM -0400, Emery Clark wrote:
> On Tue, Sep 9, 2008 at 2:51 PM, David Young <dyoung%pobox.com@localhost> 
> wrote:
> > On Tue, Sep 09, 2008 at 02:31:49PM -0400, Emery Clark wrote:
> >> Hi all!
> >>
> >> I am having problems with a NetBSD install on an old system of mine.
> >>
> >> First, I cannot get the operating system to configure my Ethernet
> >> card. The kernel recognizes it as a "Davicom DM9102A Ethernet" and
> >> attempts to assign the tlp (Tulip) drivers to the hardware device.
> >> Although the Tulip drivers seem to be very well known (and compiled
> >> into the GENERIC kernel?) I cannot configure the device.
> >>
> >> Dmesg gives me:
> >> "tlp0 at pci0 dev 5 function 0: DAvicom DM9102A Ethernet, pass 3.1
> >> tlp0: unable to map device registers"
> >
> > Maybe the BIOS has not correctly initialized either the BARs, the memory-
> > or the I/O-enable.
> >
> > What does 'pcictl pci0 dump -d 5' say?  Also, how about 'pcictl pci0
> > dump -d 0' ?
> >
> 
> Sorry for the delayed response.
> 
> $ pcictl pci0 dump -d 5
> PCI configuration registers:
>   Common header:
>     0x00: 0x91021282 0x02100000 0x02000031 0x00004200
> 
>     Vendor Name: Davicom Semiconductor (0x1282)
>     Device Name: DM9102 10/100 Ethernet (0x9102)
>     Command register: 0x0000
>       I/O space accesses: off
>       Memory space accesses: off

Both of these being off will cause the 'unable to map'.

>       Bus mastering: off

This should probably be on, so set the BIOS accordingly


If the BIOS has a PnP OS option, try setting it to non-PnP.
Hopefully that will allow it to work.

        Jonathan Kollasch