Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 Feb 2007 14:20:48 -0700 (MST)
From:      Warner Losh <imp@bsdimp.com>
To:        freebsd-drivers@freebsd.org, anatoli.marinov@gmail.com, olli@lurza.secnetix.de
Subject:   Re: problem with rl network card
Message-ID:  <20070214.142048.78796550.imp@bsdimp.com>
In-Reply-To: <200702142114.l1ELEsjf073038@lurza.secnetix.de>
References:  <f147fd390702141245g3b42cb7fhcee856e76255417b@mail.gmail.com> <200702142114.l1ELEsjf073038@lurza.secnetix.de>

next in thread | previous in thread | raw e-mail | index | archive | help
From: Oliver Fromme <olli@lurza.secnetix.de>
Subject: Re: problem with rl network card
Date: Wed, 14 Feb 2007 22:14:54 +0100 (CET)

> Anatoli Marinov wrote:
>  > Unfortunately the patch with simple new code for vendor in .h file didnt
>  > work. See the attached file. It is verbose dmesg after booting.
> 
> Thanks.  These are the important lines:
> 
>  > pci2: child re0 requested type 4 for rid 0x10, but the BAR says it is an memio
>  > re0: couldn't map ports/memory
>  > pci2: child rl0 requested type 4 for rid 0x10, but the BAR says it is an memio
>  > rl0: couldn't map ports/memory
> 
> Uhm, strange, why do both re and rl try to attach?  It's
> clearly not an re device.  Did you make any other changes
> to the source code, beside the one I told you?  Something
> seems to be confused there in the drivers.

re and rl have attach code that allocates resources and talks to the
card to see what revision the card is.  That's why he's seeing thsoe lines.

> However, it seems that the driver cannot alloacte the PCI
> resources correctly.

This likely means that this card isn't a realtek interface.

What would be nice is to know what the number of the chip on the NIC
card is.  And its maker.  That would help us a lot to know which
drivers to recommend.

Warner



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070214.142048.78796550.imp>