problem with rl network card

[Anatoli Marinov]

Guys,
What should I do with my RTL 8139D NIC.
Is there someone who knows how I can use this card with freebsd?
Is it possible?

Toli

2007/2/16, Anatoli Marinov <anatoli.marinov at gmail.com>:
>
> NIC pictures - RTL8139D
> http://snimka.bg/album.php?album_id=105612
>
> Is there a driver?  :)
>
> 2007/2/16, M. Warner Losh < imp at bsdimp.com>:
> >
> > In message: <f147fd390702152233n38df2790kc6c169bc61861557 at mail.gmail.com
> > >
> >             "Anatoli Marinov" <anatoli.marinov at gmail.com> writes:
> > : OK.  I will.
> >
> > I could download them, but I stopped the download of the first one
> > after 20 minutes and it had only finished 1/3 of the picture... just
> > enough to see the RTL8139D on the badge...
> >
> > Warner
> >
> > : Thanks
> > :
> > : 2007/2/15, Warner Losh <imp at bsdimp.com>:
> > : >
> > : > > I have photos.
> > : > > This is the link http://free.bsd-bg.net/NIC/
> > : > > Definitly the chip is RTL8139D.
> > : > >
> > : > > Is there functional driver for it or not?
> > : >
> > : > I think that it might be wise for me to snag these pictures and
> > mirror
> > : > them somewhere.  The download time is very very slow.  I chose the
> > : > smallest image and it is taking a very long time.
> > : >
> > : > Warner
> > : >
> > : >
> > : > > Toli
> > : > >
> > : > > 2007/2/15, Anatoli Marinov < anatoli.marinov at gmail.com>:
> > : > > >
> > : > > > I am going to prepare high resolution photos and will post links
> > there
> > : > > >
> > : > > > 2007/2/14, Warner Losh < imp at bsdimp.com>:
> > : > > > >
> > : > > > > From: Oliver Fromme <olli at 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
> > : > > > >
> > : > > >
> > : > > >
> > : >
> >
>
>