Dear all forum members,
i have a problem with my motherboard bios. i'm newbie,so i'm sorry if may be this is not the correct section.

the point is:
i need to add an EDID data into my bios since there are no one of preinstalled EDID data in the bios suitable with my lvds screen resolution (1024x600). and there are no option in the bios to upload any custom EDID data.

motherboard: Gigabyte H77TN-00 rev1.0
bios: Aptio AMI EFI 2.15.1229
gigabyte original bios version: f2 (http://www.gigabyte.com/products/pro...?pid=4458#bios)
rw file: https://app.box.com/s/ufoy86ukzem1duvqlmjh
system bios version: 4.6

screen panel: hannstar hsd1001fw1
the EDID data at the last pages of datasheet: http://www.datasheet4u.com/datasheet...nStar.pdf.html


last condition:
1. i try to make .inf file with this panel EDID to override the driver (i use windows7 sp1) and i found that intel hd graphics doesnt support EDID override method.

2. the best one that i can do is use 1024x768 EDID from the bios. it makes the screen works, but i cant see the lower part of the screen (windows task bar) since i "lost" 168pixel of vertical size.
so i think, i have no other choice except modding the bios. but i have no any experience to mod the bios.

3. i try to open the .f2 bios file with MMTool Aptio and AMIBCP v4.53 but, i dont know which module that i need to edit, and how to do it.

please give me a guidance how to solve this problem....

Best Regards,
Erwin

@ween

I have attached a VBIOS with a 1024x600 resolution. Open BIOS file in MMTool, go to Replace, check link present, select 8086,162 and browse for the attached 8086-0162.bin, then hit replace button and save. Flash this and test. If I were you, I would start by updating everything with UBU (which you will find here) and then use MMTool with the file I provided, to avoid any compatibility problems.

Use at your own risk and report back.

Dear Lordkag & Fernando,
thank you so much, already downloading UBU and your mod file. but i left the computer in the company's workshop where i'm working for. As in Switzerland, there are easter holiday until monday. so i can try this on next tuesday. I will reporting to you soon.

once again, thanks a lot
regards,
Erwin

@ween

Actually, I think you should avoid using that VBIOS and rather keep it as a last solution. The resolution may only work while booting, but not after. You should have provided more info, like what video card is used (exact model) and type of the connection. There is a way to input DTD (EDID Detailed Timing Descriptor) data, but I don't know how you could obtain that. The links you provided do not work, but I managed to get the datasheet and it is blank, no EDID info.

You should instead create a custom resolution. For Intel you have this page.

@lordkag

here is the datasheet with edid data. i'm sorry about the datasheet dead link, because 3 days ago, it still works.

for the costums resolution, i already try it, but since in bios i select 15" 1024x768 screen, i make costum resolution with 1024x600, and set the porch. the results: it works to 1024x600, but there are a big black frame on the top of the screen even i try to "play" with front and back vertical porch settings

Best regards,
Erwin

Another things that make me confused, why in the bios update download from gigabyte website, there are two bios files? what the differences between "H77TN.f2" and "H77TN_M8.f2"? which one of them that i need to modify?

@lordkag

after clear cmos, i try with two approach:

1. without ubu update, i replace the 8086-0162 files to both "H77TN.f2" and "H77TN_M8.f2" using MMTool Aptio and flashing the motherboard with this files, but it failed with message: "unable to start a secure flash session"

2a. i replace the 8086-0162 files to both "H77TN.f2" and "H77TN_M8.f2" using MMTool Aptio and update everything with ubu. but when try to flashing it at motherboard, it also failed: "problem opening file for reading"

2b. because i think when we running ubu, it change the H77TN.f2 become bios.bin that makes afu303 cant read it. i rename it back to H77TN.f2 and try to flashing it again, but failed again with message: "unable to start a secure flash session"

any idea, why it happen like this?

Your BIOS is protected against modding. Maybe it can be bypassed, but you should rather start with this. You should get the EDID from your monitor, because the pdf is missing some bytes. Use MonInfo or madVR and get the raw data. Then you can use this for your work.

If this doesn't work, there is a way to input this in the VBIOS. But you haven't provided the basic info that I requested: what video card is used (if Intel, what CPU), how is the monitor connected. This might not seem important, but it is a step in the right direction. Until now you provided one useful information - the BIOS to extract the VBIOS - and one half good information - standard EDID.

I was about to abandon this, because the datasheet I have found had no EDID info, leaving me to think that you haven't even searched or read anything. If you provide all the info, including raw EDID data straight from monitor, maybe I will take a look. But only after you have tested the above method and all the others you could find. There is however no promise that I will start to work on it right away.

@lordkag

ok, i will try it......and will try to extract the raw edid data directly from monitor also.

basic info as your request:
1. intel hd graphics celeron g540
2. the monitor connected via lvds cable and 40pin lvds port from motherboard

but during bios flash & windows installation, i use normal benq monitor via hdmi port. because the default lvds settings in motherboard bios is disabled. and after enabling lvds port from bios, windows recognize it as main monitor (and hdmi monitor as secondary screen) more or less similar like windows behavior in laptop/all in one pc.

@lordkag
i try DTD calculator. but i dont know why, the dtd calculator cant access the edid from intel hd graphics. and i try to put the edid manually from hannstar data sheet and put it in registry hack, but there are still no effect. the intel hd graphics seems only following the edid which sets from bios. screenshooted below:

You should try to change the resolution from Windows, maybe it will work.

Also, I told you to first read the raw EDID data with MonInfo, madVR and every software you can find. Only then you should have used EDID override. It may be possible that the raw data can't be extracted (I get a real-time mode in MonInfo with direct access), but now it should be impossible, since you messed the registry with incomplete data.

I have asked the raw EDID data from monitor and instead you posted a picture of the registry override. I don't know if you expect me to confirm the obvious or to extract the data one byte at a time. Let's put aside that you are trying to connect a laptop screen to a desktop. While I am left with the heavy work of inserting this to VBIOS and tweak it to work like in a mobile VBIOS + avoiding the BIOS protection, I have only requested from you to provide the data for immediate use. Instead you post a picture with some bytes that might not even be right for your monitor. I'm sorry, but I think you are on your own on this one.

Zitat von lordkag im Beitrag #12

---

You should try to change the resolution from Windows, maybe it will work.

Also, I told you to first read the raw EDID data with MonInfo, madVR and every software you can find. Only then you should have used EDID override. It may be possible that the raw data can't be extracted (I get a real-time mode in MonInfo with direct access), but now it should be impossible, since you messed the registry with incomplete data.

I have asked the raw EDID data from monitor and instead you posted a picture of the registry override. I don't know if you expect me to confirm the obvious or to extract the data one byte at a time. Let's put aside that you are trying to connect a laptop screen to a desktop. While I am left with the heavy work of inserting this to VBIOS and tweak it to work like in a mobile VBIOS + avoiding the BIOS protection, I have only requested from you to provide the data for immediate use. Instead you post a picture with some bytes that might not even be right for your monitor. I'm sorry, but I think you are on your own on this one.

---

Zitat von ween im Beitrag #13

---

Zitat von lordkag im Beitrag #12

---

You should try to change the resolution from Windows, maybe it will work.

Also, I told you to first read the raw EDID data with MonInfo, madVR and every software you can find. Only then you should have used EDID override. It may be possible that the raw data can't be extracted (I get a real-time mode in MonInfo with direct access), but now it should be impossible, since you messed the registry with incomplete data.

I have asked the raw EDID data from monitor and instead you posted a picture of the registry override. I don't know if you expect me to confirm the obvious or to extract the data one byte at a time. Let's put aside that you are trying to connect a laptop screen to a desktop. While I am left with the heavy work of inserting this to VBIOS and tweak it to work like in a mobile VBIOS + avoiding the BIOS protection, I have only requested from you to provide the data for immediate use. Instead you post a picture with some bytes that might not even be right for your monitor. I'm sorry, but I think you are on your own on this one.

---

i'm sorry for your inconvinience.......the edid in registry already override since i try to solve this problem at the beginning.....and when i try to get it today, only the override one appeared........i know, we need the original one, but please tell me how to get back the original edid data? should i format&reinstall the windows? be patient, please......i'm trying to looking the way to get it back.....

---

@lordkag

today i try many software to extract the raw edid data from the screen, for example:
powerstrip: