Page 38 of 59 FirstFirst ... 28363738394048 ... LastLast
Results 371 to 380 of 581

Thread: HOWTO Fix A Buggy DSDT File

  1. #371
    Join Date
    Nov 2009
    Location
    Costa Rica
    Beans
    3
    Distro
    Kubuntu 9.10 Karmic Koala

    Re: HOWTO Fix A Buggy DSDT File

    Hi 67GTA!

    I read in that you can do magic with DSDT.
    I need your help. I have these four errors and don´t know how to fix them:


    /home/cali/DSDT.dsl 9164: Alias (^AGP.VGA.UDCS, UDSC)
    Error 4064 - Object not found or not accessible from scope ^ (UDSC)

    /home/cali/DSDT.dsl 9165: Alias (^AGP.VGA.LCD, PLCD)
    Error 4064 - ^ Object not found or not accessible from scope (PLCD)

    /home/cali/DSDT.dsl 9166: Alias (^PB2.VGA.UDCS, UDS1)
    Error 4064 - Object not found or not accessible from scope ^ (UDS1)

    /home/cali/DSDT.dsl 9167: Alias (^PB2.VGA.LCD, PLC1)
    Error 4064 - ^ Object not found or not accessible from scope (PLC1)



    My laptop is a Toshiba L505D-S5992.
    Here is my dsdt.dsl file:



    Attached Files Attached Files

  2. #372
    Join Date
    Jan 2007
    Location
    Kentucky, USA
    Beans
    1,684
    Distro
    Ubuntu Development Release

    Re: HOWTO Fix A Buggy DSDT File

    Calimancer:

    Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 23 Optimizations

    dsdt.aml.tar.gz

  3. #373
    Join Date
    Nov 2009
    Location
    Costa Rica
    Beans
    3
    Distro
    Kubuntu 9.10 Karmic Koala

    Re: HOWTO Fix A Buggy DSDT File

    Thanks 67GTA!!!
    Now, I'm going to try it.
    Why Toshiba has this kind of problems if they are one of the precursors of ACPI?

  4. #374
    Join Date
    Jan 2007
    Location
    Kentucky, USA
    Beans
    1,684
    Distro
    Ubuntu Development Release

    Re: HOWTO Fix A Buggy DSDT File

    Quote Originally Posted by calimancer View Post
    Thanks 67GTA!!!
    Now, I'm going to try it.
    Why Toshiba has this kind of problems if they are one of the precursors of ACPI?
    Most of the time, the hardware vendors use the Microsoft compiler to recompile the DSDT against their hardware. The PC manufacturers as a whole usually are not aware of the difference between MSFT and IASL, just developers and programmers.

  5. #375
    Join Date
    Mar 2007
    Beans
    24
    Distro
    Kubuntu 9.10 Karmic Koala

    Re: HOWTO Fix A Buggy DSDT File

    I just tried fixing this under an updated 9.10 installation before I saw the warning on the OP... Is there no longer a way to fix it by myself?

    BTW, where should I file a bug report?

  6. #376
    Join Date
    Jan 2007
    Location
    Kentucky, USA
    Beans
    1,684
    Distro
    Ubuntu Development Release

    Re: HOWTO Fix A Buggy DSDT File

    The only way is to compile your own kernel with the DSDT patch included. I wouldn't recommend this method. You need to register and file a bug on launchpad.

  7. #377
    Join Date
    Nov 2009
    Beans
    1

    Re: HOWTO Fix A Buggy DSDT File

    Hello Friends,

    can anyone fix my dsdt. I'm newbie and my english is bad.

    Code:
    Intel ACPI Component Architecture
    ASL Optimizing Compiler version 20090521 [Jun 30 2009]
    Copyright (C) 2000 - 2009 Intel Corporation           
    Supports ACPI Specification Revision 3.0a             
     
    dsdt.dsl  5696:                             If (LOr (MP0P (Local6), MP1P (Local6)))
    Warning  1092 -                                         ^ Called method may not always return a value
     
    dsdt.dsl  5696:                             If (LOr (MP0P (Local6), MP1P (Local6)))
    Warning  1092 -                                         ^ Called method may not always return a value
     
    dsdt.dsl  5698:                                 Multiply (MCRS (Local6), 0x08000000, BF0F)
    Warning  1092 -  Called method may not always return a value ^                            
     
    dsdt.dsl  5700:                                 If (MPCR (Local6))
    Warning  1092 -                                        ^ Called method may not always return a value
     
    dsdt.dsl  5702:                                     If (MP0P (Local6))
    Warning  1092 -                                            ^ Called method may not always return a value
     
    dsdt.dsl  5704:                                         If (MP1P (Local6))
    Warning  1092 -    Called method may not always return a value ^          
     
    dsdt.dsl  5715:                                 If (MP0P (Local6))
    Warning  1092 -                                        ^ Called method may not always return a value
     
    dsdt.dsl  5717:                                     Store (MP0N (Local6), Local5)
    Warning  1092 -   Called method may not always return a value ^                  
     
    dsdt.dsl  5721:                                     If (MP1P (Local6))
    Warning  1092 -                                            ^ Called method may not always return a value
     
    dsdt.dsl  5723:                                         Store (MP1N (Local6), Local5)
    Warning  1092 -       Called method may not always return a value ^                  
     
    dsdt.dsl  5727:                                 If (LGreater (BNKN, MCDB (Local5)))
    Warning  1092 -      Called method may not always return a value ^                 
     
    dsdt.dsl  5729:                                     Store (MCDB (Local5), BNKN)
    Warning  1092 -   Called method may not always return a value ^                
     
    dsdt.dsl  5732:                                 If (LLess (BNKX, MCDB (Local5)))
    Warning  1092 -   Called method may not always return a value ^                 
     
    dsdt.dsl  5734:                                     Store (MCDB (Local5), BNKX)
    Warning  1092 -   Called method may not always return a value ^                
     
    dsdt.dsl  5737:                                 If (LGreater (COLN, MCDC (Local5)))
    Warning  1092 -      Called method may not always return a value ^                 
     
    dsdt.dsl  5739:                                     Store (MCDC (Local5), COLN)
    Warning  1092 -   Called method may not always return a value ^                
     
    dsdt.dsl  5742:                                 If (LLess (COLX, MCDC (Local5)))
    Warning  1092 -   Called method may not always return a value ^                 
     
    dsdt.dsl  5744:                                     Store (MCDC (Local5), COLX)
    Warning  1092 -   Called method may not always return a value ^                
     
    dsdt.dsl  5785:             Method (MP0P, 1, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (MP0P)
     
    dsdt.dsl  5813:             Method (MP1P, 1, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (MP1P)
     
    dsdt.dsl  5841:             Method (MPCR, 1, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (MPCR)
     
    dsdt.dsl  5869:             Method (MP0N, 1, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (MP0N)
     
    dsdt.dsl  5897:             Method (MP1N, 1, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (MP1N)
     
    dsdt.dsl  5925:             Method (MCRB, 1, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (MCRB)
     
    dsdt.dsl  5953:             Method (MCRS, 1, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (MCRS)
     
    dsdt.dsl  5981:             Method (MCDB, 1, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (MCDB)
     
    dsdt.dsl  6004:             Method (MCDC, 1, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (MCDC)
     
    dsdt.dsl  6353:             Method (_DSM, 4, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (_DSM)
     
    dsdt.dsl  6353:             Method (_DSM, 4, NotSerialized)
    Warning  1080 -                        ^ Reserved method must return a value (_DSM)
     
    dsdt.dsl  6532:             Method (GAPR, 0, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (GAPR)
     
    dsdt.dsl  6552:                     Store (ROPO (Local0), Local1)
    Warning  1092 -                               ^ Called method may not always return a value
     
    dsdt.dsl  6577:             Method (ROPO, 1, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (ROPO)
     
    dsdt.dsl  6917:             Method (_DSM, 4, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (_DSM)
     
    dsdt.dsl  6917:             Method (_DSM, 4, NotSerialized)
    Warning  1080 -                        ^ Reserved method must return a value (_DSM)
     
    dsdt.dsl  7365:             Method (WMNV, 3, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (WMNV)
     
    dsdt.dsl  7593:                                 Return (^^IXVE.IGPU._DSM (MUID, REVI, SFNC, ARGD))
    Warning  1092 -            Called method may not always return a value ^
     
    dsdt.dsl  7598:                                 Return (^^XVR0.VGA._DSM (MUID, REVI, SFNC, ARGD))
    Warning  1092 -           Called method may not always return a value ^
     
    dsdt.dsl  7605:                                 Return (^^IXVE.IGPU._DSM (MUID, REVI, SFNC, ARGD))
    Warning  1092 -            Called method may not always return a value ^
     
    dsdt.dsl  7610:                                 Return (^^XVR0.VGA._DSM (MUID, REVI, SFNC, ARGD))
    Warning  1092 -           Called method may not always return a value ^
     
    dsdt.dsl  8002:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
     
    dsdt.dsl  8016:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
     
    dsdt.dsl  8031:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
     
    dsdt.dsl  8046:             Acquire (MUTE, 0x0FFF)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
     
    dsdt.dsl  8060:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
     
    dsdt.dsl  8075:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
     
    dsdt.dsl  8090:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
     
    dsdt.dsl 11324:             Method (GMLE, 1, Serialized)
    Warning  1087 -                        ^ Not all control paths return a value (GMLE)
     
    dsdt.dsl 11337:             Method (SMLE, 1, Serialized)
    Warning  1087 -                        ^ Not all control paths return a value (SMLE)
     
    dsdt.dsl 11357:             Method (WLLC, 1, NotSerialized)
    Warning  1087 -                        ^ Not all control paths return a value (WLLC)
     
    ASL Input:  dsdt.dsl - 15439 lines, 454389 bytes, 7331 keywords
    AML Output: dsdt.aml - 58399 bytes, 1839 named objects, 5492 executable opcodes
     
    Compilation complete. 0 Errors, 49 Warnings, 0 Remarks, 63 Optimizations
    My Laptop is a Asus k70I0
    Attached Files Attached Files
    Last edited by kruemelchen26; November 12th, 2009 at 09:53 AM.

  8. #378
    Join Date
    Nov 2009
    Beans
    3

    Re: HOWTO Fix A Buggy DSDT File

    hi ;D

    obviously, i also have a problem with dsdt... so, here partial dmesg:

    [ 18.962087] ACPI Error (psargs-0359): [^CKDY] Namespace lookup failure, AE_NOT_FOUND
    [ 18.962100] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.BASM] (Node ffff880037a653b0), AE_NOT_FOUND
    [ 18.962175] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.CIMP] (Node ffff880037a65590), AE_NOT_FOUND
    [ 18.962252] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IXVE.IGPU.NVIF] (Node ffff880037a65c70), AE_NOT_FOUND



    hardware is:

    fujitsu-siemens v6555, core2duo t5870, chipset nvidia mcp79 - buyed without os (;D)

    i suppose this dsdt is not working correctly, because fans not work at all; here the output by sensors (by thermal and coretemp modules):

    acpitz-virtual-0
    Adapter: Virtual device
    temp1: +72.8 C (crit = +199.8 C)

    coretemp-isa-0000
    Adapter: ISA adapter
    Core 0: +73.0 C (high = +100.0 C, crit = +100.0 C)

    coretemp-isa-0001
    Adapter: ISA adapter
    Core 1: +73.0 C (high = +100.0 C, crit = +100.0 C)



    finally, i tried to fix dsdt, but i'm not so able ;D - here first output:


    iasl -d dsdt.dat

    [...]
    Loading Acpi table from file dsdt.dat
    Acpi table [DSDT] successfully installed and loaded
    Pass 1 parse of [DSDT]
    Pass 2 parse of [DSDT]
    Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
    .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. ....................................
    Parsing completed

    Found 3 external control methods, reparsing with new information
    Pass 1 parse of [DSDT]
    Pass 2 parse of [DSDT]
    Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
    .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. .................................................. ....................................
    Parsing completed
    Disassembly completed, written to "dsdt.dsl"



    and again:

    iasl -tc dsdt.dsl

    [...]
    dsdt.dsl 1: ACPI // Address Base
    Error 4095 - ^ syntax error, unexpected PARSEOP_NAMESEG, expecting PARSEOP_DEFINITIONBLOCK

    ASL Input: dsdt.dsl - 7495 lines, 251808 bytes, 0 keywords
    Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 0 Optimizations



    i tried to search for some fix about "4095 error" and i found that is first row to delete:
    first row in dsdt.dsl is
    "ACPI Error: ACPI path has too many parent prefixes (^) - reached beyond root node 20090521 nsaccess-526"

    and finally, if i delete this row and try to recompile with -tc, i have 201 errors ;D


    ok, i have to stop ;D



    in attach, there are dsdt.dat (same /proc/acpi/dsdt), dsdt.dsl and dsdt.hex


    ah! searching for "linux + fujitsu amilo v6555" in google... obtain 0 (ZERO) results ;D
    too, too young :/


    pardon for my english, but i'm italian

    p.s.: i'm using debian (testing) - i think it's not so different fro *ubuntu, but in doubt i preferred to specify

    thanks in advance,
    Max
    Attached Files Attached Files
    Last edited by k0smik0; November 12th, 2009 at 05:31 PM. Reason: i forgot attachment

  9. #379
    Join Date
    Nov 2009
    Beans
    3

    Re: HOWTO Fix A Buggy DSDT File

    hi ;D

    another box

    this time is for Lenovo 3000 N200 (celeron64, 82801H / ICH8 chipset, vga GM965)

    here the output of iasl -tc

    http://pastebin.com/f7083a7a4

    dsdt files in attach

    tnx ;D,
    Max
    Attached Files Attached Files

  10. #380
    Join Date
    Nov 2009
    Beans
    1

    Re: HOWTO Fix A Buggy DSDT File

    67GTA and other community members,

    I have been finding great difficulty in trying to locate any information on the following error/warning messages when I compile dsdt.dsl to dsdt.aml using iasl version 20090903:

    Code:
    bash-3.2# ./iasl -ta dsdt.dsl
    
    Intel ACPI Component Architecture
    ASL Optimizing Compiler version 20090903 [Sep  3 2009]
    Copyright (C) 2000 - 2009 Intel Corporation
    Supports ACPI Specification Revision 4.0
    
    dsdt.dsl  9624:         Method (VGET, 1, NotSerialized)
    Warning  1087 -                    ^ Not all control paths return a value (VGET)
    
    dsdt.dsl  9669:         Method (TGET, 1, NotSerialized)
    Warning  1087 -                    ^ Not all control paths return a value (TGET)
    
    dsdt.dsl  9722:         Method (FGET, 1, NotSerialized)
    Warning  1087 -                    ^ Not all control paths return a value (FGET)
    
    dsdt.dsl  9753:             Store (VGET (Local0), Local1)
    Warning  1092 -                       ^ Called method may not always return a value
    
    dsdt.dsl  9795:             Store (TGET (Local0), Local1)
    Warning  1092 -                       ^ Called method may not always return a value
    
    dsdt.dsl  9828:             Store (FGET (Local0), Local1)
    Warning  1092 -                       ^ Called method may not always return a value
    
    dsdt.dsl 10145:                                         ShiftRight (BUF2, 0x04)
    Warning  1105 -             Result is not used, operator has no effect ^
    
    ASL Input:  dsdt.dsl - 10317 lines, 333408 bytes, 4839 keywords
    AML Output: dsdt.aml - 38570 bytes, 996 named objects, 3843 executable opcodes
    
    Compilation complete. 0 Errors, 7 Warnings, 0 Remarks, 69 Optimizations
    Perhaps my search terms aren't exacting enough when trying to find an explanation for any of the 7 warning messages listed above. I apologize if it has already been mentioned under this topic.

    In closing, I am kindly requesting anyone's assistance in trying to resolve or remove the error/warning messages listed above.

    I am not sure if it matters, but the attached dsdt.dsl is from an ASUS P5Q.

    Thank you very much for your time!


    Best regards,

    IanT


    PS. Is it best practice to extract dsdt from an original, unmodified, bios? The reason why I ask this, especially as a post-script message, is because I wonder if some of my problems are attributed to a modified bios, and hence dsdt might have been altered somehow...?
    Attached Files Attached Files

Page 38 of 59 FirstFirst ... 28363738394048 ... 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
  •