dansherer

updated

11 years ago

D

dansherer

4 Posts

0

162347

February 23rd, 2012 00:00

fn key brightness on broken dell m6600

fn brightness key Issue: system | dell m6600 | win  7 64 | nvidia 300m | Optimus enabled

Using the hot key "fn+up" or "fn+down" iniates the brightness ui like normal, however no change in brightness and no change in the ui level indicator. It just stays in the same spot.

Also, none of the windows 7 (64 bit )brightness settings or adjustments  sliders effect the brightness either. The sliders just slide without any effect.

Same with the Premier Color application. Slides but no change.

Using the on screen key board doesn't work either.

Every other fn key works like expected, it's just the brightness.

However, I still have brightness control in the bios and it seems the sytem is staying where the bios has been set. For instance if I us ac-power, it is set to the bios brightness on ac, and if i use the battery, it will dim to the bios brightness on battery setting.

This is happening on two dell m6600's.

I just recently updated to the latest whql certified nvidia verde driver on both (ver295) and the Optimus stability has been way, way, way better. Dare i say it's working as expected.

I have tried updating one of the m6600's dell system management  to the dell features enhancement pack (which is supposedly the new system management) and still exactly the same, except the ui has been overhauled and resemble a regretable 1990's world of ui design.  

Any tech savvy folks out there wanna take a crack at solving this. There aren't any error reports associated to this in my event viewer that i am aware of, but I am new to the world of de-bugging.

Thanks in advance,

Daniel

 

 

  • dansherer

    4 Posts

    5592

    1

    Posted February 23rd, 2012 10:00

    Follow up to my original post above: Issue Solved!!!! (for now)

    I had also recently installed the latest Intel graphics driver from the Intel website (version 8.15.10.2509) to troubleshoot the Optimus issues I was having with my systems. I ran across this thread: 

    ...and someone had mentioned that when they had installed the intel provided drivers, they had a similar issue with the fn brightness key not working. 

    So, I re-installed the latest Dell provided release of the Intel graphics driver (r307994, version 8.15.10.2418). The installer notified my that I was installing an older version of the driver, but I decided to do it anyway. 

    The fn brightness key is back baby! Ok, so now that I got some satisfaction, does anyone have a hypothesis as to why this would happen? What does Dell do to the driver before they release it on their website besides certify it and wrap it up in their own package installer?

    It boggles my mind...

    However, I am yet to find out if Optimus is still stable after having reverted back on the Intel graphics driver. I'm hoping the recently updated Nvidia verde driver (295) was all I needed all along....

    Fingers crossed.

  • 5931

    1

    Posted July 4th, 2014 14:00

    For everyone, who has some brightness-problems, too. Here is my fix:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000]
    "FeatureTestControl"=dword:0000ffff
    "KMD_EnableBrightnessInterface2"=dword:00000000
    "KMD_EnableBrightnesslf2"=dword:00000000

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0001]
    "FeatureTestControl"=dword:0000ffff

    [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\intelkmd]
    "FeatureTestControl"=dword:0000ffff

    Without the both KMD...-Settings, the brightness kept like it was set in bios/uefi.

    Thanks to another Win 8.1-Forum, it is solved for me :-)

    Regards

  • dansherer

    4 Posts

    5592

    0

    Posted February 23rd, 2012 15:00

    WAIT!!! The plot thickens. It seems that the solution isn't necessarily the Intel provided graphics driver vs. the  Dell provided Intel graphics driver.

    I applied this fix to one of two machines that I am troubleshooting with the exact same issue and surprise surprise. Out of nowhere, the machine that has the latest Intel provided driver installed has magically fixed itself, in regards to the fn brightness key???

    I did just wake the computer up from a hibernation of about 4 hours, so let's see how long its last...It could mean that something didn't fully load out of hibernation? I don't know.... It's all guess work at this point.

  • eduncan911

    1 Rookie

    •

    19 Posts

    5592

    0

    Posted August 31st, 2012 17:00

    Yep buddy, join the club.  I've been trying to get the M4600 and M6600 display driver working for some time.  It worked solidly for about 6 months, and then nada.  Yep, installed newer, and reverted to older Dell Feature Enhancement Packs, nada.  Even installed Microsoft VC++ Redistrobution pack as a hunch (it fixed my E1705 for display brightness).

    Recently, I've slammed Windows 8 onto the M4600.  Windows 8 seems to have native support for Fn Key brightness control, with no Dell drivers!  Believe it or not, the Fn key and Arrow up/down worked!  It worked as-is with no driver install!

    Of course, I had to go and install the Intel chipset drivers as well as the touchscreen drivers and touchpad.  After those are installed, the brightness stops working again.  ARGH.

    I was using the chipset drivers straight from Intel.  I'll try to install Dell's older ones, but the newer Intel ones enabled full SATA3 support under Windows 8 (though SATA3/USB3 is native to Win8).  

    I've recently installed WIndows 8 again (be careful, no more "trial" available in Windows 8 - it activates every time now).  After a raw install, the brightness did not work ever, unlike before where it did work after a fresh install before the Intel drivers.  

    Who knows... It's so buggy.

    Subscribing to this thread, so you can keep us posted in your success.  

  • paladin66

    12 Posts

    5592

    0

    Posted November 25th, 2012 20:00

    Dansheer,

    This problem is with the Optimus being enables.  Once to disable Optimus the Fn keys for brightness always work.  That may be a clue for you.  I have a M6600 and a M4600 both having the same problem.  It is not the drivers, its Optimus.  Dell is no help as they do not know of a solution.

    Thanks

    Paladin

  • paladin66

    12 Posts

    5592

    0

    Posted January 4th, 2013 21:00

    Orisocean,

    Disable Optimus in your Bios setup and you should be good.  There is no other solution.  

    Thanks

    Paladin  

  • orisocean

    2 Posts

    5592

    1

    Posted January 4th, 2013 21:00

    I have M4600 with same problem here, Fn+up or Fn+down is not working

    Help me to solve the topic

    Thanks

  • eduncan911

    1 Rookie

    •

    19 Posts

    5592

    0

    Posted January 5th, 2013 16:00

    I too have verified it is Optimus enabled in the bios.  The custom Dell bios has a bug in it for when Optimus is enabled, there is little to no Fn key support (oddly enough, it works the first couple of reboots during OS install - then nada).

    Personally, I must use Optimus.  I constantly get 3.5 to 4.5 hours out of my 6 cell battery in meetings all day, running two VMware VMs - both with 4 virtual CPUs and 6 GB of ram each.  Without Optimus, I only get 1.5 to maybe 2 hours with the nvidia card powered up.  I do this every day - I constantly run my battery down, every day.  I was one of the first who got this laptop in early May 2011, before the ship dates was announced on the site.  Even technical support didn't have my tag number in their system when I got mine!  

    So needless to say, I've been cycling my batteries quite a lot and know the advantages of Optimus.  I also use Optimus to power 4 displays from my M4600.  Two from the Nvidia card (HDMI and Display Port), and two from the Intel 3000HD graphics on the CPU (VGA and laptop screen).  With my advanced port replicator, I always use 3 monitors (two DVI and one VGA).  You cannot do more than 2 displays with Optimus disabled - that is because the Nvidia 500 series cards only support 2 displays (the 600 series supports 4 per GPU!). 

    Tip for those that want to get the most out of Optimus: First, make sure  you aren't using any Dell drivers.  Install real Nvidia drivers, and real Intel HD3000 drivers.  Next, make sure to goto the Nvidia control panel and in the menu bar, under Desktop I think, make sure to show the GPU Activity icon in your tooltray.  Then go down into your tooltray, and force it to show at all times.  What this icon does is it changes colors from black (Nvidia GPU is off) to colored rainbow (Nvidia GPU is on) when something is using the GPU.  I constantly scan that icon to make sure my GPU is disabled, for maximum battery life.  If it is in use, you can click it to see exactly what is using the GPU - so you can exit the program (Logitech G930 headphones want to use my GPU? Why in the hell?  Denied it by shutting it down).  Finally, go into your Nvidia Control Panel and into 3D Settings for the Optimus settings.  Makes sure the defaults are all selecting Integrated Graphics (which is the Intel HD3000).  That gets you 99% of all on Optimus.  I had to force a few things to use Optimus, like IE9 (switched to Chrome now) because IE9 thinks it needs the full pwoer of the Nvidia GPU to render flash videos - it doesn't.

    Bottomline, there is a bug in the Dell bios for the M4600 for when Optimus is enabled you can't control the brightness.  Tech Support doesn't even know how to use Optimus properly, and advices (on every call I've had with them) to disable Optimus.  Very sad for consumers.

  • paladin66

    12 Posts

    5653

    0

    Posted March 30th, 2013 17:00

    Out of nowhere.  When the PC is put in hibernation and it comes out of it, the brightness keys start to work.

  • 64dude

    1 Rookie

    •

    70 Posts

    2055

    0

    Posted March 31st, 2013 10:00

    I've got the same problem with two Dell m6600 too for Windows 8. Latest drivers, quickset from Dell, hasn't resolved in a year of troubleshooting this. Any Thoughts?

    MW64