M17xR3 HDMI IN not working: **Work around from Nvidia** at last!

Discussion in 'Alienware 17 and M17x' started by mattaddiction, Apr 17, 2012.

Thread Status:
Not open for further replies.
  1. mattaddiction

    mattaddiction Notebook Enthusiast

    Reputations:
    48
    Messages:
    24
    Likes Received:
    2
    Trophy Points:
    6
    Hi,

    Regarding the HDMI Input not working with non-Dell drivers, I’ve had a response from Nvidia support having raised the issue with them a while ago.

    The issue seems to be Dell’s end, so not something they can fix within the Nvidia Reference driver (due to possible incompatibility with other systems). Sounds like the ball is in Dells court and need Dell to provide up-to-date drivers (with the fix or difference the system needs), so sounds like Dell are aware of the issue and the cause.

    I’m quite shocked Dell aren’t on the ball with driver updates for a premium gaming system like the M17xR3… tbh

    Nvidia’s advice is to contact Dell to get an fixed, up-to-date driver.

    Anyway, the work around they have given me and seems to work. I’m running the latest Beta driver and I had an image on the screen for a few minutes (as long as I tested it for) rather than the half a second flash… (My System: M17xR3 with 580m GTX).


    -----------------------------------------------------------------------------------------

    Nvidia support asked me to first point out they in no way indorse editing your Registry, recommend against. You proceed entirely at your own risk. Back up your system first etcetc…. And this workaround not yet being made public.

    Nvidia recommend: “recommendation is for users impacted by this issue to simply contact Dell directly and ask for a driver update with the fix”.

    **To use at your own risk**

    1. Make sure you are running the 296.10 driver or newer driver.
    2. In Registry editor Go to registry location:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{active graphics device}\0000
    (You will have to work out which is the active graphics device if you have more than one listed)
    3. Create a new key by right-clicking on the right-hand pan of the registry editor window and then select "New" > "DWORD (32-bit) Value".
    4. Label the name of the new key as "DisableHPDFakeMonitor".
    5. Once key has been created, double click the new key and then add the "1" to Value data area. Click OK to save.
    6. Restart Windows.
    7. Check HDMI-In functionality.

    **To use at your own risk**

    I've been advised this will not need reapplying if doing a driver update, but will if the driver is uninstalled and a new driver installed (i.e. clan install).

    ------------------------------------------------------------------------------------

    Hope that’s some help to those suffering with this issue.

    Cheers

    Matt
     
  2. olbengc

    olbengc Newbie

    Reputations:
    3
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    5
    woah!, it really does work!!

    thanks a lot man, i had lost all hope in my hdmi-in port, but i tried this and it seems to work (even though i just tested it for like 5 minutes)

    (gtx580m, 3d screen, driver 296.10)
     
  3. mattaddiction

    mattaddiction Notebook Enthusiast

    Reputations:
    48
    Messages:
    24
    Likes Received:
    2
    Trophy Points:
    6
    Thanks need to go to Nvidia, I'm impressed with them helping out the "little guy" (Nvidia equipt, M17x's must be a very small nechie in there global market), looking in to the issue and coming back with a usable resolution, rather than the corporate "it's Dell's Issue, talk to them"!

    -m
     
  4. Veloster84

    Veloster84 Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    I have been having this same issue as well. I have been trying to find out what file is my active graphics device out of the 7 listed. Any help how to figure this out? I have tried dxdiag, device manager etc and none of them match up to anything I find.
     
  5. charlie22911

    charlie22911 Notebook Enthusiast

    Reputations:
    0
    Messages:
    32
    Likes Received:
    1
    Trophy Points:
    16
    This worked great!

    Look for an entry "DriverDesc", the value of that key should have the name of your card in it. That is the folder you are looking for.
     
  6. Veloster84

    Veloster84 Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    Where exactly is this DriverDesc entry. Is it in the dxdiag? Some listing in device manager under the graphics card? As you can probably tell I am out of my limited comfort zone with this stuff. I am learning as I go. Thanks for the response either way. You figure since this machine costs so much, I would really like to have all available options working....its pretty sad they have not fixed this issue yet.
     
  7. vunamdeptrai

    vunamdeptrai Newbie

    Reputations:
    0
    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    5
    It can be obtained through Device Manager by right-clicking on the device, selecting Properties > Details tab, and selecting "Device Class GUID" from the drop-down menu.
     
  8. Jody

    Jody Notebook Deity

    Reputations:
    339
    Messages:
    1,093
    Likes Received:
    8
    Trophy Points:
    56
    Thank you for the update! That's awesome. I discussed with Dell folks before. The problem isn't very simple. The way it is implemented on newer cards isn't compatible with the way it is implemented in the M17X. The newer drivers support the newer implementation so that it works with a bunch of different cards but it breaks the functionality in our laptops. I know Dell was trying to find a way to get it to work. NVidia can't/won't change the present implementation in order to fix our issue. What I got out of the conversation was that Dell was trying to find a workaround for the M17X and Nvidia was sort of boxed in due to the need to support multiple cards with some of them doing it a newer and "better" way.
     
  9. FoxSky

    FoxSky Newbie

    Reputations:
    0
    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    5
    lol, I search everywhere for a solution and I registered here just to say thank you.

    Edit:
    Ok, i'm stuck...
    On my "device Class GUID" for my 460m I got {4d36e968-e325-11ce-bfc1-08002be10318}
    Whereas in my regedit at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\ there's
    {393BACAF-7ACA-4207-BC55-41B16FA13E4B}
    {42cf9257-1d96-4c9d-87f3-0d8e74595f78}
    {94900405-3C67-46C6-85A9-777EF1917304}
    {b043b95c-5670-4f10-b934-8ed0c8eb59a8}
    {DEB039CC-B704-4F53-B43E-9DD4432FA2E9}
    {F92BFB9B-59E9-4B65-8AA3-D004C26BA193}

    I'm at a total lost, someone please help me (-_-)'
     
  10. Jody

    Jody Notebook Deity

    Reputations:
    339
    Messages:
    1,093
    Likes Received:
    8
    Trophy Points:
    56
    You have to look inside them. Look at the 0000 key for each one. One of them will have a bunch of 3D and NVidia related settings. The others won't.
     
Loading...
Thread Status:
Not open for further replies.

Share This Page