hello again
I also updated bios in HP6820s (F.0B A) and now I can not activate: /
EDIT:
i call to service, a downgrade bios is safe, i back to F.09 and works.
Last edited by lukasek2312; 10-01-2008 at 02:23 PM.
Hi flagmax.
I'm assuming at the new bios there isn't a SLIC anymore, so WoW doesn't work.
I thought about to make a universal patch to introduce a fresh SLIC.
First I've seen that right behind the XSDT there are mostly 8 bytes free to insert a new call (to SLIC). This should be verified. I'll check it again....
Secondly, even more important:
Some acpi tables are called from RSDT AND from XSDT!
The RSDT and the XSDT point to MCFG, for example. (Both tables have got THE SAME entry to MCFG, except the address length). Additionally our first mods were made to replace this table.
So the idea:
Since there are two calls to MCFG (from RSDT AND XSDT) what about to replace the call to MCFG at XSDT to the new written SLIC at a free place?
The MCFG will be remained since it's called from RSDT as well. The fresh introduced SLIC will be called from XSDT (only) so activation should work.
Result: MCFG will not get lost, SLIC will be there to activate....
So the new code should check for RSDP revision 2, find XSDT, after that locate call from XSDT to MCFG. Find a free place for SLIC, write SLIC, replace call to MCFG with call to SLIC at XSDT. Finally patch OEM and OEM table ID's to be the same of SLIC.
What do you think? IMO it sounds promising
Edit:
To make it even more universal your new code can find a 'double called' acpi table by itself (called from RSDT and XSDT, just find a equal address entry). So the only premise must be RSDP revision 2. AFAIK all newer bioses have got the revision 2, at least Notebook bioses.
Last edited by Yen; 10-01-2008 at 09:44 PM.
You really know about the quality of your question after you've got the reply for it.
-PLEASE NO mod request via PM! Therefore use the mod request forums. Thanks.
NOTE: I'll be absent from 15.02-28.03.2010. Ancestor(v) will represent me when I'm away.
A shoe too large trips one up. Walking shoeless hurts anyway.
Yen.
hello all,
I try to activate an hp oem vista ultimate sp1 instalation, on a hp550, using this metod:
http://forums.mydigitallife.info/sho...&postcount=199
everything goes ok, but the vista is not activated... I steel have the 30 days limit.
I attach my acpi file. I do not know anything about BIOS and how to mod a BIOS, I do not even know what kind of BIOS I have.
Could you be so kind to help me ?
Thank you.
Yen: That does look very promising as long as MCFG will still be called from RSDT. One thing on my mind is where to find 176h bytes of free space. I wish my PC had XSDT table to test. Can we test this idea with RW first since we got the scripter and it won't take much time to make .rw file?
Thanks for your offer to help. If you don't mind you can post your AcpiScope report file to have a look at it.
Thanks!
@flagmax
Sure, but unfortunately I don't have XSDT, too
We can ask petar for additional help, since he's got XSDT and is familiar with all the needed tools already....
To get the free space to write SLIC I suggest to scan for highest address entry of XSDT and to add let's say a fixed amount (500h) bytes secure offset. Additionally check if calculated needed space consists of FFh bytes. (If not add again 500h and recheck)-->loop. Finally write SLIC and replace its start address at XSDT (where MCFG entry was located).
Or simply add 100000h (1Mbyte) to highest address entry, no check at all.....
Practically you can write SLIC to any writeable FFh bytes physical memory you want to.
According to ACPI specification the OSPM - Operating System-directed Power Management will later at boot process notice it as used (allocated) acpi namespace......this you can't simulate perfectly using rw everything, since boot process of OS is already done and the calculated space for SLIC could be used by drivers or programs already.
The chain to find SLIC destination is: OSPM--->RSDP--->XSDT--->SLIC
The present code to patch a SLIC (wow) I would use as well. First search if SLIC is present, if yes, use the code, if no jump to new..
Flagmax, I know it's a easy speaking I'm doing here. I'm not able to program anything regarding that matter.
I don't know if my approach / ideas are going too far or aren't realisable....
I'll PM petar and ask for support.....petars original *.ats report is located somewhere at this thread.....
Last edited by Yen; 10-02-2008 at 06:35 PM.
You really know about the quality of your question after you've got the reply for it.
-PLEASE NO mod request via PM! Therefore use the mod request forums. Thanks.
NOTE: I'll be absent from 15.02-28.03.2010. Ancestor(v) will represent me when I'm away.
A shoe too large trips one up. Walking shoeless hurts anyway.
Yen.
Yen: Your pseudocode is right on the money. It's how it should be done. One thing I don't understand is memory layout. My PC has 1gb of RAM. Thats 3FFFFFFFh/1073741823d bytes total. My RSDT lives at 3FFFC000. How do I know when to stop scanning for FF's? What happens when you add 1meg and it goes over 1gb, I tried HWDirect to read at 40000000h and my PC rebooted.
The one attached to this post http://forums.mydigitallife.info/sho...&postcount=364 it is not good?
Hallo Yen, I've seen your PM and I will be glad to help...
Here are my ats report's...
http://rapidshare.com/files/136241002/petar.rar
http://rapidshare.com/files/136366773/petar.rar
http://rapidshare.com/files/136504334/petar.rar
http://rapidshare.com/files/136505696/asus.rar
There should be a report from the modded, unmodded bios, as well as while using the WoW patch (asus.rar).
I'm not shure at the moment which is which, I just linked them again from rapidshare, so I dont have to flash back at the unmodded bios wright away.
Bookmarks