Friday, March 28th 2025

Intel Reportedly Abandoned Higher-end Arc Xe2 "Battlemage" dGPU Project Last Year

Intel GPU enthusiasts have been waiting patiently for news regarding higher-end models; ever since the launches of wallet-friendly Arc Xe2 "Battlemage" B580 and B570 graphics cards. As the cliché goes; recent silence has been deafening—we last heard about a speculative expanded lineup of B-series SKUs around late January. At the time, three mysterious "Battlemage" PCI identifiers turned up online; courtesy of Tomasz Gawroński's detective work. Opinions were split about the exact nature of these leaked "BMG" IDs; one camp envisioned Team Blue having professional variants of their existing B580 in the pipeline—presumably with generously specced pools of 24 GB VRAM onboard. A more optimistic group posited that Intel's Arc Xe2 desktop gaming family would welcome more potent "B750, B770," and (maybe) "B780" SKUs.

Yesterday, Tomasz Gawroński (aka GawroskiT) interacted with another notable source of inside track information: Jaykihn (jaykihn0). Plenty of Team Blue-related "scoops" have emerged via Jaykihn's social media channel; mostly predictions regarding upcoming desktop, mobile and enterprise CPUs. Their latest leak indicates Intel's alleged abandoning of a high-end/larger "BMG-G31" GPU die in 2024; within the third quarter of that year. Insiders have long insisted that the Arc Xe2 "Battlemage" project navigated choppy waters during development; hence the appearance of endless theories about the whole caboodle being called off. Jaykihn clarified that he believes that a "retail" launch of "BMG-G31" dGPUs will no longer take place. Many watchdogs will assume that a gap will be filled by forthcoming Arc Xe3 "Celestial" discrete GPUs. Jaykihn stated that they have no fresh insights into how that project is going.
Sources: Wccftech, Overclocking Dot Com, jaykihn0 Tweet
Add your own comment

64 Comments on Intel Reportedly Abandoned Higher-end Arc Xe2 "Battlemage" dGPU Project Last Year

#51
lexluthermiester
GodisanAtheistFrom that link, Secure Boot isn't required. I can confirm the same on my main system with a 6800xt, B550 board, and Win10.

To enable Resizable BAR:

- Enter the system’s BIOS/UEFI firmware configuration menu by pressing the DEL key during system start up. This key may vary between each system manufacturer, please check with your system manufacturer for specific instructions as necessary.
- Compatibility Support Module (CSM) or Legacy Mode must be disabled and UEFI boot mode must be Enabled.
- Ensure the following settings are set to Enabled (or Auto if the Enabled option is not present):
Above 4G Decoding
Re-Size BAR Support
- Use the Intel® Driver and Support Assistant (Intel DSA) to confirm that Resizable BAR is enabled on your system.



-Miceosoft demands secure boot for Win11. Its not inherently a Rebar requirement.
Having done this myself, with both ARC and Geforce cards, I can verify that, at least in Windows, Secureboot is required for Rebar to work. Rebar does not work without Secureboot enabled, in Windows. Feel free, nay, feel invited to try this for yourself.
Posted on Reply
#52
Draconis
lexluthermiesterHaving done this myself, with both ARC and Geforce card, I can verify that, at least in Windows, Secureboot is required for Rebar to work. Rebar does not work without Secureboot enabled, in Windows. Feel free, nay, feel invited to try this for yourself.
It might be system dependent. I also have a B550 board and a RX 6750 on Win 10. I've been running with Rebar on and Secureboot off for ages and like @GodisanAtheist it works fine. I do however sometimes forget to turn Secureboot off when I update my bios so I double checked last night and it definitely works for me.
Posted on Reply
#53
bug
lexluthermiesterOther than it not working when I've tried it? No. But there is this;
www.intel.com/content/www/us/en/support/articles/000090831/graphics.html


You would be wrong, or so says microsoft;
answers.microsoft.com/en-us/windows/forum/all/i-want-to-enable-resize-bar/9eb1f448-830f-4645-81e9-ba8ac2b635d8
I tested this. Enabling Secureboot allows Rebar to work. Disabling it disables both.
So yeah, deal breaker for me.

Thus my hope that future ARC cards perform well without Rebar.
You do realize you've just posted a link from Intel that does not mention SecureBoot, a GPU-Z screenshot that does not mention SecureBoot and a random post from an unofficial forum that says "turn on SecureBoot" (as others have pointed out, that's more of a Windows requirement).
Posted on Reply
#54
GodisanAtheist
lexluthermiesterHaving done this myself, with both ARC and Geforce card, I can verify that, at least in Windows, Secureboot is required for Rebar to work. Rebar does not work without Secureboot enabled, in Windows. Feel free, nay, feel invited to try this for yourself.
-Mayhap it's just an Intel/Nvidia driver level thing?

AMD has always been known to play it a little faster and a little looser, maybe there is some kind of vulnerability there to be able to access the entire GPU VRAM pool without secureboot but AMD doesn't require it for SteamOS/Linux compatibility reasons?

Who knows, other than AMD users being able to activate SAM without Secure Boot.
Posted on Reply
#55
stickleback123
GodisanAtheistAnyone who has been paying attention to Intel's MO over the last decade or more knew they weren't in it for the long haul. Intel just isn't built like that, they're a purely MBA driven quarter to quarter company where anything that doesn't add value to the stock is quickly spun off and axed, which has resulted in Intel being good at one thing and one thing only: CPUs. And now they're not even good at CPUs anymore.

I think we're going to get Celestial, and then MAYYYYYBEEEE Druid out of Intel, and in very Battlemage-esq "see we launched a few, go away and leave us alone", before their dGPU stack gets the kibosh.
Much more than a decade. All Intel have ever really done successfuly is rip the arse out of people for x86 when they have no competition, everything else they either fail at (Itanium), give up on (X Point/Optane), or both.

They even managed to screw up their ability to rob people in x86 now through greedy short termist management. If I'd have told you 10 years ago that AMD would be worth more than Intel in 2025 you'd have laughed in my face.
Posted on Reply
#56
lexluthermiester
DraconisIt might be system dependent.
Maybe. Or maybe there's a workaround that is being done without advertising it.
bugYou do realize you've just posted a link from Intel that does not mention SecureBoot
Miss the part about CSM/Legacy settings? For many motherboards, disabling CSM/Legacy and enabling UEFI also automatically enables Secureboot. It's not stated but rather directly implied.
GodisanAtheist-Mayhap it's just an Intel/Nvidia driver level thing?
DraconisIt might be system dependent. I also have a B550 board and a RX 6750 on Win 10. I've been running with Rebar on and Secureboot off for ages and like @GodisanAtheist it works fine. I do however sometimes forget to turn Secureboot off when I update my bios so I double checked last night and it definitely works for me.
I'm starting to get that sneaking suspicion that this might be one of those "it depends" things.
Posted on Reply
#57
bug
lexluthermiesterMiss the part about CSM/Legacy settings? For many motherboards, disabling CSM/Legacy and enabling UEFI also automatically enables Secureboot. It's not stated but rather directly implied.
I have not missed that. Nor have I seen a motherboard turn on SecureBoot just because I enabled UEFI mode (though most motherboards do come with both UEFI and SecureBoot turned on). Still, how does any of that make SecureBoot a requirement for ReBAR?
Posted on Reply
#58
Draconis
lexluthermiesterI'm starting to get that sneaking suspicion that this might be one of those "it depends" things.
With a sample size of 3, stats tell it has to be so and absolute truth :D. Joking aside I think this thread may be useful down the line when users have odd issues as to when secureboot and rebar do/do not not play nicely together.

@GodisanAtheist Good catch. I was mostly verifying that the combo works for ME, never considered the WHY. Only excuse is overwhelmed at work at the moment and don't frequent tech sites in my personal time.

Watching tech is part of my job.
Posted on Reply
#59
lexluthermiester
DraconisWith a sample size of 3, stats tell it has to be so and absolute truth :D. Joking aside I think this thread may be useful down the line when users have odd issues as to when secureboot and rebar do/do not not play nicely together.

@GodisanAtheist Good catch. I was mostly verifying that the combo works for ME, never considered the WHY. Only excuse is overwhelmed at work at the moment and don't frequent tech sites in my personal time.

Watching tech is part of my job.
I tested this at the shop today after asking my techs about it and the differences of opinion we have here were echoed there. Then we booted up a bunch of different systems and put it to the test. AMD's SAM seems to work fine regardless of the Secureboot setting or who makes the board. Intel systems however are the kicker. Some require SecureBoot for Rebar, some do not. And there is no consistency to it. Some Dell systems require it and others do not. Same with HP. We had the same experience with the various board makers. AMD's fine, Intel boards are all over the place. Very irritating.
Posted on Reply
#60
bug
lexluthermiesterI tested this at the shop today after asking my techs about it and the differences of opinion we have here were echoed there. Then we booted up a bunch of different systems and put it to the test. AMD's SAM seems to work fine regardless of the Secureboot setting or who makes the board. Intel systems however are the kicker. Some require SecureBoot for Rebar, some do not. And there is no consistency to it. Some Dell systems require it and others do not. Same with HP. We had the same experience with the various board makers. AMD's fine, Intel boards are all over the place. Very irritating.
That settles it. ReBAR does not require SecureBoot. But UEFI implementations can be messed up like nobody's business.
Thanks for taking the time to put this to test.
Posted on Reply
#61
GodisanAtheist
lexluthermiesterI tested this at the shop today after asking my techs about it and the differences of opinion we have here were echoed there. Then we booted up a bunch of different systems and put it to the test. AMD's SAM seems to work fine regardless of the Secureboot setting or who makes the board. Intel systems however are the kicker. Some require SecureBoot for Rebar, some do not. And there is no consistency to it. Some Dell systems require it and others do not. Same with HP. We had the same experience with the various board makers. AMD's fine, Intel boards are all over the place. Very irritating.
-Appreciate you taking the time to actually test and coming back with an honest assessment.

Speaks to your character in a good way.
Posted on Reply
#62
bug
GodisanAtheist-Appreciate you taking the time to actually test and coming back with an honest assessment.

Speaks to your character in a good way.
Meet @lexluthermiester ;)
Posted on Reply
#63
bitsandboots
lexluthermiesterI tested this at the shop today after asking my techs about it and the differences of opinion we have here were echoed there. Then we booted up a bunch of different systems and put it to the test. AMD's SAM seems to work fine regardless of the Secureboot setting or who makes the board. Intel systems however are the kicker. Some require SecureBoot for Rebar, some do not. And there is no consistency to it. Some Dell systems require it and others do not. Same with HP. We had the same experience with the various board makers. AMD's fine, Intel boards are all over the place. Very irritating.
Interesting investigation. Thats kinda wild and newsworthy in its own right because I don't see much on the internet about it so who could have expected buying intel + intel is going to give you some Windows restrictions that amd + intel doesn't have.
Posted on Reply
#64
lexluthermiester
bitsandbootsInteresting investigation. Thats kinda wild and newsworthy in its own right because I don't see much on the internet about it so who could have expected buying intel + intel is going to give you some Windows restrictions that amd + intel doesn't have.
Right? Very odd indeed. One of my Asus boards does this but the AsRock does not. Very irritating.
Posted on Reply
Add your own comment
Nov 18th, 2026 00:28 CST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts