Welcome
|
You have to register before you can post on our site.
|
|
How To Update Award CPU Microcode
|
Posts: 4,248
Threads: 399
Joined: Apr 2009
Reputation:
62
CBROM BIOS.BIN /pci release - Then select the right rom
CBROM BIOS.BIN /logo release
I honestly dont know if removing the raid rom will break the bios. In theory if you arent using it then it shouldnt matter but you never know until you try
What I meant by TDP is there is a Phyiscal power limitation on some motyherboards which make them incompatible with certain cpus. For example people who want to run Phenom II's on their old boards sometimes cant because some Phenom II CPU's have a TDP of 125W and the board only accepts CPU's with a TDP of 95W or less. This means the CPU either doesnt work at all or runs at a highly reduced speed.
Admin
Posts: 112
Threads: 29
Joined: Oct 2009
Reputation:
0
01-25-2011, 12:48 PM
(This post was last modified: 01-25-2011, 12:51 PM by marcusj0016.)
any way to upgrade Intel i3 Microcode?
it's a clarkdale, i'd perfer to have that brand new Sandy Bridge microcode AVX, and anyother advanced microcodes too.
how do i do this with AMI?
Posts: 2,296
Threads: 62
Joined: Jul 2009
Reputation:
63
Hi marcus,
We can update any of the microcode you need. Please create a seperate thread so we don't contaminate this one, but if you post the board and the BIOS in question ina new thread I'll be happy to help you out.
TheWiz
Posts: 3
Threads: 0
Joined: Dec 2011
Reputation:
0
I've had CBROM 198 and 195 crash on me when trying to implement newer microcode on an M2NPV-MX BIOS. One error suggested it was a DEP issue, so I tried disabling DEP on that application (W7 x64) then I tried on a system with no hardware DEP (W2008 x86) and finally in a Windows 98 VM, all crashing when trying to implement the microcode. Any experience or assistance with this?
Posts: 8
Threads: 2
Joined: Jan 2012
Reputation:
0
Is there a way to update the M613Z_19.BIN bios to support Phenom 1 HD9500WCJ4BGD?
Posts: 223
Threads: 20
Joined: May 2010
Reputation:
9
here's my bios I just modded the microcodes. I included the instructions and tools
enjoy guys this should take the mystery out of the process.
https://docs.google.com/file/d/0B06TVjAy...sp=sharing
AMI Bios Section Moderator
By requesting, downloading, and flashing a modified
bios you are held responsible for what you choose
to do with it. flash at your own risk! And please
remember to let us know if our mods work for you!
Posts: 16
Threads: 5
Joined: Oct 2010
Reputation:
0
(04-17-2013, 06:25 AM)f3bandit Wrote: here's my bios I just modded the microcodes. I included the instructions and tools
enjoy guys this should take the mystery out of the process.
https://docs.google.com/file/d/0B06TVjAy...sp=sharing
Tutorial is really confusing.
I'd love to know how to do this because nobody will respond to my request for Turion 64 ML-34 support on my K8MM-V, even after saying I'd donate some coin to get it done.
I'm reluctant to even try it myself since the board doesn't have a removable BIOS chip, and a failed flash is going to brick it.
Posts: 5
Threads: 3
Joined: Jul 2013
Reputation:
0
07-05-2013, 09:05 AM
(This post was last modified: 07-14-2013, 03:03 AM by KOLANICH.)
1 Can we update Phoenix Bioses (as we know in fact they are Award) the same way?
2 How can we use microcodes from intel site?
my bios is http://msi.com/service/download/bios-7896.html
[offtop]
What else useful can I do with it?
[/offtop]
3 Code: ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД[compiled@07.09.2009]ДДД
BIOS Info Tool v1.4, Copyright(c) 2004 by Serge Galkin (StarGaz0r)
Win9x/Win2k/XP version e-mail: stargaz0r@nm.ru
НННННННННННННННННННННННННННННННННННННННННННННННННННННННННННННННННННННННННННН
ю ROM BIOS by Award Software International Inc., http://www.award.com/
BIOS ID Strings: 06/13/2008-Broadwater-6A79LM4CC-00, 6A79LM4C
Model: Phoenix - AwardBIOS v6.00PG (Medallion BIOS), 06/13/08
Vendor: Micro-Star International Co. Ltd.
Version String: W7235IMS V1.11 061308 11:10:04
Peripheral bus(es): ISA/PCI
ю BIOS update interface: awdflash hook
[ы] Supported Flash ROM Size: 8 Mbit
[ы] Flash Chip Block(s) Size: 64KB
[ы] NT Flash Support
ю Supported features:
[ы] IntelR ACPI 0.9/1.x
[ы] PCI IRQ Routing Table v1.0 (incorrect!)
[ы] EL TORITO CD-ROM Boot Specification
ю Award Decompression BIOS structure:
ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
No. Item-Name Original-Size Compressed-Size Original-File-Name
ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
0 System BIOS 20000h (128K) 153A0h (84,91K) 6A79LM4C.BIN
1 XGROUP CODE E7E0h (57,97K) 9A0Dh (38,51K) awardext.rom
2 ACPI table 4D96h (19,4K) 1CAFh (7,17K) ACPITBL.BIN
3 EPA pattern 168Ch (5,64K) 2AAh (0,67K) AwardBmp.bmp
4 YGROUP ROM A820h (42,03K) 52C1h (20,69K) awardeyt.rom
5 GROUP ROM[0] 54C0h (21,19K) 25C2h (9,44K) _EN_CODE.BIN
6 Other(4069:0000) 68A0h (26,16K) 68D7h (26,21K) MEMINIT.BIN
7 Other(4067:0000) 1E8Dh (7,64K) C9Ah (3,15K) PPMINIT.ROM
8 Other(4046:0000) 4B30Ch (300,76K) 9507h (37,26K) P4_01_BIOS5.bmp
9 Other(404E:0000) 34D0h (13,2K) 57Ch (1,37K) 64N8IMB.BMP
10 Other(404F:0000) 33E0h (12,97K) 938h (2,3K) 64N8IVT.BMP
11 Other(4050:0000) 33E0h (12,97K) 827h (2,04K) 64N8IPP.BMP
12 Other(4051:0000) 33E0h (12,97K) 73Bh (1,81K) 64N8ICP.BMP
13 Other(4052:0000) 33E0h (12,97K) 82Fh (2,05K) 64N8ICPO.BMP
14 Other(4053:0000) 33E0h (12,97K) 84Eh (2,08K) 64N8ICR.BMP
15 PCI driver[A] 7C00h (31K) 44A4h (17,16K) jmb361_1.06.63_raid.bin
16 PCI driver[B] A000h (40K) 5E5Fh (23,59K) RTGBPXE.LOM
(Realtek Semicon. Undefined Device was built before Class Code definitions were finalized BIOS)
ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
ю Award Decompression BIOS Modules Header CheckSum Status:
ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
No. Item-Name CheckSum Calculated-CheckSum Address Status
ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
0 System BIOS 45h 45h 10001h Correct
1 XGROUP CODE B1h B1h 253A2h Correct
2 ACPI table DBh DBh 2EDAFh Correct
3 EPA pattern 01h 01h 30A5Eh Correct
4 YGROUP ROM C5h C5h 30D08h Correct
5 GROUP ROM[0] 52h 52h 35FC9h Correct
6 Other(4069:0000) 74h 74h 3858Bh Correct
7 Other(4067:0000) 9Fh 9Fh 3EE62h Correct
8 Other(4046:0000) 60h 60h 3FAFCh Correct
9 Other(404E:0000) C7h C7h 49003h Correct
10 Other(404F:0000) D1h D1h 4957Fh Correct
11 Other(4050:0000) E1h E1h 49EB7h Correct
12 Other(4051:0000) EAh EAh 4A6DEh Correct
13 Other(4052:0000) 0Fh 0Fh 4AE19h Correct
14 Other(4053:0000) E3h E3h 4B648h Correct
15 PCI driver[A] 53h 53h 4BE96h Correct
16 PCI driver[B] 2Bh 2Bh 5033Ah Correct
ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
ю Award Decompression BIOS Main CheckSums Status:
ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
No. Item-Name CheckSum Calculated-CheckSum Address Status
ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
0 System BIOS FFh 90h 253A0h Wrong
1 XGROUP CODE ДДД 70h ДДДДДД Absent
2 ACPI table ДДД 29h ДДДДДД Absent
3 EPA pattern ДДД 40h ДДДДДД Absent
4 YGROUP ROM ДДД 94h ДДДДДД Absent
5 GROUP ROM[0] ДДД 11h ДДДДДД Absent
6 Other(4069:0000) ДДД 1Fh ДДДДДД Absent
7 Other(4067:0000) ДДД 50h ДДДДДД Absent
8 Other(4046:0000) ДДД 0Ch ДДДДДД Absent
9 Other(404E:0000) ДДД 76h ДДДДДД Absent
10 Other(404F:0000) ДДД C4h ДДДДДД Absent
11 Other(4050:0000) ДДД EAh ДДДДДД Absent
12 Other(4051:0000) ДДД 3Ch ДДДДДД Absent
13 Other(4052:0000) ДДД CFh ДДДДДД Absent
14 Other(4053:0000) ДДД F0h ДДДДДД Absent
15 PCI driver[A] ДДД 74h ДДДДДД Absent
16 PCI driver[B] ДДД 01h ДДДДДД Absent
ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
ю Award Decompression BIOS Map:
ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
No. Item-Name Start Address End Address Original-File-Name
ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
0 System BIOS 10000h 253A0h
1 XGROUP CODE 253A1h 2EDAEh
2 ACPI table 2EDAEh 30A5Dh
3 EPA pattern 30A5Dh 30D07h
4 YGROUP ROM 30D07h 35FC8h
5 GROUP ROM[0] 35FC8h 3858Ah
6 Other(4069:0000) 3858Ah 3EE61h
7 Other(4067:0000) 3EE61h 3FAFBh
8 Other(4046:0000) 3FAFBh 49002h
9 Other(404E:0000) 49002h 4957Eh
10 Other(404F:0000) 4957Eh 49EB6h
11 Other(4050:0000) 49EB6h 4A6DDh
12 Other(4051:0000) 4A6DDh 4AE18h
13 Other(4052:0000) 4AE18h 4B647h
14 Other(4053:0000) 4B647h 4BE95h
15 PCI driver[A] 4BE95h 50339h
16 PCI driver[B] 50339h 56198h
ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
Error: MEMINIT.BIN: Bad CRC during expansion - data may be invalid!
I see wrong checksums
Posts: 3
Threads: 1
Joined: Sep 2013
Reputation:
0
Thanks for the awesome tut. I successfully stole the CPU microcodes from a Foxconn board and used them on my Abit board to gain support for LGA771 Xeon CPU's
Posts: 1
Threads: 0
Joined: Apr 2014
Reputation:
0
04-21-2014, 01:25 AM
(This post was last modified: 04-21-2014, 01:30 AM by pflatlyne.)
(01-19-2011, 05:46 PM)mockingbird Wrote: Quote:raid_or is the RAID Storage Controller Option ROM required for RAID
As for the AGESA Equivalent , there isnt one. Intel just use microcodes although hardware specific limitations like the TDP support of the motherbaord will prevent you installing some processors (Obviously the CPU SOcket type has to match too!)
Can I safely get rid of raid_or? I will probably never use the 8212F's IDE raid.
Quote:Nope, the TDP doesn't matter. What matters - is the socket pins being changed when Core2 was implemented. Thus preventing Core2 CPU from starting on old boards. But anyway the BIOS must support Core2 and microcodes are not enough.
A thing to work out? Smile
So here's the question... Why would a 945P board not be able to electrically support the Core2 chips? And if so, how could the later 945P boards support the Pentium D and the Core/Core2?
Also another thing which I'm confused about... You say microcodes are not enough, that the BIOS must support it - can you elaborate?
In any case, what command would I use in CBROM to remove raid_or or the Foxconn logo?
Because the socket is not wired correctly to the chipset for it. For instance,if you look at socket m and socket p,they are similar. At first,it looks like just two wires are different. But if you look closer,there are a bunch more connections that were changed. So,for instance,you cant put a socket P cpu in a socket M board. I too thought if it was just microcode and perhaps a couple wires different I could make it work. For instance,I could perhaps cut the two pins off,and with some clever use of epoxy and conductive ink,add some tiny traces,then a layer of epoxy insulation,then epoxy new pins in place and connect them in reversed order. It would be intricate and tedeous,but would work,for two pins. But there are dozens of pins that are off,usually by one or two spots. So its not practical. I breifly considered the idea of making a little circuit board,wtih a grid of solder balls,that swapped all the right pins,then soldering the chip to the socket,then soldering the socket to the board just like any other BGA chip. But ultimately the one thing I cant do is increase the memory. Well,ok,I have a lenovo t60,which runs core bios,so I bet if I was clever I could. I bet I could do some sort of thing where I could bank select rows on a pair of 4gb simms or something,calling an exception handler to deal with it. I understand that System Management Mode can do things completely independant of the OS. I bet you could make it transparant,but if not,you could at least make it work in Linux. But then I realized,cool as it would be to have a core quad (heck,might as well go for broke) and 8gb in a T60 (uber geek cred there) I have better things to do with my time,and I have laptops with those capabilities already.
Another crazy idea I thought of was 16gb of DDR3 in my HP-G71. The idea is that the G71 uses a G45 variant chipset. As such,it supports both DDR2 and DDR3. I have not looked too hard (once again becuase I realized,I have a life,and a job,and enough projects like my old truck im fixing up) ,but the idea was that all the lines from the chipset to the ram are probably used for both types of ram. As such,maybe I could make my own SODIMM PCBs that would fit in the sockets. I could likely route any additional connections if need be. Then I would have to figure out something to do with the BIOS. Thats the worst part. The idea was,to do the undoable. Find a laptop that was similar enough,and hack its bios. The idea is,if I have the schematics of both laptops I could perhaps track down and spot the differences in the chipset initialization and using a lot of patience figure out the changes needed to get he new bios to work. In fact,if I were REALLY lucky,I might find one that already did! But once again,I realized its a lot of time,and a cool idea,and I might have done it 15 years ago,but now if I really really want a 16gb laptop Ill go buy one.
Oh,then there was yet another crazy idea along the same lines. Get a 1st gen macbook bios. Then try to figure out what is different in the hardware of the early macbooks and my t60. Same chipset. Prob different support chips. But the initialization is understood (coreboot supported). If I could actually get the thing to boot off a macbook bios,it would be the ultimate hackintosh. But then I realized,I have a job and a life... and if I want a macbook,Ill go buy one.
Then I thought,I bet there is some laptop out there thats virtually identical to the macbook. If I look far and wide enough,I bet I could find one. Once again,job and life.
Still would be fun to have a Thinkpad that natively booted OSX.
Actually,I thought of using Coreboot + EFIboot and and merging the stuff from one of the Hackintosh loaders into it... but you know what I realized after thinking about it a few minutes. (Yea,I have a lot of interesting ideas)
But I am trying to get the G71 to use a E8135 CPU. That either will work with a simple bios hack or not. Actually,Im considering the idea of a core 2 quad in it if the E8135 works well. The problem is the motherboard schematics show the board has some parts that have to be populated differently for the quad cores. Most of them are for the debug port so Im not sure of those will actually be required. But some are for the AGTL+ reference so those will be needed. Im guessing thats why so many people try the quads in laptops not made for them and they wont work.
|
Users browsing this thread: 2 Guest(s)
|