Re: Driver para las gráficas Intel funcional a medias
El día 7 de octubre de 2014, 16:47, Camaleón <noelamac@gmail.com> escribió:
> El Mon, 06 Oct 2014 21:08:34 +0200, Javier Silva escribió:
>
>> El día 6 de octubre de 2014, 15:51, Camaleón <noelamac@gmail.com> escribió:
>>>
>>> Como te dice Yukiteru san, gnome-shell necesita un adaptador gráfico con
>>> aceleración 3D (tanto en hardware como el driver), así que eso es lo
>>> primero que tendrías que comprobar, si se ha instalado/habilitado
>>> correctamente y siendo un chipset de intel no deberías tener problemas.
>>>
>>> grep -i dri /var/log/Xorg.0.log
>
> (...)
>
>> [ 8.034] (II) intel(0): direct rendering: DRI2 Enabled
>> [ 8.061] (EE) AIGLX error: Calling driver entry point failed
>> [ 8.062] (II) AIGLX: Screen 0 is not DRI capable
>> [ 8.114] (II) GLX: Initialized DRISWRAST GL provider for screen 0
>
> Bueno, ahí veo un error (EE). Mira a ver si tienes instalado el paquete
> "libgl1-mesa-glx". Ese DRISWRAST me suena a "DRI software raster" que me
> parece que es renderizado por software, no por hardware.
>
dpkg -l libgl* |grep -i "^ii"
ii libgl1-mesa-dri:amd64 8.0.5-4+deb7u2
amd64 free implementation of the OpenGL API -- DRI
modules
ii libgl1-mesa-dri-experimental:amd64 8.0.5-4+deb7u2
amd64 free implementation of the OpenGL API -- Extra
DRI modules
ii libgl1-mesa-glx:amd64 8.0.5-4+deb7u2
amd64 free implementation of the OpenGL API -- GLX
runtime
ii libglade2-0 1:2.6.4-1
amd64 library to load .glade files at runtime
ii libglapi-mesa:amd64 8.0.5-4+deb7u2
amd64 free implementation of the GL API -- shared
library
ii libglew1.7:amd64 1.7.0-3
amd64 OpenGL Extension Wrangler - runtime environment
ii libglib-perl 3:1.260-1
amd64 interface to the GLib and GObject libraries
ii libglib2.0-0:amd64 2.33.12+really2.32.4-5
amd64 GLib library of C routines
ii libglib2.0-bin 2.33.12+really2.32.4-5
amd64 Programs for the GLib library
ii libglib2.0-cil 2.12.10-5
amd64 CLI binding for the GLib utility library 2.12
ii libglib2.0-data 2.33.12+really2.32.4-5
all Common files for GLib library
ii libglibmm-2.4-1c2a:amd64 2.32.1-1
amd64 C++ wrapper for the GLib toolkit (shared
libraries)
ii libglu1-mesa:amd64 8.0.5-4+deb7u2
amd64 Mesa OpenGL utility library (GLU)
>> Esto, después de la instalación del libgl1-mesa-dri-experimental,
>> exactamente igual que antes.
>>
>> La gráfica si que tiene aceleración, lo que creo es que debe tener
>> alguna cosa 'extraña' con el tema de la nueva aceleración SNA ¿es
>> posible?
>
> A ojos de gnome-shell lo único que le debe interesar para iniciarse
> es que esté activada la aceleración 3D en el driver de la tarjeta
> gráfica, que vaya más fino o a trompicones sería otro cantar :-?
>
Efectivamente veo que el problema es la falta de aceleración 3D, pero
lo cierto es que no veo de qué forma reparar esto, si es que tiene
solución, o simplemente es una carencia del propio driver.
Aquí hay más información del sistema que tiene dicho problema:
# dmesg |grep -i intel
[ 0.000000] Reserving Intel graphics stolen memory at 0x7b000000-0x7effffff
[ 0.097086] smpboot: CPU0: Intel(R) Celeron(R) CPU N2930 @
1.83GHz (fam: 06, model: 37, stepping: 08)
[ 0.097153] Performance Events: PEBS fmt2+, 8-deep LBR, Silvermont
events, full-width counters, Intel PMU driver.
[ 0.994946] intel_idle: MWAIT substates: 0x33000020
[ 0.994949] intel_idle: v0.4 model 0x37
[ 0.994952] intel_idle: lapic_timer_reliable_states 0xffffffff
[ 1.018237] Intel P-state driver initializing.
[ 1.018260] Intel pstate controlling: cpu 0
[ 1.018298] Intel pstate controlling: cpu 1
[ 1.018332] Intel pstate controlling: cpu 2
[ 1.018369] Intel pstate controlling: cpu 3
[ 2.099252] fb: switching to inteldrmfb from simple
[ 2.150964] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[ 2.176045] intel_rapl: RAPL domain uncore detection failed
[ 2.176052] intel_rapl: RAPL domain dram detection failed
[ 2.978133] fbcon: inteldrmfb (fb0) is primary device
[ 4.658686] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 4.729176] snd_hda_intel 0000:00:1b.0: irq 107 for MSI/MSI-X
[ 4.990791] input: HDA Intel PCH Headphone as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input13
[ 4.991369] input: HDA Intel PCH HDMI/DP,pcm=3 as
/devices/pci0000:00/0000:00:1b.0/sound/card0/input14
# dmesg |grep -i microcode
[ 0.979799] microcode: CPU0 sig=0x30678, pf=0x8, revision=0x80c
[ 0.979816] microcode: CPU1 sig=0x30678, pf=0x8, revision=0x80c
[ 0.979828] microcode: CPU2 sig=0x30678, pf=0x8, revision=0x80c
[ 0.979844] microcode: CPU3 sig=0x30678, pf=0x8, revision=0x80c
[ 0.979974] microcode: Microcode Update Driver: v2.00
<tigran@aivazian.fsnet.co.uk>, Peter Oruba
No es muy extenso el archivo de errores, por lo que prefiero dejarlo
aquí para futuras referencias de otras personas con el mismo problema,
en lugar de llevar su contenido a pastebin:
$ cat .xsession-errors
/etc/gdm3/Xsession: Beginning session setup...
localuser:javier being added to access control list
openConnection: connect: No existe el fichero o el directorio
cannot connect to brltty at :0
[intel_init_bufmgr:584] Error initializing buffer manager.
gnome-session-is-accelerated: No hardware 3D support.
gnome-session-check-accelerated: Helper exited with code 256
x-session-manager[3396]: WARNING: Session 'gnome' runnable check
failed: Salió con el código 1
GNOME_KEYRING_CONTROL=/home/javier/.cache/keyring-rWZuZ4
SSH_AUTH_SOCK=/home/javier/.cache/keyring-rWZuZ4/ssh
GNOME_KEYRING_CONTROL=/home/javier/.cache/keyring-rWZuZ4
SSH_AUTH_SOCK=/home/javier/.cache/keyring-rWZuZ4/ssh
GNOME_KEYRING_CONTROL=/home/javier/.cache/keyring-rWZuZ4
SSH_AUTH_SOCK=/home/javier/.cache/keyring-rWZuZ4/ssh
GNOME_KEYRING_CONTROL=/home/javier/.cache/keyring-rWZuZ4
SSH_AUTH_SOCK=/home/javier/.cache/keyring-rWZuZ4/ssh
GPG_AGENT_INFO=/home/javier/.cache/keyring-rWZuZ4/gpg:0:1
p11-kit: invalid config filename, will be ignored in the future:
/etc/pkcs11/modules/gnome-keyring-module
(gnome-panel:3504): Gtk-CRITICAL **:
gtk_accelerator_parse_with_keycode: assertion `accelerator != NULL'
failed
** (gnome-panel:3504): WARNING **: Unable to parse mouse modifier '(null)'
glibtop: Non-standard uts for running kernel:
release 3.16-0.bpo.2-amd64=3.16.0 gives version code 200704
Initializing tracker-miner-fs...
Initializing tracker-store...
Tracker-Message: Setting up monitor for changes to config
file:'/home/javier/.config/tracker/tracker-miner-fs.cfg'
Starting log:
File:'/home/javier/.local/share/tracker/tracker-miner-fs.log'
Tracker-Message: Setting up monitor for changes to config
file:'/home/javier/.config/tracker/tracker-store.cfg'
Tracker-Message: Setting up monitor for changes to config
file:'/home/javier/.config/tracker/tracker-store.cfg'
Starting log:
File:'/home/javier/.local/share/tracker/tracker-store.log'
(gnome-panel:3504): Gtk-CRITICAL **:
gtk_accelerator_parse_with_keycode: assertion `accelerator != NULL'
failed
** (gnome-panel:3504): WARNING **: Unable to parse mouse modifier '(null)'
p11-kit: invalid config filename, will be ignored in the future:
/etc/pkcs11/modules/gnome-keyring-module
(gnome-panel:3504): GLib-GObject-WARNING **:
/tmp/buildd/glib2.0-2.33.12+really2.32.4/./gobject/gsignal.c:2459:
signal `size_request' is invalid for instance `0xfc4c60'
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area
(gnome-settings-daemon:3458): PackageKit-WARNING **: couldn't parse
execption 'GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_5ftransaction_5ferror.Code4:
GetDistroUpgrades not supported by backend', please report
(gnome-settings-daemon:3458): updates-plugin-WARNING **: failed to get
upgrades: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_5ftransaction_5ferror.Code4:
GetDistroUpgrades not supported by backend
Muchas gracias por la ayuda que me estáis prestando.
Saludos,
Javier Silva.
Reply to: