On Fri, 24 Mar 2006, walt wrote:
> Michael Chan wrote:
> > Walt wrote:
> >
> >> Nope, it was the second one: Skip phy power down...
>
> > It doesn't make sense. This code should have no effect on your
> > 5702. With or without this patch, the 5702 will be powered down
> > the same with tg3_writephy(tp, MII_BMCR, BMCR_PDOWN) if WOL
> > is not enabled when you ifdown.
> >
> > Also, for this code to have any effect, you must do ifdown or
> > suspend. So presumably the driver loaded fine at least once and
> > you get the failure during subsequent modprode...
>
> I confess I'm a bit confused by your question. I have no idea
> why an ifdown would be executed during boot, but the startup
> scripts are so complicated that I can't understand what they do.
>
> The network script does print a message that the eth0 interface
> doesn't exist, so I assume that the script tried to use ifconfig
> to do something and failed (wouldn't that most likely be an ifup
> rather than ifdown, during bootup?).
The eth0 interface not existing does sound somewhat like the tg3
problem I had. Did you check if you had PCI_MMCONFIG enabled in
your config?
-Bill
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
