F5F Stay Refreshed Software Operating Systems Specialized VRAM tailored for integrated GPUs in Linux versus Windows environments

Specialized VRAM tailored for integrated GPUs in Linux versus Windows environments

Specialized VRAM tailored for integrated GPUs in Linux versus Windows environments

Z
ZwarteMeneke
Member
53
01-09-2016, 05:05 PM
#1
I installed both Linux and Windows on my laptop, with minimal gaming use but occasional playback. I wanted to verify the hardware details for each operating system. On Windows, the integrated GPU has 2 GB of dedicated RAM assigned. However, when checking with the "lspci" command in Linux, it shows a VGA controller with 256 MB of memory. This suggests Linux is using a different approach to allocate resources compared to what’s listed on Windows. Regarding your question about dynamic allocation, it seems Linux does offer more flexible memory management, which could explain the lower reported RAM for the GPU. Let me know if you need further clarification.
Z
ZwarteMeneke
01-09-2016, 05:05 PM #1

I installed both Linux and Windows on my laptop, with minimal gaming use but occasional playback. I wanted to verify the hardware details for each operating system. On Windows, the integrated GPU has 2 GB of dedicated RAM assigned. However, when checking with the "lspci" command in Linux, it shows a VGA controller with 256 MB of memory. This suggests Linux is using a different approach to allocate resources compared to what’s listed on Windows. Regarding your question about dynamic allocation, it seems Linux does offer more flexible memory management, which could explain the lower reported RAM for the GPU. Let me know if you need further clarification.

S
spikes3411
Member
76
01-13-2016, 07:26 PM
#2
Unless LSPCI reported an incorrect value, since dmesg indicates VRAM should match Windows standards, a 2048 MB figure aligns with that expectation.
S
spikes3411
01-13-2016, 07:26 PM #2

Unless LSPCI reported an incorrect value, since dmesg indicates VRAM should match Windows standards, a 2048 MB figure aligns with that expectation.

G
Goku_Jerome
Senior Member
428
01-14-2016, 01:56 AM
#3
Lspci is employed to display PCIe devices, but it lacks specific details about GPUs. It isn't the appropriate tool for this purpose. From my perspective, the displayed size refers to the memory the CPU can preload. This isn't connected to the GPU's VRAM quantity. The data is technically correct, yet it doesn't match what you expect. It pertains to the PCIe bus and how a device's memory is accessible by the CPU. It doesn't represent the full memory capacity of the device.
G
Goku_Jerome
01-14-2016, 01:56 AM #3

Lspci is employed to display PCIe devices, but it lacks specific details about GPUs. It isn't the appropriate tool for this purpose. From my perspective, the displayed size refers to the memory the CPU can preload. This isn't connected to the GPU's VRAM quantity. The data is technically correct, yet it doesn't match what you expect. It pertains to the PCIe bus and how a device's memory is accessible by the CPU. It doesn't represent the full memory capacity of the device.

M
Mandy2727
Member
231
01-25-2016, 09:15 PM
#4
It seemed like a mix-up at first, but after checking the NVIDIA SMI data versus LSPCI details, I realized the differences. Initially doubted the numbers, but seeing the NVIDIA source clarified things. Thanks for the help!
M
Mandy2727
01-25-2016, 09:15 PM #4

It seemed like a mix-up at first, but after checking the NVIDIA SMI data versus LSPCI details, I realized the differences. Initially doubted the numbers, but seeing the NVIDIA source clarified things. Thanks for the help!

1
1kitty1
Junior Member
21
01-25-2016, 10:49 PM
#5
Yes, the dmesg output typically displays system messages and errors you're interested in.
1
1kitty1
01-25-2016, 10:49 PM #5

Yes, the dmesg output typically displays system messages and errors you're interested in.

C
chongyicheng
Member
51
01-26-2016, 03:25 AM
#6
Yes, it works too. Tools like glxinfo can achieve this, for instance using the command: glxinfo | egrep -i 'device|memory'. Many users get confused because lspci sometimes shows what they expect, such as the details for my RX 6600. It highlights things like vendor, version, and memory specs clearly.
C
chongyicheng
01-26-2016, 03:25 AM #6

Yes, it works too. Tools like glxinfo can achieve this, for instance using the command: glxinfo | egrep -i 'device|memory'. Many users get confused because lspci sometimes shows what they expect, such as the details for my RX 6600. It highlights things like vendor, version, and memory specs clearly.