Comment 332 for bug 1958019

(In reply to Cameron Berkenpas from comment #301)
> Created attachment 297623 [details]
> attachment-8392-0.html
>
> Yes, it's a known issue that the sound card is non-resettable. The
> really good is is that this generally isn't a problem.
>
>  If through your testing you start having problems, you might need to
> stop/start the VM, and in some cases, fully shut down the machine. I did
> tons of testing, and very rarely did I need to do anything more than
> restart the VM. Only twice did I need to shut off the entire laptop.
>
> Anyway, getting Windows to use the right driver is a bit tricky, but it
> can absolutely be done. I don't have the same machine, but looking at
> your alsa-info, this should mostly work.
>
> I don't have the URL for your laptop, but here's the Lenovo version as
> an example:
> https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/legion-
> series/legion-7-15imhg05/81yu/81yucto1ww/mp1t35d3/downloads/driver-list/
>
> Find the equivalent part of the Lenovo site for your model and then
> download your sound driver.
>
> When opening the driver, choose to extract the driver (it won't hurt if
> you also install it).
>
> Anyway, here are the instructions I posted earlier in this bug:
>
> You need to force the device expanded above to use the RealTek driver. I was
> able to force it by *extracting* rather than installing the sound driver
> from the Lenovo site. Selecting update driver on the sound device listed
> under "Sound, video and game controllers", and from there I did:
> "Browse my computer for drivers"
> "Let me pick from a list of available drivers on my computer"
> "Have Disk"
> Browse to:
> C:\Drivers\Audio\201211706.15485923\Realtek\Codec_8975.1\HDXLVSST.inf
> Press Ok
> You should see "Realtek High Definition Audio(SST)" as an option. It's the
> only option for me)
> Next
> Yes
> Restart the VM when prompted
>
> Hopefully after these steps, you'll see the "Realtek High Definition
> Audio(SST)" device in device manager as your sound card and you'll get
> sound from windows.
>
> By getting a Win10 VM running with the JCS Qemu means you're a good
> chunk of the way done.
>
> -Cameron
>
> PS: I looked into RtHDDump_V236 and I don't think it's anything I needed
> for my particular case. It seems it can be used to figure out what pins
> should be connected to what. We'll see if you need any of that, but not yet.
>
> On 6/25/21 12:31 PM, <email address hidden> wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=208555
> >
> > --- Comment #299 from Vincent Morel (<email address hidden>) ---
> > I tried to follow the information about installing Qemu
> >
> >
> (https://github.com/ryanprescott/realtek-verb-tools/wiki/How-to-sniff-verbs-from-a-Windows-sound-driver),
> > but ran into problem and I'm not able to install the driver in windows (I
> > have
> > an error while starting qemu abut my soundcard address
> > -> qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no
> available
> > reset mechanism.
> > ).
> > So sadly I'm not able to get the hda_verb output here... :( Would love to
> > help
> > but for today I'm done. Maybe will have time sunday to try something else.
> > Is there a program I can run into a windows partition to sniff the hda? I'm
> > almost sure I saw something but I cannot remember where...
> >

Pffff, tried everything.
-I re-compiled the Qemu with the sme configure arguments as you
-Then started the VM, try witth th 0000 in front of the audio adress (0000:00:1f.3 vs 00:1f.3), same.
Always have qemu-system-x86_64: vfio: Cannot reset device 0000:00:1f.3, no available reset mechanism.
And I am not able to install the driver, I even went the "browse" way (where funily windows show you A:/ by default!)...The driver for my 13s gen2 ITL seems to be 9030.
And yes befor e strating Qemu I did:
sudo ./vfio-bind.sh 0000:00:1f.0 0000:00:1f.3 0000:00:1f.4 0000:00:1f.5
(My sundcard seems to have those other address added, do I have to pass them to qemu also?)...