Home/ Questions/Q 8137479
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T11:08:15+00:00

I’m running a debian stable ThinkPad X1 (1294-3QG) with exactly three packages from squeeze-backports

  • 0

I’m running a debian stable ThinkPad X1 (1294-3QG) with exactly three packages from squeeze-backports needed for the GraphicsModi:

initramfs-tools 0.99~bpo60+1
linux-base 3.4~bpo60+1
linux-image-3.2.0-0.bpo.2-amd64 3.2.9-1~bpo60

While running that kernel, starting for example paraview results in those errors:

Unrecognized deviceID 126
X Error: BadAlloc (insufficient resources for operation) 11
  Extension:    154 (Uknown extension)
  Minor opcode: 3 (Unknown request)
  Resource id:  0x3200273
X Error: GLXBadContext 169
  Extension:    154 (Uknown extension)
  Minor opcode: 5 (Unknown request)
  Resource id:  0x32002b0
paraview: ../../src/xcb_io.c:183: process_responses: Zusicherung »!(req && current_request && !(((long) (req->sequence) - (long) (current_request)) <= 0))« nicht erfüllt.

Somewhere on the net, I found the hint to offer the memory settings in the xorg.conf, but that did not solve my problem.
Starting within the current stable kernel works fine.

Running glxgearsresults similar:

Unrecognized deviceID 126
X Error of failed request:  BadAlloc (insufficient resources for operation)
  Major opcode of failed request:  154 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Serial number of failed request:  27
  Current serial number in output stream:  29

I further tried, to solve the problem by updating xserver-xorg-video-intel (and all dependencies libdrm-intel1 libxfont1, xserver-common, xserver-xorg, xserver-xorg-core, xserver-xorg-input-evdev, xserver-xorg-video-fbdev and xserver-xorg-video-vesa) to backports, but that was not prosperous.

Additional, I found the entry

[drm] MTRR allocation failed.  Graphics performance may suffer.

in the output of dmesg.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I solved it now on my own by updating some mesa concerning packages. I’m running debian stable with those following packages from backports:

    initramfs-tools, libdrm-intel1, libgl1-mesa-dev, libgl1-mesa-dri,
    libgl1-mesa-glx, linux-base, linux-headers-3.2.0-0.bpo.1-all-amd64,
    linux-headers-3.2.0-0.bpo.1-amd64, linux-headers-3.2.0-0.bpo.1-common,
    linux-headers-3.2.0-0.bpo.1-common-rt,
    linux-headers-3.2.0-0.bpo.1-rt-amd64,
    linux-headers-3.2.0-0.bpo.2-all-amd64,
    linux-headers-3.2.0-0.bpo.2-amd64, linux-headers-3.2.0-0.bpo.2-common,
    linux-headers-3.2.0-0.bpo.2-common-rt,
    linux-headers-3.2.0-0.bpo.2-rt-amd64, linux-image-3.2.0-0.bpo.2-amd64,
    linux-kbuild-3.2, mesa-common-dev

    Hoping this info will help other, too.

    • 0