Ok, I had issues with my left speaker on my laptop. It was dead.
So if I were to order the exact replacement it would cost more than $100 for the entire front panel palm rest it was also out of warranty.
But it is not worth it because a speaker isn't worth that much for a replacement.
I had 2 approaches.
1)Remove the left speaker and replace the speaker (actually it is called a tweeter) with a Generic Internal Part.
This failure because the Generic Tweeters sold are not as high quality as the original and wasn't able to generate the exact frequency and amplitude of the original and undamaged right speaker.
2)Buy a off the shelf speaker set from ebay and replace the left speaker.
This approach worked.
I got a speaker set of another laptop model.
The speaker is an identical 4 ohm 2 watt speaker.
However I had to cut out the speaker connectors as they are split into 2 pin left, 2 pin right rather than the original 4 pin .
After some modification I was able to get the connectors right. Plugging them in works as well, producing the right sound.
However the right speaker was still slightly louder, I suspect the original speaker had an air column under which produced louder bass.
I am still satisfied with the final result as 1)it doesn't cost much 2)the new speakers were of comparable sound quality.
Quick Links
Friday, December 18, 2009
Saturday, December 5, 2009
Nvidia Driver Release
Nvidia WHQL Notebook Driver version 195.62 is released.
Please note that the new Nvidia Driver fixes the issue of not being able to throttle to default clock in Windows Desktop so please use this driver instead of the Acer Download (187.XX) which has the problem.
This driver is recommended.
This driver is recommended.
Acer Aspire 4530 Actual Fan Control
I found the actual control variable of Acer Aspire 4530 Fan.
It is actually a hex value located in the EC.
To access the EC Control Variables, Download and install Rw-Everything.
Next run the program.
Select EC Button to view the EC Variables
You should see the following as shown below:
If you set it to 13 then click done, you will quickly hear the fan spining at maximum speed.
Other values between 0-13 also alter the RPM but there are also values in between that does nothing.
Happy Experimentation!
It is actually a hex value located in the EC.
To access the EC Control Variables, Download and install Rw-Everything.
Next run the program.
Select EC Button to view the EC Variables
You should see the following as shown below:
If you set it to 13 then click done, you will quickly hear the fan spining at maximum speed.Other values between 0-13 also alter the RPM but there are also values in between that does nothing.
Happy Experimentation!
Monday, November 30, 2009
K10STAT AMD Griffin Processor UnderVolting Guide
___________________________________________________________________________
Revision to Guide
Why UnderVolt?
Because if a lower voltage can sustain your clockspeed undervolting preserve battery life and reduce heat generated without affecting your CPU performance at all!!
0 performance handicap with less heat issues and longer battery life!!
If it is so great why manufacturers don't undervolt?
Because they create processors in bulk you can't expect them to test & undervolt every single processor!
So they simply take the a slightly higher approximate stable voltage and burn the same value into every chip of the same family!
Will it spoil my processor?
No it won't. Because it doesn't involve making it hotter.
In non-biological system usually heat destroys and cold preserves.
During testing, BSOD is common but after a restart the Processor Voltage is restored to original value.
After finalising the stable voltages then you set the program to run every startup.
Why don't you use Windows Startup to run it?
Because Windows Defender will complain.
Which Processor is it for ?
AMD Griffin Series Processor, ZM,RM,QL and SI series
But I am a Intel Guy not a AMD Guy; Intel Ownz AMD !!
Then go here and don't come back.(Just Joking =P)
But I am using AMD TL Series and below Processors ?
Go join the Intel people in the previous link.
By the way you will find people having identical processor yet different undervolting margins.
There are processors of the same model working however some are actually chips on the brink of failure.
The reason I said this is that AMD did the testing without considering the thermal output as a criteria. If you are lucky you get a AMD Processor that undervolts properly and doesn't put up as much heat.
My opinion is AMD is struggling to overclock these K8 Chips beyond their potential to keep up with Intel. Good Chips yielding is low because they are pushing the redline or do not have good production facilities therefore they do shoddy testing work moreover their current debt situation isn't helping.
You don't see the same problems with the new K10 Architecture Caspian because the new design have greater clock potential.
If you are an owner of a lousy chip you can consider sueing AMD for this (I feel is reasonable).
AMD believes they are safe because consumers usually think their laptop overheat because of the faults of OEM (HP, Acer etc) not them carrying their IC chip.
By the way you will find people having identical processor yet different undervolting margins.
There are processors of the same model working however some are actually chips on the brink of failure.
The reason I said this is that AMD did the testing without considering the thermal output as a criteria. If you are lucky you get a AMD Processor that undervolts properly and doesn't put up as much heat.
My opinion is AMD is struggling to overclock these K8 Chips beyond their potential to keep up with Intel. Good Chips yielding is low because they are pushing the redline or do not have good production facilities therefore they do shoddy testing work moreover their current debt situation isn't helping.
You don't see the same problems with the new K10 Architecture Caspian because the new design have greater clock potential.
If you are an owner of a lousy chip you can consider sueing AMD for this (I feel is reasonable).
AMD believes they are safe because consumers usually think their laptop overheat because of the faults of OEM (HP, Acer etc) not them carrying their IC chip.
___________________________________________________________________
Configure K10STAT
When you run K10STAT you should see the menu above.
You can set a maximium of 5 Profiles.
FID: The multiplier for the Processor
(NOTE: FID doesn't work in AMD Mobile Processors)
DID: The P-State of the Processor.
ZM/RM has 3 P-State, P0,P1,P2 while QL/SI should only have 2 P-State.
CPU-Voltage that is what we are interested in.
To set the voltage for P0 simply Select P0 and select the corresponding voltage and apply.
Remember: Min 0.75 V Max 1.2 V!
For me I tested -0.05 is the Max Stable voltage for each default state any higher it BSOD!
Up%: This is the amount of CPU load before the processor changes P-State.
Currently it is set at 60% meaning it will switch from P2 to P1 when processor detect 60% load and the same applies from switching from P1 to P0.
Down%:It is basically the opposite of Up%.
Up(ms):It is the time the processor takes to switch from one P-State to the next higher P-State.(Try to set this to 100ms (lower better) so it will ramp up performance quickly when you need it, however setting this low will cause higher temperatures)
Down(ms):It is basically the opposite of Up(ms).(Try to set this to 100ms (lower better) so it will ramp down performance quickly when you don't need it, more power save; less heat produced.
However setting this low will cause higher temperatures)
However setting this low will cause higher temperatures)
After you have set suitable values (-0.05 recommended).
Use Vista Processor Power Management to test different levels.
To test simply click on the core of the P-State immediate the Processor will assume the P-State.
Test each P-State by running Intel Burn In or any suitable CPU loading tool.
You should have 4 Windows Open to control and test each p-state as shown above.
For me the voltage values that passed Intel Burn In test are 1.075V, 0.850V and 0.750V.
At 1.025V it BSOD after 2 mins.
At 1.0372V-1.050V it produced the wrong result.
To pass LinPack the result calculated by the CPU must be consistent.
After you have affirmed the stable voltage values then you may proceed to set it to start automatically.
After you have affirmed the stable voltage values then you may proceed to set it to start automatically.
Setting K10STAT for StartUp
Open >> Start Menu\All Programs\Accessories\System Tools\Task Scheduler
Create a Task
Alternatively you can make it run as a SYSTEM task (as shown below)
Click "Change User or Group" then Enter "System" then choose "Check Names" then select OK.
or you can create it as a startup process as shown below. (RECOMMENDED because it will run before a logon is required)
**Please note a file called K10stat.dat containing the undervolt settings will be created in the C:\Windows\System32 folder because it is the default path for admin rights unless you changed the "Start In (Optional)" parameters, the setting just under the "Add Arguments (Optional)" parameters.
The program will load the settings from K10STAT.dat so make sure all the changes are overwritten to the file. When you launch K10STAT manually a new K10STAT.dat will be created in C:\Program Files\K10STAT which Task Scheduler WILL NOT LOAD. It will only load the K10STAT.dat in C:\Windows\System32 unless you change the "Start In" parameters.
The following arguments are available (Source:http://dsus4.blog126.fc2.com/blog-entry-3.html)
Command Line Option
-lp:#(1-5) - load profile#(1-5) and write to MSR.
-nw - Start K10stat with NoWindow.
-ClkCtrl:#(0-4) - Enable Clock Control by K10stat.
0:No Control
1:Control clock of each core.
2:Control clock of all cores together (Criterion is most loaded core).
3:Control clock of all cores together (Criterion is average of all cores).
4:Control clock of all cores together (Criterion is least loaded core).
It is recommended that you set -ClkCtrl:2 for faster setting.
Because Windows proceed on the assumption that cores are unganged by default.
-StayOnTray - use this option with -nw for Clock Control Mode.(Note after a sleep if the CPU registers are resetted voltages will revert to default hence you need -StayOnTray to ensure it is always running in the background)
e.g.Target:
"C:\Program Files\K10stat\K10STAT.exe" -lp:1 -ClkCtrl:2 -StayOnTray -nw
-lp:#(1-5) - load profile#(1-5) and write to MSR.
-nw - Start K10stat with NoWindow.
-ClkCtrl:#(0-4) - Enable Clock Control by K10stat.
0:No Control
1:Control clock of each core.
2:Control clock of all cores together (Criterion is most loaded core).
3:Control clock of all cores together (Criterion is average of all cores).
4:Control clock of all cores together (Criterion is least loaded core).
It is recommended that you set -ClkCtrl:2 for faster setting.
Because Windows proceed on the assumption that cores are unganged by default.
-StayOnTray - use this option with -nw for Clock Control Mode.(Note after a sleep if the CPU registers are resetted voltages will revert to default hence you need -StayOnTray to ensure it is always running in the background)
e.g.Target:
"C:\Program Files\K10stat\K10STAT.exe" -lp:1 -ClkCtrl:2 -StayOnTray -nw
Finally you can Control your CPU using the K10STAT Systray if you enabled -StayOnTray manually as well.
-ClkCtrl:#(0-4) - Enable Clock Control by K10stat (Refer to above).
0:No Control
1:Control clock of each core.
UnGanged means each CPU Core #0 & #1 operates independently of each other so at any one time their frequency and DID could be different.(This is the original intent of the design of the Turion Chips as they are given different power planes.)
2:Control clock of all cores together (Criterion is most loaded core).
This means the CPU will raise/drop the DID of Core #0 & #1 together when it detects the one of higher Core has reached the criteria for a Frequency boost/Throttle Down.
3:Control clock of all cores together (Criterion is average of all cores).
This means the CPU will raise/drop the DID of Core #0 & #1 together when it detects the average of both core has reached the criteria for a Frequency boost/Throttle Down.
4:Control clock of all cores together (Criterion is least loaded core).
This means the CPU will raise/drop the DID of Core #0 & #1 together when it detects the one of lowest Core has reached the criteria for a Frequency boost/Throttle Down.
Note that when K10STAT is scheduled a file called k10stat.dat will be created in C:\Windows\System32.
0:No Control
1:Control clock of each core.
UnGanged means each CPU Core #0 & #1 operates independently of each other so at any one time their frequency and DID could be different.(This is the original intent of the design of the Turion Chips as they are given different power planes.)
2:Control clock of all cores together (Criterion is most loaded core).
This means the CPU will raise/drop the DID of Core #0 & #1 together when it detects the one of higher Core has reached the criteria for a Frequency boost/Throttle Down.
3:Control clock of all cores together (Criterion is average of all cores).
This means the CPU will raise/drop the DID of Core #0 & #1 together when it detects the average of both core has reached the criteria for a Frequency boost/Throttle Down.
4:Control clock of all cores together (Criterion is least loaded core).
This means the CPU will raise/drop the DID of Core #0 & #1 together when it detects the one of lowest Core has reached the criteria for a Frequency boost/Throttle Down.
Note that when K10STAT is scheduled a file called k10stat.dat will be created in C:\Windows\System32.
This is because the default path is C:\Windows\System32 in Administrator mode, if you want the k10stat.dat to be created in the K10STAT folder you have to enter "C:\Program Files\K10STAT" in the start in textbox when creating the task.
The file will contain voltage profile to be loaded when booted hence any changes in configuration must be made to that file by cutting and pasting the file to that folder, otherwise K10STAT will continue to use the old k10stat.dat located in C:\Windows\System32.
The file will contain voltage profile to be loaded when booted hence any changes in configuration must be made to that file by cutting and pasting the file to that folder, otherwise K10STAT will continue to use the old k10stat.dat located in C:\Windows\System32.
Further Testing
__________________________________________________________________
Original Factory Default Settings
__________________________________________________________________________
UnderVolted 1.075V
In Unganged Mode
__________________________________________________________________
UnderVolted 1.075V
In Ganged Mode (Based on highest core)
__________________________________________________________________
Thats All !
AMD Technical Documentation Regarding Turion Processors here
(Contains Temperature Limits P-States and Voltages)
Wednesday, November 25, 2009
BIOS Version 3334 to 3335 to 3336
First of all thanks to christian who kept me informed about the new BIOS for Aspire 4530.
Unfortunately there is no change log regarding the BIOS, therefore I decided to take an unorthodox approach.
First I decided to try out the BIOS Version 1.3336.
However it was dissappointing the stupid initial turn on restart issue in Version 1.3335 was brought forth.
Next I stressed tested the Laptop running Furmark and Intel Burn In Concurrently.
Strangely usually after sometime the temperature will climb and abruptly shutdown however this BIOS did not make that happen.
Instead the BIOS made the CPU throttle agressively reducing performance and temperature at the same time.
The WebCam Image quality is also decidedly better than 1.3334
Therefore I decided to do a hybrid approach since I don't know which module is responsible for the stupid power bricking issue.
I did an analysis of the 3 BIOS copy I have
1.3334, 1.3335 and 1.3336.
The changes are as follows
From 1.3334 to 1.3335 the following modules changed:
BIOSCOD00.ROM and HOLE0.ROM
Therefore one of them should be responsible for bricking the smooth powerup procedure in from 1.3334 to 1.3335
From 1.3334 to 1.3336 the following modules were changed:
BIOSCOD00.ROM, BIOSCOD03.ROM, BIOSCOD04.ROM, HOLE0.ROM & TEMPLAT.ROM.
Personally I am pretty sure TEMPLAT.ROM disable the options to select either 64MB or 256MB for the VGA BIOS but note you do not have any option in the first place the BIOS 1.3334 will ALWAYS default to 256MB regardless of what you choose.
So I decided to insert BIOSCOD03.ROM and BIOSCOD04.ROM and TEMPLAT.ROM. into BIOS Version 1.3334 to avoid the powerup issue (I think the programmer took the 1.3335 to make 1.3336 hence the mistake).
True enough the new 1.3334 BIOS with partial 1.3336 BIOS doesn't exhibit the powerup issue.
Anyway another thing to note is the 1.3336 doesn't have SLIC2.1 either most likely it is just an update with the EC Fan Controller with more agressive throttling.
Upon further testing I have isolated the issue to the module HOLE0.ROM.
Without the HOLE0.ROM the bootup was absolutely smooth.
I have compiled a BIOS contain all the previous changes I did to 1.3334 plus the updated BIOS modules from 1.3336 without the stupid issue of the HOLE0.ROM.
My advice to users because of the powerup shutdown restart issue this may not be the final BIOS when it is properly resolved I will then mod it to include SLIC 2.1. Until then keep a close lookout for Acer BIOS releases.
You can download the modded BIOS Version 1.3334 with 1.3336 BIOS
Unfortunately there is no change log regarding the BIOS, therefore I decided to take an unorthodox approach.
First I decided to try out the BIOS Version 1.3336.
However it was dissappointing the stupid initial turn on restart issue in Version 1.3335 was brought forth.
Next I stressed tested the Laptop running Furmark and Intel Burn In Concurrently.
Strangely usually after sometime the temperature will climb and abruptly shutdown however this BIOS did not make that happen.
Instead the BIOS made the CPU throttle agressively reducing performance and temperature at the same time.
The WebCam Image quality is also decidedly better than 1.3334
Therefore I decided to do a hybrid approach since I don't know which module is responsible for the stupid power bricking issue.
I did an analysis of the 3 BIOS copy I have
1.3334, 1.3335 and 1.3336.
The changes are as follows
From 1.3334 to 1.3335 the following modules changed:
BIOSCOD00.ROM and HOLE0.ROM
Therefore one of them should be responsible for bricking the smooth powerup procedure in from 1.3334 to 1.3335
From 1.3334 to 1.3336 the following modules were changed:
BIOSCOD00.ROM, BIOSCOD03.ROM, BIOSCOD04.ROM, HOLE0.ROM & TEMPLAT.ROM.
Personally I am pretty sure TEMPLAT.ROM disable the options to select either 64MB or 256MB for the VGA BIOS but note you do not have any option in the first place the BIOS 1.3334 will ALWAYS default to 256MB regardless of what you choose.
So I decided to insert BIOSCOD03.ROM and BIOSCOD04.ROM and TEMPLAT.ROM. into BIOS Version 1.3334 to avoid the powerup issue (I think the programmer took the 1.3335 to make 1.3336 hence the mistake).
True enough the new 1.3334 BIOS with partial 1.3336 BIOS doesn't exhibit the powerup issue.
Anyway another thing to note is the 1.3336 doesn't have SLIC2.1 either most likely it is just an update with the EC Fan Controller with more agressive throttling.
Upon further testing I have isolated the issue to the module HOLE0.ROM.
Without the HOLE0.ROM the bootup was absolutely smooth.
I have compiled a BIOS contain all the previous changes I did to 1.3334 plus the updated BIOS modules from 1.3336 without the stupid issue of the HOLE0.ROM.
My advice to users because of the powerup shutdown restart issue this may not be the final BIOS when it is properly resolved I will then mod it to include SLIC 2.1. Until then keep a close lookout for Acer BIOS releases.
You can download the modded BIOS Version 1.3334 with 1.3336 BIOS
Sunday, November 22, 2009
Wireless Suspend and Resume on Aspire 4530
The issue has been fixed with the latest Linux Kernel 2.6.31-16 updates, I will still leave the post open in case someone needs sleep, resume custom scripts.
As noted after suspend resume the wireless doesn't work due to a bug that broke suspend and resume in ath9k drivers.
However I found a workaround.
Create a script with the following inside
Then put the script into /etc/pm/sleep.d folder.
Make it executable by running
sudo chmod +x /etc/pm/sleep.d/ath9kreset
After that wireless should work after each suspend.
As noted after suspend resume the wireless doesn't work due to a bug that broke suspend and resume in ath9k drivers.
However I found a workaround.
Create a script with the following inside
!# /bin/shCall it ath9kreset for easy recalling of its purpose.
sudo modprobe -r ath9k
sudo modprobe ath9k
Then put the script into /etc/pm/sleep.d folder.
Make it executable by running
sudo chmod +x /etc/pm/sleep.d/ath9kreset
After that wireless should work after each suspend.
Friday, November 13, 2009
Sunday, November 8, 2009
DSDT Testing
How to overload DSDT into Windows
1)Download Microsoft ASL Compiler
2)Go to Microsoft ASL Compiler from the start menu program
Right Click on ASL Compiler Command Window, select Run as Administrator
3)At the Command Prompt Window
Change Directory to Desktop.
Eg (cd "C:\Users\{Your Username}\Desktop")
Leave the command prompt open
4)Download the AML File into Desktop (in this example call it DSDT.AML
5)Using the Command Prompt Window in 3) Type:
asl /loadtable DSDT.AML
and Enter.
You should see loadtable successful
Restart for changes to take place.
You should see something like this in event log meaning THRM is enumerated
I am trying to make improvement to Aspire 4530 DSDT
The following is done using the Thermal Control Values from Aspire 4535G because I didn't hear overheated 4535Gs
I feel that this DSDT mod is good but I hope you get your feedback before incorporating the changes into BIOS release.
Please try this especially Gamers!
The aim is to reduce temperature during gaming!
Download the trial DSDT here
Changelog:
1)Added CPU1 to the list of thermal devices to be controlled
2)Use the THRM values of Aspire 4535G for the following methods
a)_TMP return value
b)_PSV
c)_TSP
d)_TC1
e)_TC2
1)Download Microsoft ASL Compiler
2)Go to Microsoft ASL Compiler from the start menu program
Right Click on ASL Compiler Command Window, select Run as Administrator
3)At the Command Prompt Window
Change Directory to Desktop.
Eg (cd "C:\Users\{Your Username}\Desktop")
Leave the command prompt open
4)Download the AML File into Desktop (in this example call it DSDT.AML
5)Using the Command Prompt Window in 3) Type:
asl /loadtable DSDT.AML
and Enter.
You should see loadtable successful
Restart for changes to take place.
You should see something like this in event log meaning THRM is enumerated
I am trying to make improvement to Aspire 4530 DSDT
The following is done using the Thermal Control Values from Aspire 4535G because I didn't hear overheated 4535Gs
I feel that this DSDT mod is good but I hope you get your feedback before incorporating the changes into BIOS release.
Please try this especially Gamers!
The aim is to reduce temperature during gaming!
Download the trial DSDT here
Changelog:
1)Added CPU1 to the list of thermal devices to be controlled
2)Use the THRM values of Aspire 4535G for the following methods
a)_TMP return value
b)_PSV
c)_TSP
d)_TC1
e)_TC2
Subscribe to:
Posts (Atom)
Posts
