*HP HDX 9000 DRAGON Owners Lounge, Part 2*

Discussion in 'HP' started by 2.0, Sep 3, 2010.

  1. remdale

    remdale Notebook Evangelist

    Reputations:
    41
    Messages:
    456
    Likes Received:
    173
    Trophy Points:
    56
  2. t456

    t456 1977-09-05, 12:56:00 UTC Moderator

    Reputations:
    1,942
    Messages:
    2,586
    Likes Received:
    2,030
    Trophy Points:
    181
    Yes, but it depends on the graphics drivers as to whether they're actually taking effect.

    Either way, a good option to try out.
    Flashing can easily be reversed to 8-bit, of course. The number of possible colours would indeed be less, but it really depends on the quality of the screen as to that being noticeable since most of the theoretical combinations won't be reproducible anyway.
     
  3. remdale

    remdale Notebook Evangelist

    Reputations:
    41
    Messages:
    456
    Likes Received:
    173
    Trophy Points:
    56
    Well, the driver was not installed. I'm speaking of the device ID that showed in the device manager after flashing the vBIOS. The driver was not installed for that ID yet.
    Is it possible to do all of that without having a flash programmer?
     
  4. remdale

    remdale Notebook Evangelist

    Reputations:
    41
    Messages:
    456
    Likes Received:
    173
    Trophy Points:
    56
    It seems like you're right. The LCD specification is saying:
     
  5. triturbo

    triturbo Long live 16:10 and MXM-B

    Reputations:
    1,577
    Messages:
    3,835
    Likes Received:
    1,231
    Trophy Points:
    231
    Great work!

    Alienware M17x-R1 was equipped with 8bit RGB LED display and GTX 280m, it was MXM 3 though, but I think crossflashing is possible.
     
  6. t456

    t456 1977-09-05, 12:56:00 UTC Moderator

    Reputations:
    1,942
    Messages:
    2,586
    Likes Received:
    2,030
    Trophy Points:
    181
    Ok, that might work then. Though Microsoft's 'Basic VGA' is also a driver, albeit with minimal functionality.
    Yes, provided the dGPU has direct access to the screen, so no Optimus/Enduro. You can use the tools and guide from this post.

    The current edid can be exported from the registry:
     
  7. remdale

    remdale Notebook Evangelist

    Reputations:
    41
    Messages:
    456
    Likes Received:
    173
    Trophy Points:
    56
    Just tried again now. The vBIOS chip was flashed with vBIOS from Lenovo and the 280M vBIOS was in the system BIOS. It booted up with the 280M vBIOS, but when I checked up in the device manager, it was FX3700M device ID. So I erased the vBIOS chip and booted up again. The ID was from 280M then. It seems like it picks up vBIOS from the chip after or during POST, so it's better to keep the chip blank. It could be used as a workaround for using HP vBIOS in this way. But again, it didn't help to output 8 bits all the other times before.
    Didn't help, the same thing. I guess it all is because of the missing MXM structure and the reduced performance mode the video cards are talking about is probably about the 6 bit output as well. Regardless the vBIOS type. It's all in the MXM structure which basically resides in system BIOS and not possible to call without system calls. Among the other things described in MXM structures, there's LVDS setting which points out "Digital signal MXM pin connection". Among many options there are
    What we need here is dual-link 24-bit (3 colors x 8 bits). But as the MXM structure is absent in the Dragon, there could be a way around this like this:
    Sounds good, but as I've seen in all cases, video cards rely on the MXM structure and simply ignore LVDS settings in EDID.

    This thing looks hopeless, but there's FX3700M vBIOS which is non MXM compliant and so doesn't need any MXM structures. Even though it booted up with 2 purple screens on 1 screen and nothing was visible after OS boot, the screen looked bright and I could adjust brightness there. But still there was the same noise on the screen. So the best thing we can do now is to play around with this vbios I assume or find another one that is non MXM compliant.
     
  8. remdale

    remdale Notebook Evangelist

    Reputations:
    41
    Messages:
    456
    Likes Received:
    173
    Trophy Points:
    56
    [​IMG]
    I've flashed vBIOS from Dell and again, the it reported device ID 0618 which belongs to GTX 260M. So again, I've edited the inf file and installed the same driver for FX3700M with help of a VGA screen. After restarting Windows, the picture appeared on the Dragon's screen. It was dim and had noise, but I could adjust brightness. What's interesting in all cases is that the noise comes up during OS boot and goes away during power off.

    What if the screen doesn't boot up with the newly flashed EDID? Will I have to use a VGA monitor and that tool to revert everything back?
     
  9. t456

    t456 1977-09-05, 12:56:00 UTC Moderator

    Reputations:
    1,942
    Messages:
    2,586
    Likes Received:
    2,030
    Trophy Points:
    181
    Yes, that would be possible. You might want to do a trial run first; boot with the usb stick and VGA attached and then check whether both the panel and monitor show an image and that the panel can still be approached by the I2C tools.

    Haven't heard of an instance where the edid flash actually bricked a screen though. But you could indeed use it to flash an incompatible edid such as making it claim '4K' or 'CRT' and the like (the 'CRT' value being what bricked most lcd panels in the first place). The bit-ness can cause artifacting and, at the extreme end, an illegible screen, but as long as the edid is valid (checksum) then it will happily permit booting.
     
  10. MobileArtist

    MobileArtist Notebook Deity

    Reputations:
    234
    Messages:
    1,597
    Likes Received:
    343
    Trophy Points:
    101
Loading...
Similar Threads - 9000 DRAGON Owners
  1. jojonono
    Replies:
    7
    Views:
    913

Share This Page