Support for the S0ix sleep state

[e6lk7dqzm83p]

Current status

Initial support of S0ix is available for testing; see #6411 (comment).

---

Editor's note: The original issue description below is somewhat out-of-date. This issue is now narrowly focused on support for the S0ix sleep state (aka "Modern Standby," "Low Power S0 Idle," "InstantGo," "Connected Standby," etc.) found in newer CPUs (especially Tiger Lake and later).

---

The problem you're addressing (if any)

It appears Qubes does not support Intel's latest version of processors.

Describe the solution you'd like

Support for Intel's latest version of their processors (i.e., tiger lake)

Where is the value to a user, and who might that user be?

People who want to benefit from the significant performance upgrades of Tiger Lake

Describe alternatives you've considered

N/A

Additional context

N/A

Relevant documentation you've consulted

N/A (I've checked GitHub for any open issues on this but either I've missed it or my SearchFu is weak)

Related, non-duplicate issues

N/A

[e6lk7dqzm83p]

@marmarek I believe this has to do with the current kernel Qubes is using?

[DemiMarie]

That would not surprise me. R4.1 has several advantages here, including being able to include multiple kernels in the install ISO.

[e6lk7dqzm83p]

@DemiMarie, does that mean R4.1 will support Tiger Lake? Sorry if I'm being obtuse.

[DemiMarie]

@e6lk7dqzm83p that’s a question that @marmarek would be better positioned to answer, sorry.

[e6lk7dqzm83p]

No problem; I appreciate the insight!

[marmarek]

I believe this is close related to #5374, which this time is more about Xen than Linux. @e6lk7dqzm83p do you see some specific error message?

[e6lk7dqzm83p]

Apologies, I do not. I was talking to System76 about about their Qubes support with the newer chipsets and was informed that Tiger Lake was not currently supported due to a kernel issue (I'm trying to ensure Qubes support before I purchase my new computer). I was trying to see what the status of that issue was and couldn't find any documentation here so I opened the request.

Sorry if that was in error/off protocol.