Damnation
Content Type
Profiles
Forums
Events
Posts posted by Damnation
-
-
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 -
I see there is code for handling the "ACPI Processor Container" in the Windows 10 acpi.sys driver under AcpiProcessorContainerIrpDispatch
can you make an implementation of this for XP acpi.sys please?
I'd like my CPU to not consume so much power.
0 -
Here is my latest ntoskrnl extender source code
It's building those ntosxlibs that's the most challenging part for my version, you can use the prebuilt ones for now, but I can help you to build your own if you like.
0 -
5 hours ago, Dietmar said:
Can you please describe all the steps, that you have done until now,
for to enable Ndis6 on XP?
I never worked with the Extender from @Mov AX, 0xDEAD,
I made use of both the ntoskrnl extender source code as well as the leaked XP/2K3 source code with my attempts to make this work.
I'll upload my source code on here when I get the chance.
5 hours ago, Dietmar said:so I also need basic steps, how to setup Compiler and which programs I need etc.
Do you work for this under XP or which OS?
I also want to try, if this until now builded files from you can work under Win7 SP1 Embedded Standard
Dietmar
To compile ntoskrnl extender I used a Windows 10 VM and the Windows 7 DDK
For my customized internal ntos libraries I used and XP VM and the razzle build environment.
I'll upload my source code on here when I get the chance.
0 -
10 hours ago, Dietmar said:
Until now, I have not seen this device.
But I notice,
that on all boards with the 12900k cpu the power consumption without doing anything is also about 40 Watt on XP
Dietmar
The board I'm using that has this ACPI container device is an ASRock B550 Steel Legend.
If you can get one of these boards for yourself can you test it?
0 -
Do any of your boards have this "ACPI Processor Container Device" on them?
0 -
I think @George King backported the Windows 8.0 x64 version, it'd be part of his XP2ESD project. you can ask him.
0 -
So my processors are in a new ACPI 6.0 container - linux talks about it here - https://patchwork.kernel.org/project/linux-acpi/patch/1449065446-26115-2-git-send-email-sudeep.holla@arm.com/
Can you add in support for this to the ACPI driver?
edit: It's called "ACPI Processor Container Device" on Windows 11
and as "Generic Bus" on XP
0 -
I compared my 5950X system with my threadripper, On threadripper the CPUs are installed but not on my 5950X. I'm quite sure that this is the issue, but I'm not sure how to get the CPUs installed in Device manager.
Any idea how to install them?
0 -
I am quite that a Surface Pro 1 will be UEFI only. There is experimental UEFI support for XP x64, but it's nowhere near stable.
0 -
If you can get me a copy of the driver I can check if the .sys file has it's dependencies met by the ntoskrnl extender. If dependencies are met That'll give you basic sound output at least.
The bundled software still won't work though.
1 -
I think there should be some USB Sound Cards that will work with XP.
0
Compiling ACPI v2.0 driver for Windows XP SP3 and Windows 2003 SP2 (x32/x64)
in Windows XP
Posted
this got ommitted from the main post by mistake I think
patch.exe -Np1 -u -l -i sp1_to_sp3(ACP2).patch