Jump to content

Mov AX, 0xDEAD

Member
  • Posts

    328
  • Joined

  • Last visited

  • Days Won

    6
  • Donations

    0.00 USD 
  • Country

    Uzbekistan

Everything posted by Mov AX, 0xDEAD

  1. @Dietmar@Andalu patch already has "7) BSOD 0xA5 (0x11, 0x08, ..., ...) error in _AMLILoadDDB() (doubled device definition)" workaround, new boards may have other issue
  2. Hi George King Sorry for looong response 1) memcmp for x32 already done by MS in one of .lib, i think in storport.lib, to enable add new section: 2) MmMapIoSpaceEx - OK 3) RtlInitAnsiStringEx - OK if it is w2003/xp copypaste 4) RtlInitUnicodeStringEx - OK if it is w2003/xp copypaste 5) RtlDowncaseUnicodeChar - Wrong, use w2003/xp copypaste, require copy of macros and probably static tables Nls844UnicodeUpcaseTable/Nls844UnicodeLowercaseTable p.s. may be towlower() is alternative, there is argument type mismath 6) PoFx* - as i wrote before, stubs is OK, but not enough, driver still waits for callbacks from kernel
  3. DIFF patch in first post updated to v6 for Windows XP and Windows 2003 Changes: Fix for XOR opcode ACPI0007 CPU definition
  4. acpi.sys v7777.5, Virtual 12 Cores CPU qemu 2.10: qemu 3.1: After reboot both qemus show right names on all cores First Device detection log is same for "Processor" and "QEMU Virtual CPU version 2.5+"
  5. Hi Daniel, Just for extreme fun, i will try run QEMU or Bochs with max 32 cores
  6. OK, seems issue doesn't depend on multicores run. I asked to test because when i played with last acpi.sys in debugger, breakpoint was triggered on same asm opcode from different threads, so i thinked this may be "race condition" problem in patch
  7. @Dietmar One more test please ? in boot.ini create dublicate line with existing config, but add /ONECPU After loading Windows will have only one core in Task Manager, but all cores in Device Manager 1) Repeat deleting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ACPI\GenuineIntel_* 2) Reboot 3) Look for changes in Device Manger after first reboot
  8. pre-v6 diff patch is what you already have, no any changes. There is no more to test, your KDNET log is fine, patcher do anything right, all device definition patched succesfully, all 64 definitions named correctly "intel bla-bla" at ACPI side. Issue happens later outside of processor definition, i have no idea.
  9. This is OK, after reboot or rescan devices, windows request ACPI for device list and get processors: setupapi.log: ACPI\GenuineIntel_-_x86 has priority over acpi\processor, so IntelPPM_Inst section selected Maybe Windows has bug with installing same driver for multi cpu ? You can check yourself: 1) backup current setupapi.log 2) delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ACPI\GenuineIntel_-_x86_Family_6_Model_151 3) reboot 4) backup again setupapi.log, 5) compare first and second setupapi.log, look only for new lines, it will be 10 or 12 detections depending on luck
  10. AML Interpretator error, something wrong with patch or vendor's DSDT code You can make checked build, pre-v6 for XP https://pastebin.com/QKAwg2TE
  11. @Dietmar 1) Orig definition is PR00, PR01, ... , PR63 Modded is C001, C002, ... , C03F and not in same position as orig Later DSDT has definition of _SB->PEPD->DEVY with link to _SB.PR00, _SB.PR01, ... On modded bios, these links linked to nothing 2) Do you always get right names of all cores with modded bios and prev acpi.sys ? 3) Check PM for free version
  12. genuine2 (error) has many missed "ActiveService"="intelppm" on random cores May be problem is out acpi.sys..... Can you show how you patched SSDT to work with previous acpi.sys (where Processor(PR00, 0, 0x1810, 6) was inserted) ?
  13. @Dietmar Can you save registry path to file ? HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ACPI\GenuineIntel_-_Intel64_Family_6_Model_
  14. @Dietmar This acpi.sys patch Device(...) to Processor(...) opcode and equivalent to: All 32 definitions (cuted from 64) have right "GenuineIntel - x86 Family 6 Model 151" name: APIC table:
  15. Thanks, ACPIGetProcessorStatus() was called 64 times, i think SSDT has static definition for 64 cores, it is OK I need dump of current APIC table, you can grab it any way, with "RW Anything"/AIDA64/command line/... After i will send you special compiled acpi.sys with more logging output.
  16. OK, something still wrong with emulating Processor(), if you can dump acpi logs from this board, i think i will find solution. But it may require more time because i don't know where is problem, so it is try&report way
  17. On left screen ACPI show enumerated 1A(#27) core, but in DM name translating broken on 27-32 cores. Do you can setup remote kernel debugging on this board to dump logs with custom acpi.sys?
  18. Hi All Does some else have new board with ACPI007 processor definition ? Experimental patch need to clarify, it works on Dietmar's board but not on Damnation's one
  19. @reboot12 1) Did you sure about Intel SSD Toolbox, Solid State Doctor, etc ? On pre-Vista OSes these utils must traverse NTFS filesystem, find free clusters and send TRIM to disk for each found cluster number. Check with "trimcheck" for real results. 2) Try TxBENCH, it supposed do right way to calculate TRIM clusters on XP, may be it will works with SCSI too
  20. Debug log has enough info about fault source line: mod = div something wrong with math calculation in DSDT/SSDT EDIT: i forget add "break;" to all cases of switch(), probably this is my code problem, not DSDT issue, check fix: =>
  21. 7z and WinRAR has internal memory-load benchmark mode with using all available cores. If Win7+ has better cpu managment, it may has better compression/decompression speed
  22. Nice, seems proper _UID handling is important I dont trust benchmark score as one number(in exUSSR these numbers called "score in parrots" ), run pure cpu load like 7z/WinRAR/What-you-like and check "XP vs Win7+" compression/decompression speed with same CPU
  23. Win2000 acpi driver sources was not leaked, only acpi.sys binary patch possible, no peoples who can do this job (adding acpi2.0 extended syntax and fixing know acpi incompatibilites on first page of topic)
×
×
  • Create New...