Carbon X1 and new 1.17 BIOS

[AdamKski]

I made the mistake of being an early adopter of this BIOS upgrade. But in my defense, the update utility said it was a 'critical' update!

As a result my Carbon X1 will no longer stay hibernated if I have a USB device plugged into the USB port on the right side of my laptop. The red light flashes, the laptop goes into hibernation and about 2 seconds later the red light comes back on. I don't have this issue if I plug my mouse transceiver into the USB port on the left side.

I've already tried disabling the 'always on' USB option in the BIOS settings without success. I've also tried disabling the boot from USB device option. I'd like to keep the mouse transceiver in the port on the right and keep the left port free for my external drive. Lenovo says there is no way to revert back to the previous BIOS after this upgrade. When I spoke with tech support they asked me to send my Carbon in for a new motherboard, but that was before I discovered the ability to move the transceiver to the other port. I'm not sure a newer version of the motherboard will fix this, but I'd rather not be without my laptop for 6 to 8 business days.

Anyone else run into this and have a work around?

[EOMtp]

Welcome to the forum!
You can revert to an older BIOS version as long as the corresponding ECP firmware level is the same. Look at the X1 BIOS versions table at the bottom of the following page:
http://support.lenovo.com/us/en/downloads/ds039782

Notice that there are two versions of BIOS 1.16 -- one for ECP 1.15 and the other for ECP 1.14. You will be able to revert to the package labeled "1.16-1.15".

There is a flag one can set on the program which flashes the BIOS to force it to accept an older BIOS version than what is on the machine, but I don't recall it .. it is something like "wflash2.exe /ign" <-- (ignore BIOS version check) ... wait until someone on the forum pitches in and provides the correct command and syntax.

Good luck!

[AdamKski]

Welcome to the forum!
You can revert to an older BIOS version as long as the corresponding ECP firmware level is the same. Look at the X1 BIOS versions table at the bottom of the following page:
http://support.lenovo.com/us/en/downloads/ds039782

Notice that there are two versions of BIOS 1.16 -- one for ECP 1.15 and the other for ECP 1.14. You will be able to revert to the package labeled "1.16-1.15".

There is a flag one can set on the program which flashes the BIOS to force it to accept an older BIOS version than what is on the machine, but I don't recall it .. it is something like "wflash2.exe /ign" <-- (ignore BIOS version check) ... wait until someone on the forum pitches in and provides the correct command and syntax.

Good luck!

I can do this even though they state:
"Version 1.17
UEFI: 1.17 / ECP: 1.15

[Important] Fixed a security vulnerability.
(Note)
If the UEFI BIOS has been updated to version 1.17 or higher, it is no longer able to roll back to the version before 1.17 for security improvement"?

Support told me the same thing. I'd hate to brick my laptop.....

[EOMtp]

I can do this even though they state:
If the UEFI BIOS has been updated to version 1.17 or higher, it is no longer able to roll back to the version before 1.17 for security improvement"?

Well, given that specific note, perhaps 1.17 is a "special case". My response addressed the general case, unaware of the specific note you quoted regarding 1.17.

[AdamKski]

I'm going to go ahead and send the X1 Carbon in for the recommended motherboard replacement. I've been having issues hibernating with the power plugged into the laptop. 3 seconds after the shutdown the red light comes back on. If I unplug all USB devices and the power cord it hibernates and stays off.

[distancesprinter]

I am experiencing a similar issue with two 20A7 X1 Carbon laptops. If I have my Logitech Unifying Receiver plugged in, the computer will not hibernate. This began occurring after a 1.17 BIOS update.

Please let me know if the replacement motherboard fixes your issue. I doubt it--it sounds software-related.

[AdamKski]

I am experiencing a similar issue with two 20A7 X1 Carbon laptops. If I have my Logitech Unifying Receiver plugged in, the computer will not hibernate. This began occurring after a 1.17 BIOS update.

Please let me know if the replacement motherboard fixes your issue. I doubt it--it sounds software-related.

It's at the depot on a parts hold. Sounds like they are replacing not only the motherboard, but the display and a display cable?? The tech support manager was confident this would fix the issue as it is a "known problem" according to him. I will report back as soon as it returns.

BTW, I had the same issue with hibernation once even without my USB device plugged in?? I pulled the power cable and then it successfully shut down. I didn't test it enough times before sending it in to see if it was even related to the power cable or just a random event.

[distancesprinter]

I am experiencing a similar issue with two 20A7 X1 Carbon laptops. If I have my Logitech Unifying Receiver plugged in, the computer will not hibernate. This began occurring after a 1.17 BIOS update.

Please let me know if the replacement motherboard fixes your issue. I doubt it--it sounds software-related.

It's at the depot on a parts hold. Sounds like they are replacing not only the motherboard, but the display and a display cable?? The tech support manager was confident this would fix the issue as it is a "known problem" according to him. I will report back as soon as it returns.

BTW, I had the same issue with hibernation once even without my USB device plugged in?? I pulled the power cable and then it successfully shut down. I didn't test it enough times before sending it in to see if it was even related to the power cable or just a random event.

This is really hard for me to believe because my machine works fine once the USB fob is removed, and was working properly prior to 1.17... It is also duplicated on another 20A7 manufactured last month in October.

Keep me posted.

[AdamKski]

This is really hard for me to believe because my machine works fine once the USB fob is removed, and was working properly prior to 1.17... It is also duplicated on another 20A7 manufactured last month in October.

Keep me posted.

It's back. They replaced the motherboard and the display. The problem persists. But, I have a nice new display! The old one had a few white spots on it.

I called support to let them know this didn't solve the problem. They said to keep my eyes open for a BIOS upgrade to resolve the issue.

[distancesprinter]

This is really hard for me to believe because my machine works fine once the USB fob is removed, and was working properly prior to 1.17... It is also duplicated on another 20A7 manufactured last month in October.

Keep me posted.

It's back. They replaced the motherboard and the display. The problem persists. But, I have a nice new display! The old one had a few white spots on it.

I called support to let them know this didn't solve the problem. They said to keep my eyes open for a BIOS upgrade to resolve the issue.

BIOS 1.18 is posted, haven't tested yet, but will do tomorrow.

[AdamKski]

BIOS 1.18 is posted, haven't tested yet, but will do tomorrow.

I just tried it. Doesn't fix the issue.....

[distancesprinter]

BIOS 1.18 is posted, haven't tested yet, but will do tomorrow.

I just tried it. Doesn't fix the issue.....

I can confirm. Just tried it too. Does not fix the issue.

I did have a problem updating the BIOS with the computer in the docking station with dual monitors. The computer shut down normally to flash the BIOS, but the BIOS flashing screen did not appear on my dual monitor setup via the docking station. This seems to be another flaw. I had to disconnect the computer from power and use the reset pin hole on the bottom of the computer to the left side. The pin hole is actually smaller than a paperclip, so I had to use a piece of 5 mm lead from a mechanical pencil to hit the reset button. Once I hit the reset button, the computer turned off and I was able to power it back on normally. Once I did this, the old BIOS 1.17 was still present, so I repeated the BIOS update without being connected to the docking station.

[AdamKski]

The recently released 1.19 BIOS also does NOT fix this issue. Sigh.........

[AdamKski]

So I just went through all of the devices in 'Device Manager' and found that one of my Network Adapters had the 'Allow this device to wake the computer' turned on under it's 'Power Management' settings?? As I always do, I had disabled these when I first setup this computer. I guess somehow the BIOS upgrade had changed this??

I've been through about 5 hibernation cycles now and it stays asleep like it should!

[distancesprinter]

So I just went through all of the devices in 'Device Manager' and found that one of my Network Adapters had the 'Allow this device to wake the computer' turned on under it's 'Power Management' settings?? As I always do, I had disabled these when I first setup this computer. I guess somehow the BIOS upgrade had changed this??

I've been through about 5 hibernation cycles now and it stays asleep like it should!

The network card should have nothing to do with this issue. I need to keep "Allow this device to wake the computer" checked for Wake-On-LAN functionality. This machine should be able to support Wake-On-LAN and hibernation with a USB mouse receiver at the same time.

[AdamKski]

The network card should have nothing to do with this issue. I need to keep "Allow this device to wake the computer" checked for Wake-On-LAN functionality. This machine should be able to support Wake-On-LAN and hibernation with a USB mouse receiver at the same time.

Agreed. Fortunately for me I don't need Wake-On-LAN. When I called support yesterday they wanted me to send in my laptop again. I told them they had already replaced the MB and display last month. The response was "if you send it in again and the problem isn't fixed, you'll get a new X1 on your 3rd call". I tried to explain to him that I don't think it's an issue with the machine, but a BIOS issue they introduced in version 1.17 and that this NEEDS to be sent up the chain for resolution. He said that wouldn't happen until the 3rd repair attempt?!

[distancesprinter]

The network card should have nothing to do with this issue. I need to keep "Allow this device to wake the computer" checked for Wake-On-LAN functionality. This machine should be able to support Wake-On-LAN and hibernation with a USB mouse receiver at the same time.

Agreed. Fortunately for me I don't need Wake-On-LAN. When I called support yesterday they wanted me to send in my laptop again. I told them they had already replaced the MB and display last month. The response was "if you send it in again and the problem isn't fixed, you'll get a new X1 on your 3rd call". I tried to explain to him that I don't think it's an issue with the machine, but a BIOS issue they introduced in version 1.17 and that this NEEDS to be sent up the chain for resolution. He said that wouldn't happen until the 3rd repair attempt?!

Finally got escalated above the "hotline" group and spoke to someone that sounded competent after threatening to return all of our X1 Carbon machines. As always, will keep you posted. If anybody else has this issue, please report it so that it will get the attention it deserves from Lenovo Development/Engineering.

[distancesprinter]

Lenovo has confirmed the bug and finds that this issue is only present when USB receiver is plugged into the right USB port.

Is this consistent with the behavior of others having the problem?

Turning off Wake-on-LAN in Ethernet device driver is also confirmed as a temporary work around.

[AdamKski]

Lenovo has confirmed the bug and finds that this issue is only present when USB receiver is plugged into the right USB port.

Is this consistent with the behavior of others having the problem?

Turning off Wake-on-LAN in Ethernet device driver is also confirmed as a temporary work around.

That's pretty much what I've experienced. Although I had it wake up a few times even without anything plugged into the right USB with wake on LAN enabled. With wake on LAN disabled it has never woken up regardless of USB devices.

[AdamKski]

BIOS version 1.20 was released on 1/23/2015. So far, so good....

[distancesprinter]

BIOS version 1.20 was released on 1/23/2015. So far, so good....

Per Lenovo, this issue is resolved with 1.20. Tested and confirmed working.

You're welcome Carbon owners. After about 20 hours of haggling my way through multiple tiers of support, including a hell of a time with the front line support desk in Atlanta (most aggravating) and multiple premature issue closures without getting a call and no documented reason for closing the tickets in Lenovo's system, persistence and the threat of returning a bulk order of Carbon laptops has paid off and an actual bug was fixed. Believe it or not, this one wasn't user error; there are actually bugs out there! That is all.

[AdamKski]

BIOS version 1.20 was released on 1/23/2015. So far, so good....

You're welcome Carbon owners.

Thanks!!

[AdamKski]

When my Carbon went in the first time for a motherboard replacement to fix this issue, (which of course it didn't fix), they also changed the display. About twice a week the display would go berserk as if someone were touching the screen rapid fire in the upper left quarter of the screen. The only way to stop it was to reboot, or if I could get to the device manager, terminating the USB Root Hub would stop it. Then I would rescan and the devices would come back happy. In the mean time this BIOS fix came along and cured the initial problem. I still had to send in the Carbon back in, this time to the "Lenovo SWAT" group for a new display. I guess that's an engineering department rather than the typical depot. I got it back in 3 days, not the usual week to the depot. It's been solid for a couple of weeks now!