I'll see if I have the time. And if I can hahaha.

Is there a clear list of instructions in this thread? I'm lost in all the messages.

I can read the thread trying to compile what to do. But if someone could point me where to look, maybe that can save me an hour or two.

(In reply to Cameron Berkenpas from comment #315)
> That is a resounding yes! Unsurprisingly for AMD, PCI passthrough is 
> available.
> 
> Is there anyone with a Legion 7 16ACHg6 who's up to setting up pci 
> passthrough for their sound card and compiling JCS's Qemu all to run a 
> Windows 10 VM? Someone can either try to do that for themselves or wait 
> for me and hope there's sufficient availability.
> 
> On 6/25/2021 7:45 PM, <email address hidden> wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=208555
> >
> > --- Comment #314 from Pablitar (<email address hidden>) ---
> > Here it is:
> > [    0.293604] iommu: Default domain type: Translated
> > [    0.487357] pci 0000:00:00.2: AMD-Vi: IOMMU performance counters
> supported
> > [    0.487484] pci 0000:00:01.0: Adding to iommu group 0
> > [    0.487493] pci 0000:00:01.1: Adding to iommu group 1
> > [    0.487500] pci 0000:00:01.2: Adding to iommu group 2
> > [    0.487511] pci 0000:00:02.0: Adding to iommu group 3
> > [    0.487518] pci 0000:00:02.1: Adding to iommu group 4
> > [    0.487526] pci 0000:00:02.2: Adding to iommu group 5
> > [    0.487538] pci 0000:00:08.0: Adding to iommu group 6
> > [    0.487544] pci 0000:00:08.1: Adding to iommu group 6
> > [    0.487550] pci 0000:00:08.2: Adding to iommu group 6
> > [    0.487560] pci 0000:00:14.0: Adding to iommu group 7
> > [    0.487566] pci 0000:00:14.3: Adding to iommu group 7
> > [    0.487587] pci 0000:00:18.0: Adding to iommu group 8
> > [    0.487593] pci 0000:00:18.1: Adding to iommu group 8
> > [    0.487599] pci 0000:00:18.2: Adding to iommu group 8
> > [    0.487606] pci 0000:00:18.3: Adding to iommu group 8
> > [    0.487612] pci 0000:00:18.4: Adding to iommu group 8
> > [    0.487618] pci 0000:00:18.5: Adding to iommu group 8
> > [    0.487624] pci 0000:00:18.6: Adding to iommu group 8
> > [    0.487629] pci 0000:00:18.7: Adding to iommu group 8
> > [    0.487640] pci 0000:01:00.0: Adding to iommu group 9
> > [    0.487648] pci 0000:01:00.1: Adding to iommu group 9
> > [    0.487656] pci 0000:02:00.0: Adding to iommu group 10
> > [    0.487664] pci 0000:03:00.0: Adding to iommu group 11
> > [    0.487671] pci 0000:04:00.0: Adding to iommu group 12
> > [    0.487685] pci 0000:05:00.0: Adding to iommu group 6
> > [    0.487688] pci 0000:05:00.2: Adding to iommu group 6
> > [    0.487693] pci 0000:05:00.3: Adding to iommu group 6
> > [    0.487696] pci 0000:05:00.4: Adding to iommu group 6
> > [    0.487700] pci 0000:05:00.6: Adding to iommu group 6
> > [    0.487703] pci 0000:06:00.0: Adding to iommu group 6
> > [    0.487707] pci 0000:06:00.1: Adding to iommu group 6
> > [    0.489073] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
> > [    0.490935] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4
> > counters/bank).
> > [    0.535396] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <email address hidden>
> >
> > Seems it is supported?
> >
> > (In reply to Cameron Berkenpas from comment #312)
> >> Maybe try:
> >>
> >> dmesg | grep -i iommu
> >>
> >> On 6/25/2021 6:24 PM, Cameron Berkenpas wrote:
> >>> You're welcome. I understand the frustration!
> >>>
> >>> Can you or anyone else with a Legion 7 16ACHg6 check if your CPU has
> >>> IOMMU support? I'm not able to find an answer to this one way or
> >>> another. If so, likely the same trick can be used to find the codec
> >>> initialization verb sequence.
> >>>
> >>>
> >>> On 6/25/21 5:06 PM, <email address hidden> wrote:
> >>>> https://bugzilla.kernel.org/show_bug.cgi?id=208555
> >>>>
> >>>> --- Comment #307 from Pablitar (<email address hidden>) ---
> >>>> And thank you so much for what you are doing Cameron!
> >>>>
> >>>> (In reply to Cameron Berkenpas from comment #305)
> >>>>> You're not the first person to report that these fixes don't work for
> >>>>> the 2021 Legion.
> >>>>>
> >>>>> Can you post your alsa-info?
> >>>>>
> >>>>> I'd like to order one as soon as they become available here in the USA,
> >>>>> but I'm unsure what the availability will be. If I managed to snag one,
> >>>>> I'll work on getting sound working there too.
> >>>>>
> >>>>> On 6/25/21 4:52 PM, <email address hidden> wrote:
> >>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=208555
> >>>>>>
> >>>>>> Pablitar (<email address hidden>) changed:
> >>>>>>
> >>>>>>               What    |Removed                     |Added
> >>>>>>
> >>>>>
> >>
> ----------------------------------------------------------------------------
> >>>>>> CC|                            |<email address hidden>
> >>>>>>
> >>>>>> --- Comment #304 from Pablitar (<email address hidden>) ---
> >>>>>> Hey!
> >>>>>>
> >>>>>> I've tested some of these fixes on my Lenovo 16ACHg6 and had no luck.
> >>>>>>
> >>>>>> What I've tested:
> >>>>>> - Using the applyverbs.py with verbs-working.txt
> >>>>>> - Applying the legion-alc287-0.0.4.patch as per instructions
> >>>>>> - Applying the legion-alc287-0.0.5.patch as per instructions
> >>>>>>
> >>>>>> Something that may be important is that this new model is running
> >>>>>> an AMD
> >>>>>> processor and the sound controller appears as:
> >>>>>>
> >>>>>> 'Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models
> >>>>> 10h-1fh)
> >>>>>> HD Audio Controller'
> >>>>>>
> >>>>>> On Alsa Mixer, it says the "Chip" is ALC287 but the "Card" is HD-Audio
> >>>>>> Generic.
> >>>>>>
> >>>>>> Is that important? I'm bringing this up because the instructions say:
> >>>>>>
> >>>>>> # Patch file to enable output on speakers.
> >>>>>> options snd-hda-intel patch=legion-alc287-0.0.4.patch
> >>>>>>
> >>>>>> And the intel part there may be something to change?
> >>>>>>
> >>>>>> But honestly I'm clueless so this may be waaay off.
> >>>>>>
> >>>>>> Thanks in advance!
> >>>>>>