Re: 2.6.23-mm1 tg3 wake-on-lan oddity...
On Tue, 27 Nov 2007 13:34:57 PST, Michael Chan said: > Ideally, the BIOS should modify the NVRAM's setting when it is changed. > We will talk to Dell to get their opinion on this as this is very > confusing to the user. That would certainly explain what I'm seeing, and I can certainly wait if the answer is indeed "Buggy BIOS, fixed in D820 A08 or A09 or whenever". (If Dell cares, I'm at BIOS A07 already). In the meantime, I just stuck an 'ethtool -s eth0 wol d' in /etc/rc.local until a proper fix shows up. pgp9JdH9SLzg5.pgp Description: PGP signature
Re: 2.6.23-mm1 tg3 wake-on-lan oddity...
On Tue, 2007-11-27 at 01:35 -0800, [EMAIL PROTECTED] wrote: > > Issue: > > I (for unrelated reasons) run powertop, and it suggests I conserve power > by doing 'ethtool -s eth0 wol d'. I look at it, and think that it's daft, > because (a) the Dell factory default is WOL disabled and (b) if it wasn't > the default, I'd have *set* it to disabled, and (c) I even went back and > rebooted and checked the BIOS setting - disabled. Nonetheless: > > # ethtool eth0 | grep Wake > Supports Wake-on: g > Wake-on: g > > Is this expected behavior? What's happening is that there are 2 WoL settings: one in the BIOS and one in the NIC's NVRAM. For WoL to work, I think both settings have to be enabled. Apparently in this case, when you turn off WoL in the BIOS, the NVRAM's WoL setting is unchanged, and will be seen by tg3 as enabled. Ideally, the BIOS should modify the NVRAM's setting when it is changed. We will talk to Dell to get their opinion on this as this is very confusing to the user. Thanks. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-mm1 tg3 wake-on-lan oddity...
On Tue, 27 Nov 2007 08:04:28 PST, Michael Chan said: > [EMAIL PROTECTED] wrote: > > > (a) the Dell factory default is WOL disabled and (b) > > if it wasn't > > the default, I'd have *set* it to disabled, and (c) I even > > went back and > > rebooted and checked the BIOS setting - disabled. Nonetheless: > > > > # ethtool eth0 | grep Wake > > Supports Wake-on: g > > Wake-on: g > > > > Is this expected behavior? > > > > The new tg3 is supposed to follow the WoL setting in the > NVRAM, so this is not expected. We'll have to look into > this. Any info that would help? printk's to stick in tg3.c? Dumping the relevant bytes of NVRAM? etc? pgphBCOmCjmo6.pgp Description: PGP signature
Re: 2.6.23-mm1 tg3 wake-on-lan oddity...
[EMAIL PROTECTED] wrote: > (a) the Dell factory default is WOL disabled and (b) > if it wasn't > the default, I'd have *set* it to disabled, and (c) I even > went back and > rebooted and checked the BIOS setting - disabled. Nonetheless: > > # ethtool eth0 | grep Wake > Supports Wake-on: g > Wake-on: g > > Is this expected behavior? > The new tg3 is supposed to follow the WoL setting in the NVRAM, so this is not expected. We'll have to look into this. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-mm1 tg3 wake-on-lan oddity...
[EMAIL PROTECTED] wrote: (a) the Dell factory default is WOL disabled and (b) if it wasn't the default, I'd have *set* it to disabled, and (c) I even went back and rebooted and checked the BIOS setting - disabled. Nonetheless: # ethtool eth0 | grep Wake Supports Wake-on: g Wake-on: g Is this expected behavior? The new tg3 is supposed to follow the WoL setting in the NVRAM, so this is not expected. We'll have to look into this. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-mm1 tg3 wake-on-lan oddity...
On Tue, 27 Nov 2007 08:04:28 PST, Michael Chan said: [EMAIL PROTECTED] wrote: (a) the Dell factory default is WOL disabled and (b) if it wasn't the default, I'd have *set* it to disabled, and (c) I even went back and rebooted and checked the BIOS setting - disabled. Nonetheless: # ethtool eth0 | grep Wake Supports Wake-on: g Wake-on: g Is this expected behavior? The new tg3 is supposed to follow the WoL setting in the NVRAM, so this is not expected. We'll have to look into this. Any info that would help? printk's to stick in tg3.c? Dumping the relevant bytes of NVRAM? etc? pgphBCOmCjmo6.pgp Description: PGP signature
Re: 2.6.23-mm1 tg3 wake-on-lan oddity...
On Tue, 2007-11-27 at 01:35 -0800, [EMAIL PROTECTED] wrote: Issue: I (for unrelated reasons) run powertop, and it suggests I conserve power by doing 'ethtool -s eth0 wol d'. I look at it, and think that it's daft, because (a) the Dell factory default is WOL disabled and (b) if it wasn't the default, I'd have *set* it to disabled, and (c) I even went back and rebooted and checked the BIOS setting - disabled. Nonetheless: # ethtool eth0 | grep Wake Supports Wake-on: g Wake-on: g Is this expected behavior? What's happening is that there are 2 WoL settings: one in the BIOS and one in the NIC's NVRAM. For WoL to work, I think both settings have to be enabled. Apparently in this case, when you turn off WoL in the BIOS, the NVRAM's WoL setting is unchanged, and will be seen by tg3 as enabled. Ideally, the BIOS should modify the NVRAM's setting when it is changed. We will talk to Dell to get their opinion on this as this is very confusing to the user. Thanks. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.23-mm1 tg3 wake-on-lan oddity...
On Tue, 27 Nov 2007 13:34:57 PST, Michael Chan said: Ideally, the BIOS should modify the NVRAM's setting when it is changed. We will talk to Dell to get their opinion on this as this is very confusing to the user. That would certainly explain what I'm seeing, and I can certainly wait if the answer is indeed Buggy BIOS, fixed in D820 A08 or A09 or whenever. (If Dell cares, I'm at BIOS A07 already). In the meantime, I just stuck an 'ethtool -s eth0 wol d' in /etc/rc.local until a proper fix shows up. pgp9JdH9SLzg5.pgp Description: PGP signature
