BIOS Modding: Name question

Discussion in 'BIOS Mods' started by zoliky, May 27, 2010.

  1. zoliky

    zoliky MDL Novice

    May 25, 2010
    17
    0
    0
    I modified the DSDT in ACPITBL.BIN (Award BIOS). The ACPITBL is "one" byte bigger.

    I think, this is a problem for the sensitive modules. I can fix this problem re-inserting the module with the name: ACPITB.BIN (removing the "L").

    Does this modification cause a problem for the BIOS or any operating system?
    Thanks!
     
  2. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,250
    11,063
    340
    The better way is to gain space by modifying one of the acpitables, e.g. the creator ID.

    Please upload the files to help you..
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,250
    11,063
    340
    Is this the same mod you have pm'ed me about?

    Correct me if I'm wrong:

    You did a DSDT mod and the modded acpitbl module doesn't fit anymore since its compressed size is one byte too big.

    Well, it's no problem to alter the acpitables to gain a few bytes of space...
    To remain the acpitable modules position is the better choice if it should be possible...

    You may upload your modded acpitbl.bin.....

    I'll check it later this evening...

    Let's talk about here and not via PM...

    Let's first check if you need to put the acpimodule at the end.....it's all about its compressed size....a few bytes too big isn't a real problem..since we can adjust it by editing some tables...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. zoliky

    zoliky MDL Novice

    May 25, 2010
    17
    0
    0
    #4 zoliky, May 27, 2010
    Last edited by a moderator: Apr 20, 2017
    (OP)
  5. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,250
    11,063
    340
    Cbrom uses lha to compress the modules. The uncompressed acpitable binary is 52A5h in size. After your modification the same.
    The compression is now worse. It cannot compress to get the original size and hence they are different.
    I try to fix that by altering 'unimportant' bytes and will reply...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. zoliky

    zoliky MDL Novice

    May 25, 2010
    17
    0
    0
    thank you!
     
  7. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,250
    11,063
    340
    #7 Yen, May 27, 2010
    Last edited by a moderator: Apr 20, 2017
    It took me some time to fiddling around.

    Change the OEMID of the TCPA table from HTC to GBC. The OEMID doesn't matter at this table.

    Code:
    Offset      0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F
    
    000001F0               54 43 50 41  32 00 00 00 01 00 47 42       TCPA2.....GB
    00000200   43 20 20 20 48 54 43 41  43 50 49 20 31 2E 30 42   C   HTCACPI 1.0B
    00000210   47 42 54 55                                        GBTU
    
    
    Then use cbrom to compress the module, its size will be right then.

    Copy and overwrite it at the original offset of the untouched bios. 1E14Ch to 1FCA1h.

    Finally make any further action with cbrom.

    This step is needed to make cbrom to correct the sums. I suggest to use cbrom196 therefore.

    You may extract the last module, then release it and re-add it again, it's the LAN bootrom PXE
    23. PCI ROM[D] 10000h(64.00K) 093C6h(36.94K) RTEGROM.LOM
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. zoliky

    zoliky MDL Novice

    May 25, 2010
    17
    0
    0
    Wow! Thank you very much. I owe you so much!
    Do you know where can I obtain CBROM196? I searched google.. I found just verion 195 :(
     
  9. 911medic

    911medic MDL Guru

    Aug 13, 2008
    5,778
    491
    180
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,250
    11,063
    340
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,250
    11,063
    340
    You can upload your mod and the original bios if you want. I can check it before you flash...(except your DSDT modification, because I don't know about that...)

    Edit: Please note that the release command removes the module from the bios. So it's NOT needed for the acpitbl module since you are inserting by overwriting it using an hexeditor...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,250
    11,063
    340
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. zoliky

    zoliky MDL Novice

    May 25, 2010
    17
    0
    0
    Thanks, mate! I will test the BIOS soon as possible..
     
  14. zoliky

    zoliky MDL Novice

    May 25, 2010
    17
    0
    0
    It works. Thank you!
    I realised at a later stage that I needed to add more stuff into the DSDT. Arghhhh... Sorry :(
    I tried the other method (OEM7 module instead of ACPITBL) and it also worked.

    I just reduced the size of the header bytes to 23h.

    Do you think this "OEM7" method can cause instability problems? Does the BIOS take the oem7 file into consideration?
    Thanks again for all your help!
     
  15. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,250
    11,063
    340
    Since the OEM7 binary contains no code, but random bytes, it just acts as placeholder.... to change the acpitable's position can result to hibernation wake up / sleep state issues.....

    You have reduced the header bytes??? :eek: How? Better to reduce the dummy bytes!!!
    The header bytes are specified! Each byte has its own function ( sum, length, link...)
    A damaged header could lead to serious trouble....(brick!!)

    Edit: What size is the final acpitbl then?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. zoliky

    zoliky MDL Novice

    May 25, 2010
    17
    0
    0
    1B56h - 23h = 1B33h
    1B33h in decimal: 6963.

    I filled the 6963 space with random data.
    Are you sure about the "24h"? It makes my OEM7 module bigger with one byte.

    I will check the sleep thing.
     
  17. zoliky

    zoliky MDL Novice

    May 25, 2010
    17
    0
    0
    Sleep seems to work in Ubuntu. I will test in Windows 7.
     
  18. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,250
    11,063
    340
    Fact is that cbrom formats the module. As long as you adjust the size of the dummy binary you are safe. (You did that at your calculation, but you've said you have modified the header.)
    It will be fatal if you would delete a header byte ..

    Hmm..strage. yes 24h bytes is right.
    1B56h-24h = 1B32h (6962)
    Why bigger? a smaller dummy bin should give a smaller OEM7 module since the random bytes are not compressed......

    You didn't a mistake..only fatal thing would be to cut the header (first 24h bytes of the created OEM module)..


    I cannot download here and cannot use any tool, I'll check that later.....
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. zoliky

    zoliky MDL Novice

    May 25, 2010
    17
    0
    0
    Some people use the SLIC.BIN to fill the space. All of this people have sleep issues? Is there a way to fix the sleep issue?
     
  20. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,250
    11,063
    340
    Well it occurs only at special bioses for an unknown reason...the only way is to remain its original position...sleep issues are well known even at the original bioses from the OEM. They simply don't match the acpi specifications (sloppy programmer)...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...