Jump to content

Compiling ACPI v2.0 driver for Windows XP SP3 and Windows 2003 SP2 (x32/x64)


Recommended Posts

Posted

Ah thanks, that explains it!
Reading that section of the thread it looks like the only way of connecting the computers for debugging is with a direct Ethernet connection, which I can't do on the Flex 10 as it doesn't have an Ethernet port.
That would surely be the case with most modern computers though, very few if any seem to have Ethernet ports now.
Reading between the lines, it looks as if wi-fi connection isn't an option either, so is a direct USB connection the only option?
The USB debugging lead linked to in the thread is USB 3.0 only as far as I can see, and it says it isn't backwards compatible.
As my main desktop doesn't have USB 3.0 hardware, that's a non-starter too.

So, is there actually no way that I can do this debugging?
:dubbio: :(


Posted (edited)

@Mov AX, 0xDEAD

I succeed with the direct Sata install of XP SP3 and the acpi.sys V5 on the Biostar z690A board.

But this install works only with install of XP from a real CD.

The Intel 1006 driver seems to come in conflict with the video output (some strange symbols appear on screen during install of XP) and then Bsod.

The only generic Sata driver until now is the driver from Kai Schtrom

Dietmar

PS: No other version of Windows bit32 can be installed on the Biostar z690A board, only XP SP3.

Edited by Dietmar
Posted

@Dave-H

The only way of debugging the Flex 10 is via its internal PCIe mini port.

This works only with the use of an EEpromer, because you have to kill the Whitelist from Lenovo in its Bios chip

Dietmar

Posted

@Dietmar

Oh dear, I had a nasty feeling that would be the answer!
So debugging with recent machines with no Ethernet ports is only possible via direct USB connection with a special lead by the sound of it.
I do remember now that you said before that you used a connection via the PCIe miniport where the Wi-Fi/Bluetooth card goes.
I don't think I'll be doing that, but at least I tried!
:(
Your Flex 10 also had the restart freezing problem if I remember rightly, did you ever manage to debug that? :dubbio:
Cheers, Dave.
:)

Posted (edited)

Because I want to understand, what is going on with the Biostar z690A board,

I make a XP SP3 german real setup DVD with all SP3 updates until April 2014 and all Posready until May 2019 via Nlite 1.4.9.3 .

Into this I integrate by hand the Intel 1006 driver but only with the entry for

iaAHCI_600_6        = "Intel(R) SATA AHCI Controller DEV_7AE2 added by Dietmar"

because I noticed, that the Setup routine always takes a wrong variant of this Intel driver during TXT setup, which gives Bsod.

With UltraIso I put my laast acpi.sys V5 into the *.iso. The size of this *.iso is 836.354.048 Bytes.

This is the minimal size of an original XP SP3 with all updates.

And voila, XP installs via this modded Intel 1006 driver direct on the Biostar z690A board,

very fast because it is via DVD

Dietmar

20220605-113115.jpg

 

 

Edited by Dietmar
Posted (edited)

@Mov AX, 0xDEAD

Can you help me, please?

How do I know the ACPI code/opcode that causes the crash? I want to learn.

I've run a kernel debug session with the checked version of acpi.sys SP3.

It runs AsyncEvalObject on all Devices.

AsyncEvalObject(\_SB.AWAC._STA) seems to succeed, but something happen before showing processing device, which should be DSC0?

f6d60283: Device(AWAC)OSNotifyCreate: 850EF760 (AWAC) = 00000103
...
f6d6222f: Device(DSC0)OSNotifyCreate: 850F4344 (DSC0) = 00000103

Z490.7z

Edited by daniel_k
Posted (edited)
3 hours ago, daniel_k said:

@Mov AX, 0xDEAD

Can you help me, please?

How do I know the ACPI code/opcode that causes the crash? I want to learn.

AsyncEvalObject(\_SB.AWAC._STA) seems to succeed, but something happen before showing processing device, which should be DSC0?

 

@daniel_k

this log doesn't have info about c0140001

AMLILoadDDB is parent wrapper on AML Interpretator, error can be anywhere before

you can enable more debug options, but log will be HUGE, probaly you never see end of it !

example of custom DSDT under VM

Quote

fffffadff96cf9db: | | | | | | AMLI:| | | | | | PrintIndent!
AMLI:| | | | | | ParseIntObj(pbOp=f96cf9db,pdataResult=fa3cf838,fErrOK=1)
AMLI:| | | | | | ParseIntObj=c0140001 (pbOp=f96cf9db,Value=0)
AMLI:| | | | | | ParseString(pbOp=f96cf9db,pdataResult=fa3cf838,fErrOK=1)
AMLI:| | | | | | ParseString=c0140001 (Value=<null>)

in extended debug mode ParseIntObj()/ParseString() and many other functions output more info
 

to enable patch trace.c

Quote

BOOLEAN EXPORT IsTraceOn(UCHAR n, char *pszProcName, BOOLEAN fEnter)
{
    BOOLEAN rc = FALSE;

     ....

to

Quote

BOOLEAN EXPORT IsTraceOn(UCHAR n, char *pszProcName, BOOLEAN fEnter)
{
    BOOLEAN rc = TRUE;

    TraceIndent(); - don't sure about this, must indent must be better with it

   ....

 

Edited by Mov AX, 0xDEAD
Posted (edited)
On 6/5/2022 at 2:30 PM, Dietmar said:

Because I want to understand, what is going on with the Biostar z690A board,

I make a XP SP3 german real setup DVD with all SP3 updates until April 2014 and all Posready until May 2019 via Nlite 1.4.9.3 .

Into this I integrate by hand the Intel 1006 driver but only with the entry for

iaAHCI_600_6        = "Intel(R) SATA AHCI Controller DEV_7AE2 added by Dietmar"

because I noticed, that the Setup routine always takes a wrong variant of this Intel driver during TXT setup, which gives Bsod.

With UltraIso I put my laast acpi.sys V5 into the *.iso. The size of this *.iso is 836.354.048 Bytes.

This is the minimal size of an original XP SP3 with all updates.

And voila, XP installs via this modded Intel 1006 driver direct on the Biostar z690A board,

very fast because it is via DVD

Dietmar

20220605-113115.jpg

 

 

you are doing very well I have been following this topic for a long time. I'm trying to try it on my primary computer.

CPU: Ryzen 5 3500 6-Core

Motherboard : A320M-HDV R4.0 (ASRock)

RAM: 16GB (Teamgroup) will use Patch PAE

VGA : GTX 750 TI (I may switch to GT 210 soon) because the card has a problem

BIOS : P7.20 (latest version) 04/27/2022

Sorage : KINGSTON SA2000M 8250G 250GB 

Which ACPI do I have to choose which is compatible?

Edited by tpao12
Posted (edited)

@Mov AX, 0xDEAD

Enabled Trace, but top of log is cut off and it ends with Stop 0x7E @ ACPI.sys ( ACPI!ConPrintf+2d)

So sad.

Any ideas?

PS: Do you still have your original source of XP SP3 acpi.sys without the ACPI2+ fixes?
If you do, can you please build a debug version of it for me, please? Maybe it doesn't crash like the checked version from MS.

Z490Trace.7z

Edited by daniel_k
Posted
2 hours ago, daniel_k said:

@Mov AX, 0xDEAD

Enabled Trace, but top of log is cut off and it ends with Stop 0x7E @ ACPI.sys ( ACPI!ConPrintf+2d)

Any ideas?

error in StrCpy(), it try to show endless string,

In  StrCpy() + StrLen() remove lines to enable debug output

Quote

 

ENTER(5, ("StrCpy(Dst=%s,Src=%s,n=%d)\n", pszDst, pszSrc, n));

EXIT(5, ("StrCpy=%s\n", pszDst));

ENTER(5, ("StrLen(str=%s,n=%d)\n", psz, n));

EXIT(5, ("StrLen=%u\n", dwLen));

 

2 hours ago, daniel_k said:

PS: Do you still have your original source of XP SP3 acpi.sys without the ACPI2+ fixes?
If you do, can you please build a debug version of it for me, please? Maybe it doesn't crash like the checked version from MS.

Z490Trace.7z 27.97 kB · 0 downloads

i have old sp1->sp3 sources, but you need compile it yourself, see PM for link

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...