Have you taken a look at /etc/conf.d/net.example around line 700?
To quote:
##############################################################################
# ADVANCED CONFIGURATION
#
# Four functions can be defined which will be called surrounding the
# start/stop operations. The functions are called with the interface
# name first so that one function can control multiple adapters. An extra
two
# functions can be defined when an interface fails to start or stop.
#
# The return values for the preup and predown functions should be 0
# (success) to indicate that configuration or deconfiguration of the
so just write yourself a preup function that sets the correct ethtool
setting on your adapter before brining it up. This is very likely the
correct way of doing it in Gentoo.
preup() {
if ethtool -s ${IFACE} duplex full; then
return 0
fi
ewarn "Couldn't set ${IFACE} to full duplex"
return 1
}
On 9/7/07, A. Khattri <[EMAIL PROTECTED]> wrote:
>
> On Fri, 7 Sep 2007, Jared Klett wrote:
>
> > In the past I've used ethtool with great results. For example:
> >
> > ethtool -s duplex full eth0
>
> I was hoping there would be a standard way to do this at boot time
> without hackign together a "local" script?
>
>
> >
> > On 9/7/07, A. Khattri <[EMAIL PROTECTED]> wrote:
> >>
> >> I Googled for this but found nothing useful. After a power outage in
> our
> >> data center one of my Gentoo servers failed to startup networking
> >> correctly. It looks like the NIC failed to autonegotiate a full-duplex
> >> connection to the switch and subsequently eth0 failed to come up
> properly.
> >>
> >> What is the preferred way to tell Gentoo to force full duplex on all
> NICs?
> >>
> >>
> >> --
> >> A
> >> --
> >> [EMAIL PROTECTED] mailing list
> >>
> >>
> >
>
> --
> A
> --
> [EMAIL PROTECTED] mailing list
>
>
