Page 50 of 59 FirstFirst ... 404849505152 ... LastLast
Results 491 to 500 of 581

Thread: HOWTO Fix A Buggy DSDT File

  1. #491
    Join Date
    Oct 2009
    Beans
    1

    Re: HOWTO Fix A Buggy DSDT File

    67GTA or computer.technician,

    Can you help with this one? I am adding a firewire hack to get rid of the power conservation issue. This is for an XPS M1530 Dell Laptop. running both Linux and OSX86 Snow.


    Here is the error:

    /Users/osxfr33k/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl 6100: [*** iASL: Read error on source code temp file /Users/osxfr33k/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.src ***]
    Error 4096 - syntax error, unexpected $end ^

    ASL Input: /Users/osxfr33k/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl - 6101 lines, 194479 bytes, 2019 keywords
    Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 0 Optimizations


    Here is the Hack I inserted from EVO DSDTSE a nice Gui Application with a ton of fixes like HPET, RTC and the list goes on and on.






    Firewire power conservation Hack.

    It´s a nice idea to change all your firewire names on DSDT to apple´s ones, for example from FIWI to FRWR.



    Locate Scope (_GPE), add this on the end.

    Method (_L1A, 0, NotSerialized) /* <-- Added for firewire */
    {
    Notify (\_SB.PCI0.PCIB.FRWR, 0x00)
    Notify (\_SB.PWRB, 0x02)
    }


    Locate your Firewire device (or create it with this code if it doesn´t exist)


    Device (FRWR) /*Add all this code if you don´t have firewire device on DSDT*/
    {
    Name (_ADR, 0x00070000)
    Name (_GPE, 0x1A)
    Method (_DSM, 4, NotSerialized) /* Add from here if you already have a firewire device on dsdt*/
    {
    Store (Package (0x02)
    {
    "fwhub",
    Buffer (0x04)
    {
    0x00, 0x00, 0x00, 0x00
    }
    }, Local0)
    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
    Return (Local0)
    } /* End of code if you just add to a existing firewire device */
    }








    My DSDT.dsl is attached.

    Thanks for having a look and trying to help. If you are able to fix it can you post what was wrong and what you did to rectify the error?





    EDITED THE NEXT DAY:

    I think I can see why this Hack is nto going to work.

    Notify (\_SB.PCI0.PCIB.FRWR, 0x00)
    Notify (\_SB.PWRB, 0x02)

    I do not have a PCIB nor a PWRB device. I guess if I add those devices I can assume this script will compile correctly?

    PWRB is just power button and I see that EVO has a small script for that I can add that easily. But what is the PCIB device I have no idea?
    Attached Files Attached Files
    Last edited by osxfr33k; June 30th, 2010 at 08:32 PM. Reason: Possible reason for the compiling issue?

  2. #492

    Re: HOWTO Fix A Buggy DSDT File

    I scanned over the external references that the SSDT-AMICPU-PROC table contains and the arguments are used in the DSDT but I see no use for them in this table. The question that I cannot answer and would appreciate someone answering is; "What does this table operate on the Arguments after calling them?" If in fact this table is able to call the arguments because it does not store them for any use and then returns to the external reference in the DSDT. I'll have to keep my original opinion that this table is useless and you don't need it other than for BIOS byte length padding. I'm not an expert and can in no way say that the original programmer didn't have a use for them but with a parsing error of the arguments then the method will not use them. You could even comment out the references to Arg0-Arg3 for each of the methods because they are not used and then it would compile with IASL. The DSDT had a few warnings and remarks and I corrected those but I'm assuming that you could perform that yourself because they were fairly easy patches so I did not upload them. Hope this information helps and please let me know if you find out that there is a reason for those arguments use in this particular table.

    Update: I made a rookie mistake whenever disassembling the SSDT tables which you may have made as well. Whenever there are external references then you must parse the the table with the DSDT. I had included all of the SSDT tables with the -e option but forgot to reference them with the DSDT. I'm either tired because it's 04:00 or getting lazy. Anyways, I've uploaded the corrected and compiled tables. Use at your own risk.
    Quote Originally Posted by choodalls View Post
    Hi,
    No actually they were taken direct from a linux environment using an acpi-dump python script from a live Opensuse CD (i.e. using the acpidump tool). Yes, I have opened in a mac environment, but what i sent to you were the originals from the linux extraction........they are the manufacturer supplied and unpatched tables,
    The Dell Vostro is a 3500 running latest Bios of A04.
    Please though if you feel that there is something amiss then feel free to download again.
    I have been doing patching, but not at all to the tables i supplied to you - they are 100% as Dell made them. I would not ask for Darwin patching here, but am grateful for any help that you feel able to give me with what look to me to be slightly odd examples and in particular with the _PR scope issue.
    Thanks again.
    Attached Files Attached Files
    Last edited by computer.technician; July 1st, 2010 at 10:44 AM. Reason: Update to ACPI tables

  3. #493

    Re: HOWTO Fix A Buggy DSDT File

    There are other forums for hacking firmware to support the Darwin kernel.
    Quote Originally Posted by osxfr33k View Post
    67GTA or computer.technician,

    Can you help with this one? I am adding a firewire hack to get rid of the power conservation issue. This is for an XPS M1530 Dell Laptop. running both Linux and OSX86 Snow.


    Here is the error:

    /Users/osxfr33k/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl 6100: [*** iASL: Read error on source code temp file /Users/osxfr33k/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.src ***]
    Error 4096 - syntax error, unexpected $end ^

    ASL Input: /Users/osxfr33k/Library/Application Support/EvOSoftware/DSDT/DSDTFiles/dsdt.dsl - 6101 lines, 194479 bytes, 2019 keywords
    Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 0 Optimizations


    Here is the Hack I inserted from EVO DSDTSE a nice Gui Application with a ton of fixes like HPET, RTC and the list goes on and on.






    Firewire power conservation Hack.

    It´s a nice idea to change all your firewire names on DSDT to apple´s ones, for example from FIWI to FRWR.



    Locate Scope (_GPE), add this on the end.

    Method (_L1A, 0, NotSerialized) /* <-- Added for firewire */
    {
    Notify (\_SB.PCI0.PCIB.FRWR, 0x00)
    Notify (\_SB.PWRB, 0x02)
    }


    Locate your Firewire device (or create it with this code if it doesn´t exist)


    Device (FRWR) /*Add all this code if you don´t have firewire device on DSDT*/
    {
    Name (_ADR, 0x00070000)
    Name (_GPE, 0x1A)
    Method (_DSM, 4, NotSerialized) /* Add from here if you already have a firewire device on dsdt*/
    {
    Store (Package (0x02)
    {
    "fwhub",
    Buffer (0x04)
    {
    0x00, 0x00, 0x00, 0x00
    }
    }, Local0)
    DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
    Return (Local0)
    } /* End of code if you just add to a existing firewire device */
    }








    My DSDT.dsl is attached.

    Thanks for having a look and trying to help. If you are able to fix it can you post what was wrong and what you did to rectify the error?





    EDITED THE NEXT DAY:

    I think I can see why this Hack is nto going to work.

    Notify (\_SB.PCI0.PCIB.FRWR, 0x00)
    Notify (\_SB.PWRB, 0x02)

    I do not have a PCIB nor a PWRB device. I guess if I add those devices I can assume this script will compile correctly?

    PWRB is just power button and I see that EVO has a small script for that I can add that easily. But what is the PCIB device I have no idea?

  4. #494
    Join Date
    Aug 2009
    Beans
    5

    Re: HOWTO Fix A Buggy DSDT File

    Quote Originally Posted by computer.technician View Post
    I scanned over the external references that the SSDT-AMICPU-PROC table contains and the arguments are used in the DSDT but I see no use for them in this table. The question that I cannot answer and would appreciate someone answering is; "What does this table operate on the Arguments after calling them?" If in fact this table is able to call the arguments because it does not store them for any use and then returns to the external reference in the DSDT. I'll have to keep my original opinion that this table is useless and you don't need it other than for BIOS byte length padding. I'm not an expert and can in no way say that the original programmer didn't have a use for them but with a parsing error of the arguments then the method will not use them. You could even comment out the references to Arg0-Arg3 for each of the methods because they are not used and then it would compile with IASL. The DSDT had a few warnings and remarks and I corrected those but I'm assuming that you could perform that yourself because they were fairly easy patches so I did not upload them. Hope this information helps and please let me know if you find out that there is a reason for those arguments use in this particular table.
    Thanks for your time. BTW managed to download the attachment fine today - think there was something odd about my log in yesterday that prevented me accessing properly.

  5. #495

    Re: HOWTO Fix A Buggy DSDT File

    NP. Yesterday, I had the same problem with logging in and uploading the archive to this forum. Perhaps, these will be helpful to you. Do you plan on replacing your original module in your BIOS with this one?
    Quote Originally Posted by choodalls View Post
    Thanks for your time. BTW managed to download the attachment fine today - think there was something odd about my log in yesterday that prevented me accessing properly.

  6. #496
    Join Date
    Dec 2009
    Beans
    12

    Re: HOWTO Fix A Buggy DSDT File

    Hi,

    Can you guys please help me with my dsdt file.
    Here's the output and the dsdt.dsl file.

    /home/ubuntu/dsdt.dsl 8873: Method (_GTM, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 8873: Method (_GTM, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 9033: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9033: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9101: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9101: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9174: Method (_GTM, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 9174: Method (_GTM, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 9334: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9334: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9402: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9402: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9507: Method (_GTM, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 9507: Method (_GTM, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 9667: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9667: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9735: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9735: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9808: Method (_GTM, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 9808: Method (_GTM, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 9968: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9968: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 10036: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 10036: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    ASL Input: /home/ubuntu/dsdt.dsl - 10111 lines, 370896 bytes, 4450 keywords
    AML Output: /home/ubuntu/dsdt.aml - 38326 bytes, 939 named objects, 3511 executable opcodes

    Compilation complete. 0 Errors, 24 Warnings, 0 Remarks, 37 Optimizations

    Many thanks in advance
    Attached Files Attached Files
    Last edited by hornedfiend; July 10th, 2010 at 11:10 AM. Reason: forgot to update

  7. #497

    Re: HOWTO Fix A Buggy DSDT File

    Patched and compiled this DSDT with zero warnings, errors, or remarks using IASL 20091214. Use at your own risk.
    Quote Originally Posted by hornedfiend View Post
    Hi,

    Can you guys please help me with my dsdt file.
    Here's the output and the dsdt.dsl file.

    /home/ubuntu/dsdt.dsl 8873: Method (_GTM, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 8873: Method (_GTM, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 9033: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9033: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9101: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9101: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9174: Method (_GTM, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 9174: Method (_GTM, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 9334: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9334: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9402: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9402: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9507: Method (_GTM, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 9507: Method (_GTM, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 9667: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9667: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9735: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9735: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9808: Method (_GTM, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 9808: Method (_GTM, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTM)

    /home/ubuntu/dsdt.dsl 9968: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 9968: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 10036: Method (_GTF, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_GTF)

    /home/ubuntu/dsdt.dsl 10036: Method (_GTF, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_GTF)

    ASL Input: /home/ubuntu/dsdt.dsl - 10111 lines, 370896 bytes, 4450 keywords
    AML Output: /home/ubuntu/dsdt.aml - 38326 bytes, 939 named objects, 3511 executable opcodes

    Compilation complete. 0 Errors, 24 Warnings, 0 Remarks, 37 Optimizations

    Many thanks in advance
    Attached Files Attached Files

  8. #498
    Join Date
    Apr 2005
    Location
    New Port Richey, Florida,
    Beans
    27
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: HOWTO Fix A Buggy DSDT File

    Can you patch this DSDT from Lenovo Y730?

    Warnings:

    Code:
    dsdt.dsl  1606:             Method (_WED, 1, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (_WED)
    
    dsdt.dsl  1606:             Method (_WED, 1, NotSerialized)
    Warning  1080 -                        ^ Reserved method must return a value (_WED)
    
    dsdt.dsl  5855:                     Method (HKDS, 1, NotSerialized)
    Warning  1087 -                                ^ Not all control paths return a value (HKDS)
    
    dsdt.dsl  6329:                             Method (_CFG, 0, NotSerialized)
    Warning  1098 -                  Unknown reserved name ^  (_CFG)
    
    dsdt.dsl  6379:                             Method (VPCR, 1, Serialized)
    Warning  1087 -   Not all control paths return a value ^  (VPCR)
    
    dsdt.dsl  6402:                                     Name (_T_0, Zero)
    Remark   5110 -                Use of compiler reserved name ^  (_T_0)
    
    dsdt.dsl  6696:                             Method (_CFG, 0, NotSerialized)
    Warning  1098 -                  Unknown reserved name ^  (_CFG)
    
    ASL Input:  dsdt.dsl - 9443 lines, 342961 bytes, 3826 keywords
    AML Output: dsdt.aml - 35636 bytes, 899 named objects, 2927 executable opcodes
    Attached Files Attached Files

  9. #499
    Join Date
    Dec 2009
    Beans
    12

    Re: HOWTO Fix A Buggy DSDT File

    Unfortunately, the DSDT implementation failed. I'm not seeing any lines as stated in the first post (after I compile and update the kernel) after the output file is created.
    Why is that? Am I doing something wrong, I followed the instructions exactly. Does it make any difference that I changed the user and installed ubuntu with wubi (I previously used usb installer and had ubuntu installed on an usb stick)?

  10. #500
    Join Date
    Jul 2010
    Beans
    1

    Re: HOWTO Fix A Buggy DSDT File

    HI !!

    Please, someone can help me with my DSDT? It´s from my HP DV3540es.

    I´m having all these warnings:


    Intel ACPI Component Architecture
    ASL Optimizing Compiler version 20090730 [Aug 12 2009]
    Copyright (C) 2000 - 2009 Intel Corporation
    Supports ACPI Specification Revision 4.0

    /Library/DSDT/DSDTFiles/dsdt.dsl 3430: Method (_HOT, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_HOT)

    /Library/DSDT/DSDTFiles/dsdt.dsl 3430: Method (_HOT, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_HOT)

    /Library/DSDT/DSDTFiles/dsdt.dsl 3491: Method (_HOT, 0, NotSerialized)
    Warning 1087 - Not all control paths return a value ^ (_HOT)

    /Library/DSDT/DSDTFiles/dsdt.dsl 3491: Method (_HOT, 0, NotSerialized)
    Warning 1080 - Reserved method must return a value ^ (_HOT)

    ASL Input: /Library/DSDT/DSDTFiles/dsdt.dsl - 9559 lines, 378314 bytes, 4177 keywords
    AML Output: /Library/DSDT/DSDTFiles/./dsdt.aml - 42513 bytes, 864 named objects, 3313 executable opcodes

    Compilation complete. 0 Errors, 4 Warnings, 0 Remarks, 35 Optimizations
    Attached Files Attached Files
    Last edited by Ed_Saxman; July 18th, 2010 at 08:35 PM.

Page 50 of 59 FirstFirst ... 404849505152 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •