06-13-2017 08:05 PM
It appears that the only way to report a BIOS bug to Lenovo is to post in the Forum (at least that is what hardware support told me), so here goes!
BIOS Issue related to Wake On LAN and Thunderbolt 3:
BIOS Issue 2:
Solved! Go to Solution.
06-14-2017 07:04 AM
Issue #2 is easy so I'll start there. Security-related settings are never changed by loading defaults. It's working as designed.
For your observation about "FOR EVALUATION ONLY. NOT FOR RESALE.", I will pass this along to BIOS team. Clearly an oversight!
For issue #1, it will take me some time to research this. I'll get back to you soon.
06-14-2017 11:30 AM - edited 06-14-2017 11:33 AM
I have also seen boot stalling at sproadic spinning dots with only repeated powercycling gets me running. I just saw the post above, turned WOL onto 'AC Only" and saw 1st clean boot right away (while connected to AC, no dock, no external screen).
Before googling and hitting the post above I had spent days occasionally switching off extras, security and boot related settings at bios, including switching WOL from enabled to disabled. I was suspecting my multimonitor/dock setup myself -- my typical experience was to suspend-sleep or shutdown in dock with power, wired lan and multiple monitors, restarting with no dock, with or without AC power, different network, sometimes with different external monitor, only to see dots & Lenovo banner but could I not see repeatable pattern.
My system is 20HFS07J00, bios 1.10, smbios 3.0, emb controller 1.13. W10 creators, with all MSFT patches; from Lenovo Companion updates following are out of date/have not been installed - Intel Rapid Storage driver; Lenovo SSD Fw Upd Tool; Intel Mgmt Engine 11.6 Fw, Lenovo APS; Realtek Audio. (Latter fails to install). Factory SanDisk 128G in mine. Happy to test, provide more info if anyone reaches out 1:1.
06-14-2017 08:50 PM
I have to say I am impressed with the fast response. I was a bit disappointed to hear from phone support that the only submission channel for reporting BIOS and/or driver issues was via the forums - I figured I'd post here and be lucky if anyone actually noticed. Given the speed of the response (and assuming you're successful in getting my report passed along to the BIOS team), I'm pretty happy! It's always frustrating to go to the work of pinning down a bug's behavior as precisely as possible and then documenting it, only to discover I can't get it to the right team, so I'm glad that wasn't the case this time.
Obviously I have a workaround for the indefinite future. I only disable WOL because I think of it as a hardening step, but it's not like it's very much of an attack vector since I always adjust the Network Boot setting to point to the hard drive.
I didn't realize the Security settings are always left alone by loading defaults, but I guess that makes sense. As long as it's intentional, that's fine with me.
06-15-2017 05:03 AM
We were able to reproduce the issues related to Wake On LAN = Disabled:
1. hang (spinning dots) while boot on battery
2. thunderbolt device shown in Device Manager even when thunderbolt port is disabled
BIOS engineer is currently investigating these 2 issues. Thank you for your problem report!
10-24-2017 04:49 PM
This issue should be fixed in the latest T470s BIOS package 1.19
I did not test it myself to confirm the fix, but this is the information I got from BIOS team.
10-25-2017 01:00 AM
10-25-2017 06:08 AM
Thanks for the quick reply! In the BIOS readme, was the following item the fix related to the bug we were seeing? - (Fix) Fixed an issue where ethernet is unstable when network boot was tried before Windows boot. The other items seem to be unrelated. In that case, it seems that moving the network down in the boot order should be an alternative to the WOL workaround described in the OP. That is worth a try (at least for people that want to avoid experimenting with irreversible BIOS upgrades).
That is a different issue. The issue of this thread is not mentioned in the readme (I don't know why). However I just tested the latest BIOS on my own T470s here, with Wake On LAN disabled in BIOS setup, and I confirmed the issue is fixed.