Sound failure on VirtualBox due to nonsensical resource conflict

Ask your support questions in here

Moderator: Moderator Team

Post Reply
RobinHood2021
Posts: 1
Joined: Tue Apr 13, 2021 5:35 am

Sound failure on VirtualBox due to nonsensical resource conflict

Post by RobinHood2021 »

Hi.

I installed ReactOS debug build 2343 (I have not gotten a chance to get build 2344 yet) on a VirtualBox machine, and attempted to install the AC97 audio driver on it, but it does not work.

I've set up the serial port as described in "VirtualBox\Get debug output" in the Wiki and generated a logfile using PuTTY. The entire logfile is yards long, so I can't paste the whole thing here; however, I can paste the critical output relating to my attempt to install the AC97 driver.

Code: Select all

Starting system audio services
Starting sysaudio service
(/ntoskrnl/mm/ARM3/sysldr.c:182) Loading: \SystemRoot\System32\drivers\sysaudio.sys at F7734000 with f pages
(/ntoskrnl/mm/ARM3/sysldr.c:182) Loading: \SystemRoot\system32\drivers\ALCXWDM.SYS at F771C000 with 18 pages
(/ntoskrnl/mm/ARM3/sysldr.c:182) Loading: \SystemRoot\system32\drivers\portcls.sys at F76C2000 with 5a pages
(/ntoskrnl/mm/ARM3/sysldr.c:182) Loading: \SystemRoot\system32\drivers\drmk.sys at F76B8000 with a pages
(/ntoskrnl/mm/ARM3/sysldr.c:2556) ImageBase 0xF771C000 ImageSize 0x17800 Section 7 VA 0x16a80 Raw 0xd80 virt 0xd50
Starting wdmaud service
(/ntoskrnl/io/pnpmgr/pnpres.c:641) Resource conflict: IRQ (0xb 0xb vs. 0xb 0xb)
(/ntoskrnl/io/pnpmgr/pnpres.c:641) Resource conflict: IRQ (0xb 0xb vs. 0xb 0xb)
(/ntoskrnl/mm/ARM3/sysldr.c:182) Loading: \SystemRoot\System32\drivers\wdmaud.sys at F767E000 with 3a pages
Device added to list
Processing existing devices
* Service started
(/drivers/wdm/audio/backpln/portcls/interrupt.cpp:258) Vector 59 Level 16 Flags 0 Affinity ffffffff
(/drivers/wdm/audio/backpln/portcls/interrupt.cpp:272) CInterruptSync::Connect result 0
As you can see, there are two nonsensical resource conflict errors which are causing the audio device to fail to function correctly. The question now becomes, what can we do about this?

Brandon Taylor
User avatar
binarymaster
Posts: 423
Joined: Sun Nov 16, 2014 7:05 pm
Location: Russia, Moscow
Contact:

Re: Sound failure on VirtualBox due to nonsensical resource conflict

Post by binarymaster »

RobinHood2021 wrote: Tue Apr 13, 2021 5:43 am As you can see, there are two nonsensical resource conflict errors which are causing the audio device to fail to function correctly.
These errors are not related to the audio initialization failure.

Also I'm able to get audio on latest nightly build (0.4.15-dev-2344-g8ddbfdeb57) with the usual way - AC'97 driver installed from RAPPS, and two reboots afterwards. VirtualBox 6.1.18.
Pinochet
Posts: 1
Joined: Mon May 10, 2021 3:51 pm

Re: Sound failure on VirtualBox due to nonsensical resource conflict

Post by Pinochet »

So what is the solution? I'm running 4.13 in this version of VB:

version 6.1.14 r140239 (Qt5.6.2)

I've set the sound to AC97 before starting. I found the driver to download in the Applications area and installed and rebooted a couple times. I'm still getting a 'system device' not installed error. When I click the Sound under the control panel, it give an error, you click ok, and kind of works except for being able to play any of the installed waves.
katheko
Posts: 1
Joined: Tue May 18, 2021 7:08 pm
Contact:

Re: Sound failure on VirtualBox due to nonsensical resource conflict

Post by katheko »

Hello, could you solve it? Something similar happened to me and I would like to know to see if I can fix it
MadWolf
Posts: 598
Joined: Sat Dec 31, 2005 4:19 am
Contact:

Re: Sound failure on VirtualBox due to nonsensical resource conflict

Post by MadWolf »

RobinHood2021 wrote: Tue Apr 13, 2021 5:43 am Hi.

I installed ReactOS debug build 2343 (I have not gotten a chance to get build 2344 yet) on a VirtualBox machine, and attempted to install the AC97 audio driver on it, but it does not work.

I've set up the serial port as described in "VirtualBox\Get debug output" in the Wiki and generated a logfile using PuTTY. The entire logfile is yards long, so I can't paste the whole thing here; however, I can paste the critical output relating to my attempt to install the AC97 driver.

Code: Select all

Starting system audio services
Starting sysaudio service
(/ntoskrnl/mm/ARM3/sysldr.c:182) Loading: \SystemRoot\System32\drivers\sysaudio.sys at F7734000 with f pages
(/ntoskrnl/mm/ARM3/sysldr.c:182) Loading: \SystemRoot\system32\drivers\ALCXWDM.SYS at F771C000 with 18 pages
(/ntoskrnl/mm/ARM3/sysldr.c:182) Loading: \SystemRoot\system32\drivers\portcls.sys at F76C2000 with 5a pages
(/ntoskrnl/mm/ARM3/sysldr.c:182) Loading: \SystemRoot\system32\drivers\drmk.sys at F76B8000 with a pages
(/ntoskrnl/mm/ARM3/sysldr.c:2556) ImageBase 0xF771C000 ImageSize 0x17800 Section 7 VA 0x16a80 Raw 0xd80 virt 0xd50
Starting wdmaud service
(/ntoskrnl/io/pnpmgr/pnpres.c:641) Resource conflict: IRQ (0xb 0xb vs. 0xb 0xb)
(/ntoskrnl/io/pnpmgr/pnpres.c:641) Resource conflict: IRQ (0xb 0xb vs. 0xb 0xb)
(/ntoskrnl/mm/ARM3/sysldr.c:182) Loading: \SystemRoot\System32\drivers\wdmaud.sys at F767E000 with 3a pages
Device added to list
Processing existing devices
* Service started
(/drivers/wdm/audio/backpln/portcls/interrupt.cpp:258) Vector 59 Level 16 Flags 0 Affinity ffffffff
(/drivers/wdm/audio/backpln/portcls/interrupt.cpp:272) CInterruptSync::Connect result 0
As you can see, there are two nonsensical resource conflict errors which are causing the audio device to fail to function correctly. The question now becomes, what can we do about this?

Brandon Taylor
hi
are you testing a release build for example 0.4.13 or a Nightly build for example Revision 9f549db
reactos-bootcd-0.4.15-dev-2569-g9f549db-x86-gcc-lin-dbg
post the name of the .iso you used to install ReactOS

try installing a new Nightly build to see if it has been fixed. I have had problems with the audio driver in the past where I install the driver and it failed to run then I shutdown ReactOS maybe 2 or 3 times then the sound starts working. some times I have reinstalled the same build where the audio driver failed to run then after the reinstall the driver starts working. sometimes the opposite happens audio driver was working but after the reinstall driver failed to run

you can use pastebin then add a link to the full debug log
Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests