Public Beta Test: 11th Gen BIOS v3.03 + Driver Bundle 2021_08_31

Thanks cowpod! I assume setting it to 1 (or whatever the initial value was) will reinstate S0?

I prefer having the control of S3 myself. Sometimes I know I’ll be using it in a couple of hours, and I like knowing that it’ll come on near instant when lifting the lid.

Now one thing that I do like about S0 is that, from what i’ve read, hibernating is better on the battery. Not just in the obvious way, but because I read that it is not good for a battery to constantly be in a state of discharge. By hibernating the battery is at rest.

But it is also a perception thing. When I sleep a computer, I don’t expect it to process anything until I’m back at the keyboard and asking it to do so. The idea that my laptop is going to listen to network activity and keep outlook up to date is not something I want or ever asked for. My smartphone is much better at that.

Anyway, thanks!

1 Like

Reporting back to say that I was able to update the bios and used the new driver back. So far no issues. I did however enabled S3.

One thing I’m noticing is that resuming from S3 suspend takes about 6 seconds. During which the screen is blank, and the keys and mouse are not responsive. The power button is lit though.

I noticed this exact same behavior when resuming from suspend on Ubuntu.

So I’m wondering is this just how long it takes because of the amount of RAM in the system?

Thermal performance seems improved by about 4C in my use case. I used to hover around 42C, and now I’m sitting around 38-39C with the same amount of programs open and activity.

1 Like

I’m thinking that this isn’t true S3 sleep, and that it instead is hibernating. Can’t prove this though, so not sure.

1 Like

I had a slight scare, but it worked out in the end:

  • Ran bios update from windows 10, while plugged into eGPU. Realized that would’ve went more smoothly after it started, if I disconnected the eGPU.
  • Waited about 10 minutes after reboot, still black screen. Forced shutdown and reboot, still black screen (power LED was green).
  • Disconnected battery & CMOS battery, reconnected, and rebooted
  • Success

Whew, glad you were able to recover. Been there, and I would definitely have been sweating a bit!

1 Like

@pixelforest any updates on the Linux front?


@Kieran_Levin and I have been working on it, but we got a bit more swamped/behind than we anticipated this week. We will make a quick post here as soon as it’s available, we appreciate your patience as I know quite a few have been waiting for this.


Tested on a 1165G7 without issue

1 Like

@iaredavid interesting finding, I guess we may have attempted to load the eGPU option rom and display video via the eGPU during the firmware update. We will suggest to unplug any eGPU devices during the update.


Intel Smart Sound is causing issues for me when I use external USB speakers (Yamaha THR II, actually a guitar amp).

When the device is plugged in, trying to start any app that uses sound either has a massive delay or just crashes / gives “not responding”. This includes the Sounds control panel, Sounds settings window, Spotify, or just clicking the volume icon in the taskbar.

I was able to resolve this by manually uninstalling Smart Sound via Device Manager.

1 Like

The Beta Driver bundle only nets 39 minutes of sleep before hibernating due to the following ‘problem’ device:

Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller (\_SB.PC00.HDAS)


Re-running the driver update bundle seems to have solved this, and now sleep power draw is much lower.

Hey everyone, we wanted to give you a quick update.

We have been reviewing and working to debug the issues noted in this thread before we push any further updates (thanks for all the reports again!). With that said, the Linux beta is taking a bit longer, but as soon as we have more information we will post again here!


If you are taking suggestions for future BIOS revisions, I’d love to be able to specify the USB-A as a boot priority whenever something is plugged into it by default.


If you are talking about USB-A vs something in USB-C modules, I think the operating system is clueless about the difference as both types are passed through USB-C.

1 Like

I was thinking of being able to specify a boot priority of modules in the BIOS pre-OS. Maybe being able to give preference to a specific idVendor/idProduct.

While installing multiple OSes (from the 250gb modules as opposed to the nvme), it would sometimes make the plugged in Ventoy USB-A no longer the default boot device requiring you to change the boot order. Ideally, the 250gb modules would be treated like drives and the open USB-A/C would be treated like temporary drives. While it’s just an inconvenience, it would be nice to specify that “temporary” drives take precedence over “permanent” drives.


Do you have any details on the hold ups that remain or a rough ETA? I appreciate you guys keeping up communication about this. It’s always a nice surprise when linux ins’t completely ignored


@malachid try going into the bios menu and go to Boot-> New Boot Device Priority.
I think if you change it to Last, it will boot from the last attached device as the first priority.


I’ll try that. I wasn’t clear on what First/Last were supposed to indicate. During the testing I had tried both options, but the list didn’t seem to change. Probably should have tried rebooting after changing that rather than looking at the boot order list.

1 Like

I have been swapping NVMe’s between a win10 install (fully up to date) and a Linux install (Slackware-current). I updated the bios with the windows NVMe and it went smoothly, took about a minute after EFI flash (32GB RAM, non-vPro i7). I still have occasional bugs, but they are not performance related. One was, if i plugin different USB-C power adapters, I’ve once had the screen blank and the fingerprint reader light go out and things went non-responsive. then after un-plugging then re-plugging the USB-C power adapter (not the one, but an 80 watt I usually use on another laptop) the screen and square light came back on. I was then able to wake the screen and login. The system hadn’t gone to sleep it didn’t look like. I once had a similar thing happen (pre UEFI update) when I plugged in a USBC 3.1 NVMe drive caddy. At the time the laptop was on battery power so I assumed it drew too much power. I tried again after connecting the charger and it was fine. Each only happened once. If i can find a way to reproduce, i’ll post steps. I’m very happy with the laptop so far. Keyboard, screen resolution and auto-disabling the touchpad while typing in linux are all excellent.

1 Like