Skip Navigation

Search

Should I use zram?

Hello, I came across zram recently and I'd like to know if I should use it, my laptop only has ~4GB of ram, and for the most part it'll only stutter when I open multiple programs or a game, so would zram be adequate in my case?

Also, would the compressing and decompressing have a significant impact on my cpu?

8

steam is rendering strange

Xwayland was borked. Reinstalled all graphics drivers and mesa, Xwayland has fixed the issue, now all CEF windows render normally.

################################# Og post

a few applications that use CEF to render applications have serious artifacting (main install of arch with sway), i dont believe this is a gpu issue as i installed arch with sway minimal config and the issue was resolved.

anyway i am hoping someone smarter than me could direct me on where to start with debugging this issue :)

system:

OS: Arch Linux

KERNEL: 6.7.3-arch1-2

CPU: AMD Ryzen 7 5800X 8-Core

GPU: AMD Radeon RX 6900 XT (radeonsi, navi21, LLVM 16.0.6, DRM 3.57, 6.7.3-arch1-2)

GPU DRIVER: 4.6 Mesa 24.0.0-devel (git-95ad0c750c)

RAM: 32GB

3

Device goes to emergency mode: "Timed out waiting for device"

Screenshot as text (excuse me if I have mistyped anything) DMAR: [Firmware Bug]: No firmware reserved region can cover this Contact BIOS vendor for fixes x86/cpu: SGX disabled by BIOS. ima: Error Communicating to TPM chip ima: Error Communicating to TPM chip ima: Error Communicating to TPM chip ima: Error Communicating to TPM chip ima: Error Communicating to TPM chip ima: Error Communicating to TPM chip ima: Error Communicating to TPM chip ima: Error Communicating to TPM chip /dev/sda2: clean, 529831/31162368 files, 8432995/1246456392 blocks Timed out waiting for device dev-disk-by\x2duuid-1ee4Scef\x2deb91\x2... Dependency failed for drive.mount - /drive. Dependency failed for local-fs.target - Local File Sustems. You are in emergency mode mode. After logging in, type “journalctl -xb" to view system logs, "systemctl reboot" to reboot, “systemctl default" or "exit" to boot into default mode. Give root password for maintenance (or press Control-D to continue):

I installed an m.2 SATA SSD into the device in addition to the old SATA SSD. However, it wouldn't boot properly. I decided to take it out, and now it won't boot using the existing SSD either. Does anyone know what could be the issue? So far, I've tried the following:

  1. Checking boot media order in BIOS
  2. Resetting BIOS
  3. Ensuring fstab used UUID's (it already did)
  4. Updating initramfs

I'm using Debian 6.1.38-2 (2023-07-27).

EDIT: Dran's suggestion to remove the /drive entry from fstab resolved the issue.

5