Damnation Posted August 18, 2022 Posted August 18, 2022 @Dietmar Here are the 2 ACPI tables that I load with grub2 for my mod - https://ufile.io/3fv1ijg9
Dietmar Posted August 18, 2022 Posted August 18, 2022 @Damnation Here it is. Be careful, because your XP will not longer start if something goes wrong Dietmar https://ufile.io/ummtcs4q
Damnation Posted August 18, 2022 Posted August 18, 2022 @Dietmar No problems thus far, but the DSDT is unmodified, can you make one for the CPU SSDT too? that's where all the changes are made.
Dietmar Posted August 18, 2022 Posted August 18, 2022 @Damnation They are both in this acpi.reg file: DSDT and SSDT2. It should work. My compi refuses to boot, after I offered him this acpi.reg file, which simple means, that it is loaded. The only problem that I had before was, when I take the DSDT direct out of the Bios. With the acpi tables taking from running windows, all is nice now. Everything works for me, even with acpi.reg from other compi Dietmar PS: By the way I noticed, that RWEverything reads out the loaded ACPI tables and not them from Bios. So, with RW Everything you can make a very quick check, if the tables are loaded.
Damnation Posted August 18, 2022 Posted August 18, 2022 @Dietmar OK, I checked in the registry and I see that the keys were applied, however XP seems to just be ignoring these keys entirely and my CPU still runs at 140W and DSDT is from BIOS.
Dietmar Posted August 18, 2022 Posted August 18, 2022 @Damnation Make sure, that Secure Boot is disabled in your compi Bios settings. With Microsoft I think, that then no Acpi Tables are taken from registry, only from Bios Dietmar
Dietmar Posted August 18, 2022 Posted August 18, 2022 @Damnation Because it works for me on the Asrock z690 Extreme board and also on the Asrock z370 k6 gaming board, the only idea that I have is, that some settings on your Bios does not match for to upload those tables Dietmar
Damnation Posted August 18, 2022 Posted August 18, 2022 @Dietmar Moving these keys to CurrentControlSet instead of ControlSet001 results in an A5 BSOD
Dietmar Posted August 18, 2022 Posted August 18, 2022 @Damnation Exact this happens to me, when I take the DSDT from the Bios and not from the running XP Dietmar
Dietmar Posted August 18, 2022 Posted August 18, 2022 (edited) @Damnation Make a new extract of all Acpi files under running Win10 from your compi. Do you have Bios 2.2? Because from the Asrock Webside I read, that with from Bios 2.10 upward enable AMD CPU fTPM in BIOS default. Can you disable fTPM in Bios? If not, you can go back to an older Bios, BUT ALWAYS RISK to change something in BIOS. And then try to upload its own dsdt.raw with the asl.exe tool under XP SP3. Later you can edit a little thing via dsdt.dsl and look, if it is still loaded after reboot with the asl.exe tool Dietmar Edited August 18, 2022 by Dietmar
Damnation Posted August 19, 2022 Posted August 19, 2022 @Dietmar Yes I have BIOS 2.2 TPM is on with the default settings, but I made sure to switch it off since since I wanted to install Windows 11 in CSM mode on this machine.
Dietmar Posted August 19, 2022 Posted August 19, 2022 @Damnation Have you tested the DSDT patcher at boottime from @Mov AX, 0xDEAD? He updated his Tutorial here at MSFN, now it is much more easier and it works, I tested Dietmar
Dietmar Posted August 19, 2022 Posted August 19, 2022 (edited) @Damnation Edited August 19, 2022 by Dietmar
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now