- Top Pick: MSI GeForce RTX 5070 12G Gaming Trio OC
- Runner-up: Sapphire Pulse Radeon RX 9070 XT
- Also consider: ASUS Dual GeForce RTX 5060 Ti 16GB OC Edition
Every graphics card has a doorway between your processor and its video memory, and for decades that doorway was a small fixed window. Resizable BAR widens it so the whole frame buffer can be mapped at once; AMD sells the same idea as Smart Access Memory. On Linux the feature behaves differently than on Windows: the kernel, the firmware and the driver negotiate it together, and nothing pops up a badge telling you it worked.
That is why Linux gamers keep asking the same questions. Is it already on? How do you check without booting into Windows? Does your card’s vendor treat it as a bonus or as a requirement? This guide covers what the feature does at the PCIe level, how to verify it from a terminal, how to enable it in UEFI firmware, and where each vendor stands according to its own documentation.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
Resizable BAR lets your CPU address all of your graphics card’s memory at once instead of through a small window, and on Linux it is mostly a firmware matter: enable Above 4G Decoding and Re-Size BAR in UEFI, keep CSM off, then confirm with lspci that the prefetchable BAR matches your card’s full memory size.
What Resizable BAR actually is
A PCIe device exposes its memory through Base Address Registers, or BARs. In the classic layout, the processor could only see a 256 MB slice of a graphics card’s frame buffer at any moment. Drivers worked around that window by paging data through it in chunks, which was fine when textures were small, but modern games stream large assets constantly and the window becomes an extra step in every transfer.
Resizable BAR is a PCIe capability that lets the system negotiate a much larger BAR size during boot. With it active, the processor addresses the card’s entire video memory directly instead of paging through the old aperture. AMD’s Smart Access Memory is not a separate technology; it is AMD’s name for the same PCIe feature, marketed around Ryzen processors paired with Radeon cards. The feature does not change what your card renders, only how efficiently the processor talks to its memory.
How to check whether it is active on Linux
Linux answers this better than most operating systems, because the negotiated BAR size is visible in plain text. The fastest check is lspci: pull the verbose listing for your card’s slot and look at the memory region lines. If Resizable BAR is working, the prefetchable region matches the card’s memory, so a card with 16 GB of video memory shows a 16G region. If the feature is off, the same line shows the legacy 256M window.
The kernel log tells the same story. The AMD driver prints its detected and visible VRAM amounts during boot, and sysfs files under the card’s device directory expose both total video memory and the CPU-visible portion; when those figures match, the full BAR is mapped. NVIDIA’s tooling helps too: the BAR1 readout in nvidia-smi reports a total equal to your card’s full memory when the large BAR is in use. If every check still shows the small window, the cause is almost always firmware settings.
Enabling it in UEFI firmware
Three firmware settings decide whether Resizable BAR can work. First, Above 4G Decoding must be enabled, because a multi-gigabyte BAR cannot be placed in the address space below the 4 GB line. Second, the Re-Size BAR Support option itself must be on; some boards reveal it only after Above 4G Decoding is enabled. Third, the Compatibility Support Module, or CSM, must be disabled, because legacy boot mode cannot handle the large address assignment and silently falls back to the small BAR.
Vendors place these options in different menus, usually near the PCIe or advanced settings, and the labels vary. A firmware update is worth doing first on older boards, since some gained the option through an update rather than shipping with it. After saving, boot back into Linux and repeat the lspci check; no reinstall or special package is needed.
Where each GPU vendor stands
NVIDIA documents Resizable BAR support for GeForce RTX 30 series cards and everything newer. The launch came with a condition that still trips people up: the first RTX 30 series cards needed a graphics card firmware update, delivered by the board partner or through NVIDIA’s update tool for its reference design, before the feature could be switched on. NVIDIA also activated the feature per game through driver profiles on Windows, adding titles only after checking them. The platform requirement is a motherboard and processor whose firmware offers the setting, covering most AM5 and recent Intel platforms plus many late AM4 boards after updates.
AMD introduced Smart Access Memory alongside the Radeon RX 6000 series and Ryzen 5000 processors, then widened the supported combinations in later releases, including earlier Ryzen generations and the RX 5000 series. The Linux picture is simpler than the marketing: the kernel’s PCI layer and the amdgpu driver request the largest BAR the firmware offers, so an AMD card commonly runs with its full memory mapped whenever the UEFI settings are right, with no branded toggle in a control panel.
Intel is the strictest of the three. Intel’s platform guidance for Arc graphics treats Resizable BAR as a requirement for proper performance rather than an optional extra, and board partners print the same condition in their system requirements. Arc cards lean heavily on the large BAR for memory management, so an Arc system on an old board without the setting leaves much of the card’s performance unreachable. If you are shopping for Arc, the motherboard check comes before the card check.
Why the gains vary so much between games
Resizable BAR removes a bottleneck; it does not add rendering power. Whether that matters depends on how a game moves its data. Engines that stream textures and geometry constantly, especially open-world titles juggling large asset pools, benefit most, because every transfer used to queue at the small window. A game that loads its assets once and keeps them resident has little to gain.
A minority of titles even run slightly worse with the feature on, usually because their upload patterns interact badly with the fully mapped memory. That uneven behaviour is exactly why NVIDIA gated the feature behind per-game profiles on Windows instead of enabling it globally. On Linux the situation is more uniform, since AMD’s driver treats the large BAR as its normal mode. Enable it, confirm it with the checks above, and judge by the games you actually play.
Graphics cards and a board that support it
MSI GeForce RTX 5070 12G Gaming Trio OC
A current Blackwell card, and a good example of how the firmware problem has gone away: RTX 50 series cards ship Resizable BAR ready, so only the motherboard settings remain.
- Specs:
- Memory: 12 GB GDDR7, 192-bit bus
- Interface: PCIe 5.0 x16
- Boost clock: 2625 MHz in Extreme Performance mode
- Power: 250 W board rating, single 16-pin connector
- Outputs: 3x DisplayPort 2.1, 1x HDMI 2.1
Sapphire Pulse Radeon RX 9070 XT
AMD’s RDNA 4 flagship in Sapphire’s Pulse trim. On Linux this is the low-effort route: enable the firmware options and the amdgpu driver maps the full 16 GB without extra software.
- Specs:
- Memory: 16 GB GDDR6
- Architecture: AMD RDNA 4
- Boost clock: up to 2970 MHz
- Interface: PCIe 5.0 x16
- Model number: 11348-03-20G
Sparkle Intel Arc B580 TITAN OC
The card that makes this guide mandatory reading. Sparkle’s own system requirements for this model call for a motherboard that supports Resizable BAR or Smart Access Memory, because Arc performance depends on it.
- Specs:
- Memory: 12 GB GDDR6, 192-bit bus
- Interface: PCIe 4.0 x8
- Boost clock: 2760 MHz
- Power: 200 W board power, 600 W minimum system supply per Sparkle
- Outputs: 1x HDMI 2.1, 3x DisplayPort 2.1
ASUS Dual GeForce RTX 5060 Ti 16GB OC Edition
A compact dual-fan Blackwell card with a generous memory allocation for its tier. Like the rest of the RTX 50 series it arrives Resizable BAR ready, leaving firmware setup as the only task.
- Specs:
- Memory: 16 GB GDDR7
- Interface: PCIe 5.0
- OC mode clock: 2632 MHz
- Design: 2.5-slot, dual Axial-tech fans
- Model number: DUAL-RTX5060TI-O16G
ASUS TUF Gaming B650-Plus WiFi
The platform half of the equation. This AM5 board’s UEFI provides the Above 4G Decoding and Re-Size BAR options the feature needs, and it is deliberately a different pick from the boards in our Linux motherboard roundup.
- Specs:
- Socket: AMD AM5, B650 chipset
- Memory: DDR5, four DIMM slots
- Networking: WiFi 6, 2.5 Gb Ethernet
- Storage: PCIe 5.0 M.2 support
- Form factor: ATX
How to choose
Start with the platform, not the card. Confirm your motherboard’s manual lists Above 4G Decoding and a Re-Size BAR option, and update the firmware if either is missing, because no graphics card can enable the feature on a board that does not offer it. Intel Arc buyers should treat that check as a hard requirement. AMD buyers on Linux have the simplest path, since the driver uses the large BAR as its normal mode once firmware allows it. NVIDIA buyers with an early RTX 30 series card should confirm the card’s firmware supports the feature; newer series need nothing beyond the motherboard settings. Whatever you buy, verify the result afterwards with the lspci region size.
Who should skip this
Skip the shopping entirely if your system already shows a full-size BAR in lspci; there is nothing to buy. Owners of much older platforms, such as early AM4 or pre-400-series Intel boards with no firmware support, will not unlock the feature with a new graphics card alone, and a platform upgrade is a bigger decision. Laptop gamers can sit this out too, since mobile systems either ship with the feature configured or do not expose the settings. And if you play older titles known to dislike the feature, leaving it off costs you nothing.
FAQ
Does Linux need a driver setting to turn Resizable BAR on?
No. There is no distribution-level switch for it. The firmware decides what BAR sizes are offered during boot, and the kernel and driver use the large BAR when it is available. Your only jobs are the UEFI settings and an lspci check afterwards.
Is Smart Access Memory different from Resizable BAR?
No. Smart Access Memory is AMD’s marketing name for the same PCIe Resizable BAR capability, introduced around Ryzen processors paired with Radeon cards. The firmware menu, the boot negotiation and the result are the same.
My board has Above 4G Decoding but no Re-Size BAR option. What now?
Update the motherboard firmware first, because several vendors added the option in later releases. If it is still absent, the board cannot offer a large BAR, and an Arc card should not be bought for that system, since Intel treats the feature as a requirement.
Will enabling Resizable BAR break my Linux install?
The settings are safe and reversible. The one real gotcha is disabling CSM: a system installed in legacy boot mode may not boot afterwards until converted to UEFI booting, or until CSM is turned back on. Check how your system boots first.
Final verdict
Resizable BAR on Linux is a firmware errand, not a software project. Set Above 4G Decoding and Re-Size BAR in UEFI, keep CSM off, and prove it worked by reading the prefetchable region size in lspci. AMD cards then use the full mapping as their normal state, current NVIDIA cards arrive ready, and Intel Arc cards treat the exercise as compulsory. Do the setup once and verify it from the terminal.










