Jump to content

svl7

Retired Staff
  • Posts

    4643
  • Joined

  • Last visited

  • Days Won

    789

Everything posted by svl7

  1. You can try, but the problem is you won't be able to flash from 3.05. That's the trouble...
  2. EDIT: All instructions and files moved to the main posts: http://forum.techinferno.com/lenovo-ibm/4668-lenovo-y410p-y510p-unlocked-bios-wlan-whitelist-mod-vbios-mod.html
  3. What's a reasonable default 3d voltage for that chip? 1V? Or put differently, how high does the nvidia driver set the voltage when the card boosts?
  4. Hahaha, okay, well, that's why I'm saying Lenovo is doing some odd stuff.
  5. Yeah, don't worry. That would be 80.07.A8.00.2E, right? Lenovo is doing some odd stuff there.
  6. v3.05 uses vbios 80.07.9D.00.3C for the 750m, right?
  7. It will fix the throttling as far as you don't push the cards beyond the power limit on the motherboard of the AW18, if you push the cards too far then it will still not perform properly since Dell crippled the mobo. Here. Please send me a copy of your vbios, thanks. Dell K5100m.rom.zip
  8. Can you check your CPU temp and maybe PCH temp?
  9. Yeah, no problem, no need to hurry, I'm just curious
  10. That should work for the latest WHQL. Make sure to override the driver signature check. nvdmi.zip
  11. Cool, please post some comparison pics if you get the chance!
  12. Thanks, reflashing won't be necessary. I'll have to take a look at the vbios again. I'm sorry, I won't work on bios mods unless I know that there's at least a chance of flashing a modified firmware without issues. Thanks to secure boot and related crap it can be impossible to just flash an unsigned image. I'll need you to run this in DOS and send me the file / post the file it creates. That will already give me some information I need. Also I'll need a link to an official bios update if available.
  13. How about a CPU-Z verification link and some pics?
  14. If you're paranoid about something like this, then simply format the disk and make a fresh install of the OS. Of course you'll still have the Intel backdoor called ME firmware on Intel systems
  15. The mobile equivalent to the PCI-e standard is called MXM, current revision is 3.1 (backwards compatible to 3.0). It's a standard that specifies a mechanical and a software interface for mobile GPU modules. Alienware adheres to those specs pretty well in many of their systems, e.g. AW17, AW18, M18x R1, R2, M17x R2, R3 and R4, M15x. MSI has shown decent MXM supports as well in the past. Clevo is a bit weird, while they praise themselves for full MXM compatibility (especially the reseller called eurocom), that's simply not the case. While the mechanical interface is MXM, the software mechanism is crippled in most systems and usually doesn't allow you to get a next-gen or even two gen newer card to work properly. That's really a pity, cause those systems could have great potential if the firmware was as well implemented as in for example AW systems. A reason to restrict MXM functionality is obvious... some OEMs don't want you to be able to upgrade the GPU for years, they want you to buy a new system. That's why Asus doesn't adhere to the MXM specs AT ALL. Different module size, layout, and especially software interface. No MXM compatibility there. Tl;dr: Mobile GPU equivalent to desktop PCIe GPUs is called MXM. With Alienware and MSI systems that use MXM you have a good chance that you can upgrade your GPU. With Asus you simply can't. With Clevo it's usually pretty tricky and newer gen cards than the system was shipped with most likely cause issues.
  16. I'll try to post the mod this week. 3.05 compared to v2.07 has quite some changes. Most importantly they locked it down, so flashing anything from 3.05 is not easily possible. Major BIOS changes include update ME firmware, new nvidia vbios, updated intel vbios, Win8.1 acpi entry and quite some "under the hood" fixes that most won't notice I guess.
  17. You might want to read the instructions / documentation of RealTemp. Hello captain obvious... I'm not talking about a part that's designed for one-time-use, please, some common-sense. You'd have to use something like this.
  18. Odd, I'll try to look into that. What was your original vbios version? Your vbios is probably part of the system bios. What kind of system are you using?
  19. Dude... that's exactly what I wrote in the post above. Please read again. You don't need to read out the temp with a program, you need to measure the temp at the spot where you mount the "switch" aka thermal cutout.
  20. With the EC. Without having documentation it's super tricky. You could politely ask @Mumak, he might be able to support fan control for this machine in HwInfo (it's Compal-based) as he had some success with AW systems, but he's usually super busy, so you might have to be patient to get a reply. Best will be to head to the HwInfo main thread for this.
  21. That should be super easy, find a place where you can easily mount a thermal cutout (e.g. on the heatsink) measure temperature there (at load) and then get a thermal cutout that fits your temperature range. Cut the wire, solder the cutout between the cut ends, mount the thermal cutout, done.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.