• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

What can be changed in a VBIOS file? (PCI vendor etc)

andiOak

New Member
Joined
Apr 18, 2024
Messages
8 (0.09/day)
What can be changed in a BIOS file?

I am having issues identifying the card I have, and what it supposedly should register in GPU-Z / drivers as its features.

This specific item in GPU-Z is particularly interesting:
Device ID - more importantly the last 8 digits, specifying the PCI vendor (subsystem id 1787 2379 in my case).

Can this item be changed using a VBIOS file?

It has not been entered into the bios file the card is currently running as its bios. So where is it coming from?? GPU-Z just fabricated it? Or read it on the board?

Here is the photo of the thing:

VBIOS FLASHING - 001 - Första försök att flasha, med hans 570-rom - efter flash-reboot 2 - ...png


I have no thermal sensors in GPU-Z nor can I install drivers correctly.
 

W1zzard

Administrator
Staff member
Joined
May 14, 2004
Messages
27,229 (3.70/day)
Processor Ryzen 7 5700X
Memory 48 GB
Video Card(s) RTX 4080
Storage 2x HDD RAID 1, 3x M.2 NVMe
Display(s) 30" 2560x1600 + 19" 1280x1024
Software Windows 10 64-bit
Some of those are hardcoded inside the GPU (1002 = ATI/AMD, 67DF = RX 470 and others)
some in the BIOS (1787 = ATI AIB/TUL/PowerColor/others, 2379 is their model number)
 

andiOak

New Member
Joined
Apr 18, 2024
Messages
8 (0.09/day)
Some of those are hardcoded inside the GPU (1002 = ATI/AMD, 67DF = RX 470 and others)
some in the BIOS (1787 = ATI AIB/TUL/PowerColor/others, 2379 is their model number)

Some in the BIOS? So the subvendor/PCI vendor number, i.e. "1787" is able to be modified in the BIOS file?
 

W1zzard

Administrator
Staff member
Joined
May 14, 2004
Messages
27,229 (3.70/day)
Processor Ryzen 7 5700X
Memory 48 GB
Video Card(s) RTX 4080
Storage 2x HDD RAID 1, 3x M.2 NVMe
Display(s) 30" 2560x1600 + 19" 1280x1024
Software Windows 10 64-bit
Some in the BIOS? So the subvendor/PCI vendor number, i.e. "1787" is able to be modified in the BIOS file?
Yes I think so
 
Joined
Apr 18, 2019
Messages
2,206 (1.15/day)
Location
Olympia, WA
System Name Sleepy Painter
Processor AMD Ryzen 5 3600
Motherboard Asus TuF Gaming X570-PLUS/WIFI
Cooling FSP Windale 6 - Passive
Memory 2x16GB F4-3600C16-16GVKC @ 16-19-21-36-58-1T
Video Card(s) MSI RX580 8GB
Storage 2x Samsung PM963 960GB nVME RAID0, Crucial BX500 1TB SATA, WD Blue 3D 2TB SATA
Display(s) Microboard 32" Curved 1080P 144hz VA w/ Freesync
Case NZXT Gamma Classic Black
Audio Device(s) Asus Xonar D1
Power Supply Rosewill 1KW on 240V@60hz
Mouse Logitech MX518 Legend
Keyboard Red Dragon K552
Software Windows 10 Enterprise 2019 LTSC 1809 17763.1757
I see Ellesmere. :D
1713562054154.png



'nuther 'former mining' RX480/580 2048SP / RX470/570?
(Or, just 'playing with' vBIOS modding on a card from when one still could?)

If you're trying to restore usability of a mining card,
there are dozens of threads on finding an appropriate vBIOS for your example. A warning though, It doesn't work out for everyone.

For example,
even when it's 'fixed' it crashes or has HDMI problems.
Note: Forcing one of these 'exhibiting' cards to PCIe Gen2 via UEFI/BIOS often resolves the HDMI, etc. problems.
(The 'custom' PCB cards were 100% intended for PCIe Gen2 Switch-equipped mining boards, etc.)


Keep in mind,
a lot of these 'mining Ellesmere/Polaris' cards are sold as 'new' but are either:
A. Used, 'cleaned up' mining cards
or
B. 'New', vBIOS modded (mining ready) cards
or
C. Assembled from eWaste (which, I actually quite enjoy; when it works correctly)


While TPU has searchtools/filters for the "Unverified" vBIOSes, I've had the best luck using google's adv. search tools.
Example "Search Phrase":
Which, stumbles us upon...
etc.

IIRC, you'll need to visibily verifiy what (and, how much) VRAM is on the card first, to 'match' the vBIOS' VRAM model, timings, etc.
 
Last edited:

W1zzard

Administrator
Staff member
Joined
May 14, 2004
Messages
27,229 (3.70/day)
Processor Ryzen 7 5700X
Memory 48 GB
Video Card(s) RTX 4080
Storage 2x HDD RAID 1, 3x M.2 NVMe
Display(s) 30" 2560x1600 + 19" 1280x1024
Software Windows 10 64-bit
Hmm. The bios file I am using does not contain any such number in its data that I can see in the AMDVBFLASH utility. Is it in some hidden info, like header information?
Did you consider the byte order?
 

andiOak

New Member
Joined
Apr 18, 2024
Messages
8 (0.09/day)
Did you consider the byte order?

Hmm, not sure what that means. :)

Here is an output of what the divice info looks like in amdvbflash v2.93:

Bash:
C:\Users\User Usersson\Desktop\atiflash_293>amdvbflash -ai
Adapter  0 (BN=01, DN=00, FN=00, PCIID=00001002, SSID=00002379)
    Asic Family     :  Polaris10
    Flash Type         :  GD25Q21B    (256 KB)
    Product Name is :    D00003 Polaris20 8G J1407LCA.CLC 2021
    Bios Config File:  J1407LCA.CLC
    Bios P/N is     :    113-D0000301_100
    Bios Version    :    015.050.002.001.000000
    Bios Date is    :    04/06/21 22:18
Image 1 -- Offset 0x0
=======================
  ROM header contents:
    Signature              0xAA55
    PCIR offset            0x024C
  PCI Data Structure
    Signature              PCIR
    Vendor ID              0x1002
    Device ID              0x67DF
    PCI Revision           0x00
    Image size             0xEA00
    Code revision          0x0F32
    Indicator              0x00   (Not last image)
    Code type              0x00   (PCAT Image)
  Legacy BIOS File Name    J1407LCA.CLC
  Legacy BIOS Part Number  113-D0000301_100
  Legacy BIOS Build Number 559303
  Legacy BIOS Change List  2286876
  Binary BIOS_IDTF         0xCE097603
  ByteCheckSum             0
Image 2 -- Offset 0xEA00
=======================
  ROM header contents:
    Signature              0xAA55
    PCIR offset            0x001C
  PCI Data Structure
    Signature              PCIR
    Vendor ID              0x1002
    Device ID              0x67DF
    PCI Revision           0x00
    Image size             0xE600
    Code revision          0x0000
    Indicator              0x80   (last image)
    Code type              0x03   (EFI Image)
    EFI Signature          0x0EF1
    Compression Type       0x0001 (compressed)
    Machine type           0x8664 (X64)
    Subsystem              0x000B (EFI boot service driver)
    EFI image offset       0x0050 (abs: 0xEA50)
  Uefi Ids from EFI_PCI_EXPANSION_ROM_HEADER:
    UefiSourceRevision     GOP AMD REV: 1.70
    UefiSourceChangeList   xxxx
    UefiBiosBuildNumber    xxxx

  Dump Gop Driver Info:
    Machine type code      X64
    The GOP Driver appears to be Authenticode signed.
    Size Of Gop Image      97856 (95 KB)
    GOP Driver Name: AMD GOP X64 Release Driver Rev.1.70.0.15.50.Jul 13 2020.23:42:33
    GOP AMD_Build          3457
    GOP AMD_CL             2143793
    GOP BIOS_IDTF          0xDEADBEEF
    GOP Driver does not carry tables!

Does anything stand out here?

(perhaps the last bit, "GOP Driver does not carry tables!" ??)

The entry Asic Family : Polaris10 does not add up. It was introduced by this version of the AMDVBFLASH v2.93 utility, because when I use v5.x I get it saying that it is a Polaris 20 XL, which is the die on the card, as the pictures above prove.
 

W1zzard

Administrator
Staff member
Joined
May 14, 2004
Messages
27,229 (3.70/day)
Processor Ryzen 7 5700X
Memory 48 GB
Video Card(s) RTX 4080
Storage 2x HDD RAID 1, 3x M.2 NVMe
Display(s) 30" 2560x1600 + 19" 1280x1024
Software Windows 10 64-bit
Hmm, not sure what that means. :)
if you search for a hex value of AABB you probably want to search for the bytes BB AA in this order

google: intel byte order
 
Top