Jump to content

Damnation

Member
  • Posts

    775
  • Joined

  • Last visited

  • Days Won

    3
  • Donations

    0.00 USD 
  • Country

    Australia

Everything posted by Damnation

  1. @Mov AX, 0xDEAD I'm guessing this would require a BIOS and SSDT modification? or can the acpi.sys driver be written to handle it in this way by itself?
  2. @Mov AX, 0xDEAD Yeah, I'm going with commenting out those 3 lines as a sub-optimal solution. I'll email gigabyte about it and maybe they'll fix it, I wouldn't get my hopes up though, they'll likely just say to RMA my board rather than giving an actual solution.
  3. @Mov AX, 0xDEAD Could there be some hints in the linux kernel source for how to handle this properly? https://github.com/torvalds/linux/search?q=AE_ALREADY_EXISTS
  4. @Mov AX, 0xDEAD I would like to try and find the exact cause of the USB\RESET_FAILURE problem for devices connected to the HUB on the 149C USB3 controller. I don't know where to start going about this with my debugging setup though, would you be willing to help me do this? I don't think this will be easy, as XP reports USB3 Controller and Hub as working normally, only the devices themselves report a problem.
  5. @Dietmar here - https://ufile.io/1obwi832 note: the way I did is sloppy so put it in it's own XPSP1_64 source tree away from the 32bit tree, seems to break the 32bit tree if left in there.
  6. @Mov AX, 0xDEAD Can you recreate this error by creating a duplicate object with the same name in a QEMU VM SSDT? edit: Option 1 worked - no more A5 0x11 0x08 BSOD.
  7. @George King updated amd64 build https://anonfiles.com/zcCehfa1yf/acpi_xp_amd64_forGK_3_7z and src https://anonfiles.com/v5Y4hfaby3/acpi_v4_amd64_src_7z
  8. @Mov AX, 0xDEAD I recall from my linux boot logs (sorry I don't have it to share right now) WT1A was not the only duplicate device, there were about 10 other duplicates or so. I can boot into linux and get the log if you're curious. I'll give option 1 a try since it seems to be easiest. I wounder how Windows 8.1 handles duplicates? does it just ignore them? or handle them some other way? edit: from the linux boot logs 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT5D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT4D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT4D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT3D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT3D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT2D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT2D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.MT1D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CD.WT1D], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT5C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT4C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT4C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT3C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT3C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT2C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT2C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.MT1C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CC.WT1C], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT5B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT4B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT4B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT3B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT3B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT2B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT2B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.MT1B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CB.WT1B], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT5A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT4A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT4A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT3A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT3A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT2A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT2A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.MT1A], AE_ALREADY_EXISTS (20190816/dswload2-326) 17:26:04 kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220) 17:26:04 kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.I2CA.WT1A], AE_ALREADY_EXISTS (20190816/dswload2-326)
  9. @George King I'll make a new ACPI x64 once @Mov AX, 0xDEAD has a fix for object already existing.
  10. @Mov AX, 0xDEAD I get these AE_ALREADY_EXISTS errors when I boot into Linux and check the boot logs too. Linux at least, although it notes the error, seems to not care.
  11. @Mov AX, 0xDEAD I followed example set by @Andalu and got this output. too large to attach uncompressed, sorry. TRX40_DESIGNARE_ACPI_DEBUG_1.zip
  12. @Mov AX, 0xDEAD OK, I got it started - Microsoft (R) Windows Debugger Version 10.0.19041.685 X86 Copyright (c) Microsoft Corporation. All rights reserved. Using NET for debugging Opened WinSock 2.0 Waiting to reconnect... Connected to target 192.168.88.22 on port 50000 on local IP 192.168.88.33. You can get the target MAC address by running .kdtargetmac command. Connected to Windows XP 2600 x86 compatible target at (Mon Apr 25 15:29:39.685 2022 (UTC + 8:00)), ptr64 FALSE Kernel Debugger connection established. ************* Path validation summary ************** Response Time (ms) Location OK C:\Symbols Symbol search path is: C:\Symbols Executable search path is: Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible Built by: 2600.xpsp_sp3_qfe.180912-0606 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 System Uptime: not available Break instruction exception - code 80000003 (first chance) nt!DbgBreakPoint: 8052b718 cc int 3 ************* Path validation summary ************** Response Time (ms) Location OK C:\Symbols Symbol search path is: C:\Symbols Executable search path is: Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible Built by: 2600.xpsp_sp3_qfe.180912-0606 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 System Uptime: not available Break instruction exception - code 80000003 (first chance) nt!DbgBreakPoint: 8052b718 cc int 3 kd> g ACPIInitializeDDB: AMLILoadDDB failed 0xc0000035 *** Assertion failed: ACPIInitializeDDB: AMLILoadDDB failed to load DDB 0 *** Source File: e:\xpsp1\nt\base\busdrv\acpi\driver\shared\acpiinit.c, line 509 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? I recall you saying I need to enter !amli set spewon verboseon logon traceon after ed KD_ACPI_Mask 0xFFFFFFF at some point but I haven't reached that point yet. so what do I type in next?
  13. @Mov AX, 0xDEAD Tomorrow, I'm also gonna try and get KDNET debugging up and running for my AMD Threadripper system, can you send me all the files I'll need to get started? P.S - I only have 1 PC screen, will that be an issue?
  14. @pappyN4 @Dietmar you might need a crossover cat6 for direct PC-to-PC link, at least if MDIX is not supported. I would imagine these cards would support MDIX though.
  15. b9a129fe: Name(SLIC,Buffer(Zero){}AMLI_ERROR(c0000206): Invalid buffer size Buffer: invalid buffer size (size=0) [/code] why would buffer size be 0?
  16. @WinWord2000 Use XP Integral Edition with Optional Patch Integrator Script. In the script use options 1,3,4,5 and 7. put customized ISO onto USB with Wintoflash, install XP.
  17. @daniel_k Oh, that's much simpler than I thought it was going to be, thanks! Some systems might need the OS version lie however, it seems @George King has a system where the GPU is hidden behind ACPI OS version code. Although it seems for this specific case "Windows 2006" should be sufficient given that ACPI 5048 worked.
  18. @George King What was the modification to 5048 ACPI for GPU to work? we should implement this in C code if we can.
  19. @Andalu Here, I made a checked build x86 acpi.sys for you. https://anonfiles.com/hfHcw4Z1x4/checked_acpi_xp_forandalu_7z
  20. @pappyN4 Do you get this behavior with the default XP x64 acpi.sys too?
  21. @George King @Dietmar I think using my x64 acpi.sys for your XP2ESD project should be a safe choice then I think.
  22. @Dietmar Prior to using my x64 acpi.sys did this board have any BSODs with the original x64 acpi.sys?
  23. @Dibya Yeah, we know about those already. We've gotten XP to boot in UEFI already, XP x64 on real hardware only though, and it's unstable.
×
×
  • Create New...