Jump to content

octiceps

Registered User
  • Posts

    1016
  • Joined

  • Last visited

  • Days Won

    6

Posts posted by octiceps

  1. Very interesting, thanks for posting this. Have you tried one of @svl7 modded vbios for overclocking? I think he might have a GT 650M one.

    Yeah he's got one for the most recent BIOS revision on the Lenovo IdeaPad Y500. We're still trying to figure out how to get the vBIOS on the second GPU to flash so that overclocking in SLI works. That was the reason I took apart my GPU and shot these photos in the first place.

  2. It would be interesting to know for sure whether the vbios is in fact on a separate eeprom on that thing. So I would be looking for a certain 8-pin chip.

    Does the EEPROM chip say something specific on it? I've got my GPU disassembled here in front of me right now and there are ten "8-pin chips" on both the top (where the GPU core is) and bottom. Some of them are so small I can't read the writing without a flashlight and magnifying class. Want to get this right because this thing was a pain to take apart and I don't want to have to do it again.

    I'll take pictures of everything and put them in my next post.

    • Thumbs Up 1
  3. svl7,

    I did notice one "problem" with the vbios after spending a little more time with it. It looks like it only flashed on the first card.

    I can overclock card 0 as high as I like, but card 1 caps at 924 (+135).

    In NvidiaInspector, Card 0 shows a modified bios as expected, but card 1 shows stock.

    Any suggestions?

    Thanks again, everything else looks solid.

    Hey LewsTherin05, when you attempted to overclock both cards did you adjust their clocks separately or sync them? I know that in SLI one of them is the "master" card and the other is the "slave" card. I thought that if you sync them the clocks on the slave card will always match those of the master. So even though the +135 limit hasn't been unlocked on the second GPU shouldn't it still be able to bypass that as long as it has been unlocked on the first GPU? Have you tried using MSI Afterburner?

    Let me know if I'm way off-base because I haven't flashed to modded 2.02 yet, just waiting on the outcome of this whole thing.

  4. I need to check one or two things, but I'm running out of ideas.

    Has anyone ever disassembled the ultra bay GPU?

    Not that I know of. Another Y500 owner disassembled his single-GPU machine here with pictures but no Ultrabay GPU.

    What specifically are you looking for and what should I be photographing? I can disassemble mine later today if needed. Hope I can put it all back together when I'm done lol.

    In the meantime, these are some images and specifications of the disassembled Ultrabay GPU from the Lenovo hardware manual. They're pretty crude illustrations but might be of some use until I get around to taking apart my GPU. View full size as they are from an iPad.

    http://i.imgur.com/DHb6u6Q.png

    http://i.imgur.com/UM9Hktq.png

    http://i.imgur.com/81TFb8n.png

    http://i.imgur.com/JV62fGx.png

    http://i.imgur.com/j170BJh.png

    post-10698-14494994942576_thumb.jpg

  5. I don't have SLI, and how can I save a copy of my bios?

    Use the fptw64 tool in the first post of this thread. After unzipping the folder right-click on fptw64.exe and go to its Properties. Under the Compatibilty tab tick 'Run this program as administrator.' Then, double-click on backup.bat and it will generate a copy of the BIOS as a .bin file in the same folder.

    • Thumbs Up 1
  6. Did you successfully use the 2.02 Modded Bios? Also, when I boot into Legacy, USB drives still dont appear. Any tips? Thanks for the help by the way. Its just that flashing BIOS is something very very fragile. And the first links dont work for me...

    Haven't flashed yet. Still waiting on the fix to unlock the OC limit for SLI.

    Maybe you made a mistake when creating the USB drive and it is not bootable.

    What links don't work?

  7. Does this go for anyone with 2.02. Also, I seem to have a major problem, with maybe a minor fix. So my bios in bootmenu is only showing HDD IPv4 and IPv6, so disc drive or USB drive. I need help with this if I am going to flash a modded bios

    Edit:

    In the readme it says "disabled wlan" does that mean whitelist is gone or that you actually disabled wlan in the bios. Just want to be safe.

    Boot in Legacy mode instead of UEFI and your drive will show up.

    There is a setting in the BIOS to disable WLAN but this mod just removes the whitelist. Your WiFi will still work just fine.

  8. However, I did run it as admin, i right click the .bat, then I click run as admin. I also ticked the fptw as admin in compatibility.

    Maybe someone with teamviewer can help me please?

    You don't need to run backup.bat as admin. Just make sure fptw64.exe or whatever is ticked to run as admin.

    Is there an error file that is generated in the folder after you try to make the backup? What does it say?

  9. Not sure what I'm doing wrong. I ran the 64 bit and the dos backup as admin, and nothing is showing up.

    Assuming you're using Fptw64.exe, you need to right-click on it, go to Properties and tick 'Run this program as administrator' under the Compatibility tab. Then, when you double click on backup.bat, it will dump the BIOS into a .bin file in the same folder.

  10. Is here anyone who has SLI and has and older BIOS than 2.02?

    Good question. I still have a Y500 with BIOS v1.05 that I flashed with your modded 1.05. I can mount my second GPU in its Ultrabay. How may I be of service?

    However, this unit is going to be returned soon and the unit I am going to keep has BIOS v2.02 and that is the machine I hope to flash. I haven't done it yet since you guys are still figuring out how to mod the vBIOS on the second GPU.

  11. svl7,

    I did notice one "problem" with the vbios after spending a little more time with it. It looks like it only flashed on the first card.

    I can overclock card 0 as high as I like, but card 1 caps at 924 (+135).

    In NvidiaInspector, Card 0 shows a modified bios as expected, but card 1 shows stock.

    Any suggestions?

    Thanks again, everything else looks solid.

    Hmm, I thought I changed both, let me check again.

    - - - Updated - - -

    Edit: @LewsTherin05 - It seems the extension bay handles the vbios stuff differently... I'm not sure how exactly it works, but maybe the vbios gets copied to the extension module and since you already had that version there it didn't update... but that's wild guessing.

    Can you try dumping the vbios of GPU1 with GPU-Z or nvflash? Though I doubt you can access it.

    I too have the SLI configuration. I will be following these developments as I have yet to perform the flash.

  12. Yes. Also, my BIOS has an issue with detecting any external bootable drives. For example, on the boot priority list, only HDD shows up and IPv4 and IPv6. USB and Disc drive never appear. This is keeping me from installing Ubuntu, something I'd very much like to use.

    Sounds like you are in UEFI mode but whatever media you are trying to boot from is not UEFI-bootable. Try setting the BIOS in Legacy mode and see if your drive shows up on boot menu when you press F12.

  13. You think this bios update will unlock overclocking past +135 with this modded vbios? I am getting some conflicting opinions on this.

    I haven't read about anybody in the Kepler vBIOS mods thread with this problem and they're all using svl7's mods. We won't know whether it is a problem for this machine until a modded BIOS for GT 650M that unlocks the overclocking limit is released but I'm pretty certain it is a problem with Nvidia Inspector when using the newer drivers.

  14. FYI I am able to overclock my sli gt650's by forcing nvidia inspector (.bat script) to 980 MHz on the 310.9 stock bios but when I install the new 314.22 it maxes out at 924 MHz. Is this usual behavior on the y500? Note I have not flashed to the custom vbios discussed in this thread but I too look forward to seeing a 2.0 custom version. I am afraid to flash it to the 1.5 version if that is even possible. Bioshock Infinite does run smoother on Ultra setting (1920x1080)and with out micro-stutters on 314.22 30-60 fps.

    Anything past 310.90 will cause you to hit the +135 MHz artificial limit on the core when you use Nvidia Inspector and the .bat files to overclock.

    What I am really waiting for is a BIOS/vBIOS unlock that will remove the artificial OC limit once and for all so that I can use MSI Afterburner and the latest drivers to overclock to the max. I have already sent svl7 my BIOS v2.02 and vBIOS version and hope that he will be able to mod an unlocked overclocking BIOS.

    Not that I would recommend you flash using the 1.05 mod but I have a hunch that nothing has changed since then. I previously had a Y500 on 1.05 BIOS that I returned and the GUI and settings are all identical to my current Y500 on 2.02 BIOS.

  15. Yes, exactly.

    Well, actually I can't really remember whether I included the vbios mod in the mods I posted... let me know. If not tell me your vbios version.

    No you didn't post a vBIOS mod for the GT 650M in the Kepler vBIOS mods thread. The vBIOS version is 80.07.27.00.33.

    post-10698-14494994882011_thumb.png

    I tried using GPU-Z to save the vBIOS to a file but it kept returning this error.

    post-10698-14494994882221_thumb.png

    EDIT: Disregard my question about the error. I just realized that since I have a laptop the vBIOS is part of the BIOS and can't be extracted this way.

  16. Dump the bios with this tool, there should be a backup.bat or so included.

    The GPU stuff is part of the vbios, you won't notice it in the bios, but as soon as you use an overclocking utility such as nvidia inspector you'll notice the change.

    Doh! I knew that, especially since I already performed the flash before. Thanks for the pointer svl7.

    So you're saying that the +135 limit has already been unlocked since the vBIOS is part of the BIOS on this machine? So I can use Afterburner to bypass the limit instead of using Inspector to force P-states using .bat files?

×
×
  • 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.