i'm afraid of rebooting at this point.....Code:administrator@904:~$ dmesg > ./Desktop/dmesg
administrator@904:~$ zip ./Desktop/dmesg.zip ./Desktop/dmesg
adding: Desktop/dmesg (deflated 92%)
Printable View
i'm afraid of rebooting at this point.....Code:administrator@904:~$ dmesg > ./Desktop/dmesg
administrator@904:~$ zip ./Desktop/dmesg.zip ./Desktop/dmesg
adding: Desktop/dmesg (deflated 92%)
Don't freak out:D You can delete the custom DSDT and update the initramfs to revert it back to before we started.
Code:sudo rm /etc/initramfs-tools/DSDT.aml
Just to be sure you didn't mess up somewhere in the DSDT file, try the one I fixed. This file is read by the kernel at boot to know how to interact with your hardware. One tiny error, and it will choke on something.Code:sudo update-initramfs -u -k 2.6.28-14-generic
Attachment 123085
i've got my past 3 kernels in my /boot/grub/menu.lst, so i'm not that worried.
rebooting.....now
holy f'n sht
amazing!
i can boot on battery power now!!
also boots quicker!!!
uses the fan at more appropriate times!!
also, no longer do i get the USB enumeration message over and over and over and over ......you get the point...
my next inquiry.....is canonical on top of this problem in the development process, or does this duty get passed on to you for yet another version of "stable" ubuntu releases?
The Ubuntu devs and Linux devs in general are not able to fix this. For decades the major PC and BIOS companies used the IASL AML compiler to generate DSDT files. It is jointly developed by Intel, HP, Toshiba, Phoenix, and... Microsoft. It was an industry standard, and worked with every operating system. It also conformed to the ACPI standards for all OS's. The IASL is what I'm using to fix the buggy DSDT's. The reason this has become a big problem in the last 2-3 years is that Microsoft has decided to create their own AML compiler (MSFT) that breaks the ACPI standards and breaks ACPI compatability for evry OS except for Windows. Sometimes it is the BIOS manufacturer that uses it, and sometimes hardware manufacturers like Nvidia use it to recompile the DSDT when their chipset is put in the PC. I don't know if any of these people are aware of the problem it causes. The only way to fix this once it is done, is to manually fix the screwed up DSDT and tell the OS to use the custom one. It is sad to say, but like I've told countless others, even when you purchase a PC.....Microsoft still owns it. My HP dv6815nr came with Vista preinstalled. It worked perfectly. Ubuntu had over heating problems because of the _HOT and _CRT errors. At first I thought what most people did and blamed Ubuntu, but was determined to find out why and fix it. That's when I came across this info. After fixing my DSDT for Linux, I used the MSFT compiler in Vista and it said there were zero errors in the DSDT. Then I ran across this: http://digg.com/linux_unix/Newly_leaked_Antitrust_Memo_Bill_Gates_on_Making_A CPI_Not_Work_with_Linux
Click on the link to download the PDF email.
"The only thing necessary for the triumph of evil is for good men to do nothing." Edmund Burke
so what became of mr. comes?
http://iowa.gotthefacts.org/
http://www.iowamicrosoftcase.com/
i'll be reading this all day.....found it on BING!
I'm not sure about Mr. Comes. For Microsoft lawsuits look here: http://www.groklaw.net/articlebasic....41228040645419
polygon:
Attachment 123222
scottybones:
What is in /proc/acpi/battery?
scottybones:
I made a small tweak to the battery section. Try this DSDT and keep your fingers crossed. Runand post a copy.Code:sudo dmseg > dmesg
Attachment 123257