FBSD 7.0-p3 NIC driver problem (Realtek)

[Fernando Apesteguía]

On 2/23/09, Pyun YongHyeon <pyunyh at gmail.com> wrote:
> On Sun, Feb 22, 2009 at 06:15:55PM +0100, Fernando Apestegu?a wrote:
> > On Sat, Feb 21, 2009 at 2:55 AM, Pyun YongHyeon <pyunyh at gmail.com> wrote:
> > > On Fri, Feb 20, 2009 at 05:25:26PM +0100, Fernando Apestegu?a wrote:
> > >> Hi all,
> > >>
> > >> I copy here the mail I sent to freebsd-questions cause I didn't get any answers:
> > >>
> > >>
> > >> Yesterday I updated to 7.1-p3 on AMD64 arch.
> > >>
> > >> Since then, the NIC is not detected anymore. ifconfig doesn't show it
> > >> and I can't connect to the Internet.
> > >>
> > >> There were well-known issues with this NIC model before,
> > >> (http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2008-11/msg00299.html)
> > >>  but the weird thing is that it seemed to be fine with
> > >> 7.1-RELEASE and newer till this -p3.
> > >>
> > >> It doesn't recognize the card in 4/5 boot sequences (really annoying).
> > >>
> > >> Anybody with this problem?
> > >
> > > I'm not sure you're suffering from MAC power saving issue of
> > > RealTek PCIe controller. Sometimes re(4) used to fail to wakeup the
> > > controller which in turn resulted in 'no driver' for the
> > > controller. If this is the case you can see "MII without any phy!"
> > > message in dmesg output.
> >
> > You are right, I see that message.
> >
> > > r188358(cvs if_re.c 1.95.2.40) should fix the issue so please try
> > > latest 7-stable or copy if_re.c, if_rlreg.h and if_rl.c from HEAD/
> > > 7-stable to your 7.1-RELEASE box and rebuild kernel.
> > > If you still see the same issue please let me know.
> >
> > I copied the files and restarted my computer 5 times and the NIC was
> > present in all of them.
>
> Glad to hear that.
>
> > I will watch this issue and I will let you know if I notice more problems.
> >
> > Thanks so much for your help.
> >
>
> No problem.
>
> > >
> > > Btw, stable@ is more appropriate list for this type of issues.
> >
> > Even if I'm not using -STABLE?
> >
>
> Yes, you're not using CURRENT.

OK, I'll keep that in mind.

>