Damnation
Content Type
Profiles
Forums
Events
Posts posted by Damnation
-
-
Throttlestop did not help for this, my CPU is unsupported apparently. I think this ACPI0010 device is interfering with it in this case too. I can get you a screenshot of what I'm seeing if you want.
Do either of you have any systems with this ACPI0010 Device?
0 -
0
-
Yes!!
Using grub2 I did a DSDT and SSDT ACPI table modification and I can now confirm with 100% certainty that this ACPI0010 "ACPI Processor Container" Device is the cause of the issue!
I know you're not motivated at all @Mov AX, 0xDEAD but a permanent fix implemented through acpi.sys would still be very much appreciated.
0 -
Oooh! which 10Gbe card works in XP SP3?
0 -
I tried the Rightmark HALT utility, no change.
Can you please patch XP acpi.sys to support ACPI Processor Container?
0 -
how goes your attempts at getting NDIS6 to work?
0 -
3 hours ago, Dibya said:
Thats an Intel driver
Given that there is an IntelPPM service in registry on my threadripper system I'm assuming the driver is generic.
0 -
I really would like like Mov Ax, 0xDEAD to logon more often, sometimes I feel like I'm being ignored.
0 -
I noticed that the IntelPPM.sys driver is not installed on my 5950x PC - I tried creating an IntelPPM service in registry but this resulted in a 7E BSOD.
Any idea how to install it correctly?
0 -
missing functions needed for amdppm.sys with ntoskrn8.sys
QuoteKeEnumerateNextProcessor
KeInitializeEnumerationContext
KeCountSetBitsAffinityEx
KeRemoveProcessorAffinityEx
KeAddGroupAffinityEx
NtQuerySystemInformationEx
KeOrAffinityEx
KeCopyAffinityEx
KeCheckProcessorAffinityEx
KeAddProcessorAffinityEx
KeQueryActiveProcessorAffinity
KeInitializeAffinityEx
KeProcessorGroupAffinity0 -
this got ommitted from the main post by mistake I think
patch.exe -Np1 -u -l -i sp1_to_sp3(ACP2).patch
0 -
I want to try something - Have acpi.sys treat ACPI0010 device as a CPU Processor instead of just a generic device since it contains all the CPUs within it.
Do you know how we could do this with acpi.sys source code?
0 -
Which sites are accessible for you?
0 -
There is an Micro-ATX version of this board that is a bit cheaper, but even if more affordable there is a chance that it does not have this ACPI0010 device in it's CPU SSDT ACPI table that the full sized version does.
0 -
Will you be able to get your own ASRock B550 steel Legend for testing?
0 -
This might be the same issue being described here -
0 -
Could you write a command line test program to check if HLT or MWAIT CPU command is working correctly in XP?
0 -
The work around right now is to use XP compatible USB 1gb LAN adapters.
0 -
IIRC It's netio.sys that is giving us the most trouble getting NDIS6 working right?
0 -
A fix for this would be very much appreciated.
0 -
0
-
Could you try making this ACPI0010 device in a QEMU VM and see if it affects CPU power state? (assuming QEMU can do something like that)
here it is in my CPU SSDT
---
Quote
* Intel ACPI Component Architecture
* AML/ASL+ Disassembler version 20220331 (32-bit version)
* Copyright (c) 2000 - 2022 Intel Corporation
*
* Disassembling to symbolic ASL+ operators
*
* Disassembly of ssdt2.dat, Sat Jul 23 03:15:04 2022
*
* Original Table Header:
* Signature "SSDT"
* Length 0x000003F1 (1009)
* Revision 0x02
* Checksum 0x65
* OEM ID "ALASKA"
* OEM Table ID "CPUSSDT"
* OEM Revision 0x01072009 (17244169)
* Compiler ID "AMI "
* Compiler Version 0x01072009 (17244169)
*/
DefinitionBlock ("", "SSDT", 2, "ALASKA", "CPUSSDT", 0x01072009)
{
Scope (\_SB)
{
Device (PLTF)
{
Name (_HID, "ACPI0010" /* Processor Container Device */) // _HID: Hardware ID
Name (_CID, EisaId ("PNP0A05") /* Generic Container Device */) // _CID: Compatible ID
Name (_UID, One) // _UID: Unique ID
Device (C000)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, Zero) // _UID: Unique ID
}Device (C001)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, One) // _UID: Unique ID
}Device (C002)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x02) // _UID: Unique ID
}Device (C003)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x03) // _UID: Unique ID
}Device (C004)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x04) // _UID: Unique ID
}Device (C005)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x05) // _UID: Unique ID
}Device (C006)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x06) // _UID: Unique ID
}Device (C007)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x07) // _UID: Unique ID
}Device (C008)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x08) // _UID: Unique ID
}Device (C009)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x09) // _UID: Unique ID
}Device (C00A)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x0A) // _UID: Unique ID
}Device (C00B)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x0B) // _UID: Unique ID
}Device (C00C)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x0C) // _UID: Unique ID
}Device (C00D)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x0D) // _UID: Unique ID
}Device (C00E)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x0E) // _UID: Unique ID
}Device (C00F)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x0F) // _UID: Unique ID
}Device (C010)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x10) // _UID: Unique ID
}Device (C011)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x11) // _UID: Unique ID
}Device (C012)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x12) // _UID: Unique ID
}Device (C013)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x13) // _UID: Unique ID
}Device (C014)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x14) // _UID: Unique ID
}Device (C015)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x15) // _UID: Unique ID
}Device (C016)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x16) // _UID: Unique ID
}Device (C017)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x17) // _UID: Unique ID
}Device (C018)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x18) // _UID: Unique ID
}Device (C019)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x19) // _UID: Unique ID
}Device (C01A)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x1A) // _UID: Unique ID
}Device (C01B)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x1B) // _UID: Unique ID
}Device (C01C)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x1C) // _UID: Unique ID
}Device (C01D)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x1D) // _UID: Unique ID
}Device (C01E)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x1E) // _UID: Unique ID
}Device (C01F)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x1F) // _UID: Unique ID
}
}
}
}0 -
Are you sure? I was thinking perhaps the ACPI driver can't control the CPU power state since the processors are now all inside this container device now instead of on their own outside the container like they are with my other machines, including my threadripper which does not have this issue.
I really think this new ACPI0010 device is the cause as it's the only thing that's different from my other AMD systems.
---
I tried an intelppm.sys that @Dietmar sent me earlier but it did not make any difference, still 140W idle.
I noticed that windows 7 and later has an amdppm.sys driver - maybe this needs to be ported to XP?
---
But if you're sure intelppm.sys will resolve the issue can you send me a patched version?
---
P.S
I also tried manually installing processor onto the "ACPI0007" devices in device manager, but I got code 10: cannot start, so I reverted
0 -
I think my way could potentially work since you have some ability to use internal unexported ntoskrnl code which you can't do with the normal ntoskrnl extender.
But it could be that this approach will not work as intended.
@Mov AX, 0xDEAD still knows way more about this than I do.
To build just the ntoskrnl extender you need only to use Windows 7 DDK in a Windows 10 VM
After installing 7 DDK Open "Free Build Environment" from the start menu and navigate to C:\NTOSKRNL_Emu-master_21jul2022_ndis6
then type
bcz
to build extender.
---
To make ntosxlibs:
To make ntosxlibs you will need leaked XP/2K3 source code, an XP VM to built it in, and a mass find/replace tool like powergrep to append ntoskrnX onto the end of all exported ntoskrnl functions so you don't run into conflicts later on.
But this is all very complicated to describe so 1st thing to do would be to get razzle setup and running and building everything in the base folder of the Vanilla Win2k3 source tree.
Once that is working we can continue from there.
0
Compiling ACPI v2.0 driver for Windows XP SP3 and Windows 2003 SP2 (x32/x64)
in Windows XP
Posted
@daniel_k
also, why are you getting angry at me and accuse me of faking my screenshot? when have I ever done that?
I simply reported that an ACPI table mod that removed ACPI0010 resolved the issue.