Cinnamon / ejecutandose en modo de renderizado por software. exDebian
  1. Inicio
  2. Foros
  3. General
  4. Instalación
  5. Cinnamon / ejecutandose en modo de renderizado por software.

Cinnamon / ejecutandose en modo de renderizado por software.

19 envíos / 0 nuevos
Inicie sesión o regístrese para comentar
Último envío
#1 Mar, 07/08/2018 - 22:16
Gnome
Imagen de Gnome
Desconectado/a
se unió: 06/08/18

Cinnamon / ejecutandose en modo de renderizado por software.

Estado: 
[ACTIVO]

Hola. he instalado debian 9.5 con el escritorio de cinnamon y me arroja la siguiente al iniciar.

 

 

Quisiera saber donde solucionar el problema con el driver o algún otro problema.

Mar, 07/08/2018 - 22:31
rockyiii
Imagen de rockyiii
Desconectado/a
administrator
se unió: 11/01/16

abre una terminal  e instala lshw

su
apt update && apt install lshw

luego ejecuta

lshw -short

y pega su contenido aca

Mié, 08/08/2018 - 02:08
Gnome
Imagen de Gnome
Desconectado/a
se unió: 06/08/18

lshw -short

root@debian:/home/gnome# lshw -short
H/W path         Device      Class       Description
====================================================
                             system      Compaq 15 Notebook PC (J2N28LA#AKH)
/0                           bus         21F7
/0/0                         memory      128KiB BIOS
/0/f                         memory      4GiB System Memory
/0/f/0                       memory      4GiB SODIMM DDR3 Synchronous Unbuffered
/0/15                        processor   AMD E1-2100 APU with Radeon(TM) HD Grap
/0/15/16                     memory      128KiB L1 cache
/0/15/17                     memory      1MiB L2 cache
/0/100                       bridge      Family 16h Processor Root Complex
/0/100/1                     display     Kabini [Radeon HD 8210]
/0/100/1.1                   multimedia  Kabini HDMI/DP Audio
/0/100/2.1                   bridge      Family 16h Processor Functions 5:1
/0/100/2.3                   bridge      Family 16h Processor Functions 5:1
/0/100/2.3/0                 generic     RTS5229 PCI Express Card Reader
/0/100/2.4                   bridge      Family 16h Processor Functions 5:1
/0/100/2.4/0     wlo1        network     AR9485 Wireless Network Adapter
/0/100/2.5                   bridge      Family 16h Processor Functions 5:1
/0/100/2.5/0     enp4s0      network     RTL8101/2/6E PCI Express Fast/Gigabit E
/0/100/10                    bus         FCH USB XHCI Controller
/0/100/10/0      usb3        bus         xHCI Host Controller
/0/100/10/0/2                bus         USB2.0 Hub
/0/100/10/1      usb4        bus         xHCI Host Controller
/0/100/11                    storage     FCH SATA Controller [AHCI mode]
/0/100/12                    bus         FCH USB OHCI Controller
/0/100/12/1      usb5        bus         OHCI PCI host controller
/0/100/12/1/1                input       Wireless Device
/0/100/12.2                  bus         FCH USB EHCI Controller
/0/100/12.2/1    usb1        bus         EHCI Host Controller
/0/100/13                    bus         FCH USB OHCI Controller
/0/100/13/1      usb6        bus         OHCI PCI host controller
/0/100/13.2                  bus         FCH USB EHCI Controller
/0/100/13.2/1    usb2        bus         EHCI Host Controller
/0/100/13.2/1/1              multimedia  HP Webcam
/0/100/14                    bus         FCH SMBus Controller
/0/100/14.2                  multimedia  FCH Azalia Controller
/0/100/14.3                  bridge      FCH LPC Bridge
/0/100/14.7                  generic     FCH SD Flash Controller
/0/101                       bridge      Family 16h Processor Function 0
/0/102                       bridge      Family 16h Processor Function 0
/0/103                       bridge      Family 16h Processor Function 1
/0/104                       bridge      Family 16h Processor Function 2
/0/105                       bridge      Family 16h Processor Function 3
/0/106                       bridge      Family 16h Processor Function 4
/0/107                       bridge      Family 16h Processor Function 5
/0/1             scsi0       storage     
/0/1/0.0.0       /dev/sda    disk        120GB FUJITSU MHW2120B
/0/1/0.0.0/1                 volume      511MiB Windows FAT volume
/0/1/0.0.0/2     /dev/sda2   volume      20GiB EXT4 volume
/0/1/0.0.0/3     /dev/sda3   volume      7290MiB EXT4 volume
/0/1/0.0.0/4     /dev/sda4   volume      3535MiB Linux swap volume
/0/1/0.0.0/5     /dev/sda5   volume      1300MiB EXT4 volume
/0/1/0.0.0/6     /dev/sda6   volume      79GiB EXT4 volume
/0/2             scsi1       storage     
/0/2/0.0.0       /dev/cdrom  disk        DVDRW  GUB0N
/1                           power       OA03031
root@debian:/home/gnome#

 

Mié, 08/08/2018 - 13:09
Panko
Imagen de Panko
Desconectado/a
moderador
se unió: 18/02/16

Posiblemente sea problema de drivers de vídeo, viendo que tienes una amd kabini, sería interesante que nos pusieras la salida del comando

journalctl -b -p err

para ver si hay algún problema de falta de firmware para tu gráfica. Es posible que falte la instalación de algún paquete de firmwares, así como el driver xserver-xorg-video-amdgpu para que use éste en lugar del otro radeon.

 

P.D.: Como a todos digo... usa el botón "insertar fragmento de código" para meter la salida de  los comandos, así te quedará como me ha quedado a mí el que te he pedido y el post será más cómo de leer y más "entendible".

  No hay bar que por bien no venga....
Mié, 08/08/2018 - 21:49
Gnome
Imagen de Gnome
Desconectado/a
se unió: 06/08/18 
gnome@debian:~$ journalctl -b -p err
Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
No journal files were opened due to insufficient permissions.
gnome@debian:~$

 

Mié, 08/08/2018 - 23:37
rockyiii
Imagen de rockyiii
Desconectado/a
administrator
se unió: 11/01/16

En principio necesitas tener permisos de root para ejecutar ese comano

su
journalctl -b -p err

 

Jue, 09/08/2018 - 00:45
Gnome
Imagen de Gnome
Desconectado/a
se unió: 06/08/18 
gnome@debian:~$ journalctl -b -p err
Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
No journal files were opened due to insufficient permissions.
gnome@debian:~$ uname -r
4.9.0-7-amd64
gnome@debian:~$ su
Contraseña: 
root@debian:/home/gnome# journalctl -b -p err
-- Logs begin at Wed 2018-08-08 20:35:23 -04, end at Wed 2018-08-08 23:42:21 -04
ago 08 20:35:23 debian kernel: sd 2:0:0:0: [sdb] No Caching mode page found
ago 08 20:35:23 debian kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write thr
ago 08 20:35:27 debian kernel: [drm:radeon_pci_probe [radeon]] *ERROR* radeon ke
ago 08 20:35:27 debian kernel: kvm: disabled by bios
ago 08 20:35:27 debian kernel: kvm: disabled by bios
ago 08 20:35:33 debian avahi-daemon[421]: chroot.c: open() failed: No such file 
ago 08 20:35:36 debian dhclient[482]: Failed to get interface index: No such dev
ago 08 20:35:36 debian dhclient[482]: 
ago 08 20:35:36 debian dhclient[482]: If you think you have received this messag
ago 08 20:35:36 debian dhclient[482]: than a configuration issue please read the
ago 08 20:35:36 debian dhclient[482]: bugs on either our web page at www.isc.org
ago 08 20:35:36 debian dhclient[482]: before submitting a bug.  These pages expl
ago 08 20:35:36 debian dhclient[482]: process and the information we find helpfu
ago 08 20:35:36 debian dhclient[482]: 
ago 08 20:35:36 debian dhclient[482]: exiting.
ago 08 20:35:36 debian systemd[1]: Failed to start Raise network interfaces.
ago 08 20:35:39 debian kernel: r8169 0000:04:00.0: firmware: failed to load rtl_
ago 08 20:36:29 debian pulseaudio[872]: [pulseaudio] bluez5-util.c: GetManagedOb
lines 1-19/19 (END)

 

Jue, 09/08/2018 - 01:46
Panko
Imagen de Panko
Desconectado/a
moderador
se unió: 18/02/16

la salida está cortada y no se ve el final de las líneas, usa una consola más grande. Se ve que te marca, a parte de otros errores que en el momento dado se pueden tratar en otro hilo si tienes otros problemas, un error con RADEON, pero si no se ve que dice...

  No hay bar que por bien no venga....
Jue, 09/08/2018 - 01:54
Gnome
Imagen de Gnome
Desconectado/a
se unió: 06/08/18 
root@debian:/home/gnome# journalctl -b -p err
-- Logs begin at Wed 2018-08-08 20:35:23 -04, end at Thu 2018-08-09 00:52:03 -04. --
ago 08 20:35:23 debian kernel: sd 2:0:0:0: [sdb] No Caching mode page found
ago 08 20:35:23 debian kernel: sd 2:0:0:0: [sdb] Assuming drive cache: write through
ago 08 20:35:27 debian kernel: [drm:radeon_pci_probe [radeon]] *ERROR* radeon kernel modesetting for R600 or later requires firmware-amd-graphics.
ago 08 20:35:27 debian kernel: kvm: disabled by bios
ago 08 20:35:27 debian kernel: kvm: disabled by bios
ago 08 20:35:33 debian avahi-daemon[421]: chroot.c: open() failed: No such file or directory
ago 08 20:35:36 debian dhclient[482]: Failed to get interface index: No such device
ago 08 20:35:36 debian dhclient[482]: 
ago 08 20:35:36 debian dhclient[482]: If you think you have received this message due to a bug rather
ago 08 20:35:36 debian dhclient[482]: than a configuration issue please read the section on submitting
ago 08 20:35:36 debian dhclient[482]: bugs on either our web page at www.isc.org or in the README file
ago 08 20:35:36 debian dhclient[482]: before submitting a bug.  These pages explain the proper
ago 08 20:35:36 debian dhclient[482]: process and the information we find helpful for debugging..
ago 08 20:35:36 debian dhclient[482]: 
ago 08 20:35:36 debian dhclient[482]: exiting.
ago 08 20:35:36 debian systemd[1]: Failed to start Raise network interfaces.
ago 08 20:35:39 debian kernel: r8169 0000:04:00.0: firmware: failed to load rtl_nic/rtl8106e-1.fw (-2)
ago 08 20:36:29 debian pulseaudio[872]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a

 

Jue, 09/08/2018 - 13:48
Panko
Imagen de Panko
Desconectado/a
moderador
se unió: 18/02/16

A parte de algunos erroes normales que no tienen importancia, como el de chroot o el de pulseaudio, hay uno que te indica que es más que probable que necesites instalar el paquete de firmwares para radeon:

ago 08 20:35:27 debian kernel: [drm:radeon_pci_probe [radeon]] *ERROR* radeon kernel modesetting for R600 or later requires firmware-amd-graphics

con lo que necesitas ejecutar

su -
apt install firmware-amd-graphics

o buscar como desactivar el modesetting para tu gráfica.

 

Por otra parte, aunque debería ser tema de otro hilo, te adelanto que te falta también un firmware para la tarjeta de red cableada. Necesitas instalar el paquete firmware-realtek

  No hay bar que por bien no venga....
Jue, 09/08/2018 - 16:03
Gnome
Imagen de Gnome
Desconectado/a
se unió: 06/08/18

la radeon ya esta. voy a ver que tal la firmwar-realtek ;)!

Vie, 10/08/2018 - 00:14 (Responder a #11)
Panko
Imagen de Panko
Desconectado/a
moderador
se unió: 18/02/16

Gnome wrote:

la radeon ya esta. voy a ver que tal la firmwar-realtek ;)!

¿La de radeon ya está? ¿A que te refieres? El mensaje que te he puesto es de tu log, y precisamente dice que falta el paquete firmware-amd-graphics, no que falte el paquete del driver de Radeon...

  No hay bar que por bien no venga....
Sáb, 11/08/2018 - 07:24
Gnome
Imagen de Gnome
Desconectado/a
se unió: 06/08/18

tengo estos nuevos problemas...

gnome@debian:~$ su
Contraseña: 
root@debian:/home/gnome# journalctl -b -p err
-- Logs begin at Sat 2018-08-11 06:09:27 -04, end at Sat 2018-08-11 06:25:01 -04
ago 11 06:09:27 debian kernel: hub 4-1:1.0: hub_hub_status failed (err = -71)
ago 11 06:09:27 debian kernel: hub 4-1:1.0: config failed, can't get hub status 
ago 11 06:09:32 debian kernel: kvm: disabled by bios
ago 11 06:09:36 debian systemd-backlight[366]: Failed to get backlight or LED de
ago 11 06:09:36 debian systemd[1]: Failed to start Load/Save Screen Backlight Br
ago 11 06:09:39 debian avahi-daemon[497]: chroot.c: open() failed: No such file 
ago 11 06:09:41 debian dhclient[492]: Failed to get interface index: No such dev
ago 11 06:09:41 debian dhclient[492]: 
ago 11 06:09:41 debian dhclient[492]: If you think you have received this messag
ago 11 06:09:41 debian dhclient[492]: than a configuration issue please read the
ago 11 06:09:41 debian dhclient[492]: bugs on either our web page at www.isc.org
ago 11 06:09:41 debian dhclient[492]: before submitting a bug.  These pages expl
ago 11 06:09:41 debian dhclient[492]: process and the information we find helpfu
ago 11 06:09:41 debian dhclient[492]: 
ago 11 06:09:41 debian dhclient[492]: exiting.
ago 11 06:09:41 debian systemd[1]: Failed to start Raise network interfaces.
ago 11 06:10:37 debian pulseaudio[970]: [pulseaudio] bluez5-util.c: GetManagedOb
 ESCOC

 -04, end at Sat 2018-08-11 06:25:01 -04. --
.0: hub_hub_status failed (err = -71)
.0: config failed, can't get hub status (err -71)
bled by bios
[366]: Failed to get backlight or LED device 'backlight:acpi_video0': No such de
d to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
: chroot.c: open() failed: No such file or directory
iled to get interface index: No such device

 you think you have received this message due to a bug rather
an a configuration issue please read the section on submitting
gs on either our web page at www.isc.org or in the README file
fore submitting a bug.  These pages explain the proper
ocess and the information we find helpful for debugging..

iting.
d to start Raise network interfaces.
[pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Err
~
~
 ESCOC
. --

(err -71)

vice 'backlight:acpi_video0': No such device
ightness of backlight:acpi_video0.
or directory
ice

e due to a bug rather
 section on submitting
 or in the README file
ain the proper
l for debugging..

jects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Pos
~
~
 ESCOC
vice
or.NoReply: Did not receive a reply. Possible causes include: the remote applica
~~
 ESCOC

sible causes include: the remote application did not send a reply, the message b
~
 ESCOC

tion did not send a reply, the message bus security policy blocked the reply, th
~
~
 ESCOC

us security policy blocked the reply, the reply timeout expired, or the network 
~
~
 ESCOC

e reply timeout expired, or the network connection was broken.
~
~
 ESCOC

connection was broken.
~

~
~
 ESCOC

e reply timeout expired, or the network connection was broken.
~
~~
 ESCOD

us security policy blocked the reply, the reply timeout expired, or the network 
~

 ESCOD


tion did not send a reply, the message bus security policy blocked the reply, th
~

~
 ESCOD

sible causes include: the remote application did not send a reply, the message b
~
~
 ESCOD


vice




or.NoReply: Did not receive a reply. Possible causes include: the remote applica
~
~
~
lines 1-18/18 (END)...skipping...


vice


or.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the
~~
~
~
 ESCOC


plication did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
~
~
~
~
~
 ESCOC
 reply, the reply timeout expired, or the network connection was broken.
~
~
~
~
 ESCOD



plication did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
~
~
 ESCOD


r.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the
~
~~
~
 ESCOD
 end at Sat 2018-08-11 06:25:01 -04. --
ub_hub_status failed (err = -71)
onfig failed, can't get hub status (err -71)
by bios
: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
oot.c: open() failed: No such file or directory
to get interface index: No such device

think you have received this message due to a bug rather
configuration issue please read the section on submitting
 either our web page at www.isc.org or in the README file
submitting a bug.  These pages explain the proper
 and the information we find helpful for debugging..

.
start Raise network interfaces.
eaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote ap
~
~
 ESCOD
- Logs begin at Sat 2018-08-11 06:09:27 -04, end at Sat 2018-08-11 06:25:01 -04. --
ago 11 06:09:27 debian kernel: hub 4-1:1.0: hub_hub_status failed (err = -71)
ago 11 06:09:27 debian kernel: hub 4-1:1.0: config failed, can't get hub status (err -71)
ago 11 06:09:32 debian kernel: kvm: disabled by bios
ago 11 06:09:36 debian systemd-backlight[366]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
ago 11 06:09:36 debian systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
ago 11 06:09:39 debian avahi-daemon[497]: chroot.c: open() failed: No such file or directory
ago 11 06:09:41 debian dhclient[492]: Failed to get interface index: No such device
ago 11 06:09:41 debian dhclient[492]: 
ago 11 06:09:41 debian dhclient[492]: If you think you have received this message due to a bug rather
ago 11 06:09:41 debian dhclient[492]: than a configuration issue please read the section on submitting
ago 11 06:09:41 debian dhclient[492]: bugs on either our web page at www.isc.org or in the README file
ago 11 06:09:41 debian dhclient[492]: before submitting a bug.  These pages explain the proper
ago 11 06:09:41 debian dhclient[492]: process and the information we find helpful for debugging..
ago 11 06:09:41 debian dhclient[492]: 
ago 11 06:09:41 debian dhclient[492]: exiting.
ago 11 06:09:41 debian systemd[1]: Failed to start Raise network interfaces.
ago 11 06:10:37 debian pulseaudio[970]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a 
~
~
 ESCOD
-- Logs begin at Sat 2018-08-11 06:09:27 -04, end at Sat 2018-08-11 06:25:01 -04. --
ago 11 06:09:27 debian kernel: hub 4-1:1.0: hub_hub_status failed (err = -71)
ago 11 06:09:27 debian kernel: hub 4-1:1.0: config failed, can't get hub status (err -71)
ago 11 06:09:32 debian kernel: kvm: disabled by bios
ago 11 06:09:36 debian systemd-backlight[366]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
ago 11 06:09:36 debian systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
ago 11 06:09:39 debian avahi-daemon[497]: chroot.c: open() failed: No such file or directory
ago 11 06:09:41 debian dhclient[492]: Failed to get interface index: No such device
ago 11 06:09:41 debian dhclient[492]: 
ago 11 06:09:41 debian dhclient[492]: If you think you have received this message due to a bug rather
ago 11 06:09:41 debian dhclient[492]: than a configuration issue please read the section on submitting
ago 11 06:09:41 debian dhclient[492]: bugs on either our web page at www.isc.org or in the README file
ago 11 06:09:41 debian dhclient[492]: before submitting a bug.  These pages explain the proper
ago 11 06:09:41 debian dhclient[492]: process and the information we find helpful for debugging..
ago 11 06:09:41 debian dhclient[492]: 
ago 11 06:09:41 debian dhclient[492]: exiting.
ago 11 06:09:41 debian systemd[1]: Failed to start Raise network interfaces.
ago 11 06:10:37 debian pulseaudio[970]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a 
~
-- Logs begin at Sat 2018-08-11 06:09:27 -04, end at Sat 2018-08-11 06:25:01 -04. --
ago 11 06:09:27 debian kernel: hub 4-1:1.0: hub_hub_status failed (err = -71)
ago 11 06:09:27 debian kernel: hub 4-1:1.0: config failed, can't get hub status (err -71)
ago 11 06:09:32 debian kernel: kvm: disabled by bios
ago 11 06:09:36 debian systemd-backlight[366]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
ago 11 06:09:36 debian systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
ago 11 06:09:39 debian avahi-daemon[497]: chroot.c: open() failed: No such file or directory
ago 11 06:09:41 debian dhclient[492]: Failed to get interface index: No such device
ago 11 06:09:41 debian dhclient[492]: 
ago 11 06:09:41 debian dhclient[492]: If you think you have received this message due to a bug rather
ago 11 06:09:41 debian dhclient[492]: than a configuration issue please read the section on submitting
ago 11 06:09:41 debian dhclient[492]: bugs on either our web page at www.isc.org or in the README file
ago 11 06:09:41 debian dhclient[492]: before submitting a bug.  These pages explain the proper
ago 11 06:09:41 debian dhclient[492]: process and the information we find helpful for debugging..
ago 11 06:09:41 debian dhclient[492]: 
ago 11 06:09:41 debian dhclient[492]: exiting.
ago 11 06:09:41 debian systemd[1]: Failed to start Raise network interfaces.
ago 11 06:10:37 debian pulseaudio[970]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a 
~
~
lines 1-18/18 (END)

 

 

Esto no es normal... casi no puedo creer lo que estoy viendo... ojú.(Fdo.: Panko)

Dom, 12/08/2018 - 05:40
Panko
Imagen de Panko
Desconectado/a
moderador
se unió: 18/02/16

No sé como lo verás tu, pero si yo me encuentro un post como el que acabas de poner cierro y me voy a otro hilo.... Eterno, la mayoría en blanco, y lo poco que pone cortado....

Ya volveré a ver que tienes que hacer cuando esté puesto en condiciones....

  No hay bar que por bien no venga....
Dom, 12/08/2018 - 20:14
Gnome
Imagen de Gnome
Desconectado/a
se unió: 06/08/18

KJakjakja. QUe mierda, si soy nuevo, es la replica de la consola. que quieres ?...!!

Dom, 09/09/2018 - 15:38
Percontator
Imagen de Percontator
Desconectado/a
colaborador
se unió: 20/03/16

 

 ¿No puedes ensancharla más para que no haga el salto de linea a media palabra y deje la mitad de

 las lineas partidas en dos?.

 Si ya es bastante leer esos nombres y saber que te dicen, imagina que encima tengas que estar buscando

 si te lo han dicho todo o sigue a continuación.

 

 Propuesta simplista:

 Aunque el mejor desempeño de tu hardware lo obtendrás instalando lo que te piden los reportes,

 ¿Cual es la resolución máxima que consta en las características de tu ordenador?.

 ¿Aparece como soportada la proporción y resolución que le pides?.

 Alguna vez no coge porque la frecuencia de refresco necesaria para esa configuración o la resolución

 no están contempladas para ese chip gráfico.

 Posible solución "mientras tanto": Elegir un modo más modesto y básico, que no requiera mucho trabajo

 para la gráfica.

 

 Luego, cuando tengas instalados los paquetes de firmware que faltan,  ya podrás darle al acelerador.

 

  Bienvenido  Gnome,  .. pero piensa en los demás. wink

 

Vie, 11/01/2019 - 15:23
josspark
Imagen de josspark
Desconectado/a
se unió: 11/01/19

siempre nos quedara pastebin wink

Mié, 20/03/2019 - 10:21
franolicar
Imagen de franolicar
Desconectado/a
se unió: 20/03/19

Logs begin at Tue 2019-03-19 23:01:03 -04, end at Wed 2019-03-20 09:01:20 -04
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
mar 20 08:54:46 franolicar-p4m900 kernel: ACPI Exception: Could not find/resolve
lines 1-23

************

Que pasara con esta falla despues de ejecutar el comando journalctl -b -p err

Mié, 20/03/2019 - 13:29
rockyiii
Imagen de rockyiii
Desconectado/a
administrator
se unió: 11/01/16

Hola franolicar si tienes un problema similar al del usuario Gnome, te recomiendo que abras tu propio post, previa lectura de las normas del foro /normas/normas-del-foro
saludos...