Page 20 of 59 FirstFirst ... 10181920212230 ... LastLast
Results 191 to 200 of 581

Thread: HOWTO Fix A Buggy DSDT File

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

    Re: HOWTO Fix A Buggy DSDT File

    litspliff:

    The _WAK error is well documented. The method is missing a return value when the kernel tries to wake from sleep. We have to finish the method with the standard return value from the ACPI specs manual. Follow the line numbers and be sure to keep the indentation where it is originally at.

    Code:
    183 Release (\_SB.PCI0.PSMX)
    184         }
    185    Return(Package(0x02){0x00, 0x00})
    186   }
    Save and rerun iasl -tc. You should have 0 Errors, 4 Warnings, 0 Remarks, 958 Optimizations. Now we need to fix the _HOT and _CRT methods. They affect your fans and cpu heat settings. The problem is the way it is written tells the kernel that the temps can't be read. That is false. The kernel can see the temps just fine. We have to comment // out the lines that are misleading the temp readings so they are ignored. Make yours look like this and rerun iasl -tc again.

    Code:
    7178                Method (_HOT, 0, Serialized)
    7179                {
    7180//                    If (LEqual (OSYS, 0x07D6))
    7181//                    {
    7182                        Return (Add (0x0AAC, Multiply (TPC, 0x0A)))
    7183//                    }
    7184                }
    7185
    7186                Method (_CRT, 0, Serialized)
    7187                {
    7188//                    If (LLess (OSYS, 0x07D6))
    7189//                    {
    7190                        Return (Add (0x0AAC, Multiply (TPC, 0x0A)))
    7191//                    }
    7192                }
    Now you should have 0 Errors, 0 Warnings, 0 Remarks, 958 Optimizations. Follow the rest of the how to with the dsdt.aml file you produced. You will want to add the acpi_osi="Linux" definition to boot/grub/menu.lst on your machine. After you get it done and reboot, send me a copy of
    Code:
    sudo dmesg
    from a terminal so I can double check for ACPI errors. You should now be able to resume from sleep without hanging, and the machine should run quieter/cooler since your temp/fan relationship will be correct instead of guessed at. You can save a copy of
    Code:
    sudo dmesg
    before this and after to see the differences. Open a terminal, click "Edit" and then "Profile Preferences". Then click the Scrolling tab and change 512 to 3000. The terminal will run out of memory before it spits out all of the data if you don't do this and cut part of it off. I have an error free copy with me if you run in to trouble

  2. #192
    Join Date
    Jun 2007
    Location
    SO ILL
    Beans
    112
    Distro
    Ubuntu Development Release

    Re: HOWTO Fix A Buggy DSDT File

    Quote Originally Posted by 67GTA View Post
    Most people don't dig this deep(LOL) You actually have two warnings. The first two are related. Fix the first and the second fixes it's self.
    Too true. When I saw it hadn't found "errors", I considered forgetting about it, but none of it makes sense to me. We are having a strange issue with the system reporting as being on AC power when it is in fact on battery. As well as not being able to provide discharge times and obviously incorrect recharge times. This just seemed like a tangent worth exploring. I thank you for your time and input.
    Socialism is a philosophy of failure, the creed of ignorance, and the gospel of envy, its inherent virtue is the equal sharing of misery - Winston Churchill

  3. #193
    Join Date
    Jul 2009
    Location
    nebraska
    Beans
    81
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: HOWTO Fix A Buggy DSDT File

    doesn't seem right.....

    Code:
    [    0.004339] ACPI: Checking initramfs for custom DSDT
    [    0.308057] Setting APIC routing to flat
    [    0.308611] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    [    0.348678] CPU0: AMD Athlon(tm) 64 X2 Dual-Core Processor TK-57 stepping 02
    [    0.352001] Booting processor 1 APIC 0x1 ip 0x6000
    [    0.004000] Initializing CPU#1
    [    0.004000] Calibrating delay using timer specific routine.. 3800.36 BogoMIPS (lpj=7600739)
    [    0.004000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    [    0.004000] CPU: L2 Cache: 256K (64 bytes/line)
    [    0.004000] CPU: Physical Processor ID: 0
    [    0.004000] CPU: Processor Core ID: 1
    [    0.004000] System has AMD C1E enabled
    [    0.004000] Switch to broadcast mode on CPU1
    [    0.436204] CPU1: AMD Athlon(tm) 64 X2 Dual-Core Processor TK-57 stepping 02
    [    0.436217] Brought up 2 CPUs
    [    0.436219] Total of 2 processors activated (7600.31 BogoMIPS).


    Places to check before and after are: dmesg output and /proc/acpi. I would especially check /proc/acpi/fan and /proc/acpi/thermal_zone to see if they are populated after this tutorial if they weren't before. Another trick I've learned during this process is to specify the operating system at boot. More about this is explained in the links I provided. I found that by adding
    ....not populated....

  4. #194
    Join Date
    May 2005
    Beans
    101
    Distro
    Kubuntu 11.10 Oneiric Ocelot

    Re: HOWTO Fix A Buggy DSDT File

    67GTA, thank you ten thousand times. Your HOWTO completely solved my problem, and also quite a few problems I didn't even know my laptop had. You sir are the epitome of the open source movement. It is people like you that make our community so great.

    I'm attaching my fixed working dsdt in case anyone else has an hp dv9610 / dv9610us and doesn't want to make the changes I did. Nothing special; all the fixes were found in the HOWTO.

    Code:
    iasl -tc dsdt.dsl
    
    Intel ACPI Component Architecture
    ASL Optimizing Compiler version 20081204 [Jan 10 2009]
    Copyright (C) 2000 - 2008 Intel Corporation
    Supports ACPI Specification Revision 3.0a
    
    ASL Input:  dsdt.dsl - 7832 lines, 268231 bytes, 3863 keywords
    AML Output: dsdt.aml - 30658 bytes, 812 named objects, 3051 executable opcodes
    
    Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 1069 Optimizations
    Attached Files Attached Files

  5. #195
    Join Date
    Dec 2005
    Location
    Tucson, Arizona
    Beans
    Hidden!
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: HOWTO Fix A Buggy DSDT File

    Hi 67GTA,

    you fixed my laptops dsdt file, and i was wondering if you could do the same again for a different computer of mine =P

    i tried to fix as much as i could but the only thing i could get from google is the _T_0 renaming to T_0 thingy, the rest i really have no clue about. Can you at least summarize what you did? i am going to write this up on my blog so google indexes it and at least helps some poor soul out there try and fix their broken dsdt files.

    dsdt file: www.kramidnarg.com/stuff/asus_p5q_pro.dsl.tar.gz

    console output:

    Code:
    [mark@Patagonicus dsdt 2102]$ iasl -tc dsdt.dsl 
    
    Intel ACPI Component Architecture
    ASL Optimizing Compiler version 20090625 [Jun 27 2009]
    Copyright (C) 2000 - 2009 Intel Corporation
    Supports ACPI Specification Revision 3.0a
    
    dsdt.dsl  8602:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
    
    dsdt.dsl  8616:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
    
    dsdt.dsl  8631:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
    
    dsdt.dsl  8646:             Acquire (MUTE, 0x0FFF)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
    
    dsdt.dsl  8660:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
    
    dsdt.dsl  8675:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
    
    dsdt.dsl  8690:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
    
    dsdt.dsl  9650:         Method (VGET, 1, NotSerialized)
    Warning  1087 -                    ^ Not all control paths return a value (VGET)
    
    dsdt.dsl  9695:         Method (TGET, 1, NotSerialized)
    Warning  1087 -                    ^ Not all control paths return a value (TGET)
    
    dsdt.dsl  9748:         Method (FGET, 1, NotSerialized)
    Warning  1087 -                    ^ Not all control paths return a value (FGET)
    
    dsdt.dsl  9779:             Store (VGET (Local0), Local1)
    Warning  1092 -                       ^ Called method may not always return a value
    
    dsdt.dsl  9821:             Store (TGET (Local0), Local1)
    Warning  1092 -                       ^ Called method may not always return a value
    
    dsdt.dsl  9854:             Store (FGET (Local0), Local1)
    Warning  1092 -                       ^ Called method may not always return a value
    
    dsdt.dsl 10171:                                         ShiftRight (BUF2, 0x04)
    Warning  1105 -             Result is not used, operator has no effect ^ 
    
    ASL Input:  dsdt.dsl - 10343 lines, 334155 bytes, 4854 keywords
    AML Output: dsdt.aml - 38692 bytes, 1002 named objects, 3852 executable opcodes
    
    Compilation complete. 0 Errors, 14 Warnings, 0 Remarks, 70 Optimizations
    [mark@Patagonicus dsdt 2102]$
    also, is there a website besides that crappy old sourceforge page where people post their fixed DSDT files? if not, someone should create one....
    Last edited by Polygon; July 31st, 2009 at 07:45 AM.
    Jabber: markgrandi[at]gmail.com

  6. #196
    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 Scotty Bones View Post
    Too true. When I saw it hadn't found "errors", I considered forgetting about it, but none of it makes sense to me. We are having a strange issue with the system reporting as being on AC power when it is in fact on battery. As well as not being able to provide discharge times and obviously incorrect recharge times. This just seemed like a tangent worth exploring. I thank you for your time and input.
    I'll take a look at your DSDT again to see if there is anything I can tweak in the battery section.

  7. #197
    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 litspliff View Post
    doesn't seem right.....

    Code:
    [    0.004339] ACPI: Checking initramfs for custom DSDT
    [    0.308057] Setting APIC routing to flat
    [    0.308611] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    [    0.348678] CPU0: AMD Athlon(tm) 64 X2 Dual-Core Processor TK-57 stepping 02
    [    0.352001] Booting processor 1 APIC 0x1 ip 0x6000
    [    0.004000] Initializing CPU#1
    [    0.004000] Calibrating delay using timer specific routine.. 3800.36 BogoMIPS (lpj=7600739)
    [    0.004000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    [    0.004000] CPU: L2 Cache: 256K (64 bytes/line)
    [    0.004000] CPU: Physical Processor ID: 0
    [    0.004000] CPU: Processor Core ID: 1
    [    0.004000] System has AMD C1E enabled
    [    0.004000] Switch to broadcast mode on CPU1
    [    0.436204] CPU1: AMD Athlon(tm) 64 X2 Dual-Core Processor TK-57 stepping 02
    [    0.436217] Brought up 2 CPUs
    [    0.436219] Total of 2 processors activated (7600.31 BogoMIPS).

    ....not populated....
    Check to make sure you have DSDT.aml (case is sensitive) in /etc/initramfs-tools. Make sure you ran the update-initramfs command with your kernel version. If you are running a development kernel version such as in 9.10, the custom patches won't be compiled until it is considered stable. You have to be running a stable kernel release for the DSDT patch to work.

  8. #198
    Join Date
    Jul 2009
    Location
    nebraska
    Beans
    81
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: HOWTO Fix A Buggy DSDT File

    yes....stable kernel
    administrator@904:~$ uname -r
    2.6.28-14-generic
    administrator@904:~$ ls /etc/initramfs-tools/DSDT.aml
    /etc/initramfs-tools/DSDT.aml
    administrator@904:~$


    tried again....here's what i got this time....almost 2000 lines of it.

    Code:
     enumerate USB device on port 2
    [ 5832.200054] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5832.584071] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5832.968091] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5833.352064] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5833.736057] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5834.120053] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5834.504054] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5834.888055] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5835.301154] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5835.685289] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5836.069130] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5836.452058] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5836.836058] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5837.220055] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5837.604067] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5837.988081] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5838.372066] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5838.756063] hub 4-0:1.0: unable to enumerate USB device on port 2
    no coincidence that when i shut down....it repeats this over and over and over and over.....

  9. #199
    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 Polygon View Post
    Hi 67GTA,

    you fixed my laptops dsdt file, and i was wondering if you could do the same again for a different computer of mine =P

    i tried to fix as much as i could but the only thing i could get from google is the _T_0 renaming to T_0 thingy, the rest i really have no clue about. Can you at least summarize what you did? i am going to write this up on my blog so google indexes it and at least helps some poor soul out there try and fix their broken dsdt files.

    dsdt file: www.kramidnarg.com/stuff/asus_p5q_pro.dsl.tar.gz

    console output:

    Code:
    [mark@Patagonicus dsdt 2102]$ iasl -tc dsdt.dsl 
    
    Intel ACPI Component Architecture
    ASL Optimizing Compiler version 20090625 [Jun 27 2009]
    Copyright (C) 2000 - 2009 Intel Corporation
    Supports ACPI Specification Revision 3.0a
    
    dsdt.dsl  8602:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
    
    dsdt.dsl  8616:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
    
    dsdt.dsl  8631:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
    
    dsdt.dsl  8646:             Acquire (MUTE, 0x0FFF)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
    
    dsdt.dsl  8660:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
    
    dsdt.dsl  8675:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
    
    dsdt.dsl  8690:             Acquire (MUTE, 0x03E8)
    Warning  1104 -                                 ^ Possible operator timeout is ignored
    
    dsdt.dsl  9650:         Method (VGET, 1, NotSerialized)
    Warning  1087 -                    ^ Not all control paths return a value (VGET)
    
    dsdt.dsl  9695:         Method (TGET, 1, NotSerialized)
    Warning  1087 -                    ^ Not all control paths return a value (TGET)
    
    dsdt.dsl  9748:         Method (FGET, 1, NotSerialized)
    Warning  1087 -                    ^ Not all control paths return a value (FGET)
    
    dsdt.dsl  9779:             Store (VGET (Local0), Local1)
    Warning  1092 -                       ^ Called method may not always return a value
    
    dsdt.dsl  9821:             Store (TGET (Local0), Local1)
    Warning  1092 -                       ^ Called method may not always return a value
    
    dsdt.dsl  9854:             Store (FGET (Local0), Local1)
    Warning  1092 -                       ^ Called method may not always return a value
    
    dsdt.dsl 10171:                                         ShiftRight (BUF2, 0x04)
    Warning  1105 -             Result is not used, operator has no effect ^ 
    
    ASL Input:  dsdt.dsl - 10343 lines, 334155 bytes, 4854 keywords
    AML Output: dsdt.aml - 38692 bytes, 1002 named objects, 3852 executable opcodes
    
    Compilation complete. 0 Errors, 14 Warnings, 0 Remarks, 70 Optimizations
    [mark@Patagonicus dsdt 2102]$
    also, is there a website besides that crappy old sourceforge page where people post their fixed DSDT files? if not, someone should create one....
    I will take a look and try to send you something to explain what I did. The old sourceforge page is really outdated. No one uploads to it anymore. Unfortunately, this thread and here https://bugs.launchpad.net/ubuntu/+s...ux/+bug/272247 are the only places I know of that has fixed DSDT's posted. I've urged everyone to post there PC make/model along with them. If I knew how to edit the wiki, I would start listing the fixed ones on a wiki page. I would love to get this info out to more people. A lot of newer PC's are having ACPI troubles with Linux because the DSDT's are being compiled with Microsoft's homebrewed AML compiler (MSFT) instead of the industry standard IASL. New users think Linux is crap when MS is breaking stuff. I personally think this deserves another antitrust lawsiut Microsoft is now basically controlling what you put on your computer.

  10. #200
    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 litspliff View Post
    yes....stable kernel




    tried again....here's what i got this time....almost 2000 lines of it.

    Code:
     enumerate USB device on port 2
    [ 5832.200054] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5832.584071] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5832.968091] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5833.352064] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5833.736057] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5834.120053] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5834.504054] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5834.888055] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5835.301154] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5835.685289] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5836.069130] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5836.452058] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5836.836058] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5837.220055] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5837.604067] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5837.988081] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5838.372066] hub 4-0:1.0: unable to enumerate USB device on port 2
    [ 5838.756063] hub 4-0:1.0: unable to enumerate USB device on port 2
    no coincidence that when i shut down....it repeats this over and over and over and over.....
    Zip up the output of
    Code:
    sudo dmesg
    and attach it here.

Page 20 of 59 FirstFirst ... 10181920212230 ... 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
  •