Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 22 Sep 2008 10:57:19 +0900
From:      PYUN Yong-Hyeon <pyunyh@gmail.com>
To:        Bob Willcox <bob@immure.com>
Cc:        Jeremy Chadwick <koitsu@FreeBSD.org>, freebsd-stable@FreeBSD.org
Subject:   Re: RELENG_7 hangs on boot w/Gigabyte MA78GM-S2H MB
Message-ID:  <20080922015718.GB26294@cdnetworks.co.kr>
In-Reply-To: <20080920144510.GB15275@rancor.immure.com>
References:  <20080920042418.GB1322@rancor.immure.com> <20080920123914.GA72833@icarus.home.lan> <20080920132429.GA15275@rancor.immure.com> <20080920140456.GA74663@icarus.home.lan> <20080920144510.GB15275@rancor.immure.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 20, 2008 at 09:45:10AM -0500, Bob Willcox wrote:
 > On Sat, Sep 20, 2008 at 07:04:56AM -0700, Jeremy Chadwick wrote:
 > > On Sat, Sep 20, 2008 at 08:24:29AM -0500, Bob Willcox wrote:

[...]

 > > > none3@pci0:2:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x02 hdr=0x00
 > > >     vendor     = 'Realtek Semiconductor'
 > > >     device     = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC'
 > > >     class      = network
 > > >     subclass   = ethernet
 > > 
 > > Regarding the Realtek issue: I've CC'd PYUN Yong-Hyeon (surname in
 > > caps), who maintains the re(4) driver for FreeBSD.  He might have a
 > > patch available for you to try, or help determine how to get this NIC
 > > working on FreeBSD.  He'll probably need more than just pciconf -lv
 > > output, but should be able to work with you.
 > 
 > Ok, that'd be great. I must say that I'm close to simply returning this
 > MB and going with something not quite so new that is more likely to
 > work. I was hoping to get this system up and running this weekend. :(
 > 

There is one unresolved issue in re(4), some newer controllers does
not respond to PHY access so re(4) fails to attach driver. If you
can see a message like 'PHY write failed' in boot it indicates
you're suffering from the issue. I have a local patch for this but
it needs more testing as I don't have that hardware that exhibits
the issue. Did you see the message?

If you can't see 'PHY write failed' message during boot you might
have a newer controller. Please post dmesg output for the case
to add your device id to re(4).

-- 
Regards,
Pyun YongHyeon



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