• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

A380 Linux firmware

boekhold

New Member
Joined
Dec 22, 2024
Messages
3 (0.02/day)
I have an ASRock Intel Arc A380 Low Profile 6GB in a Linux box. I'm unsure which files (fw, oprom-code, oprom-data, fw-data) I can/should safely flash. The "matrix" does not list this specific card, and the Device ID doesn't seem to match any of the oprom-code/data/fw-data files from the github archive:

Code:
$ sudo ./igsc list-devices

Device [1] '/dev/mei1': 8086:56a5 1849:6006 0000:09:00.00

$ sudo ./igsc fw version --device /dev/mei1
Device: FW Version: DG02_2.2339

$ sudo ./igsc oprom-code version --device /dev/mei1
OPROM CODE Version: 14 00 27 04 00 00 00 00

$ sudo ./igsc oprom-data version --device /dev/mei1
OPROM DATA Version: 14 00 27 04 01 00 00 00

$ sudo ./igsc fw-data version --device /dev/mei1
Device: Fw Data Version: Major Version: 101, OEM Manufacturing Data Version: 0, Major VCN: 1

$ sudo ./igsc oprom-data supported-devices --image dg2_d_asrock_challenger-a380_oprom-data.rom

OPROM Data supported devices:

Vendor Id: 8086 Device Id: 56A5 SubSystem Vendor Id: 1849 SubSystem Device Id: 6004
$ sudo ./igsc oprom-code supported-devices --image dg2_c_oprom.rom

OPROM Code image does not have the supported devices extension

$ sudo ./igsc fw-data supported-devices --image fwdata/dg2_asrock_challenger-a380_config-data.bin

firmware data supported devices:

Vendor Id: 8086 Device Id: 56A5

Subsys Vendor Id: 1849 Subsys Device Id: 6004

The reason I'm keen to update "something" is because when connected with an HDMI cable to my 21:9 4K monitor, the card does not correctly detect the display and won't go into a higher resolution than 1920x1080. If I use a DisplayPort cable, the card correctly detects the display and goes into full resolution. Unfortunately, I already have another PC connected to this monitor via DisplayPort and I don't have another DP port free. I'm hoping a firmware update will fix this.

If I go to the ASRock website for this card and go to Support -> Download, I get redirected to the "Intel® Arc™ Graphics Windows* DCH Driver" page, suggesting I need to use some generic intel files?
 
Last edited by a moderator:
The reason I'm keen to update "something" is because when connected with an HDMI cable to my 21:9 4K monitor, the card does not correctly detect the display and won't go into a higher resolution than 1920x1080.
They likely just use there normal a380 roms. Though it’s also highly likely they simply have no need to update them. As for your HDMI issue IGSC won’t help you. As I believe I mentioned in those threads and the flash guide the pcon is provided because I can. But it is not updated as part of Intels normal FW update methods. It is updated using the system service in windows. Another user brought this up only weeks ago. Please see.


If you really think the HDMI issue is PCON related (kind of doubt as that issue manifested as the monitor simply not waking afaik) then your best bet is a spare drive and a windows install in which you can do a clean install using the full driver package.
 
They likely just use there normal a380 roms. Though it’s also highly likely they simply have no need to update them.
Thanks @Solaris17. So seems what I can safely update is:

Code:
sudo ./igsc fw update --device /dev/mei1 --image dg2_gfx_fwupdate_SOC2.bin
sudo ./igsc oprom-code update --device /dev/mei1 --image dg2_c_oprom.rom

Even if it doesn't help with my HDMI issue, it might improve other things.
 
Thanks @Solaris17. So seems what I can safely update is:

Code:
sudo ./igsc fw update --device /dev/mei1 --image dg2_gfx_fwupdate_SOC2.bin
sudo ./igsc oprom-code update --device /dev/mei1 --image dg2_c_oprom.rom

Even if it doesn't help with my HDMI issue, it might improve other things.
This worked. It didn't fix my HDMI issue as Solaris17 already suspected, but it didn't break anything either. I did notice once difference: previously my monitor was reported as "Unknown" in Ubuntu. Now it's reported with the correct vendor/model... Still does not detect the supported resolutions however.
 
Back
Top