Problem with vram

Hello. There is a problem on Manjaro Linux. I will now try to describe it in detail, but clearly. All this time I had a total of 8 GB of RAM and since my integrated video card (Intel uhd graphics) uses RAM as vram - vram I also had 8 GB in use. But yesterday I decided to upgrade my RAM and instead of the old 4 GB RAM I installed an 8 GB RAM (I had to check this RAM. ). In the end, I didn’t like it very much and I returned the old RAM with 4 GB. But now after this I only have 3821 MB in use according to “glxinfo -B”.
What can be done to get it back so that 8gb can be used as vram again? Please, help :_)

glxinfo -B output

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) UHD Graphics (TGL GT2) (0x9a78)
    Version: 24.1.1
    Accelerated: yes
    Video memory: 3821MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics (TGL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.1.1-manjaro1.1
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.1.1-manjaro1.1
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.1.1-manjaro1.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

P.S: I also checked on live usb with the glxinfo -B command, but everything is fine there and all 8 GB can be used.

I’m failing to understand the logic… You added more RAM; so, your system had more physical RAM at its disposal… and you didn’t like it very much?

You haven’t given any useful information about your hardware, so I’m uncertain how easily others might be able to help. Some system information might be useful, to start with.

Please provide the output of:

inxi --admin --verbosity=8 --filter --no-host --width

…in a preformatted text container (using the </> button).

Otherwise, there might be a game of 100 questions to follow; and nobody likes to guess; however, I’ll make a few quick ones:

I guess… you’re using a laptop; that there might be a setting to adjust in your BIOS to have the RAM detected properly; that the RAM might need to be re-seated, or moved to a different slot; that a BIOS update might be available to address related issues; that updating to the latest kernel (LTS) might be beneficial; that you don’t have sufficient (or any) swap space defined…

I’m sure others might be able to help if given more information.

Cheers.

2 Likes

Why is Manjaro guilty and not the supplier of the milk ? :wink:

1 Like

Sorry, its hard a some to explain it in words T-T, but i will try.

In general, all this time I had exactly the same amount of vram as ram - 8 gigabytes, since my Intel UHD Graphics uses my RAM as video memory.But yesterday, after I replaced my 4 GB RAM with an 8 GB RAM, my amount of memory for use by the video card decreased. After returning the old RAM, nothing changed. I hope I was able to explain correctly. So, I would like to try to return 8 GB to use by the video card. Previously, I could use all 8 GB, but now only 3 GB, judging by the information from glxinfo -B. But I don’t know how T-T.

Sorry for not being able to explain my problem correctly, it’s a bit complicated. Since I don’t know English very well yet, I have to use a translator.

Output of inxi:

System:
  Host: moonlight-asusvivobook Kernel: 6.1.94-1-MANJARO
    arch: x86_64 bits: 64 compiler: gcc v: 14.1.1 clocksource: tsc
    avail: acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
    root=UUID=d58d0dbe-b0e7-4f5a-8171-7795e7fd14cf rw quiet
    splash udev.log_priority=3
  Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks
    v: 6.3.0 wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro
    base: Arch Linux
Machine:
  Type: Laptop System: ASUSTeK
    product: VivoBook_ASUSLaptop X415EA_F415EA v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: X415EA v: 1.0
    serial: <superuser required> uuid: <superuser required>
    UEFI: American Megatrends LLC. v: X415EA.306 date: 11/04/2021
Memory:
  System RAM: total: 8 GiB available: 7.46 GiB
    used: 2.68 GiB (35.9%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB note: check slots: 2 modules: 2
    EC: None max-module-size: 64 GiB note: est.
  Device-1: Controller0-ChannelA type: DDR4 detail: synchronous
    size: 4 GiB speed: 3200 MT/s volts: note: check curr: 1 min: 1
    max: 1 width (bits): data: 64 total: 64 manufacturer: Samsung
    part-no: M471A5244CB0-CWE serial: N/A
  Device-2: Controller1-ChannelA-DIMM0 type: DDR4
    detail: synchronous size: 4 GiB speed: 3200 MT/s volts:
    note: check curr: 1 min: 1 max: 1 width (bits): data: 64
    total: 64 manufacturer: Samsung part-no: M471A5244CB0-CWE
    serial: 399012F5
CPU:
  Info: model: Intel Pentium Gold 7505 bits: 64 type: MT MCP
    arch: Tiger Lake level: v4 note: check built: 2020
    process: Intel 10nm family: 6 model-id: 0x8C (140)
    stepping: 1 microcode: 0xB6
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled
    cache: L1: 160 KiB desc: d-2x48 KiB; i-2x32 KiB L2: 2.5 MiB
    desc: 2x1.2 MiB L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 584 high: 1136 min/max: 400/3500 scaling:
    driver: intel_pstate governor: powersave cores: 1: 400 2: 400
    3: 400 4: 1136 bogomips: 15980
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 avx512_bitalg
    avx512_vbmi2 avx512_vnni avx512_vp2intersect
    avx512_vpopcntdq avx512bw avx512cd avx512dq avx512f
    avx512ifma avx512vbmi avx512vl bmi1 bmi2 bts cat_l2 cdp_l2
    clflush clflushopt clwb cmov constant_tsc cpuid cpuid_fault
    cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est
    f16c flexpriority flush_l1d fma fpu fsgsbase fsrm fxsr gfni
    ht hwp hwp_act_window hwp_epp hwp_notify hwp_pkg_req ibpb
    ibrs ibrs_enhanced ibt ida intel_pt invpcid invpcid_single
    lahf_lm lm mca mce md_clear mmx monitor movbe movdir64b
    movdiri msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pcid
    pclmulqdq pdcm pdpe1gb pebs pge pku pln pni popcnt pse pse36
    pts rdpid rdrand rdseed rdt_a rdtscp rep_good sdbg sep
    sha_ni smap smep split_lock_detect ss ssbd sse sse2 sse4_1
    sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust
    tsc_deadline_timer tsc_known_freq umip vaes vme vmx vnmi
    vpclmulqdq vpid x2apic xgetbv1 xsave xsavec xsaveopt xsaves
    xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass
    disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and
    __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS;
    IBPB: conditional; RSB filling; PBRSB-eIBRS: SW sequence;
    BHI: SW loop, KVM: SW loop
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Tiger Lake-LP GT2 [UHD Graphics G4]
    vendor: ASUSTeK driver: i915 v: kernel arch: Gen-12.1
    process: Intel 10nm built: 2020-21 ports: active: eDP-1
    empty: DP-1,HDMI-A-1 bus-ID: 0000:00:02.0 chip-ID: 8086:9a78
    class-ID: 0300
  Device-2: Sonix USB2.0 HD UVC WebCam driver: uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0
    bus-ID: 1-3:3 chip-ID: 322e:2103 class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland
    v: 24.1.0 compositor: kwin_x11 driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
    s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: ChiMei InnoLux 0x14d4 built: 2020
    res: 1920x1080 hz: 60 dpi: 158 gamma: 1.2 chroma: red: x: 0.592
    y: 0.349 green: x: 0.329 y: 0.557 blue: x: 0.153 y: 0.118
    white: x: 0.314 y: 0.329 size: 309x173mm (12.17x6.81")
    diag: 354mm (13.9") ratio: 16:9 modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0
    drv: iris device: 1 drv: swrast gbm: drv: iris surfaceless:
    drv: iris x11: drv: iris inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa
    v: 24.1.1-manjaro1.1 glx-v: 1.4 direct-render: yes
    renderer: Mesa Intel UHD Graphics (TGL GT2)
    device-ID: 8086:9a78 memory: 3.64 GiB unified: yes
  API: Vulkan v: 1.3.279 layers: 6 device: 0
    type: integrated-gpu name: Intel UHD Graphics (TGL GT2)
    driver: mesa intel v: 24.1.1-manjaro1.1 device-ID: 8086:9a78
    surfaces: xcb,xlib

In the BIOS there is no way to edit the amount of RAM, like video memory.

glxinfo told me that Video Memory had 8192 MB available, but now after rearranging the RAM only 3142 MB is available

It is pretty normal that the half available memory is allocated as possible space for video memory. The video memory is addressed dynamically, it is not static like on external GPU. I see no problem here. So when your application allocates more than 3821MB video memory, then it allocate more if free memory is available. This number is just a placeholder and a guideline.

1 Like

Thanks for the reply. It just scares me that before 8 GB was always available, but now after changing the RAM, only 3 GB. But do I understand correctly that this value can change frequently?

yes :+1:

1 Like

Oh, thank you very much. I was just a little confused about this, so I got worried and started asking. Now i understand how it works. :grin:

2 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.