Overclock.net - An Overclocking Community - Reply to Topic
Thread: Hawaii Bios Editing ( 290 / 290X / 295X2 / 390 / 390X ) Reply to Thread
Title:
Message:

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in


  Additional Options
Miscellaneous Options

  Topic Review (Newest First)
05-06-2020 03:07 PM
egorek375
sensitivity/granularity of fan speed in powercolor r9 290x

What is max and min sensitivity/granularity of fan speed in my powercolor r9 290x? And can I use BIOS of powercolor r9 290x battlefield 4 edition for my powercolor r9 290x? Is there a big difference between versions with and without a game? Is it dangerous to flash the BIOS from the version with the game if I have a version without a game? I know for sure that bios is somewhat different, at least in the version without a game 55% and in the version with game 40%
04-28-2020 02:45 AM
kino0924 Is there a way to query efuses in ASIC?
I really want to compare with real s7150 and my w7100 and see the difference.
w7100 released 2014 aug and s7150 released 2016 feb.
Both cards are high enterprise level and kinda skeptical that they have different efuse.
04-27-2020 02:33 AM
kino0924
Quote: Originally Posted by MihaStar View Post
Well, I see your point. And I also googled your messages here and there asking for help

Look, you can try to change the DevID to whatever you want, and simply flash the card under the DOS environment, checking for the result. You will see what bits are fused and what are not.
The final DevID impacts only the driver that will be loaded (if found matching DevID) or not.

In theory, I can try something similar with my 290X, will report the results later.

But I'm afraid your fused DevID is 692B, while the BIOS for MXRT7600 just added one bit making it 693B.

I haven't seen the resistor-related mechanism for DevID changing on AMD cards, like it's done on NVIDIA boards.
I just tried 0x694B but its still stuck at 0x693B
Am I editing wrong place?
I only modified right after 'PCIR' and there are two places to edit (BIOS and EFI)
04-27-2020 02:18 AM
MihaStar
Quote: Originally Posted by kino0924 View Post
@MihaStar
I read entire thread and there are only one post that mentions about DeviceID is being fused



So, when you say DeviceID is fused to 0x67B0 , I can go higher but not lower?
If above statement is true, the I should assume that my DeviceID is fused to 0x692B so I was able to go 0x693B but not 0x6929?
Well, I see your point. And I also googled your messages here and there asking for help

Look, you can try to change the DevID to whatever you want, and simply flash the card under the DOS environment, checking for the result. You will see what bits are fused and what are not.
The final DevID impacts only the driver that will be loaded (if found matching DevID) or not.

In theory, I can try something similar with my 290X, will report the results later.

But I'm afraid your fused DevID is 692B, while the BIOS for MXRT7600 just added one bit making it 693B.

I haven't seen the resistor-related mechanism for DevID changing on AMD cards, like it's done on NVIDIA boards.
04-27-2020 02:16 AM
kino0924 To 0x693C
Quote:
[email protected]:~$ sudo ./atiflash -f -p 0 w7100_new.rom
[sudo] password for user:
Old SSID: 3D2B
New SSID: 3D2B
Old P/N: 113-C7670800-103
New P/N: 113-C7670800-103
Old DeviceID: 693B
New DeviceID: 693C
Old Product Name: BARCO MXRT-7600
New Product Name: BARCO MXRT-7600
Old BIOS Version: 015.047.000.012.006913
New BIOS Version: 015.047.000.012.006913
Flash type: GD25Q41B
Burst size is 256
1E414/1E414h bytes programmed
1E414/1E414h bytes verified

Restart System To Complete VBIOS Update.

[email protected]:~$ sudo ./atiflash -ai
[sudo] password for user:
Adapter 0 (BN=03, DN=00, PCIID=693B1002, SSID=3D2B13CC)
Asic Family : Tonga
Flash Type : GD25Q41B (512 KB)
Product Name : BARCO MXRT-7600
Bios Config File : C7670800.103
Bios P/N : 113-C7670800-103
Bios Version : 015.047.000.012.006913
Bios Date : 06/29/16 23:00
ROM Image Type : Hybrid Images
ROM Image Details :
Image[0]: Size(65536 Bytes), Type(Legacy Image)
Image[1]: Size(58368 Bytes), Type(EFI Image)

To 0x692B
Quote:
[email protected]:~$ sudo ./atiflash -f -p 0 w7100_new.rom
Old SSID: 3D2B
New SSID: 3D2B
Old P/N: 113-C7670800-103
New P/N: 113-C7670800-103
Old DeviceID: 693B
New DeviceID: 692B
Old Product Name: BARCO MXRT-7600
New Product Name: BARCO MXRT-7600
Old BIOS Version: 015.047.000.012.006913
New BIOS Version: 015.047.000.012.006913
Flash type: GD25Q41B
Burst size is 256
1E414/1E414h bytes programmed
1E414/1E414h bytes verified

Restart System To Complete VBIOS Update.


[email protected]:~$ sudo ./atiflash -ai
[sudo] password for user:
Adapter 0 (BN=03, DN=00, PCIID=693B1002, SSID=3D2B13CC)
Asic Family : Tonga
Flash Type : GD25Q41B (512 KB)
Product Name : BARCO MXRT-7600
Bios Config File : C7670800.103
Bios P/N : 113-C7670800-103
Bios Version : 015.047.000.012.006913
Bios Date : 06/29/16 23:00
ROM Image Type : Hybrid Images
ROM Image Details :
Image[0]: Size(65536 Bytes), Type(Legacy Image)
Image[1]: Size(58368 Bytes), Type(EFI Image)

I modified my original bios to see if i can change DeviceID
I did full power-cycle after each flash
I Fix BIOS image checksum with atomtool.py

I cannot go lower or higher at all.
I see atiflash reports new DeviceID but never gets applied
04-27-2020 02:05 AM
kino0924 @MihaStar
I read entire thread and there are only one post that mentions about DeviceID is being fused

Quote:
The basic DeviceID comes from the fuses. For Hawaii / Grenada PRO and XT (8520 / 8800 ASIC) it is 67B0h with bits 15:4 being fixed (IIRC).

67B0h (XT): Bit 3:0 = 0000b
67B1h (PRO): Bit 3:0 = 0001b
So, when you say DeviceID is fused to 0x67B0 , I can go higher but not lower?
If above statement is true, the I should assume that my DeviceID is fused to 0x692B so I was able to go 0x693B but not 0x6929?
04-27-2020 01:40 AM
kino0924
Quote: Originally Posted by MihaStar View Post
Well, I checked the BIOSes you've provided, and they are WAY too different, starting with size (122kB vs 370kB), then different VRAM_Info tables and supported memory ICs (4H24MFR/4032BABG/4H24AJR vs 4H24AJR only) and many more other things I guess. Moreover, the 7150 you found is from a 7150x2 board in fact ("Master" and "Gemini" keywords in the header).

Let me simply ask, what's the reason fo such mod?
I guess both cards are FirePro-s and they should be compatible with Radeon Pro driver branch.

AFAIR when bits in DeviceID are fused to '1's, they can't be reversed back, so you can flash the DevID 290X to DevID 290 (0x67B0 -> 0x67B1), but you can't do the reversed trick.
Similarly you can't flash the 290X DevID to FirePro DevID (0x67B0 to 0x67A0).

How about trying these BIOSes:
https://www.techpowerup.com/vgabios/171144/171144 (ver. .102)
https://www.techpowerup.com/vgabios/195345/195345 (ver. .103)

You'll get a generic W7100 in the end, maybe it's enough?

My main goal is to have S7150 since the card is too pricey (still 500~700 after 10years).
FirePro S7150 is designed for MxGPU which allows user to assign single GPU to multiple VM.

BIOS size is different because it contains extra stuff for MxGPU (I am guessing) after 0x20000.
I have few other bios from S7150x2 and S7100x and they all have same data after 0x20000

I couldnt get real dump from S7150 so I used S7150x2 bios since it looks like they are pretty same but just PLX'ed


So my ultimate goal is to run MxGPU without having S7150.
I choose W7100 to modify since they are identical (same pcb, gpu, mem size)

One thing that I found before I mod is that W7100 comes with 128kb EEPROM and S7150 comes with 512kb EEPROM
my MXRT7600 also came with 512kb so I didnt have to do any hardware modification.
04-27-2020 01:10 AM
MihaStar
Quote: Originally Posted by kino0924 View Post
@MihaStar
I need some help with modifying Firepro Tonga card.

What I have (MXRT-7600 which is oem version of W7100)
What I want to be (FirePro S7150)

They are identical card from visual perspective.

DeviceID
W7100 = 0x692B
MXRT7600 = 0x693B
S7150 = 0x6929

When I flash MXRT 7600 rom, I get DeviceID = 0x693B (same as bios)
When I flash S7150 rom, I get DeviceID= 0x692B (It should be 0x6929)

I modified bios of both 7600 and 7150 to see if it changes.
I changed right after 'PCIR' and I was able to see changed DeviceID during atiflash.
But even after reboot, DeviceID still remains same as before modification.

What I dont understand is why DeviceID become 0x692B when I flashed 0x6929 BIOS
Is there ASIC lock that overwrites DeviceID? or ATOMBIOS command that sets PCIID?

I attached both BIOS
Well, I checked the BIOSes you've provided, and they are WAY too different, starting with size (122kB vs 370kB), then different VRAM_Info tables and supported memory ICs (4H24MFR/4032BABG/4H24AJR vs 4H24AJR only) and many more other things I guess. Moreover, the 7150 you found is from a 7150x2 board in fact ("Master" and "Gemini" keywords in the header).

Let me simply ask, what's the reason fo such mod?
I guess both cards are FirePro-s and they should be compatible with Radeon Pro driver branch.

AFAIR when bits in DeviceID are fused to '1's, they can't be reversed back, so you can flash the DevID 290X to DevID 290 (0x67B0 -> 0x67B1), but you can't do the reversed trick.
Similarly you can't flash the 290X DevID to FirePro DevID (0x67B0 to 0x67A0).

How about trying these BIOSes:
https://www.techpowerup.com/vgabios/171144/171144 (ver. .102)
https://www.techpowerup.com/vgabios/195345/195345 (ver. .103)

You'll get a generic W7100 in the end, maybe it's enough?
04-27-2020 12:21 AM
kino0924 @MihaStar
I need some help with modifying Firepro Tonga card.

What I have (MXRT-7600 which is oem version of W7100)
What I want to be (FirePro S7150)

They are identical card from visual perspective.

DeviceID
W7100 = 0x692B
MXRT7600 = 0x693B
S7150 = 0x6929

When I flash MXRT 7600 rom, I get DeviceID = 0x693B (same as bios)
When I flash S7150 rom, I get DeviceID= 0x692B (It should be 0x6929)

I modified bios of both 7600 and 7150 to see if it changes.
I changed right after 'PCIR' and I was able to see changed DeviceID during atiflash.
But even after reboot, DeviceID still remains same as before modification.

What I dont understand is why DeviceID become 0x692B when I flashed 0x6929 BIOS
Is there ASIC lock that overwrites DeviceID? or ATOMBIOS command that sets PCIID?

I attached both BIOS
04-19-2020 02:57 PM
kithylin
Quote: Originally Posted by michbeltre View Post
Hello everyone

I have a r9 390 that is driving me nuts for some reason the memory frequency is so unstable that when I'm not doing anything that is graphically intensive I get a black screen, I found a really cool tool called "clockblocker" and it allows me to force my memory frequency to be always at Max the downside is that it only works with old amd drivers, and some games like cod warzone and monster hunter world are forcing me to update, is there any other app that I can use to look my memory clock frequency? Or does anyone knows how can I modify my vbios to the point that I can change the idle state of my gpu memory frequency?

Thanks.
Yes, you can use AMD WattMan that is built into the drivers in modern AMD drivers released for 2020.
This thread has more than 10 replies. Click here to review the whole thread.

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off