Acer Aspire 5740G BIOS hacking (Switchable Graphics

sustmi · 08-29-2010, 04:56 PM

This notebook was proclaimed to have Switchable Graphics (ATI Mobility Radeon 5xxx & Intel Core i3/i5 Integrated Graphics).
Unfortunately there were probably some issues with drivers prior to release the notebook, so Acer has disabled this feature by software (BIOS) (downloads mentioned it many times).

I've been trying to enable the support Switchable Graphics, but without success yet.

Well, there were some interesting things I've discovered yet and I want to share those with other people interested in getting SG in their Aspire 5740G. Maybe somebody could help to get this done.

(if you are interested in the full story, just continue to the second post)

So far we can:
Enable hidden "Intel" tab in BIOS Setup.
Hidden "Intel" tab can be enabled by setting the CMOS token 0x141 to value 1.
See the second post in this thread. Chapter 4 describes the process of setting token's value.

WARNING: DO NOT SET "MCH Control Sub-Menu"→"Primary Display" TO EITHER "IGD" OR "SG" ! (unless you know how to unbrick your BIOS)

CRISIS RECOVERY DISK >>> HERE <<<

Final update: Switchable Graphics is not supported by the hardware.
Look at my comment here: Acer Aspire 5740G BIOS hacking (Switchable Graphics - not yet) (starsay, thank you for photos)

sustmi · 08-29-2010, 04:56 PM

1. Preface
As I mentioned before there are rumours that SG was disabled in BIOS just before Acer started to sell 5740G. So I realized there could be some option in BIOS Setup enabling this feature.

There is a tool called Phoenix Bios Editor which can help reveal hidden items in Phoenix BIOSes.
Unfortunately it looks like there is not a version (a leaked one) which can handle BIOS images for Aspire 5740G.

After some digging through internet I found very helpful post which describes how to decode Phoenix BIOS to enable VT-d (Virtualization Technology):
http://forum.notebookreview.com/6124996-post38.html (I will be referencing to it)
It doesn't bother with description how to get those files STRINGS00.ROM and TEMPLAT00.ROM.
There is another tool called Phoenix SLIC mod which can extract (and replace) individual files from Phoenix BIOS image.

2. Brief explanation of TEMPLAT00.ROM and STRINGS00.ROM files
It didn't take much wakeful nights to find that offset 0x232 in TEMPLAT00.ROM contains "links" to Setup menu tabs:
(All informations are related to BIOS version 1.22)

Code:

Offset      0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F

00000230   00 00 77 0D 4E 02 81 0D  86 02 8B 0D DE 02 A9 0C   ..w.N...†.‹.Ţ.©.
00000240   D6 03 F1 18 C0 09 FF 14  B4 07 00 00 00 00         Ö.ń.Ŕ.˙.´.....

(RED are addresses of something like menu item headers, while BLUE are addresses of lists of menu items (both are offsets in TEMPLAT00.ROM)
77 0D → 0x0D77 = "Information"
81 0D = "Main"
8B 0D = "Security"
A9 0C = "Intel"
F1 18 = "Boot"
FF 14 = "Exit"

Yes, there is a hidden "Intel" tab in BIOS setup.
If we look to offset 0x0D77 we can see:

Code:

Offset      0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F

00000D70                        10  0A 48 05 00 00 A7 35 B2          ..H...§5˛
00000D80   35                                                 5

10 = record type (please read excursion quote block in this post for further explanation)
48 05 → 0x548 = address in string table in STRINGS00.ROM which links to string "Information" (again this post describes how to work with STRINGS00.ROM)
0A = total record length (= 10 bytes)
00 00 = don't know (maybe second string can be specified here)
A7 35 = first jump address
B2 35 = second jump address

The jump addresses points to executable code in TEMPLAT00.ROM.
Disas*embled (prohibited) code at the offset A7 35 → 0x35a7 looks like this:

Code:

35A7                 push    bp
35A8                 mov     bp, sp
35AA                 call    sub_35AF
35AD                 pop     bp
35AE                 retf
35AF sub_35AF        proc near
35AF                 xor     ax, ax
35B1                 retn
35B1 sub_35AF        endp

The only thing this code does is that it returns 0 from the function (in AX register).

The return value of these functions (called "Fillers" in referenced post) can somehow influence whether the menu item (in this case "Information" tab) will be visible.

That's enough to know about "item headers".
Now I will shortly describe how the actual menu items in "Information" tab are stored.
Lets go back and look at offset 4E 02 → 0x24e:

Code:

Offset      0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F

00000240                                              91 18                 ‘.
00000250   00 00 85 18 00 00 A9 18  00 00 C7 0F 00 00 91 2C   ..…...©...Ç...‘,
00000260   00 00 FB 0C 00 00 EF 0C  00 00 2F 0D 00 00 AB 0D   ..ű...ď.../...«.
00000270   00 00 B7 0D 00 00 C3 0D  00 00 CF 0D 00 00 9F 0D   ..·...Ă...Ď...ź.
00000280   00 00 00 00 00 00                                  ......

These offsets contains individual menu items. For example 91 18 → 0x1891:

Code:

Offset      0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F

00001890      11 0C B0 02 00 00 78  69 83 69 8F 69             ..°...xiƒi.i

Please visit excursion quote block in the referred-to post which describes this structure pretty well.
Only thing I mention here is address B0 02 → 0x2b0 which is string "CPU Type:" (this is the first item in "Information" tab in setup menu).

This was explanation how the menu structure looks like.
And now the more interesting part the "Intel" tab.

3. Figuring out the "Intel" tab
If we use the same process for "Intel" tab (offset A9 0C → 0xca9) we will get this:

Code:

Offset      0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F

00000CA0                               10 0A 52 05 00 00 2F            ..R.../
00000CB0   32 59 32                                           2Y2

52 05 = "Intel" string
2F 32 = first function
59 32 = second function

Here is code from offset 0x322F:

Code:

322F                 push    bp
3230                 mov     bp, sp
3232                 call    sub_3237
3235                 pop     bp
3236                 retf

3237 sub_3237        proc near
3237                 push    dx
3238                 mov     ax, 141h
323B                 call    sub_5ED0 ; reads token AX, returns the value to AX
323E                 pop     dx
323F                 cmp     al, 1
3241                 jz      short loc_3245
3243                 jmp     short loc_3255
3245 loc_3245:
3245                 xor     ax, ax
3247                 call    far ptr 0F000h:4443h
324C                 test    al, 4
324E                 jnz     short loc_3255
3250                 mov     ax, 0
3253                 jmp     short locret_3258
3255 loc_3255:
3255                 mov     ax, 13h
3258 locret_3258:
3258                 retn
3258 sub_3237        endp

This is not that simple like return 0;.

The important thing is part 0x3238-0x323B where the token number 0x141 is read and then 0x323F-0x3241 where token's value is compared with 1.
The function simply does something like this (in C language):

Code:

int sub_3237() {
  if (read_token(0x141) == 1) {
    // ... some non-important stuff :-)
    return 0;
  } else {
    return 0x13;
  }
}

Return value 0x13 means something like: No don't display the menu item.
So if we want to make "Intel" tab visible we must set token 0x141 to 1.

Second function 59 32 is just another return 0; code.

4. Setting the NVRAM token value
Tokens are stored in BIOS CMOS (NVRAM) area. If we want to set the values we possibly could make the changes in $NVT section of ROMEXEC.ROM file.
This area stores BIOS Default Settings. (I will not describe this any further.)
But I failed to do this, because of breaking the checksum of CMOS.
(After flashing BIOS image modified this way and rebooting the notebook signalled the checksum error using speaker beep code.)

Much cleaner method to set token's value is using the SYMCMOS tool.
There are many posts that closely describes the process of setting tokens.
For example this one: How to Enable Intel VT and AHCI on a Napa/Santa Rosa platform Phoenix BIOS Vaio laptop
In a nutshell:

Quote:

Boot to DOS
type: symcmos -V2 -Lcmos.sav
edit the generated cmos.sav file and replace line
(0141) [0000]
to
(0141) [0001]
type: symcmos -V2 -Ucmos.sav
reboot

Now when we enter the Setup we can see the new "Intel" tab.

There are new many options we can "play" with. (Read the next chapter before any experimenting!)
But can finally enable the Switchable Graphics functionality here?
Bad news. It looks like it cannot be enabled this way.

5. Playing with the options in "Intel" tab
In "Video (Intel IGD) Control Sub-Menu" there is option "IGD - Device 2".
Possible values are:

Code:

0: [Disabled]
1: [Auto] (default)

We are unlucky here, because "IGD - Device 2" is already set to "Auto" and as we know there is no Intel Graphics among PCI devices in Device Manager (in Windows).
I didn't discover any function of this option (whether is set to "Auto" or "Disabled" IGD is not enabled).

In "MCH Control Sub-Menu" there is option "Primary Display".
Possible values are:

Code:

0: [Auto] (default)
1: [IGD]
2: [PEG]
3: [PCI]
4: [SG]

Two of these values looks pretty good: IGD (abbreviation for "Integrated Graphics Device") and SG (abbreviation for "Switchable Graphics")
! DO NOT SET ANY ANY OF THESE TWO VALUES !
Please do not set "Primary Display" to either "IGD" or "SG".
I tried and it bricked my notebook. My notebook didn't booted any more.
I had to clear CMOS settings to defaults by reflashing using Crisis Recovery Disk. (But removing the CMOS battery should be sufficient, too).

By contrast setting to "Auto", "PEG" or "PCI" does - what's the word - NOTHING.
It looks like guys in Acer really wanted not to give us this feature (not that "easy").

Here I'd like to announce that my configuration is 5740G-334G64MN (LX.PMB02.258).
(Core i3-330M, ATI Mobility Radeon HD 5650 1GB, 4GB RAM, Windows 7 Home Premium)

As I know this CPU (Core i3-330M) has integrated graphics, but if anybody with Core i5 have courage and working Crisis Disk you can test the setting "IGD" or "SG".
(Of course I take no responsibility for bricking your lappy, it's only your decision. Not talking about loss of warranty and potential illegality of this whole thing.

)

6. Another hidden option in BIOS Setup
Going through STRINGS00.ROM file I found string "Graphic Mode:".
So I backtracked the menu item which uses the string.
String is at offset 0x5AEA (it is not an actual offset in STRINGS00.ROM, because the file has a 28 bytes long header).
If you search EA 5A in STRINGS00.ROM you will find record in address table at 0x6a6.
Searching for A6 06 in TEMPLAT00.ROM will give you two results: 0xddd and 0xdf5.

The first one is part of menu item (starting at 0xddb):

Code:

00 18 a6 06 a8 06 de 37 30 38 0b 38 16 38 3b 01 b8 06 00 00 b4 06 00 00

Human readable:

Code:

Graphic Mode:
---
Functions: 0x37DE, 0x3830, 0x380B, 0x3816
Token: 0x13B
0: [Switchable]
1: []
2: [Discrete]
3: []

(The second one "Graphic Mode" is similar menu item, but it has 1: [Integrated] and 2: [] and it looks like it isn't used in any menu.)

Further backtracking (searching for DB 0D) will bring us to address 0x2a2.
Here we are somewhere in the middle of list of menu items.
This list begins at 0x286 (what a luck

).
Bytes 86 02 are at 0x238 (the second occurrence at 0x205b is only coincidence).
Yes, we've already been near this address. Remember the chapter 2?
Actually, we've just found that item "Graphic Mode:" is placed in tab "Main". More precisely between items "Video Memory" and "Quiet Boot:".

Now let's find out why the option is hidden.
Function at 0x37DE is wrapping function (only it does is calling another function) for another function at 0x37E6:

Code:

37E6 sub_37E6
37E6                 push    dx
37E7                 mov     dx, 11B8h
37EA                 in      eax, dx
37EC                 and     eax, 20h
37F0                 jnz     short loc_3806
37F2                 mov     ax, 13Bh
37F5                 call    read_token_sub_5ED0
37F8                 cmp     al, 1
37FA                 jnz     short loc_3801
37FC                 mov     ax, 13h
37FF                 jmp     short loc_3809
3801 loc_3801:
3801                 mov     ax, 0
3804                 jmp     short loc_3809
3806 loc_3806:
3806                 mov     ax, 13h
3809 loc_3809:
3809                 pop     dx
380A                 retn
380A sub_37E6        endp

OK, here is C interpretation (better, isn't it?):

Code:

int sub_37E6() {
  if (cpuio_in(0x11b8) & 0x20 == 0) {
    if (read_token(0x13b) != 1) {
      return 0;
    }
  }
  return 0x13;
}

Address 0x1180 is base offset of GPIO (General Purpose Input-Output) registers (now we talk about CPU I/O address space).
GPIOs in principle are pins which can be configured either as input or as output. They are used in digital circuits for various purposes.
Commonly GPIO pin is configured as input and used to read some status in circuit (eg. button press) or configured as output pin to control other devices in circuit (eg. powering them up and down, blinking LED).
Register 38h (0x1180+0x38=0x11b8) is GP_LVL2 (GPIO Level for Input or Output 2). Each bit in this register corresponds to one GPIO pin.
From Intel's manual p.552:

Quote:

Register corresponds to GPIO[63:32]. Bit 0 corresponds to GPIO32.

So cpuio_in(0x11b8) & 0x20 is nothing else than reading pin GPIO37.

To sum it up, if we want the option "Graphic Mode" visible then GPIO37 must be 0 (low) and NVRAM token 0x13b must not be equal 1.
The question is what's connected to GPIO pin 37.
(At this point it would be very useful to have motherboard schematic diagram.
This notebook has motherboard "JV50-CP" build by Wistron.
I found few sites specialized on notebook motherboard schematics, but haven't found schematics for this motherboard yet).

The second function 0x3830 I haven't understood yet (but returns 0 in default, so don't care of it).
The third function 0x380B is "returns 0;".
The fourth function 0x3816 wraps 0x381E:

Code:

sub_381E proc near
push    dx
mov     ax, 13Bh
call    read_token_sub_5ED0
mov     dx, 3C3h
call    write_token_sub_5EF3
pop     dx
mov     ax, 0
retn
sub_381E endp

This function always returns zero, so it doesn't look interesting. Actually it is partially interesting. Let me explain.
When we discussed the "Primary Display" option in chapter 5, I talked only about possible values. Here is whole detail of this option:

Code:

Primary Display
---
Select which of 
IGD/PEG/PCI
Graphics device
should be Primary
Display
Filters: 0x7AB6, 0x7ACC, 0x7AD7, 0x7AC1
Token: 0x3C3

0: [Auto]
1: [IGD]
2: [PEG]
3: [PCI]
4: [SG]
5: []
6: []
7: []

The interesting part is the token address 0x3C3.

Maybe I should explain one thing first. The main purpose of NVRAM tokens is to store the selected value of option in BIOS Setup.
For example if we set option "Graphics device" to value "PEG", then token 0x3C3 will hold value 2.

No what sub_381E does? Setting "Graphic Mode" (token 0x13B) is automatically stored to the token 0x3C3 aka. "Primary Display", too.
Eg. If we set "Graphic Mode" to "Switchable" then "Primary Display" is automatically set to "Auto" and setting "Graphic Mode" to "Discrete" sets "Primary Display" to "PEG".

Actually it looks like the only purpose of "Graphic Mode" option is controlling the "Primary Display" option.

And as we realized before (chapter 5), IGD can't be enabled simply by "Primary display" option (will not boot).
I thing the only useful information from this chapter is that there is something connected to GPIO37 input pin.
The open question is what is connected there.

7. ACPI SSDT Tables
I think we already need some optimistic information.
Do they (Acer) really worked on Switchable Graphics for this laptop or is it only a myth (and the BIOS Setup options are only coincidence)?
I want show you an evidence that Acer meant it seriously with Switchable Graphics.

First of all, we need to know what are ACPI SSDT tables.
In a nutshell, DSDT and SSDTs are tables which describes ACPI-compliant hardware which is present in the system.
A table consists of objects (eg. pci device), methods (eg. power-up) and data.
There is exactly one DSDT table and zero or more SSDT tables. The DSDT table is part of the system fixed description. It is loaded always when BIOS boots and cannot be unloaded. SSDT tables can extend (but not override) DSDT table.
More detailed information can be found here: http://www.drdobbs.com/mobility/222600829?pgno=3

I the first chapter I mentioned the Phoenix SLIC mod.
This tool extracts individual files from BIOS image.
Most of the files are the uEFI BIOS modules.
Also there is a file ACPI00.AML. This file contains compiled DSDT table.
You can decompile this file into DSL source code using iASL compiler.
Running the following command will do the job:

Code:

./iasl.exe -d ACPI00.AML

This will create a new file ACPI00.dsl, which contains decompiled source code of DSDT table in ACPI Source Language.

There is another file 697CFA95-B1F2-4ED7-A0D2-7AC6E47B3C99.ff.
If you look inside this file you can see well known MZ-PE header.
Yes, in fact this file is 64-bit Portable Executable file.
You can copy the content starting at 0x84 to a new file with suffix .DLL and then open it in your favourite disassembler.

After some digging I found this string in the file.

Code:

E:\JV50CP\fw\PROJECT\JV50\X64.VS2005.GreenHV1\X64\HybridGraphicDxe.pdb

So the original name of this module is HybridGraphicDxe.

After deeper investigation of this module I found that a sub-procedure at 0x186C loads PCI Vendor ID of PCI device located at 02:00.0 (bus=2, device=0, function=0) address in PCI tree.
This is the address of discreete VGA adapter on PCI-Express bus.
If the Vendor ID is 0x10DE (NVIDIA Corporation) it loads value 8E8FF4521D9E1C834F5434D87E1CABE3h into register xmm0.
If the vendor ID is 0x1002 (ATI Technologies Inc. / Advanced Micro Devices, Inc.) it loads value C706F61DD7E9278C42CA77DE76AED82Eh to the same register.

I haven't realised what exactly it does with this value yet.
But I guess that it loads the SSDT table from module identified by corresponding GUID.
You may already noticed that the uEFI BIOS modules are extracted to files named as some kind of hashes.
Actually every uEFI module has this unique GUID number.

Let's transform hexadecimal number C7 06 F6 1D D7 E9 27 8C 42 CA 77 DE 76 AE D8 2Eh
into this string (note that last two fields are backwards): 76AED82E-77DE-42CA-8C27-E9D71DF606C7.

Actually this is GUID number of another extracted file.
Inside this file (76AED82E-77DE-42CA-8C27-E9D71DF606C7.PEI) you can find "SSDT" string which starts a SSDT table.
Just copy the content of this file starting at offset 0x1c into a new file, eg. AMD.aml.
Now extract the AMD.aml using the iASL tool.

Code:

./iasl.exe -d AMD.aml

The decompiled AMD.dsl file is the interesting part of this chapter.
This SSDT Table defines methods _ON and _OFF to scope _SB.PCI0.P0P2.PEGP (discreete graphic card).
It's not a big surprise that these two methods can switch on/off the discreete graphics card.
Additionally the table defines method ATPX to scope _SB.PCI0.GFX0 (integrated graphics card).
The ATPX method can be called by operating system (or graphics card driver) to switch between integrated and discreete graphics cards.

Normally this SSDT table is not loaded. There's one condition that must be met so that sub-procedure 0x186C is called.
The input value on GPIO 37 pin must be zero. Again that mysterious GPIO 37 pin!

8. So AMD never released drivers with SG support?
Here is another one evidence that Acer really worked on Switchable Graphics for model Aspire 5740G.
There are rumours that Acer disabled this feature because there weren't drivers available when the model was released.

I fact there is one version of drivers VGA_AMD_8.713.3.3000_Win7x64 which looks like it supports chable Graphics for Aspire 5740G.
You cat get it from Acer support page if you choose model Aspire 5820TZG (direct link).

Extract the ZIP archive and go into the following folder: VGA_AMD_8.713.3.3000_Win7x64\Packages\Drivers\Display\W76A_INF
Here you can see two interesting things.
The first one is the "Intel" folder, which contains drivers for integrated graphics.
The second one is the file C7_99253.inf which contains description of AMD/ATI graphics drivers.
Look into this file and search for sting "JV50-CP" (Aspire 5740G platform name).
You will find this line:

Code:

%iILKGM0_SG% = iILKM1_PROXY, PCI\VEN_8086&DEV_0046&SUBSYS_033F1025 ; Acer/Wistron JV50-CP

Strange thing is that my laptop has subsystem ID 033E1025 not 033F1025.

But SUBSYS_033E1025 is also mentioned in this file.
Here are all the occurrences of "SUBSYS_033F1025":

Code:

"ATI Mobility Radeon HD 5470     " = ati2mtag_Manhattan_PXAI, PCI\VEN_1002&DEV_68E0&SUBSYS_033F1025
"ATI Mobility Radeon HD 5650          " = ati2mtag_Manhattan_PXAI, PCI\VEN_1002&DEV_68C1&SUBSYS_033F1025
%iILKGM0_SG% = iILKM1_PROXY, PCI\VEN_8086&DEV_0046&SUBSYS_033F1025 ; Acer/Wistron JV50-CP

And here are all occurrences of "SUBSYS_033E1025" (my laptop):

Code:

"ATI Mobility Radeon HD 5470              " = ati2mtag_Manhattan_PRAI, PCI\VEN_1002&DEV_68E0&SUBSYS_033E1025
"ATI Mobility Radeon HD 5650                        " = ati2mtag_Manhattan_PRAI, PCI\VEN_1002&DEV_68C1&SUBSYS_033E1025
%iILKGM0% = iILKM0, PCI\VEN_8086&DEV_0046&SUBSYS_033E1025

I marked the main differences.
You can see that JV50-CP from the file has ati2mtag_Manhattan_PXAI while my laptop has ati2mtag_Manhattan_PRAI.
At the beginning of this INF there's following comment:

Code:

; PX - PX Proxy mode
; PR - PX Proxy Ready

So their JV50-CP has "PX Proxy mode" while mine is "PX Proxy Ready".

It looks like there are drivers that could be able to do Switchable Graphics.
But note that this drivers are installed only if there is present a PCI device with Vendor ID 8086, Device ID 0046, Subsystem Vendor ID 1025 and Subsystem Device ID 033E (or 033F or any else from the list in the INF file).

9. Will there be working SG on Aspire 5740G ever?
You probably don't want to hear this answer... but I don't know.

Sometimes it looks like we already were very close to the goal and sometimes I want to give it up...

I have already mentioned it few times, but in this stage it will be very helpful to have schematics of the laptop's motherboard, so we can finally puzzle out what is that mysterious GPIO 37 input pin. There are few sites which sell laptop schematics, but I haven't found any that provides schematics for this laptop, yet.

Also I would appreciate if anybody who has Aspire 5740 without discreete graphics card could help us to get some low-level informations (eg. PCI configuration registers) from working system with IGD.

I'm very sorry, but I will no more update this post as I don't have enough time to write this "hacking guide".
Instead, I will post short updates in this thread any time I get some new interesting informations about Switchable Graphics on this laptop.
---
If you got this far thanks for reading.

nando4 · 08-29-2010, 08:39 PM

Quote:

Originally Posted by sustmi

..and most recent Trying DIY ViDock Setup tool).
If you got this far thanks for reading.

With the DIY ViDock testing I found that XP uses a round-robbin method to try and use whatever video card is acive. Win7 uses only the post device so it's not possible to disable the discrete graphics prior to chainloading into Win7.

Now other problem is I believe the switchable graphics *probably* just checks for an assert signal when the ATI/NVidia card is active and drives it's LVDS signals through it. So the discrete graphics would need to be disabled with the equivalent of 'setpci -s 0:0.0 54.w=0:2' for the IGP to be able to display anything. The switching designed to boot with the IGP active.

Knowing the limitation with Win7 requiring the post device active would mean needing to hot-switch to the IGP. Eg:

- boot with the discrete graphics active into DIY ViDock Setup
- ensure IGP is enabled, perform compaction on it.
- boot Win7, ensure there is no error 12 against the IGP.
- disable the discrete graphics using scripting, hwdirect/r-w everything
- do a device manager scan (devcon) to get it to now switch to the IGP.

The above is all hypothetical but I believe it adds some more variables to the mix that have not bee considered. XP would be easier to get going as a proof-of-concept.

kizwan · 08-29-2010, 11:21 PM

@sustmi, one reputation from me. Good discussion thread. Yes, we can find a lot of information when tracing the offset. I believe you will be able solve the 5740G's switchable graphic card mystery. I have one request though. Can you share the CRISIS package for 5740G, including the BIOS recovery procedure & also the type of media you use (Floppy, USB flash drive, etc)? This will help a lot of people. Most unsuccessful BIOS recovery is because they're using wrong media (USB flash drive instead the floppy disk).

davigar · 08-30-2010, 07:48 AM

In first time sorry for my english.

One question, in the 1.22 bios is updated the bios of the graphics with the intel bios unusable switchable graphics option in full. Have you tested with any previous version of BIOS if you change to have a choice?

downloads · 08-30-2010, 12:23 PM

Quote:

Originally Posted by kizwan

@sustmi, one reputation from me. Good discussion thread. Yes, we can find a lot of information when tracing the offset. I believe you will be able solve the 5740G's switchable graphic card mystery. I have one request though. Can you share the CRISIS package for 5740G, including the BIOS recovery procedure & also the type of media you use (Floppy, USB flash drive, etc)? This will help a lot of people. Most unsuccessful BIOS recovery is because they're using wrong media (USB flash drive instead the floppy disk).

I second that request- if you've already recovered 5740G could you please share the package and describe the process- preferably in the first post so that those who try and fail know what to do.

And my polite request to other posters- if you cannot contribute technically to this thread don't post here. Questions like "why did Acer disable SG" and similar do not help in any way especially that it's been already answered multiple times. Let people who really do something discuss the matters- keep other matters in the Owners Lounge. Thanks

sustmi · 09-01-2010, 05:40 PM

CRISIS RECOVERY DISK:
Build:
1. Download this archive containing WINCRIS utility and Aspire 5740G BIOS v1.22
2. Insert your USB flash drive
3. Run WINCRIS.EXE (in Vista and 7 you will need "Run as Administrator")
4. Select your drive and leave other options on default
5. Press "Start" (will overwrite all data on selected drive!!!)

Usage:
1. Turn notebook off
2. Press and hold keys: Fn + ESC
3. Turn notebook on
4. Release the keys (approx. 10 seconds after powering up)
5. Wait for until flashing process completes

It should take approx. 5 minutes and all the time screen should be black.
After flashing it automatically reboots (if not, CRISIS DISK is probably not build correctly or your flash drive is somehow not supported).

Arelenia · 09-05-2010, 09:08 AM

Hey, i found a way to open the BIOS-File with Phoenix BIOS Editor. Or better, Kizwan found the way. I only read his post in the Phoenix Bios Modding Request Thread. It's an introducing how to open a BIOS file from a PackardBell Notebook, but this notebook has the same bios like the 5740G. I tried it and it works, but i have no idea how to use PBE. But maybe someone other can use it to find a solution. I copy his post:

"
It is original BIOS. I haven't modified it yet because this BIOS have same problem as Aspire 5740G have; PBE can't open the BIOS image without error. The Intel menu is there the whole time. It is hidden from end-user. I can unhidden it but I'm not sure if PBE can re-build the BIOS image successfully (meaning without bricking your notebook). I was going to modify it, just take my time to do research about it a little bit.

In the meantime, if you want to take a look yourself:-
1) Download the BIOS image from (packard bell) Acer website
2) Extract it & go to DOS folder
3) Open the JV50122.WPH file with HEX editor
4) Split JV50122.WPH to three part:-
- 1st 200000 length: 000000 - 1FFFFF: save it as JV50122_1.ROM
- 2nd 200000 length: 200000 - 3FFFFF: save it as JV50122_2.ROM
- 3rd: 400000 - end: save it as JV50122_3.ROM
5) Open JV50122_2.ROM with PBE. At the first attempt, you will get "ROMEXEC not available!". Try open it again, PBE should be able to open it."

I used HxD as HexEditor and PBE 2.2.13 beta. I got some messages that some modules were not found, I clicked yes to continue.
I hope it helps someone to help us =)

davigar · 09-10-2010, 05:30 PM

I've been trying to flash but I can not. My notebook has an i5 430M. You can put any easy way to flash it?

kizwan · 10-03-2010, 11:49 AM

Hi sustmi,

Have you tried enabling extra PCI express root port under "PCH Control Sub-Menu"? If you haven't play around with it, can you try enabling the extra PCI express root port? I we're lucky, it may enabled the Intel HD Graphics which may connected to one of the disabled PCI express root port. Please let us know the results. Thanks.