Search the Community
Showing results for tags 'eeprom'.
Found 4 results
Recently obtained myself a bricked Y410P after undervolting my CPU, using svl7's bios mod on TechInferno. If you only take one thing away from this post, it should be the fact that NEVER SHOULD YOU EVER UNDERVOLT A LAPTOP CPU FROM A MODDED BIOS. Hindsight is never 20/20. Anyways, back to topic! I went and purchased my self one of these, in hopes of to re-program my sad bios. So far no good. I am wondering if anyone out there have had any success with this approach. Please share your journey here!
EEPROM error unable to flash vbios
LocalIdentity posted a topic in ClevoI've been trying unsuccessfully to flash the vbios on my Metabox P650RE-G. I've tried flashing with nvflash and keep encountering the message: "Identifying EEPROM... EEPROM ID (C8,4011) : GD GD25Q10 2.7-3.6V 1024Kx1S, page ERROR: ROM image too large for EEPROM" Even though the file I am attempting to flash is only 189KB. I've even tried flashing the stock vbios which is 188KB and that gives the same error. The the only change in the ROM's is that I altered some settings in Maxwell Bios Tweaker. I'm not sure if I'm meant to clear the EEPROM or doing something else. Any and all help is apprecieated CMD LOG------------------------------------------------------------------------------------------------------------- c:\GPU Overclock>nvflash --protectoff NVIDIA Firmware Update Utility (Version 5.236) Modified Version by Joe Dirt Adapter: GeForce GTX 970M (10DE,1618,1558,6543) H:--:NRM S:00,B:01,PCI,D:00,F:00 The display may go *BLANK* on and off for up to 10 seconds during access to the EEPROM depending on your display adapter and output device. Identifying EEPROM... EEPROM ID (C8,4011) : GD GD25Q10 2.7-3.6V 1024Kx1S, page Setting EEPROM software protect setting... Remove EEPROM write protect complete. c:\GPU Overclock>nvflash -6 1.rom NVIDIA Firmware Update Utility (Version 5.236) Modified Version by Joe Dirt Checking for matches between display adapter(s) and image(s)... Adapter: GeForce GTX 970M (10DE,1618,1558,6543) H:--:NRM S:00,B:01,PCI,D:00,F:00 WARNING: Firmware image PCI Subsystem ID (10DE.0000) does not match adapter PCI Subsystem ID (1558.6543). Please press 'y' to confirm override of PCI Subsystem ID's: Overriding PCI subsystem ID mismatch Current - Version:84.04.8C.00.14 ID:10DE:1618:10DE:0000 GM204 Board (Normal Board) Replace with - Version:84.04.8C.00.2E ID:10DE:1618:10DE:0000 GM204 Board (Normal Board) Update display adapter firmware? Press 'y' to confirm (any other key to abort): The display may go *BLANK* on and off for up to 10 seconds or more during the update process depending on your display adapter and output device. Identifying EEPROM... EEPROM ID (C8,4011) : GD GD25Q10 2.7-3.6V 1024Kx1S, page ERROR: ROM image too large for EEPROM
Clevo p150em & gtx 670m 1.5gb
djdblaster posted a topic in ClevoHello everyone, I bought used 670M pulled from AW system to insert in my MS 16F3. Installed, no screen on boot. Luckily, I have Clevo P150EM laying around. Installed it there, no thermal alarm, BIOS recognized it as GTX 670M, nvflash also, everything looks great. I saved its vBios and went on another computer to look for vBios version just to be sure which card it is (used NiBiTor to see vBios version which was 80.something..). Since the card is 1.5GB, I assumed it wasn't DELL/AW card because they come with 2GB? That led me to download older 70.24.. Clevo vBios which was successfully flashed after. BIOS and nvflash recognized it, no thermal alarm, great! Pulled the card out of Clevo P150EM and installed in MS 16F3. Screen on boot, no fan spinning max, everything perfect! Installing Windows for like 10 minutes and then fan starts spinning max. Installed Windows, chipset, Intel management, Intel VGA and finally nVidia driver with custom .inf from laptopvideo2go.com. Device Manager shows yellow triangle next to GTX 670M. Rebooted and tried flashing MSI vBios with nvflash. I get the line checking image and ID's, something like that, and skips flashing. Checked EEPROM and it said status Unknown. Entered Windows and 670M shows in Device Manager with yellow triangle next to it. (Code 43 was error from the beginning btw) Reinstalled 670M in Clevo, BIOS and nvflash recognized it, however nvflash cannot write anything to it. Reinstalled back to MS 16F3 and same thing with nvflash. It shows it is there, but cannot write to it. Back to P150EM, 670M shows in BIOS and nvflash, but I cannot flash it. After 2 restarts, nvflash doesn't recognize 670M, but BIOS does. So I am confused now. How can a card show up in Windows if it doesn't get recognized under nvflash nor can be flashed? Shall I try different nvflash version or reinstall in either laptop? I've put this thread under Clevo because P150EM reads a lot of cards, serves me as a diagnosis tool and I would like to get it working it there first. It might be lengthy post, but I tried to include every detail and be specific. Hopefully it helps someone else too!
Solved, see the "edit" for details. So... I just had the glorious idea to mod a very old beta vbios of an 6970m ES and try it on my card... but now there's one big problem, my system won't POST anymore. The SCROLL an d CAPS leds are blinking, which means the GPU is preventing the system from POST. ... and since it doesn't POST I can't even blind flash the card. So, my guess is, the card is still ok, but the vbios fails completely. (I don't think the card is dead...) Anyway, the only way I can think of to solve this, is putting the card in a system with 2 GPUs (e.g. M18x). Do you think such a system would boot with this card and allow it to be flashed? __________________________ EDIT: Successfully reprogrammed the serial flash memory chip which stores the VBIOS, more details about the whole procedure can be found here: Recovering a notebook GPU from a bad VBIOS flash | Tech|Inferno __________________________