HOWTO Fix A Buggy DSDT File

[67GTA]

thank u!
but i need to ask u something..
did u try to fix those errors (mentioned in the lines) or u gave me a diferent .aml?
cause i see even the cpus are written by other method than the one patched by me
this results in CPU kernel panic (testing in leopard, forgot to mention)

anyway thanks again, i fixed the 6 errors with a lot help from this thread

I only fixed the errors reported by the iasl compiler.

[67GTA]

Suspend isnt working still. When I bring it back from suspend I hold in the power button for 3 seconds, then again for 2 seconds, and then again for another 2 seconds before the screen will turn on. This is what I had to do before though. I thought fixing the bug would fix the problem. Is there something else that you know of that would fix this? I am sure I noticed the fan running cooler.

Thanks, you are amazing.

That is a weird bug. I would probably file a bug report on that one. It might be something specific to your hardware. Most of the Nvidia MCP67 chipsets return to a black screen. I guess it is good that yours actually wakes up

[gnychis]

Here is the fixed dsdt.dsl Attachment 129500

Thanks bud! I really appreciate your help.

I have two bugs I am trying to figure out. One is that, after my computer re-wakes from sleeping (Thinkpad X300 w/ Intel GMA3100) the screen becomes stretched, cut in half, and distorted:



Do you know of anything incorrect in my DSDL that might cause this, or something that could fix it?

The second problem is that I have no brightness control over the screen.

I understand if you are not sure on these problems, but I figured I would at least ask!

Thanks!
George

[67GTA]

Thanks bud! I really appreciate your help.

I have two bugs I am trying to figure out. One is that, after my computer re-wakes from sleeping (Thinkpad X300 w/ Intel GMA3100) the screen becomes stretched, cut in half, and distorted:



Do you know of anything incorrect in my DSDL that might cause this, or something that could fix it?

The second problem is that I have no brightness control over the screen.

I understand if you are not sure on these problems, but I figured I would at least ask!

Thanks!
George

There isn't any way to fix these through the dsdt. I would file bug reports on these two bugs.

[mtnova]

HEllo,

I have the following warnings.Please help if you can.

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20090521 [Jun 30 2009]
Copyright (C) 2000 - 2009 Intel Corporation
Supports ACPI Specification Revision 3.0a

/home/doma/dsdt.dsl 5016: Acquire (MUTE, 0x03E8)
Warning 1104 - Possible operator timeout is ignored ^

/home/doma/dsdt.dsl 5030: Acquire (MUTE, 0x03E8)
Warning 1104 - Possible operator timeout is ignored ^

/home/doma/dsdt.dsl 5045: Acquire (MUTE, 0x03E8)
Warning 1104 - Possible operator timeout is ignored ^

/home/doma/dsdt.dsl 5060: Acquire (MUTE, 0x0FFF)
Warning 1104 - Possible operator timeout is ignored ^

/home/doma/dsdt.dsl 5074: Acquire (MUTE, 0x03E8)
Warning 1104 - Possible operator timeout is ignored ^

/home/doma/dsdt.dsl 5089: Acquire (MUTE, 0x03E8)
Warning 1104 - Possible operator timeout is ignored ^

/home/doma/dsdt.dsl 5104: Acquire (MUTE, 0x03E8)
Warning 1104 - Possible operator timeout is ignored ^

/home/doma/dsdt.dsl 5509: Method (VGET, 1, NotSerialized)
Warning 1087 - ^ Not all control paths return a value (VGET)

/home/doma/dsdt.dsl 5554: Method (TGET, 1, NotSerialized)
Warning 1087 - ^ Not all control paths return a value (TGET)

/home/doma/dsdt.dsl 5589: Method (FGET, 1, NotSerialized)
Warning 1087 - ^ Not all control paths return a value (FGET)

/home/doma/dsdt.dsl 5624: Store (VGET (Local0), Local1)
Warning 1092 - ^ Called method may not always return a value

/home/doma/dsdt.dsl 5666: Store (TGET (Local0), Local1)
Warning 1092 - ^ Called method may not always return a value

/home/doma/dsdt.dsl 5699: Store (FGET (Local0), Local1)
Warning 1092 - ^ Called method may not always return a value

ASL Input: /home/doma/dsdt.dsl - 5960 lines, 185348 bytes, 2496 keywords
AML Output: /home/doma/dsdt.aml - 19947 bytes, 632 named objects, 1864 executable opcodes

Compilation complete. 0 Errors, 13 Warnings, 0 Remarks, 552 Optimizations


And of course:

[67GTA]

mtnova:

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

dsdt.aml.zip

[nicholasblock]

67GTA,

Hey, you had worked on my dsdt a while ago but had lots of problems. I was wondering if you still have the on you compiled that only had the two errors? If you do I would really appreciate it if you could post it for me to look over. I am attaching a fresh one if you do not have it still.

Thanks,
Nic

[Magnesium]

Howdy 67GTA!

First of all, let me thank you for sticking with this thread for so long and helping so many people individually with their DSDT problems. Don't know if you really expected that to happen , but you did it anyway, and it's people like you that are the reason open-source can be successful...so thank you.

I'd also like to offer a suggestion for your how-to of the first post, if I may. I followed your steps, and actually found a DSDT for my laptop model on acpi.sourceforge.net. But somehow, there was a little difference between his laptop and mine (amount of RAM, I think), and it rendered my Kubuntu unbootable. I managed to get my system back, but I couldn't help but think of a better way: Just before we execute

sudo update-initramfs -u -k kernel-version

I would propose adding the command

sudo cp /boot/initrd.img-kernel-version ~/init.img-kernel-version

For example,

sudo cp /boot/initrd.img-2.6.28-15-generic ~/init.img-2.6.28-15-generic

This will back up their initial RAM image, since that's all that is modified by this procedure. Then, if something goes wrong, and their computer won't boot, they can just boot into a Live CD, and execute in a terminal

sudo cp ~/init.img-kernel-version /boot/initrd.img-kernel-version

and their computer will boot again. These commands essentially eliminate the risk encapsulated in your WARNING.

Now that I've "done my duty" by offering a suggestion...could you fix my DSDT? Actually, if you've got time, I would be very appreciative if you could look at the DSDT for both my laptop and my desktop. I believe I've attached all the relevant files in the tgz. I'm not noticing any problems with thermal sensors, etc., but both of these machines completely hang upon resuming from suspend...even Alt+SysRq+R,E,I,S,U,B doesn't do anything. I'm hoping that you can solve it!

Thanks again for everything.

Mg

[mtnova]

Hey 67GTA!

Great staff!!!!!!

I want to THANK YOU very much for helping me and people around the forum, and for your effort

Will try the file later one and update on the progress.

Thanks again!!!!

Cheers,
mtnova

[HolyShnikes]

That is a weird bug. I would probably file a bug report on that one. It might be something specific to your hardware. Most of the Nvidia MCP67 chipsets return to a black screen. I guess it is good that yours actually wakes up

Thanks for the help. I really appreciate it.