Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[SOLVED] Problems with Sound Interface

Featured Replies

Hi my name is Victor.

 

Pre-Infos:
Setup:

Intel Core i3 8100
H130M M.2 (Mobo)

16GB DDR4

Radeon RX580

Sound Interface: AG06 Yamaha

 

VM: 

win10_intercafeaudioissues.xml

 

The problem is, when I turn on the virtual machine with the interface USB plugged in without the drive, the audio gets choppy and sizzling.
When I connect with the USB plugged in and the drive installed, the moment my win10 plays some sound, it crashes and that message pops up.

 

672968426_WhatsAppImage2019-12-02at00_51_48.jpeg.5fca4c421a40f8fc8fa27c6d78615db3.jpeg

 

Right after the crash VM crash.
 

Can any good soul help me? ❤️ 

Edited by victorarajooj
SOLVED

  • Author

update:

I found a person who had a similar problem, not exactly the same.
But there is the same mistake, there was an answer regarding qemu.

 

(link: https://bugs.launchpad.net/qemu/+bug/1833053 )


image.png.3c337da3a325a5242313047715ed2d39.png


I don't understand much about this qemu, how do I change it exactly? can this really have a problem?

Tools -> Diagnostics -> attach zip file.

 

Also what Unraid version are you running? I suspect 6.8.0 rc?

 

In your xml, there's this line.

<type arch='x86_64' machine='pc-q35-4.1'>hvm</type>

Change it to:

<type arch='x86_64' machine='pc-q35-3.1'>hvm</type>

 

That should change your Q35 machine back to v3.1

 

But, (and it's a big but), Q35 below 4.0 makes your PCIe runs at x1 so you need to add these codes to the end of your xml (manually) before </domain> so that it can run at full speed.

  <qemu:commandline>
    <qemu:arg value='-global'/>
    <qemu:arg value='pcie-root-port.speed=8'/>
    <qemu:arg value='-global'/>
    <qemu:arg value='pcie-root-port.width=16'/>
  </qemu:commandline>

This is assuming the root port patch hasn't been removed.

If it were removed then you would also need to downgrade to Unraid v6.7.2 (or create a new template and use i440fx machine type, again v3.1).

 

 

The best fix though is to pass through a USB PCIe device to the VM and use your Yamaha plugged into that. Hence I asked for Diagnostics to check your IOMMU group + available devices.

 

 

 

  • Author
20 hours ago, testdasi said:

Tools -> Diagnostics -> attach zip file.

 

Also what Unraid version are you running? I suspect 6.8.0 rc?

 

In your xml, there's this line.


<type arch='x86_64' machine='pc-q35-4.1'>hvm</type>

Change it to:


<type arch='x86_64' machine='pc-q35-3.1'>hvm</type>

 

That should change your Q35 machine back to v3.1

 

But, (and it's a big but), Q35 below 4.0 makes your PCIe runs at x1 so you need to add these codes to the end of your xml (manually) before </domain> so that it can run at full speed.


  <qemu:commandline>
    <qemu:arg value='-global'/>
    <qemu:arg value='pcie-root-port.speed=8'/>
    <qemu:arg value='-global'/>
    <qemu:arg value='pcie-root-port.width=16'/>
  </qemu:commandline>

This is assuming the root port patch hasn't been removed.

If it were removed then you would also need to downgrade to Unraid v6.7.2 (or create a new template and use i440fx machine type, again v3.1).

 

 

The best fix though is to pass through a USB PCIe device to the VM and use your Yamaha plugged into that. Hence I asked for Diagnostics to check your IOMMU group + available devices.

 

 

 

Hi Alright, thanks so much for the reply and sorry for my delay.

I made the changes to the XML you spoke, but when I turned on the screen only goes black.

I'll be sending the diagnostic you asked me.

 

fdge-diagnostics-20191203-1156.zip

And yes, i'am using the lastest version.

 

  • Author

note: i generet the diagnostic before your changes.

  • Author
21 hours ago, testdasi said:

Tools -> Diagnostics -> attach zip file.

 

Also what Unraid version are you running? I suspect 6.8.0 rc?

 

In your xml, there's this line.


<type arch='x86_64' machine='pc-q35-4.1'>hvm</type>

Change it to:


<type arch='x86_64' machine='pc-q35-3.1'>hvm</type>

 

That should change your Q35 machine back to v3.1

 

But, (and it's a big but), Q35 below 4.0 makes your PCIe runs at x1 so you need to add these codes to the end of your xml (manually) before </domain> so that it can run at full speed.


  <qemu:commandline>
    <qemu:arg value='-global'/>
    <qemu:arg value='pcie-root-port.speed=8'/>
    <qemu:arg value='-global'/>
    <qemu:arg value='pcie-root-port.width=16'/>
  </qemu:commandline>

This is assuming the root port patch hasn't been removed.

If it were removed then you would also need to downgrade to Unraid v6.7.2 (or create a new template and use i440fx machine type, again v3.1).

 

 

The best fix though is to pass through a USB PCIe device to the VM and use your Yamaha plugged into that. Hence I asked for Diagnostics to check your IOMMU group + available devices.

 

 

 

The problem of using i440fx, and i'm using an AMD video card (rx 580) and for some reason when i update her drivers on i440fx goes black, it just worked on the Q35.

  • Author

I'm having trouble.
I messing here just now gave another error when starting the VM:

"internal error: Unknown PCI header type '127' for device '0000: 01: 00.0'"

I hope this is not a reason to delete the VM, because there are important files inside, any problem has how to recover right?

I'll be sending the diagnosis again please help me kk

fdge-diagnostics-20191203-1326.zip

  • Author

"Device attached successfully error: Failed to attach device from /tmp/hotattach.tmp error: internal error: cannot parse product 0x0289#remove"

whats mean?

I hope when you picked i440fx, you followed my advice to create a new template and not tried to edit the current template.

 

Editing the xml template does not have any impact on your actual VM. All you need to do is to edit your not-working template in xml mode and then copy-paste your old code (presumably that's the xml you attached in the first post), save and then everything should be back to what it was.

  • Author
On 12/3/2019 at 2:40 PM, testdasi said:

I hope when you picked i440fx, you followed my advice to create a new template and not tried to edit the current template.

 

Editing the xml template does not have any impact on your actual VM. All you need to do is to edit your not-working template in xml mode and then copy-paste your old code (presumably that's the xml you attached in the first post), save and then everything should be back to what it was.

Solved, Thanks TestDasi ❤️ !!

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.