Providing the model of the laptop is the info I needed, as I can extract some profiles from the BIOS. I will start with some warnings:
- I am not responsible for the data you provided. You have provided until now 4 different EDIDs, the EEE PC BIOS has another 3 DTD for 1024x600 resolution. Choosing the right one(s) is not an easy thing.
- I am not responsible for the VBIOS mod. Even if I input right timings, I may screw something else, so it is your entire choice of flashing it. I don't have a 100% success rate in modding, two users here can vouch for my failures.
- I am not responsible for the BIOS flashing process, which will be done with special Intel or AMI tools to avoid the secure flash.
- I am not responsible for the screen malfunction because of bad timings. I will use the timings from Asus 1001P, to be as safe as possible, but beyond that, is just luck.
- I am not responsible for anything that happens. Let's review what you are trying to do: connecting a netbook screen to a desktop mainboard that has LVDS connector for only a few standard screens. The mobile VBIOS has an entire section for inputing special timings for LVDS screens, the desktop one does not.

If you agree with all the above, we can move on. It is helpful to know why you need this strange connection and for how much time. This is to determine if I need to make permanent changes for all situations and accommodating with other screens, or just a temporary patch until your work is done with this screen.

Next is to test whether the BIOS is moddable. Download FTK8 0.11 from here (CodeRush work detailed here, that offers some tools for Asus boards, but also a wrapper for Intel tools, which you will need). Run backup.bat and biosbck.bat, keep safe a copy of the .bin files you obtain. Get the file biosbck.bin. Use UBU and update only Lan ROM and EFI for this file. Take the modded bios.bin and place it in FTK folder, open biosrefl.bat and comment or remove lines 4-10, run biosrefl.bat, which will pass "fptw -rewrite -bios -f bios.bin". If you succeed, I can update the VBIOS with new timings, otherwise you will need to use a method like this to remove lock, or even use a programmer.

Once you report back with your results, I can proceed to VBIOS patching.

@lordkag

ok, let me tell you the background.......actually, i have a project of carpc.
one of the problem of this project is very difficult to get a suitable monitor in terms of resolution and size.
i have two option: using laptop based or pc based.
i need a laptop screen since its the best for this application, but in other hand i need a lot of usb connector because of many usb devices will involved in this project.

so, i choose to use thin mini itx solution with screen taken from my old eeepc that not to be used anymore. one of my friend already done also with this solution. he use intel dq77kb motherboard. he can add his own edid to the bios easily more or less as the picture below

Zitat von lordkag im Beitrag #16

---

Next is to test whether the BIOS is moddable. Download FTK8 0.11 from here (CodeRush work detailed here, that offers some tools for Asus boards, but also a wrapper for Intel tools, which you will need). Run backup.bat and biosbck.bat, keep safe a copy of the .bin files you obtain. Get the file biosbck.bin. Use UBU and update only Lan ROM and EFI for this file. Take the modded bios.bin and place it in FTK folder, open biosrefl.bat and comment or remove lines 4-10, run biosrefl.bat, which will pass "fptw -rewrite -bios -f bios.bin". If you succeed, I can update the VBIOS with new timings, otherwise you will need to use a method like this to remove lock, or even use a programmer.

Once you report back with your results, I can proceed to VBIOS patching.

---

Zitat von lordkag im Beitrag #16

---

Next is to test whether the BIOS is moddable. Download FTK8 0.11 from here (CodeRush work detailed here, that offers some tools for Asus boards, but also a wrapper for Intel tools, which you will need). Run backup.bat and biosbck.bat, keep safe a copy of the .bin files you obtain. Get the file biosbck.bin. Use UBU and update only Lan ROM and EFI for this file. Take the modded bios.bin and place it in FTK folder, open biosrefl.bat and comment or remove lines 4-10, run biosrefl.bat, which will pass "fptw -rewrite -bios -f bios.bin". If you succeed, I can update the VBIOS with new timings, otherwise you will need to use a method like this to remove lock, or even use a programmer.

Once you report back with your results, I can proceed to VBIOS patching.

---

I think I was pretty clear on the actions to be taken. Because of this I had to make something error-proof, so please read the steps carefully and do as it is written. Once you run biosrefl.bat in its original form, two things will happen: it will replace biosbck.bin with a copy from your BIOS region (no modding!) and then it will fail for not finding Asus info. If you had run it the second time with editing, it will write the clean/original biosbck.bin, so we still don't know if some protection is still there. Let's hope that we are lucky.

Change the following in BIOS:
- BIOS -> Chipset -> Panel type = Other Panel type
- BIOS -> BOOT -> Launch CSM = Enabled
- BIOS -> BOOT -> Launch Video OpROM = Legacy First / Legacy Only (you should see VBIOS version 2170 in Intel Graphic Panel -> Informations)

Unpack the attached rar. Then do exactly this:
1. Run biosbck.bat only once, to obtain biosbck.bin. Store a copy of biosbck.bin somewhere safe on a USB flash. This step only once!
2. Run VBIOS_Update.bat and wait until "Update is done...". It also tells you the next step.
3. Run biosrefl2.bat to flash this modified BIOS.
4. Reboot and test. Watch the screen during boot (POST screen), also in Windows. Change resolution in Win graphic panel and in Intel control panel, see if anything changes. Try in BIOS with "other panel type" or 1024x768, see if other displays are affected.
5. Loop 2-3-4 until you succeed or get "Testing VBIOS is done. Try #Addon-VBIOS_update.bat"
6. Loop 2-3-4 with #Addon-VBIOS_update.bat (at point 2. instead of VBIOS_Update.bat) until you succeed or get "Testing is complete!"

Report which one worked, what happened with others. I will say again that I only copied the timings from your laptop, so I'm not responsible for any accidents involving your screen.

EDIT by Fernando: The attachment has been deleted at 02/16/2017.

Zitat von lordkag im Beitrag #19

---

I think I was pretty clear on the actions to be taken. Because of this I had to make something error-proof, so please read the steps carefully and do as it is written. Once you run biosrefl.bat in its original form, two things will happen: it will replace biosbck.bin with a copy from your BIOS region (no modding!) and then it will fail for not finding Asus info. If you had run it the second time with editing, it will write the clean/original biosbck.bin, so we still don't know if some protection is still there. Let's hope that we are lucky.

Change the following in BIOS:
- BIOS -> Chipset -> Panel type = Other Panel type
- BIOS -> BOOT -> Launch CSM = Enabled
- BIOS -> BOOT -> Launch Video OpROM = Legacy First / Legacy Only (you should see VBIOS version 2170 in Intel Graphic Panel -> Informations)

Unpack the attached rar. Then do exactly this:
1. Run biosbck.bat only once, to obtain biosbck.bin. Store a copy of biosbck.bin somewhere safe on a USB flash. This step only once!
2. Run VBIOS_Update.bat and wait until "Update is done...". It also tells you the next step.
3. Run biosrefl2.bat to flash this modified BIOS.
4. Reboot and test. Watch the screen during boot (POST screen), also in Windows. Change resolution in Win graphic panel and in Intel control panel, see if anything changes. Try in BIOS with "other panel type" or 1024x768, see if other displays are affected.
5. Loop 2-3-4 until you succeed or get "Testing VBIOS is done. Try #Addon-VBIOS_update.bat"
6. Loop 2-3-4 with #Addon-VBIOS_update.bat (at point 2. instead of VBIOS_Update.bat) until you succeed or get "Testing is complete!"

Report which one worked, what happened with others. I will say again that I only copied the timings from your laptop, so I'm not responsible for any accidents involving your screen.

---

@ween

The fact that you got 2170 VBIOS version (in Intel Panel) means that the protection was by-passed, because the original BIOS had 2143 version. As to why it didn't worked, I have some ideas for testing. You must install a clean driver to read the VBIOS timings. But before that, do the following with only the Hannstar screen connected all the time, no other screen (! important):

1. Unpack the attached rar to the same folder as previous files.
2. Run biosbck.bat to get a biosbck.bin for modding.
3. Run Z_Update.bat only once, then run biosrefl2.bat to flash the updated BIOS.
4. Shutdown.
5. Boot to Windows and uninstall Intel HD Graphics as depicted here. Run all the instructions in that order.
6. Download a new driver from here for x64 OS, or here for x86 OS.
7. Install it, shutdown. Boot and test the resolution, see if you have any 1024x600 in Win or Intel Graphic panel.
8. If not, run Z_Update.bat followed by biosrefl2.bat, then shutdown and boot, until you get a working 1024x600 or you get "Testing is complete!"

If this still doesn't work, I'm afraid I'm running out of ideas. Maybe if you would post some pictures of "BIOS -> Chipset" tab and "BIOS -> Chipset -> (SA) Configuration -> Graphic Configuration -> LCD Control".

Zitat von lordkag im Beitrag #21

---

@ween

The fact that you got 2170 VBIOS version (in Intel Panel) means that the protection was by-passed, because the original BIOS had 2143 version. As to why it didn't worked, I have some ideas for testing. You must install a clean driver to read the VBIOS timings. But before that, do the following with only the Hannstar screen connected all the time, no other screen (! important):

1. Unpack the attached rar to the same folder as previous files.
2. Run biosbck.bat to get a biosbck.bin for modding.
3. Run Z_Update.bat only once, then run biosrefl2.bat to flash the updated BIOS.
4. Shutdown.
5. Boot to Windows and uninstall Intel HD Graphics as depicted here. Run all the instructions in that order.
6. Download a new driver from here for x64 OS, or here for x86 OS.
7. Install it, shutdown. Boot and test the resolution, see if you have any 1024x600 in Win or Intel Graphic panel.
8. If not, run Z_Update.bat followed by biosrefl2.bat, then shutdown and boot, until you get a working 1024x600 or you get "Testing is complete!"

If this still doesn't work, I'm afraid I'm running out of ideas. Maybe if you would post some pictures of "BIOS -> Chipset" tab and "BIOS -> Chipset -> (SA) Configuration -> Graphic Configuration -> LCD Control".

---

@ween

First of all, there is no problem with "The data is identical". If you read the above 3 lines, you will see that it compares the updated BIOS region with the flashed biosbck.bin, to make sure that there were no errors during flashing.

I think you are at the end of the line. It is better to buy a new 1024x768 LVDS screen, which will give you: native support from BIOS, full UEFI support (works with CSM disabled), no need to mess with BIOS+drivers. It is my impression that any 1024x768 will work, but you should make sure that the supplier has a return policy, otherwise buy the same screen as offered in BIOS setup. When you get one, install the original BIOS and clean install drivers as advised before.

There are several reasons why I think the netbook screen is not supported by your mainboard. It is a netbook screen and your BIOS has support for only 1024x768, 1366x768 and 1920x1080 screens. The timings from Eee PC for 1024x600 require Inverter PWM Normal at 20000Hz, your BIOS offers PWM Inverted at 0-250Hz. Your BIOS overrides the VBIOS timings with the ones from "Panel Type" and I haven't found any DTD outside VBIOS/Addon/GopDriver, which means it is simply forcing a specific timing, despite my attempts to disable the 5F40h hook.

Until your new screen arrives, here are some other things to test. Do you get any higher screen resolution than 1024x768? What happens when you change the aspect ratio setting (Proporzioni in your first screen from here)? What happens when you apply this?

Since your BIOS is overriding any values in VBIOS, let's change a few things. First set Inverter Frequency to 200 and see if anything good or bad happens, then leave it at 200Hz. When you change "Panel Type" to "Other Panel", do you get a black screen no matter if in BIOS or Windows? The "Other Panel" is needed to have the VBIOS decide the timings. When you change "LVDS Control" = Disable and "LVDS Control Function" = Disable, does it still sets 1024x768 as default? My first guess is that they should be set to Disabled, to let the VBIOS decide.

The last two tests for VBIOS I can think off. Unpack and overwrite the files in the previous working folder. Run biosbck.bat, run #Any_Update.bat and type 9, then run biosrefl2.bat. This will set 1024x768 as default panel, maybe it will somehow stretch the screen. Even if it works, the end result might not be pleasing.

The last test is to hack the default timings for 1024x768 and change them to 1024x600. Run biosbck.bat, run #Any_Update.bat and type 10, then run biosrefl2.bat and reboot. You should probably also test with "Panel Type" = "Other Panel" and "LVDS Control" = Disable + "LVDS Control Function" = Disable. Restart and check: if the screen turns black, leave them at default and test as it is.

As a last attempt, have you tried Linux, where Ubuntu and Mint are strong recommendations?

Zitat von lordkag im Beitrag #23

---

@ween

First of all, there is no problem with "The data is identical". If you read the above 3 lines, you will see that it compares the updated BIOS region with the flashed biosbck.bin, to make sure that there were no errors during flashing.

I think you are at the end of the line. It is better to buy a new 1024x768 LVDS screen, which will give you: native support from BIOS, full UEFI support (works with CSM disabled), no need to mess with BIOS+drivers. It is my impression that any 1024x768 will work, but you should make sure that the supplier has a return policy, otherwise buy the same screen as offered in BIOS setup. When you get one, install the original BIOS and clean install drivers as advised before.

There are several reasons why I think the netbook screen is not supported by your mainboard. It is a netbook screen and your BIOS has support for only 1024x768, 1366x768 and 1920x1080 screens. The timings from Eee PC for 1024x600 require Inverter PWM Normal at 20000Hz, your BIOS offers PWM Inverted at 0-250Hz. Your BIOS overrides the VBIOS timings with the ones from "Panel Type" and I haven't found any DTD outside VBIOS/Addon/GopDriver, which means it is simply forcing a specific timing, despite my attempts to disable the 5F40h hook.

Until your new screen arrives, here are some other things to test. Do you get any higher screen resolution than 1024x768? What happens when you change the aspect ratio setting (Proporzioni in your first screen from here)? What happens when you apply this?

Since your BIOS is overriding any values in VBIOS, let's change a few things. First set Inverter Frequency to 200 and see if anything good or bad happens, then leave it at 200Hz. When you change "Panel Type" to "Other Panel", do you get a black screen no matter if in BIOS or Windows? The "Other Panel" is needed to have the VBIOS decide the timings. When you change "LVDS Control" = Disable and "LVDS Control Function" = Disable, does it still sets 1024x768 as default? My first guess is that they should be set to Disabled, to let the VBIOS decide.

The last two tests for VBIOS I can think off. Unpack and overwrite the files in the previous working folder. Run biosbck.bat, run #Any_Update.bat and type 9, then run biosrefl2.bat. This will set 1024x768 as default panel, maybe it will somehow stretch the screen. Even if it works, the end result might not be pleasing.

The last test is to hack the default timings for 1024x768 and change them to 1024x600. Run biosbck.bat, run #Any_Update.bat and type 10, then run biosrefl2.bat and reboot. You should probably also test with "Panel Type" = "Other Panel" and "LVDS Control" = Disable + "LVDS Control Function" = Disable. Restart and check: if the screen turns black, leave them at default and test as it is.

As a last attempt, have you tried Linux, where Ubuntu and Mint are strong recommendations?

---

I analyzed a bit deeper and I can 90% tell you that it is a hardware problem, your LVDS connector is not able to provide the requested frequencies asked by your netbook (!) screen, which should be expected. Bottom line, buy a new screen with resolution from 1024x768 and above. Following is the explanation. The VBIOS provide 16 panels type by default:



Your BIOS has 4 default values to select. Notice how the values are linked with the resolutions from above screen. I think Gigabyte has opted to put a particular screen name (instead of the default resolutions) to avoid users complaining that another screen doesn't work, i.e. "we support only these screens". In theory, any screen with 1024x768, 1366x768, 1920x1080 and 1440x900 should work out of the box (the timings are at default) and any other normal screen after patching the VBIOS.



And this is how it passes the selected value, by using the 5F40 hook in VBIOS Addon. I repeat, there is no timing outside VBIOS/Addon/GopDriver, all it does it selects one of those 16 panels, which can be changed as the OEM pleases. Before you ask, yes I disabled those hooks and I've done a hole lot of other things to no avail:



Now, the real problem. Your netbook screen needs these values, but your mainboard can only offer 0-250Hz, which I think is available for 1024x768 and above:



Your BIOS is set to PWM Inverted by default and the setting is hidden. If you want to test with PWM Normal, download the rar, unpack to previous folder. Run biosbck.bat, run unlock.bat, run biosrefl2.bat, reboot and look for:
BIOS -> Chipset -> (SA) Configuration -> Graphic Configuration -> LCD Control -> Backlight Control

But the main problem remains the inverter frequency.

@lordkag
thank you so much.......
let me try to resume....
please correct me if i'm wrong:

1. there are 16 panel type with different resolution preset, but only 4 displayed in bios menu with "alias" name.....just curious to know, one day, if i have one of the other 12 panel resolution on the list, how to accessing it?
2. if you already disable the hooks, it means, i can override the windows registry again with chance of success? since there are no linkage again between windows/intel hd driver with vbios.
3. i know, the real problem is about the frequency......so, if i buy another screen panel, let say 1366x768, i need to check their required inverter frequency? or just any 1366x768 screen can be match easily with this motherboard?
4. i will try again your bios mod tommorow, and hope so there are (SA) Configuration -> Graphic Configuration -> LCD Control -> Backlight Control at bios chipset tab.

best regards, and once again, thanks a bunch.

1. Need to disable the System BIOS Hooks and select the panel in the first screen. But I doubt you will be able to do that by yourself, this needs to be done to VBIOS and Addon. This only applies to LVDS connections, HDMI/DVI/DP should work by default.
2. No. There is nothing you can do, because the timings are not supported, specifically the inverter is not capable of supporting your netbook screen, thus it falls back to default 1024x768. I don't think you can solve this hardware issue.
3. Any 1024x768, 1366x768, 1440x900 (as "other type") should work. Maybe you only need to set PWM Normal at 200Hz, but I think Gigabyte has already set them up as needed.
4. Report back. I think I might also need to remove some "suppress if" in Setup.

@lordkag
already executed, and here is it:
BIOS -> Chipset -> (SA) Configuration -> Graphic Configuration -> LCD Control -> Backlight Control

@ween

Before you read the following, please note that I still strongly recommend that you should buy a new 1024x768 or 1366x768 or 1920x1080p screen, to have full support, better image and no strange scaling. Once you do this, flash original BIOS, clean install video drivers, test with PWM Normal at 200Hz or PWM Inverted at 200Hz. It is more than likely that it would work.

I decided to add some last tests, because it turns out I trusted too much in the VBIOS from Eee PC and the timings are not really appropriate for your panel. The real EDID and timings are the ones you extracted with MonInfo from laptop, without any video driver. It matches the pdf, plus it has the serial and manufacturing date. There are many tests because I had to work with the following variables: PWM Inverted/Normal, Inverter at 200Hz/20000Hz, SSC on/off, BIOS Hooks on/off. These are the last tests and only the first 6 (from 11 to 16) are important, the others are just variations in case the BIOS hooks are faulty. Decide for yourself how much do you want to torture your mainboard. Besides the proper timings, I also added the proper PnP ID, which means that the monitor should be fully detected by VBIOS+drivers.

Testing goes like this: inverter frequency always set at 200Hz, run biosbck.bat, run #Any_update.bat and input a number from 11 to 22 (in this order), run biosrefl2.bat, reboot and remove all the monitor devices under Device Manager -> Monitor. Windows should add a new PnP monitor.

After the first flash (number 11), reboot, remove monitors from Device Manager, clean install HD drivers, remove monitors once more. This is to acknowledge the new timings.
With tests 11-18, switch between first and second panel type in Chipset, test with both - they are running at 1024x600, but with 2 different timings from proper EDID. With tests 11-16, 19, 21 select PWM Normal; the rest with PWM Inverted. Or you can save yourself the memorizing and test with 1st/2nd panel and PWM Normal / PWM Inverted. I know there are a lot of testing, but it was also a lot of work.

I think none will work, being a hardware incompatibility. Treat yourself with a better screen.

Zitat von lordkag im Beitrag #29

---

@ween

Testing goes like this: inverter frequency always set at 200Hz, run biosbck.bat, run #Any_update.bat and input a number from 11 to 22 (in this order), run biosrefl2.bat, reboot and remove all the monitor devices under Device Manager -> Monitor. Windows should add a new PnP monitor.

After the first flash (number 11), reboot, remove monitors from Device Manager, clean install HD drivers, remove monitors once more. This is to acknowledge the new timings.
With tests 11-18, switch between first and second panel type in Chipset, test with both - they are running at 1024x600, but with 2 different timings from proper EDID. With tests 11-16, 19, 21 select PWM Normal; the rest with PWM Inverted. Or you can save yourself the memorizing and test with 1st/2nd panel and PWM Normal / PWM Inverted. I know there are a lot of testing, but it was also a lot of work.

I think none will work, being a hardware incompatibility. Treat yourself with a better screen.

---