Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #201891 > unrolled thread

hw acceleration for display stopped working

Started byTapio Lehtonen <tale@taleman.fi>
First post2018-10-30 17:00 +0100
Last post2018-11-01 14:40 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.debian.user


Contents

  hw acceleration for display stopped working Tapio Lehtonen <tale@taleman.fi> - 2018-10-30 17:00 +0100
    Re: hw acceleration for display stopped working Curt <curty@free.fr> - 2018-11-01 14:40 +0100

#201891 — hw acceleration for display stopped working

FromTapio Lehtonen <tale@taleman.fi>
Date2018-10-30 17:00 +0100
Subjecthw acceleration for display stopped working
Message-ID<wOEAW-vd-9@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

• Debian GNU/Linux 9.5 Stretch
• 20:00.0 VGA compatible controller: NVIDIA Corporation GP108 (rev a1)
• AMD Ryzen 5 1500X Quad-Core Processor
    
Programs using hw acceleration for display stopped working yesterday.

  ┌────
  │ $ glxinfo 
  │ name of display: :0
  │ libGL error: No matching fbConfigs or visuals found
  │ libGL error: failed to load driver: swrast
  │ X Error of failed request:  GLXBadContext
  │   Major opcode of failed request:  154 (GLX)
  │   Minor opcode of failed request:  6 (X_GLXIsDirect)
  │   Serial number of failed request:  48
  │   Current serial number in output stream:  47
  └────
		      
Chromium starts, but displays page title and only a blank window.

  ┌────
  │ $ LANG=C chromium 
  │ ATTENTION: default value of option force_s3tc_enable overridden by environment.
  │ libGL error: No matching fbConfigs or visuals found
  │ libGL error: failed to load driver: swrast
  │ [11612:11612:1030/165704.452780:ERROR:gl_context_glx.cc(227)] Couldn't make context current with X drawable.
  │ [11612:11612:1030/165704.452831:ERROR:gpu_info_collector.cc(68)] gl::GLContext::MakeCurrent() failed
  │ [11571:11641:1030/165704.582923:ERROR:nss_util.cc(748)] After loading Root Certs, loaded==false: NSS error code: -8018
  │ [11710] Uncaught exception of type <type'exceptions.AttributeError'> occured
  │   File "/usr/bin/chrome-gnome-shell", line 226, in on_input
  │     self.process_request(request)
  │   File "/usr/bin/chrome-gnome-shell", line 375, in process_request
  │     'shellVersion': shell_version.unpack(),
  │ [11710] Exception: 'NoneType' object has no attribute 'unpack'
  │ tale@ryzen /home/tale
  └────
	
	
	
I'm using NVidia drivers from stretch-backports, the versions in
Stretch do not support the chip on my display card. The NVidia modules
seem to be loaded OK:
  
    ┌────
    │ $ lsmod | grep -i nvidia
    │ nvidia_drm             49152  1
    │ drm_kms_helper        196608  1 nvidia_drm
    │ drm                   454656  4 nvidia_drm,drm_kms_helper
    │ nvidia_modeset       1110016  3 nvidia_drm
    │ nvidia              14393344  83 nvidia_modeset
    │ ipmi_msghandler        61440  2 nvidia,ipmi_devintf
    └────
		    
I upgraded what was upgradeable, with -t stretch-backports to get
three packages that were held for reasons.
  
If I start
      ┌────
      │ chromium --disable-gpu
      └────
it works and pages are displayd OK.
	    
So, what is wrong with GLX, NVidia driver or something else that got
broken on my setup yesterday? How to fix? 

-- 
Tapio Lehtonen
tapio.lehtonen@iki.fi http://www.iki.fi/tapio.lehtonen

[toc] | [next] | [standalone]


#201962

FromCurt <curty@free.fr>
Date2018-11-01 14:40 +0100
Message-ID<wPlmy-TS-3@gated-at.bofh.it>
In reply to#201891
On 2018-10-30, Tapio Lehtonen <tale@taleman.fi> wrote:
>
> • Debian GNU/Linux 9.5 Stretch
> • 20:00.0 VGA compatible controller: NVIDIA Corporation GP108 (rev a1)
> • AMD Ryzen 5 1500X Quad-Core Processor
>     
> Programs using hw acceleration for display stopped working yesterday.

What happened yesterday besides hw acceleration breaking?

>   ┌────
>   │ $ glxinfo 
>   │ name of display: :0
>   │ libGL error: No matching fbConfigs or visuals found
>   │ libGL error: failed to load driver: swrast
>   │ X Error of failed request:  GLXBadContext
>   │   Major opcode of failed request:  154 (GLX)
>   │   Minor opcode of failed request:  6 (X_GLXIsDirect)
>   │   Serial number of failed request:  48
>   │   Current serial number in output stream:  47
>   └────

Maybe 

 LIBGL_DEBUG=verbose glxgears

will say something helpful about where libGL is looking for and not
finding its thingamajiggers.

-- 
When you have fever you are heavy and light, you are small and swollen, you
climb endlessly a ladder which turns like a wheel. 
--Jean Rhys, Voyage in the Dark

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web