Page 1 of 1
hd audio getting in the way of real hardware testing
Posted: Wed Feb 20, 2019 5:56 pm
by Zombiedeth
The hd audio driver included with ReactOS is really causing problems for doing testing on real hardware. It's not too bad if you only have hd audio integrated on the motherboard and can disable it in the bios but otherwise it pretty much guarantees a crash or bsod if you have hdmi or other devices that use the hd audio driver. I really think it would help ReactOS tremendously if this driver was not installed by default it's just not ready yet. Maybe it could be included in a optional folder on the ISO so people could still test it as needed.
Re: hd audio getting in the way of real hardware testing
Posted: Wed Feb 20, 2019 6:09 pm
by Reactions
I did have the same issue so I copied from Windows 10. If your pc has Nvidia Optimus, enable it in bios. If installing, have it off.
Re: hd audio getting in the way of real hardware testing
Posted: Thu Feb 21, 2019 12:33 am
by Julcar
You're right, our hdaudbus.sys driver is a pain when installing on newer laptops, what I did is disabling it of the building of a new iso
Re: hd audio getting in the way of real hardware testing
Posted: Thu Feb 21, 2019 12:39 am
by Reactions
Re: hd audio getting in the way of real hardware testing
Posted: Thu Feb 21, 2019 12:44 am
by Reactions
Re: hd audio getting in the way of real hardware testing
Posted: Tue Feb 26, 2019 12:15 pm
by ThFabba
Perhaps if instead of complaining and suggesting strange work-arounds, people actually filed good bug reports and worked with the devs to narrow down the problem (as in
https://jira.reactos.org/browse/CORE-14617), we wouldn't need to be having such discussions.
Anyone affected, please try with a8414f665b or later, and if you still encounter hdaudbus crashes, please file a ticket with a debug log and backtrace. Thanks.
Re: hd audio getting in the way of real hardware testing
Posted: Tue Feb 26, 2019 5:06 pm
by Zombiedeth
The driver literally hard locks my computer including the new version. I will try to get a debug log but a backtrace seems impossible currently.
Please consider not including this driver in the 0.4.11 release or newer release builds until the issues with it are resolved.