Debian-facile

Bienvenue sur Debian-Facile, site d'aide pour les nouveaux utilisateurs de Debian.

Vous n'êtes pas identifié(e).

#26 17-01-2017 18:38:34

robert2a
Membre
Lieu : France
Distrib. : Stretch 9
Noyau : Linux 4.9.0-3 4.9.30-2
(G)UI : Mate
Inscription : 15-11-2014

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

le boulot pas un problème , on est mal payé tongue mais on signé pour souffrir wink

donc tu a un noyau 4.8 avec le driver 3.75 sur une installation jessie ?
c'est bien ça ?

@golgot200
sur stretch il fonctionne , donc pas de commentaire encore un qui était pressé de mettre quelque chose qui fonctionne pas .

Dernière modification par robert2a (17-01-2017 18:41:57)

Hors ligne

#27 17-01-2017 18:41:39

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

quand je fais un nvidia-detect, voici le resultat, c'est louche non?

Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1c02] (rev a1)
Your card is only supported by a newer driver that is available in jessie-backports.
See http://backports.debian.org for instructions how to use backports.
You may also find newer driver packages in experimental.
It is recommended to install the
    nvidia-driver/jessie-backports


science sans conscience n'est que ruine de l'âme...

Hors ligne

#28 17-01-2017 18:47:44

robert2a
Membre
Lieu : France
Distrib. : Stretch 9
Noyau : Linux 4.9.0-3 4.9.30-2
(G)UI : Mate
Inscription : 15-11-2014

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

bon ta carte sur ma machine qui fonctionne bien


16:33:03:******************************* System ********************************
16:33:03:        CPU: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz
16:33:03:     CPU ID: GenuineIntel Family 6 Model 15 Stepping 11
16:33:03:       CPUs: 2
16:33:03:     Memory: 3.86GiB
16:33:03:Free Memory: 3.61GiB
16:33:03:    Threads: POSIX_THREADS
16:33:03: OS Version: 4.8
16:33:03:Has Battery: false
16:33:03: On Battery: false
16:33:03: UTC Offset: 1
16:33:03:        PID: 796

16:33:03:         OS: Linux 4.8.0-2-amd64 x86_64
16:33:03:    OS Arch: AMD64
16:33:03:       GPUs: 1
16:33:03:      GPU 0: NVIDIA:5 GP106 [GeForce GTX 1060 6GB]
16:33:03:       CUDA: 6.1
16:33:03:CUDA Driver: 8000
16:33:03:***********************************************************************
 


je suis en stretch driver bloqué en 367,xx , cuda version 8

le retour de nvidia-detect


nvidia-detect
 


retour de la commande


Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)

Checking card:  NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1)
Your card is supported by the default drivers.
It is recommended to install the
    nvidia-driver
package.
 

Dernière modification par robert2a (17-01-2017 18:49:45)

Hors ligne

#29 17-01-2017 18:47:49

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

un ptit résumé apres toutes ces commandes:

Je rentre bien dans ma session, mes deux ecrans sont detectés, mais:

les choses louches qui trainent:
- Lorsque je lance nvidia X server settings, on voit que ça travaille, mais rien ne se passe, ça à l'air de planter.
- Et à l'entrée en session, il y a un vieux bug graphique ou l'on voit des morceaux du bureau avant le redemarrage. (ça je ne sais pas si ça parait clair)
-Dolphin qui s'ouvre en demi fenetre au milieu de l'ecran. (genre sizé au minimum)

et ici

Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1c02] (rev a1)
Your card is only supported by a newer driver that is available in jessie-backports.
See http://backports.debian.org for instructions how to use backports.
You may also find newer driver packages in experimental.
It is recommended to install the
    nvidia-driver/jessie-backports



ici

01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c02 (rev a1)
 


il devrait reconnaitre ma carte si c'etait bien installé non?

Dernière modification par d33p (17-01-2017 18:49:47)


science sans conscience n'est que ruine de l'âme...

Hors ligne

#30 17-01-2017 18:52:56

robert2a
Membre
Lieu : France
Distrib. : Stretch 9
Noyau : Linux 4.9.0-3 4.9.30-2
(G)UI : Mate
Inscription : 15-11-2014

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

humm j'ai du mal a suivre tongue
donc un :


apt-get remove --purge nvidia-settings
 



puis un


apt-get install nvidia-settings
 



un redémarrage est nécessaire mais il doit fonctionner sans

cette manipulation te fait passer a la version 340 de jessie (l autre a un bug des backports )

Dernière modification par robert2a (17-01-2017 18:55:35)

Hors ligne

#31 17-01-2017 18:55:34

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

apt-get remove --purge nvidia-settings


Reading package lists... Done
Building dependency tree      
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libjansson4 libuuid-perl libxnvctrl0 pkg-config
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  nvidia-settings*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 3,739 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 130775 files and directories currently installed.)
Removing nvidia-settings (367.57-1~bpo8+1) ...
Purging configuration files for nvidia-settings (367.57-1~bpo8+1) ...
Processing triggers for nvidia-alternative (375.26-1~bpo8+1) ...
update-alternatives: warning: forcing reinstallation of alternative /usr/lib/nvidia/current because link group nvidia is broken
Processing triggers for libc-bin (2.19-18+deb8u7) ...
Processing triggers for glx-alternative-nvidia (0.7.3~bpo8+1) ...
Processing triggers for update-glx (0.7.3~bpo8+1) ...
Processing triggers for glx-alternative-nvidia (0.7.3~bpo8+1) ...
Processing triggers for libc-bin (2.19-18+deb8u7) ...
Processing triggers for initramfs-tools (0.120+deb8u2) ...
update-initramfs: Generating /boot/initrd.img-4.8.0-0.bpo.2-amd64


science sans conscience n'est que ruine de l'âme...

Hors ligne

#32 17-01-2017 18:57:11

robert2a
Membre
Lieu : France
Distrib. : Stretch 9
Noyau : Linux 4.9.0-3 4.9.30-2
(G)UI : Mate
Inscription : 15-11-2014

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

c'est un peu la panique ton installation hmm

tu installe comme la deuxieme ligne ? et tu teste

ps: /mode au monde entier
vous avez remarqué je n ai pas demandé de log tongue , je dois etre fatigué  roll
fin /mode

bon d33p a l air de bien se débrouillé , c'est moi qui suis a la traine tongue

si j ai bien compris il est sur son bureau avec un petit problème sur l utilitaire nvidia-settings

pour ceci , je pense que il y a eu des problèmes a  l installation


Je rentre bien dans ma session, mes deux ecrans sont detectés, mais:
les choses louches qui trainent:
1- Lorsque je lance nvidia X server settings, on voit que ça travaille, mais rien ne se passe,
 ça à l'air de planter.
2- Et à l'entrée en session, il y a un vieux bug graphique ou l'on voit des morceaux du bureau avant le redemarrage.
 (ça je ne sais pas si ça parait clair)
3-Dolphin qui s'ouvre en demi fenetre au milieu de l'ecran. (genre sizé au minimum)
 



le point 1 est résolu ci dessus ?

Dernière modification par robert2a (17-01-2017 19:18:09)

Hors ligne

#33 17-01-2017 20:02:04

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

re-coucou.
merci Robert2a

Je rentre bien dans ma session, mes deux ecrans sont detectés, mais:
les choses louches qui trainent:
1- Lorsque je lance nvidia X server settings, on voit que ça travaille, mais rien ne se passe,
ça à l'air de planter.   ---> c'est reglé
2- Et à l'entrée en session, il y a un vieux bug graphique ou l'on voit des morceaux du bureau avant le redemarrage.
(ça je ne sais pas si ça parait clair)  ---> ce n'est pas reglé
3-Dolphin qui s'ouvre en demi fenetre au milieu de l'ecran. (genre sizé au minimum) ---> à voir apres 2-3 restart



je m'absente un peu car je vais gerer les enfants.
si je suis motivé apres, je teste et redonne des infos, sinon, ce sera pour demain matin ^^
je vous remercie, à bientôt

d33p


science sans conscience n'est que ruine de l'âme...

Hors ligne

#34 17-01-2017 22:11:50

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

me voila de retour sur ma machine!
Les petits sont au lit! big_smile

Je rentre bien dans ma session, mes deux ecrans sont detectés, mais:
les choses louches qui trainent:
1- Lorsque je lance nvidia X server settings, on voit que ça travaille, mais rien ne se passe,
ça à l'air de planter.   ---> c'est reglé
2- Et à l'entrée en session, il y a un vieux bug graphique ou l'on voit des morceaux du bureau avant le redemarrage.
(ça je ne sais pas si ça parait clair)  ---> ce n'est pas reglé
3-Dolphin qui s'ouvre en demi fenetre au milieu de l'ecran. (genre sizé au minimum) ---> à voir apres 2-3 restart



Alors, le 1 est bien reglé, aucune idée de pourquoi lors de la 1ere installation, il ne l'a pas bien installé...
Le 2, semble reglé (j'ai configurer les parametres dans nvidia x server settings et ce bug ne revient plus pour le moment, ...)
Le 3, en mode user, la fenetre est normale, en mode root Dolphin s'ouvre encore en demi fenetre au milieu de l'ecran... etrange..

Quelques soucis, de tearing, "d'artefacts" lors du mouvement des fenetres... Je vais essayer de trouver les parametres qui vont bien à gauche à droite... (si vous avez quelques idées concernant l'optimisation graphique ou liens je suis toujours preneur ^^)
Une chose etrange dans, "Kinfocenter" -> direct rendering - 3D accelerator -> unknown.

Et nvidia x server settings me propose de generer un fichier de config, je l'ai enregistré dans etc/X11 et appelé xorg.conf, je ne sais pas si c'est ce qu'il fallait faire... sur certains post on voit que ce fichier est obsolete, sur d'autres il est utilisé...

c'est plus genant que grave hein ^^

en tout cas deja merci à ceux qui ont participé.

d33p

Dernière modification par d33p (17-01-2017 22:14:05)


science sans conscience n'est que ruine de l'âme...

Hors ligne

#35 18-01-2017 01:32:39

robert2a
Membre
Lieu : France
Distrib. : Stretch 9
Noyau : Linux 4.9.0-3 4.9.30-2
(G)UI : Mate
Inscription : 15-11-2014

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

le fichier xorg.conf c'est une mauvaise idée du moins tant que ton driver ne fonctionne pas correctement.

il me faut ton bureau (gnome ou mate ou xfce etc ....) , le lanceur (gdm3 , ligthdm , etc ...... ) ton profil est incomplet
et surement ton log du serveur X
tu a une carte très puissante , le dernier driver 375,xx par normal ce que tu me décris .
avec debian le xorg.conf est inutile au dessus du driver 340.xx , il est utile pour certaines configuration mais je pense pas que ce soit ton cas pour le moment .
arrivée sur le bureau , tu dois avoir un bureau étendu (par défaut)
tu a un fichier de log dans /var/log/Xserver.0.log si tu peut le poster ici , l idéal serait sans le xorg.conf .
tu a les définitions correcte sur tes 2 écrans ?
me donner le retour de cette commande ( sur une console graphique)


journalctl -r -p err
 


le log du serveur X


cat /var/log/Xserver.0.log
 


en entier si possible ( il est assez long )

ceci pas bon => Une chose etrange dans, "Kinfocenter" -> direct rendering - 3D accelerator -> unknown.
tu a kde comme bureau , je connais pas kinfocenter
nvidia-settings te donne déja les infos sur ta carte

tu a un bureau kde


KInfoCenter fournit un aperçu graphique de divers aspects du système, comme
l'utilisation de la mémoire, l'espace disque et les périphériques montés.

Ce paquet fait partie du module d'espace de travail de base de KDE.
 

Dernière modification par robert2a (18-01-2017 01:52:16)

Hors ligne

#36 18-01-2017 09:10:07

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

Hello robert2a

le fichier xorg.conf c'est une mauvaise idée du moins tant que ton driver ne fonctionne pas correctement.



le gestionnaire nvidia x server settings me l'a proposé ^^, desolé tongue

il me faut ton bureau (gnome ou mate ou xfce etc ....) , le lanceur (gdm3 , ligthdm , etc ...... ) ton profil est incomplet



J'ai KDE 4.14.2

tu a les définitions correcte sur tes 2 écrans ?


oui, un 1920*1080 et l'autre 2560*1440

Pour:

journalctl -r -p err


Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~

-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~

-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~

-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~

-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~

-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~

-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~

-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~

-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~

-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~

-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~

-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~
~
lines 1-21/21 (END)


-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~
~
lines 1-21/21 (END)

-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~
~
lines 1-21/21 (END)...skipping...
-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --                                                                                        
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~
~
lines 1-21/21 (END)...skipping...
-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --                                                                                        
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~
~
lines 1-21/21 (END)...skipping...
-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --                                                                                        
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~
~
lines 1-21/21 (END)...skipping...
-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --                                                                                        
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~
~
lines 1-21/21 (END)...skipping...
-- Logs begin at Wed 2017-01-18 00:00:27 CET, end at Wed 2017-01-18 07:51:52 CET. --                                                                                        
Jan 18 00:00:48 **mon_pc** pulseaudio[1438]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1435]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:48 **mon_pc** pulseaudio[1433]: [pulseaudio] pid.c: Daemon already running.
Jan 18 00:00:30 **mon_pc** kdm_greet[999]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No such file or directory
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004c, key code 162): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9004b, key code 136): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90048, key code 430): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90046, key code 203): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90045, key code 202): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90044, key code 149): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90043, key code 397): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90042, key code 423): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90041, key code 421): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9003d, key code 148): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9002d, key code 217): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90020, key code 418): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001f, key code 419): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x9001c, key code 120): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90018, key code 226): Invalid argument
Jan 18 00:00:28 **mon_pc** systemd-udevd[376]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0x90005, key code 212): Invalid argument
~
 



et pour

cat /var/log/Xserver.0.log


cat: /var/log/Xserver.0.log: No such file or directory


science sans conscience n'est que ruine de l'âme...

Hors ligne

#37 18-01-2017 11:42:19

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

.............. lol--.... ou pas
je cherchais à enlever le "tearing" et les fenetres qui generent des formes d'escalier lorsqu'on les deplace...
Je suis tombé sur cette formule

nvidia-settings --assign CurrentMetaMode="nvidia-auto-select +0+0 { ForceCompositionPipeline = On }"



Et là.... le drame, un screen à sauter et j'ai de nouveau le bug à l'entrée en session utilisateur sur le bureau KDE, c'est à dire:

2- Et à l'entrée en session, il y a un vieux bug graphique ou l'on voit des morceaux du bureau avant le redemarrage.



ouillle ^^


science sans conscience n'est que ruine de l'âme...

Hors ligne

#38 18-01-2017 12:10:51

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

alors apres ceci, un petit

aptitude purge '~i nvidia'


apres, re:

apt-get --reinstall install -t jessie-backports nvidia-kernel-dkms nvidia-settings nvidia-driver linux-headers-$(uname -r)



et toujours vieux bug au demarrage et plus de 2e ecran, vache, elle a fait mal cette commande :

nvidia-settings --assign CurrentMetaMode="nvidia-auto-select +0+0 { ForceCompositionPipeline = On }"


science sans conscience n'est que ruine de l'âme...

Hors ligne

#39 18-01-2017 12:38:11

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

mon 2e screen est revenu.
par contre toujours vieux bug au demarrage  ou l'on voit des morceaux du bureau avant le redemarrage.

science sans conscience n'est que ruine de l'âme...

Hors ligne

#40 18-01-2017 14:26:02

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

en lançant ceci:

lspci -nn | grep VGA


J'ai cela:

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1c02] (rev a1)


Je trouve ça louche, ne devrait-il pas m'afficher ma carte GTX 1060 ... ?


science sans conscience n'est que ruine de l'âme...

Hors ligne

#41 18-01-2017 14:40:44

robert2a
Membre
Lieu : France
Distrib. : Stretch 9
Noyau : Linux 4.9.0-3 4.9.30-2
(G)UI : Mate
Inscription : 15-11-2014

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

Bonjour
oui voila ce qu affiche  chez moi cette commande


lspci -nn | grep VGA
 



01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)
 



mon noyau sous stretch (voir mon profil)


uname -a
 



Linux debian21 4.8.0-2-amd64 #1 SMP Debian 4.8.15-2 (2017-01-04) x86_64 GNU/Linux
 



j'ai une autre machine avec le bureau gnome et steam d installé pour les jeux avec une GTX1070
ce n'est pas la faute de debian , peut etre jessie (avec les backports ça devrait pas) , que je t ai donné une mauvaise commande , que tu ne fait pas les choses correctement .
peut etre directement passer a une installation de stretch (pour l installation un seul écran suffit )
je comprend pas pourquoi tu a tous ses problèmes

sous gnome (une autre machine )
ma carte


01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1)
 


mon noyau


Linux debian11 4.8.0-2-amd64 #1 SMP Debian 4.8.15-2 (2017-01-04) x86_64 GNU/Linux
 


j ai 2 autres machines avec une gtx 1060 3 et 6Go (selon mon profil )
donc "ma carte graphique ne fonctionne pas avec debian" ça tien pas la route , juste trouver ce qui cloche.
ps: les 2 models que je n'ai pas testé , GTX1050(TI) et 1080 , la Titan X ce sera jamais (trop cher ,ainsi que la 1080 que je trouve chère )

donc je te propose de faire une installation de stretch propre sans bureau (voir wiki si tu ne sais pas ce que c'est )
si cela fonctionne , que tu peut te logger en root (console pure )pour continuer l installation je te donnerai la suite des commandes

Dernière modification par robert2a (18-01-2017 15:16:07)

Hors ligne

#42 18-01-2017 15:36:23

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

hello,
j'ai passé tellement de temps à installer des softs et configurer kde que je t'avoue qu'une nieme reinstall cela m'embete. J'en ai deja tellement fait, et si à chaque probleme je reinstalle, je ne comprendrais jamais rien...
je le ferais vraiment si je galere qq jours.
c'est destabilisant que d'un demarrage à l'autre sans forcement bidouiller le resultat est different.
merci pour tout en tout cas, je vais essayer de continuer à bricoler.

@ bientot

d33p

science sans conscience n'est que ruine de l'âme...

Hors ligne

#43 18-01-2017 15:47:18

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

Voici le bug à l'entrée en session KDE

une image est parfois plus parlante que mille mots ^^

mini_144401screen01.png

Dernière modification par d33p (18-01-2017 15:50:40)


science sans conscience n'est que ruine de l'âme...

Hors ligne

#44 18-01-2017 15:59:27

Croutons
Membre
Distrib. : Handylinux 2.5 vers Jessie et Debian Stretch
Noyau : Linux 3.16.0-4-686-pae, Linux 4.9.0-3-686-pae
(G)UI : xfce
Inscription : 16-12-2016

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

salut peut être voir avec

dmesg


C'est juste une idée je saurais même pas interpréter les messages d'erreur


-->les cahiers du debutant<--      WikiDF-->Découvrir les principales commandes Linux<--
L' expérience, c'est le nom que chacun donne à ses erreurs. Oscar Wilde

Hors ligne

#45 18-01-2017 16:14:33

èfpé
Membre
Inscription : 10-07-2016

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

Bonjour,

cat /var/log/Xserver.0.log

cat: /var/log/Xserver.0.log: No such file or directory


Cela fonctionnerait mieux avec le bon nom de fichier :

cat /var/log/Xorg.0.log


lspci -nn | grep VGA

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1c02] (rev a1)


Il s'agit effectivement d'une GeForce GTX 1060 3GB.

Dernière modification par èfpé (18-01-2017 16:36:32)

Hors ligne

#46 18-01-2017 16:19:48

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

hello croutons,

voici

pour:

dmesg



voici ce qui touche à nvidia:

[    7.320994] nvidia: loading out-of-tree module taints kernel.
[    7.321001] nvidia: module license 'NVIDIA' taints kernel.
[    7.321001] Disabling lock debugging due to kernel taint
[    7.328839] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[    7.328893] nvidia-nvlink: Nvlink Core is being initialized, major device number 247
[    7.328902] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  375.26  Thu Dec  8 18:36:43 PST 2016 (using threaded interrupts)
[    7.335526] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  375.26  Thu Dec  8 18:04:14 PST 2016
[    7.341742] [drm] Initialized drm 1.1.0 20060810
[    7.351780] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver



[    8.318936] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input37
[    8.318972] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input38
[    8.319010] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input39
[    8.927614] NVRM: Your system is not currently configured to drive a VGA console
[    8.927616] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[    8.927617] NVRM: requires the use of a text-mode VGA console. Use of other console
[    8.927617] NVRM: drivers including, but not limited to, vesafb, may result in
[    8.927618] NVRM: corruption and stability problems, and is not supported.
[    8.931419] nvidia-modeset: Allocated GPU:0 (GPU-62544cb4-6fbf-b70d-8b04-65fb04f8f7ce) @ PCI:0000:01:00.0

Dernière modification par d33p (18-01-2017 16:36:15)


science sans conscience n'est que ruine de l'âme...

Hors ligne

#47 18-01-2017 16:27:36

robert2a
Membre
Lieu : France
Distrib. : Stretch 9
Noyau : Linux 4.9.0-3 4.9.30-2
(G)UI : Mate
Inscription : 15-11-2014

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

èfpé a écrit :

Bonjour,

cat /var/log/Xserver.0.log

cat: /var/log/Xserver.0.log: No such file or directory


Cela fonctionnerait mieux avec le bon nom de fichier :

cat /var/log/Xorg.0.log



c'est la fatigue surement hmm  , je vous laisse faire wink
ps: peut etre d'autres erreurs sur mes commandes ....

Hors ligne

#48 18-01-2017 16:32:16

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

j'vais pas jeter la pierre je ferais pas mieux lol tongue

science sans conscience n'est que ruine de l'âme...

Hors ligne

#49 18-01-2017 16:35:06

d33p
Adhérent(e)
Lieu : Lorraine
Distrib. : Debian testing buster 64bits
Noyau : En fonction des updates testing buster
(G)UI : En fonction des updates testing buster
Inscription : 01-12-2015

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

hello èfpé, voici:

cat /var/log/Xorg.0.log


[     7.930]                                                                                                                                                                                                      
X.Org X Server 1.16.4                                                                                                                                                                                              
Release Date: 2014-12-20                                                                                                                                                                                          
[     7.930] X Protocol Version 11, Revision 0                                                                                                                                                                    
[     7.930] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian                                                                                                                                            
[     7.930] Current Operating System: Linux debjc 4.8.0-0.bpo.2-amd64 #1 SMP Debian 4.8.11-1~bpo8+1 (2016-12-14) x86_64                                                                                          
[     7.930] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.8.0-0.bpo.2-amd64 root=UUID=2fe0fe73-edd2-4dc9-9b99-a01942e588b1 ro quiet                                                                            
[     7.930] Build Date: 11 February 2015  12:32:02AM                                                                                                                                                              
[     7.930] xorg-server 2:1.16.4-1 (http://www.debian.org/support)                                                                                                                                                
[     7.930] Current version of pixman: 0.32.6                                                                                                                                                                    
[     7.930]    Before reporting problems, check http://wiki.x.org                                                                                                                                                
        to make sure that you have the latest version.                                                                                                                                                            
[     7.930] Markers: (--) probed, (**) from config file, (==) default setting,                                                                                                                                    
        (++) from command line, (!!) notice, (II) informational,                                                                                                                                                  
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.                                                                                                                                              
[     7.930] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan 18 15:03:30 2017                                                                                                                                  
[     7.937] (==) Using system config directory "/usr/share/X11/xorg.conf.d"                                                                                                                                      
[     7.941] (==) No Layout section.  Using the first Screen section.                                                                                                                                              
[     7.941] (==) No screen section available. Using defaults.                                                                                                                                                    
[     7.941] (**) |-->Screen "Default Screen Section" (0)                                                                                                                                                          
[     7.941] (**) |   |-->Monitor "<default monitor>"                                                                                                                                                              
[     7.943] (==) No monitor specified for screen "Default Screen Section".                                                                                                                                        
        Using a default monitor configuration.
[     7.943] (==) Automatically adding devices
[     7.943] (==) Automatically enabling devices
[     7.943] (==) Automatically adding GPU devices
[     7.948] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[     7.948]    Entry deleted from font path.
[     7.964] (==) FontPath set to:
        /usr/share/fonts/X11/misc,
        /usr/share/fonts/X11/100dpi/:unscaled,
        /usr/share/fonts/X11/75dpi/:unscaled,
        /usr/share/fonts/X11/Type1,
        /usr/share/fonts/X11/100dpi,
        /usr/share/fonts/X11/75dpi,
        built-ins
[     7.964] (==) ModulePath set to "/usr/lib/xorg/modules"
[     7.964] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[     7.965] (II) Loader magic: 0x5649f8290d80
[     7.965] (II) Module ABI versions:
[     7.965]    X.Org ANSI C Emulation: 0.4
[     7.965]    X.Org Video Driver: 18.0
[     7.965]    X.Org XInput driver : 21.0
[     7.965]    X.Org Server Extension : 8.0
[     7.965] (II) xfree86: Adding drm device (/dev/dri/card0)
[     7.966] (--) PCI:*(0:1:0:0) 10de:1c02:1458:3722 rev 161, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[     7.967] (II) LoadModule: "glx"
[     7.975] (II) Loading /usr/lib/xorg/modules/linux/libglx.so
[     8.070] (II) Module glx: vendor="NVIDIA Corporation"
[     8.070]    compiled for 4.0.2, module version = 1.0.0
[     8.070]    Module class: X.Org Server Extension
[     8.071] (II) NVIDIA GLX Module  375.26  Thu Dec  8 17:59:51 PST 2016
[     8.072] (II) Applying OutputClass "nvidia" to /dev/dri/card0
[     8.072]    loading driver: nvidia
[     8.072] (==) Matched nvidia as autoconfigured driver 0
[     8.072] (==) Matched nouveau as autoconfigured driver 1
[     8.072] (==) Matched nv as autoconfigured driver 2
[     8.072] (==) Matched nouveau as autoconfigured driver 3
[     8.072] (==) Matched nv as autoconfigured driver 4
[     8.072] (==) Matched modesetting as autoconfigured driver 5
[     8.072] (==) Matched fbdev as autoconfigured driver 6
[     8.072] (==) Matched vesa as autoconfigured driver 7
[     8.072] (==) Assigned the driver to the xf86ConfigLayout
[     8.072] (II) LoadModule: "nvidia"
[     8.076] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[     8.086] (II) Module nvidia: vendor="NVIDIA Corporation"
[     8.086]    compiled for 4.0.2, module version = 1.0.0
[     8.086]    Module class: X.Org Video Driver
[     8.087] (II) LoadModule: "nouveau"
[     8.087] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[     8.089] (II) Module nouveau: vendor="X.Org Foundation"
[     8.089]    compiled for 1.16.0, module version = 1.0.11
[     8.089]    Module class: X.Org Video Driver
[     8.089]    ABI class: X.Org Video Driver, version 18.0
[     8.089] (II) LoadModule: "nv"
[     8.090] (WW) Warning, couldn't open module nv
[     8.090] (II) UnloadModule: "nv"
[     8.090] (II) Unloading nv
[     8.090] (EE) Failed to load module "nv" (module does not exist, 0)
[     8.090] (II) LoadModule: "modesetting"
[     8.090] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     8.092] (II) Module modesetting: vendor="X.Org Foundation"
[     8.092]    compiled for 1.16.4, module version = 0.9.0
[     8.092]    Module class: X.Org Video Driver
[     8.092]    ABI class: X.Org Video Driver, version 18.0
[     8.092] (II) LoadModule: "fbdev"
[     8.092] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[     8.093] (II) Module fbdev: vendor="X.Org Foundation"
[     8.093]    compiled for 1.15.99.904, module version = 0.4.4
[     8.093]    Module class: X.Org Video Driver
[     8.093]    ABI class: X.Org Video Driver, version 18.0
[     8.093] (II) LoadModule: "vesa"
[     8.093] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[     8.094] (II) Module vesa: vendor="X.Org Foundation"
[     8.094]    compiled for 1.15.99.904, module version = 2.3.3
[     8.094]    Module class: X.Org Video Driver
[     8.094]    ABI class: X.Org Video Driver, version 18.0
[     8.094] (II) NVIDIA dlloader X Driver  375.26  Thu Dec  8 17:37:15 PST 2016
[     8.094] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[     8.094] (II) NOUVEAU driver Date:   Thu Aug 28 03:57:48 2014 +0200
[     8.094] (II) NOUVEAU driver for NVIDIA chipset families :
[     8.094]    RIVA TNT        (NV04)
[     8.094]    RIVA TNT2       (NV05)
[     8.094]    GeForce 256     (NV10)
[     8.094]    GeForce 2       (NV11, NV15)
[     8.094]    GeForce 4MX     (NV17, NV18)
[     8.094]    GeForce 3       (NV20)
[     8.094]    GeForce 4Ti     (NV25, NV28)
[     8.094]    GeForce FX      (NV3x)
[     8.094]    GeForce 6       (NV4x)
[     8.094]    GeForce 7       (G7x)
[     8.094]    GeForce 8       (G8x)
[     8.094]    GeForce GTX 200 (NVA0)
[     8.094]    GeForce GTX 400 (NVC0)
[     8.094] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     8.094] (II) FBDEV: driver for framebuffer: fbdev
[     8.094] (II) VESA: driver for VESA chipsets: vesa
[     8.094] (++) using VT number 7

[     8.097] (II) Loading sub module "fb"
[     8.097] (II) LoadModule: "fb"
[     8.097] (II) Loading /usr/lib/xorg/modules/libfb.so
[     8.098] (II) Module fb: vendor="X.Org Foundation"
[     8.098]    compiled for 1.16.4, module version = 1.0.0
[     8.098]    ABI class: X.Org ANSI C Emulation, version 0.4
[     8.098] (II) Loading sub module "wfb"
[     8.098] (II) LoadModule: "wfb"
[     8.098] (II) Loading /usr/lib/xorg/modules/libwfb.so
[     8.100] (II) Module wfb: vendor="X.Org Foundation"
[     8.100]    compiled for 1.16.4, module version = 1.0.0
[     8.100]    ABI class: X.Org ANSI C Emulation, version 0.4
[     8.100] (II) Loading sub module "ramdac"
[     8.100] (II) LoadModule: "ramdac"
[     8.100] (II) Module "ramdac" already built-in
[     8.104] (WW) Falling back to old probe method for modesetting
[     8.104] (WW) Falling back to old probe method for fbdev
[     8.104] (II) Loading sub module "fbdevhw"
[     8.104] (II) LoadModule: "fbdevhw"
[     8.104] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[     8.105] (II) Module fbdevhw: vendor="X.Org Foundation"
[     8.105]    compiled for 1.16.4, module version = 0.0.2
[     8.105]    ABI class: X.Org Video Driver, version 18.0
[     8.105] (WW) Falling back to old probe method for vesa
[     8.105] (II) NVIDIA(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[     8.105] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[     8.105] (==) NVIDIA(0): RGB weight 888
[     8.105] (==) NVIDIA(0): Default visual is TrueColor
[     8.105] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[     8.107] (**) NVIDIA(0): Enabling 2D acceleration
[     8.887] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[     8.887] (--) NVIDIA(0):     DFP-0 (boot)
[     8.887] (--) NVIDIA(0):     DFP-1
[     8.887] (--) NVIDIA(0):     DFP-2
[     8.887] (--) NVIDIA(0):     DFP-3
[     8.887] (--) NVIDIA(0):     DFP-4
[     8.888] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 1060 3GB (GP106-A) at PCI:1:0:0
[     8.888] (II) NVIDIA(0):     (GPU-0)
[     8.888] (--) NVIDIA(0): Memory: 3145728 kBytes
[     8.888] (--) NVIDIA(0): VideoBIOS: 86.06.11.00.75
[     8.888] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[     8.903] (--) NVIDIA(GPU-0): BenQ GW2765 (DFP-0): connected
[     8.903] (--) NVIDIA(GPU-0): BenQ GW2765 (DFP-0): Internal TMDS
[     8.903] (--) NVIDIA(GPU-0): BenQ GW2765 (DFP-0): 330.0 MHz maximum pixel clock
[     8.903] (--) NVIDIA(GPU-0):
[     8.935] (--) NVIDIA(GPU-0): Ancor Communications Inc VW246 (DFP-1): connected
[     8.935] (--) NVIDIA(GPU-0): Ancor Communications Inc VW246 (DFP-1): Internal TMDS
[     8.935] (--) NVIDIA(GPU-0): Ancor Communications Inc VW246 (DFP-1): 600.0 MHz maximum pixel clock
[     8.935] (--) NVIDIA(GPU-0):
[     8.935] (--) NVIDIA(GPU-0): DFP-2: disconnected
[     8.935] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[     8.935] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[     8.935] (--) NVIDIA(GPU-0):
[     8.935] (--) NVIDIA(GPU-0): DFP-3: disconnected
[     8.935] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[     8.935] (--) NVIDIA(GPU-0): DFP-3: 330.0 MHz maximum pixel clock
[     8.935] (--) NVIDIA(GPU-0):
[     8.935] (--) NVIDIA(GPU-0): DFP-4: disconnected
[     8.935] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[     8.935] (--) NVIDIA(GPU-0): DFP-4: 330.0 MHz maximum pixel clock
[     8.935] (--) NVIDIA(GPU-0):
[     8.942] (==) NVIDIA(0):
[     8.942] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[     8.942] (==) NVIDIA(0):     will be used as the requested mode.
[     8.942] (==) NVIDIA(0):
[     8.943] (II) NVIDIA(0): Validated MetaModes:
[     8.943] (II) NVIDIA(0):     "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
[     8.943] (II) NVIDIA(0): Virtual screen size determined to be 4480 x 1440
[     8.957] (--) NVIDIA(0): DPI set to (108, 107); computed from "UseEdidDpi" X config
[     8.957] (--) NVIDIA(0):     option
[     8.957] (II) UnloadModule: "nouveau"
[     8.957] (II) Unloading nouveau
[     8.957] (II) UnloadModule: "modesetting"
[     8.957] (II) Unloading modesetting
[     8.957] (II) UnloadModule: "fbdev"
[     8.957] (II) Unloading fbdev
[     8.957] (II) UnloadSubModule: "fbdevhw"
[     8.957] (II) Unloading fbdevhw
[     8.958] (II) UnloadModule: "vesa"
[     8.958] (II) Unloading vesa
[     8.958] (--) Depth 24 pixmap format is 32 bpp
[     8.958] (II) NVIDIA: Using 49152.00 MB of virtual memory for indirect memory
[     8.958] (II) NVIDIA:     access.
[     9.003] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-1:nvidia-auto-select"
[     9.063] (==) NVIDIA(0): Disabling shared memory pixmaps
[     9.063] (==) NVIDIA(0): Backing store enabled
[     9.063] (==) NVIDIA(0): Silken mouse enabled
[     9.065] (==) NVIDIA(0): DPMS enabled
[     9.065] (II) Loading sub module "dri2"
[     9.065] (II) LoadModule: "dri2"
[     9.065] (II) Module "dri2" already built-in
[     9.065] (II) NVIDIA(0): [DRI2] Setup complete
[     9.065] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[     9.065] (--) RandR disabled
[     9.069] (II) SELinux: Disabled on system
[     9.070] (II) Initializing extension GLX
[     9.070] (II) Indirect GLX disabled.
[     9.131] (II) config/udev: Adding input device Power Button (/dev/input/event8)
[     9.131] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[     9.131] (II) LoadModule: "evdev"
[     9.131] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[     9.134] (II) Module evdev: vendor="X.Org Foundation"
[     9.134]    compiled for 1.16.0, module version = 2.9.0
[     9.134]    Module class: X.Org XInput Driver
[     9.134]    ABI class: X.Org XInput driver, version 21.0
[     9.134] (II) Using input driver 'evdev' for 'Power Button'
[     9.134] (**) Power Button: always reports core events
[     9.134] (**) evdev: Power Button: Device: "/dev/input/event8"
[     9.134] (--) evdev: Power Button: Vendor 0 Product 0x1
[     9.134] (--) evdev: Power Button: Found keys
[     9.134] (II) evdev: Power Button: Configuring as keyboard
[     9.134] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input23/event8"
[     9.134] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[     9.134] (**) Option "xkb_rules" "evdev"
[     9.134] (**) Option "xkb_model" "pc105"
[     9.134] (**) Option "xkb_layout" "ch"
[     9.134] (**) Option "xkb_variant" "fr"
[     9.147] (II) config/udev: Adding input device Power Button (/dev/input/event7)
[     9.147] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[     9.147] (II) Using input driver 'evdev' for 'Power Button'
[     9.147] (**) Power Button: always reports core events
[     9.147] (**) evdev: Power Button: Device: "/dev/input/event7"
[     9.147] (--) evdev: Power Button: Vendor 0 Product 0x1
[     9.147] (--) evdev: Power Button: Found keys
[     9.147] (II) evdev: Power Button: Configuring as keyboard
[     9.147] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input22/event7"
[     9.147] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[     9.147] (**) Option "xkb_rules" "evdev"
[     9.147] (**) Option "xkb_model" "pc105"
[     9.147] (**) Option "xkb_layout" "ch"
[     9.147] (**) Option "xkb_variant" "fr"
[     9.147] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event21)
[     9.147] (II) No input driver specified, ignoring this device.
[     9.147] (II) This device may have been added with another device file.
[     9.148] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event22)
[     9.148] (II) No input driver specified, ignoring this device.
[     9.148] (II) This device may have been added with another device file.
[     9.148] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event23)
[     9.148] (II) No input driver specified, ignoring this device.
[     9.148] (II) This device may have been added with another device file.
[     9.148] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event24)
[     9.148] (II) No input driver specified, ignoring this device.
[     9.148] (II) This device may have been added with another device file.
[     9.148] (II) config/udev: Adding input device Wacom Intuos Pro S Pen (/dev/input/event0)
[     9.148] (**) Wacom Intuos Pro S Pen: Applying InputClass "evdev tablet catchall"
[     9.148] (**) Wacom Intuos Pro S Pen: Applying InputClass "Wacom USB device class"
[     9.148] (**) Wacom Intuos Pro S Pen: Applying InputClass "Wacom class"
[     9.148] (II) LoadModule: "wacom"
[     9.149] (II) Loading /usr/lib/xorg/modules/input/wacom_drv.so
[     9.150] (II) Module wacom: vendor="X.Org Foundation"
[     9.150]    compiled for 1.16.1, module version = 0.26.0
[     9.150]    Module class: X.Org XInput Driver
[     9.150]    ABI class: X.Org XInput driver, version 21.0
[     9.150] (II) wacom: Driver for Wacom graphics tablets: PenPartner, Graphire,
        Graphire2 4x5, Graphire2 5x7, Graphire3 4x5, Graphire3 6x8,
        Graphire4 4x5, Graphire4 6x8, BambooFun 4x5, BambooFun 6x8,
        Bamboo1 Medium, Graphire4 6x8 BlueTooth, CTL-460, CTH-461, CTL-660,
        CTL-461/S, Bamboo Touch, CTH-460/K, CTH-461/S, CTH-661/S1, CTH-461/L,
        CTH-661/L, Intuos 4x5, Intuos 6x8, Intuos 9x12, Intuos 12x12,
        Intuos 12x18, PTU600, PL400, PL500, PL600, PL600SX, PL550, PL800,
        PL700, PL510, PL710, DTI520, DTF720, DTF720a, DTF521, DTU1931,
        DTU2231, DTU1631, Intuos2 4x5, Intuos2 6x8, Intuos2 9x12,
        Intuos2 12x12, Intuos2 12x18, Intuos2 6x8 , Volito, PenStation,
        Volito2 4x5, Volito2 2x3, PenPartner2, Bamboo, Bamboo1, Bamboo1 4x6,
        Bamboo1 5x8, Intuos3 4x5, Intuos3 6x8, Intuos3 9x12, Intuos3 12x12,
        Intuos3 12x19, Intuos3 6x11, Intuos3 4x6, Intuos4 4x6, Intuos4 6x9,
        Intuos4 8x13, Intuos4 12x19, Intuos4 WL USB Endpoint,
        Intuos4 WL Bluetooth Endpoint, Intuos5 touch S, Intuos5 touch M,
        Intuos5 touch L, Intuos5 S, Intuos5 M, Intuos Pro S, Intuos Pro M,
        Intuos Pro L, Cintiq 21UX, Cintiq 20WSX, Cintiq 12WX, Cintiq 21UX2,
        Cintiq 24HD, Cintiq 22HD, Cintiq 24HD touch (EMR digitizer),
        Cintiq 13HD, DTK2241, DTH2242, Cintiq 22HDT, TabletPC 0x90,
        TabletPC 0x93, TabletPC 0x97, TabletPC 0x9A, CapPlus  0x9F,
        TabletPC 0xE2, TabletPC 0xE3, TabletPC 0xE5, TabletPC 0xE6,
        TabletPC 0xEC, TabletPC 0xED, TabletPC 0xEF, TabletPC 0x100,
        TabletPC 0x101, TabletPC 0x10D, TabletPC 0x116, TabletPC 0x12C,
        TabletPC 0x4001, TabletPC 0x4004, TabletPC 0x5000, TabletPC 0x5002,
        usb:172f:0024, usb:172f:0025, usb:172f:0026, usb:172f:0027,
        usb:172f:0028, usb:172f:0030, usb:172f:0031, usb:172f:0032,
        usb:172f:0033, usb:172f:0034, usb:172f:0035, usb:172f:0036,
        usb:172f:0037, usb:172f:0038, usb:172f:0039, usb:172f:0051,
        usb:172f:0052, usb:172f:0053, usb:172f:0054, usb:172f:0055,
        usb:172f:0056, usb:172f:0057, usb:172f:0058, usb:172f:0500,
        usb:172f:0501, usb:172f:0502, usb:172f:0503, usb:1b96:0001,
        usb:17ef:6004
[     9.150] (II) Using input driver 'wacom' for 'Wacom Intuos Pro S Pen'
[     9.150] (**) Wacom Intuos Pro S Pen: always reports core events
[     9.150] (**) Option "Device" "/dev/input/event0"
[     9.208] (II) Wacom Intuos Pro S Pen: type not specified, assuming 'stylus'.
[     9.208] (II) Wacom Intuos Pro S Pen: other types will be automatically added.
[     9.208] (--) Wacom Intuos Pro S Pen stylus: using pressure threshold of 27 for button 1
[     9.208] (--) Wacom Intuos Pro S Pen stylus: maxX=31496 maxY=19685 maxZ=2047 resX=200000 resY=200000  tilt=enabled
[     9.208] (II) Wacom Intuos Pro S Pen stylus: hotplugging dependent devices.
[     9.208] (EE) Wacom Intuos Pro S Pen stylus: Invalid type 'touch' for this device.
[     9.208] (EE) Wacom Intuos Pro S Pen stylus: Invalid type 'pad' for this device.
[     9.208] (II) Wacom Intuos Pro S Pen stylus: hotplugging completed.
[     9.260] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:056A:0314.0001/input/input3/event0"
[     9.260] (II) XINPUT: Adding extended input device "Wacom Intuos Pro S Pen stylus" (type: STYLUS, id 8)
[     9.260] (**) Wacom Intuos Pro S Pen stylus: (accel) keeping acceleration scheme 1
[     9.260] (**) Wacom Intuos Pro S Pen stylus: (accel) acceleration profile 0
[     9.260] (**) Wacom Intuos Pro S Pen stylus: (accel) acceleration factor: 2.000
[     9.260] (**) Wacom Intuos Pro S Pen stylus: (accel) acceleration threshold: 4
[     9.320] (II) config/udev: Adding input device Wacom Intuos Pro S Pen (/dev/input/mouse0)
[     9.320] (II) No input driver specified, ignoring this device.
[     9.320] (II) This device may have been added with another device file.
[     9.320] (II) config/udev: Adding input device Wacom Intuos Pro S Pad (/dev/input/event1)
[     9.320] (**) Wacom Intuos Pro S Pad: Applying InputClass "evdev tablet catchall"
[     9.320] (**) Wacom Intuos Pro S Pad: Applying InputClass "Wacom USB device class"
[     9.320] (**) Wacom Intuos Pro S Pad: Applying InputClass "Wacom class"
[     9.320] (II) Using input driver 'wacom' for 'Wacom Intuos Pro S Pad'
[     9.320] (**) Wacom Intuos Pro S Pad: always reports core events
[     9.320] (**) Option "Device" "/dev/input/event1"
[     9.320] (EE) Wacom Intuos Pro S Pad: Invalid type 'stylus' for this device.
[     9.320] (EE) Wacom Intuos Pro S Pad: Invalid type 'eraser' for this device.
[     9.320] (EE) Wacom Intuos Pro S Pad: Invalid type 'cursor' for this device.
[     9.320] (EE) Wacom Intuos Pro S Pad: Invalid type 'touch' for this device.
[     9.320] (II) Wacom Intuos Pro S Pad: type not specified, assuming 'pad'.
[     9.320] (II) Wacom Intuos Pro S Pad: other types will be automatically added.
[     9.321] (II) Wacom Intuos Pro S Pad pad: hotplugging dependent devices.
[     9.321] (EE) Wacom Intuos Pro S Pad pad: Invalid type 'stylus' for this device.
[     9.321] (EE) Wacom Intuos Pro S Pad pad: Invalid type 'eraser' for this device.
[     9.321] (EE) Wacom Intuos Pro S Pad pad: Invalid type 'cursor' for this device.
[     9.321] (EE) Wacom Intuos Pro S Pad pad: Invalid type 'touch' for this device.
[     9.321] (II) Wacom Intuos Pro S Pad pad: hotplugging completed.
[     9.368] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:056A:0314.0001/input/input5/event1"
[     9.368] (II) XINPUT: Adding extended input device "Wacom Intuos Pro S Pad pad" (type: PAD, id 9)
[     9.368] (**) Wacom Intuos Pro S Pad pad: (accel) keeping acceleration scheme 1
[     9.368] (**) Wacom Intuos Pro S Pad pad: (accel) acceleration profile 0
[     9.368] (**) Wacom Intuos Pro S Pad pad: (accel) acceleration factor: 2.000
[     9.368] (**) Wacom Intuos Pro S Pad pad: (accel) acceleration threshold: 4
[     9.368] (II) config/udev: Adding input device Wacom Intuos Pro S Pad (/dev/input/js0)
[     9.368] (II) No input driver specified, ignoring this device.
[     9.368] (II) This device may have been added with another device file.
[     9.369] (II) config/udev: Adding input device Wacom Intuos Pro S Finger (/dev/input/event6)
[     9.369] (**) Wacom Intuos Pro S Finger: Applying InputClass "evdev touchpad catchall"
[     9.369] (**) Wacom Intuos Pro S Finger: Applying InputClass "touchpad catchall"
[     9.369] (**) Wacom Intuos Pro S Finger: Applying InputClass "Default clickpad buttons"
[     9.369] (**) Wacom Intuos Pro S Finger: Applying InputClass "Wacom USB device class"
[     9.369] (**) Wacom Intuos Pro S Finger: Applying InputClass "Wacom class"
[     9.369] (II) Using input driver 'wacom' for 'Wacom Intuos Pro S Finger'
[     9.369] (**) Wacom Intuos Pro S Finger: always reports core events
[     9.369] (**) Option "Device" "/dev/input/event6"
[     9.428] (EE) Wacom Intuos Pro S Finger: Invalid type 'stylus' for this device.
[     9.428] (EE) Wacom Intuos Pro S Finger: Invalid type 'eraser' for this device.
[     9.428] (EE) Wacom Intuos Pro S Finger: Invalid type 'cursor' for this device.
[     9.428] (II) Wacom Intuos Pro S Finger: type not specified, assuming 'touch'.
[     9.428] (II) Wacom Intuos Pro S Finger: other types will be automatically added.
[     9.428] (--) Wacom Intuos Pro S Finger touch: maxX=4096 maxY=4096 maxZ=0 resX=26000 resY=42000
[     9.428] (II) Wacom Intuos Pro S Finger touch: hotplugging dependent devices.
[     9.428] (EE) Wacom Intuos Pro S Finger touch: Invalid type 'stylus' for this device.
[     9.428] (EE) Wacom Intuos Pro S Finger touch: Invalid type 'eraser' for this device.
[     9.428] (EE) Wacom Intuos Pro S Finger touch: Invalid type 'cursor' for this device.
[     9.428] (EE) Wacom Intuos Pro S Finger touch: Invalid type 'pad' for this device.
[     9.428] (II) Wacom Intuos Pro S Finger touch: hotplugging completed.
[     9.476] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:056A:0314.0002/input/input20/event6"
[     9.476] (II) XINPUT: Adding extended input device "Wacom Intuos Pro S Finger touch" (type: TOUCH, id 10)
[     9.476] (**) Wacom Intuos Pro S Finger touch: (accel) keeping acceleration scheme 1
[     9.476] (**) Wacom Intuos Pro S Finger touch: (accel) acceleration profile 0
[     9.476] (**) Wacom Intuos Pro S Finger touch: (accel) acceleration factor: 2.000
[     9.476] (**) Wacom Intuos Pro S Finger touch: (accel) acceleration threshold: 4
[     9.536] (II) config/udev: Adding input device Wacom Intuos Pro S Finger (/dev/input/mouse2)
[     9.536] (**) Wacom Intuos Pro S Finger: Ignoring device from InputClass "touchpad ignore duplicates"
[     9.536] (II) config/udev: Adding input device UVC Camera (046d:0823) (/dev/input/event20)
[     9.536] (**) UVC Camera (046d:0823): Applying InputClass "evdev keyboard catchall"
[     9.536] (II) Using input driver 'evdev' for 'UVC Camera (046d:0823)'
[     9.536] (**) UVC Camera (046d:0823): always reports core events
[     9.536] (**) evdev: UVC Camera (046d:0823): Device: "/dev/input/event20"
[     9.536] (--) evdev: UVC Camera (046d:0823): Vendor 0x46d Product 0x823
[     9.536] (--) evdev: UVC Camera (046d:0823): Found keys
[     9.536] (II) evdev: UVC Camera (046d:0823): Configuring as keyboard
[     9.536] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.2/input/input35/event20"
[     9.536] (II) XINPUT: Adding extended input device "UVC Camera (046d:0823)" (type: KEYBOARD, id 11)
[     9.536] (**) Option "xkb_rules" "evdev"
[     9.536] (**) Option "xkb_model" "pc105"
[     9.536] (**) Option "xkb_layout" "ch"
[     9.536] (**) Option "xkb_variant" "fr"
[     9.537] (II) config/udev: Adding input device Logitech G9x Laser Mouse (/dev/input/event2)
[     9.537] (**) Logitech G9x Laser Mouse: Applying InputClass "evdev pointer catchall"
[     9.537] (II) Using input driver 'evdev' for 'Logitech G9x Laser Mouse'
[     9.537] (**) Logitech G9x Laser Mouse: always reports core events
[     9.537] (**) evdev: Logitech G9x Laser Mouse: Device: "/dev/input/event2"
[     9.596] (--) evdev: Logitech G9x Laser Mouse: Vendor 0x46d Product 0xc066
[     9.596] (--) evdev: Logitech G9x Laser Mouse: Found 20 mouse buttons
[     9.596] (--) evdev: Logitech G9x Laser Mouse: Found scroll wheel(s)
[     9.596] (--) evdev: Logitech G9x Laser Mouse: Found relative axes
[     9.596] (--) evdev: Logitech G9x Laser Mouse: Found x and y relative axes
[     9.596] (II) evdev: Logitech G9x Laser Mouse: Configuring as mouse
[     9.596] (II) evdev: Logitech G9x Laser Mouse: Adding scrollwheel support
[     9.596] (**) evdev: Logitech G9x Laser Mouse: YAxisMapping: buttons 4 and 5
[     9.596] (**) evdev: Logitech G9x Laser Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[     9.596] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.6/5-1.6.2/5-1.6.2:1.0/0003:046D:C066.0004/input/input6/event2"
[     9.596] (II) XINPUT: Adding extended input device "Logitech G9x Laser Mouse" (type: MOUSE, id 12)
[     9.596] (II) evdev: Logitech G9x Laser Mouse: initialized for relative axes.
[     9.596] (**) Logitech G9x Laser Mouse: (accel) keeping acceleration scheme 1
[     9.596] (**) Logitech G9x Laser Mouse: (accel) acceleration profile 0
[     9.596] (**) Logitech G9x Laser Mouse: (accel) acceleration factor: 2.000
[     9.596] (**) Logitech G9x Laser Mouse: (accel) acceleration threshold: 4
[     9.596] (II) config/udev: Adding input device Logitech G9x Laser Mouse (/dev/input/mouse1)
[     9.596] (II) No input driver specified, ignoring this device.
[     9.596] (II) This device may have been added with another device file.
[     9.597] (II) config/udev: Adding input device Logitech G9x Laser Mouse (/dev/input/event3)
[     9.597] (**) Logitech G9x Laser Mouse: Applying InputClass "evdev keyboard catchall"
[     9.597] (II) Using input driver 'evdev' for 'Logitech G9x Laser Mouse'
[     9.597] (**) Logitech G9x Laser Mouse: always reports core events
[     9.597] (**) evdev: Logitech G9x Laser Mouse: Device: "/dev/input/event3"
[     9.597] (--) evdev: Logitech G9x Laser Mouse: Vendor 0x46d Product 0xc066
[     9.597] (--) evdev: Logitech G9x Laser Mouse: Found 1 mouse buttons
[     9.597] (--) evdev: Logitech G9x Laser Mouse: Found scroll wheel(s)
[     9.597] (--) evdev: Logitech G9x Laser Mouse: Found relative axes
[     9.597] (II) evdev: Logitech G9x Laser Mouse: Forcing relative x/y axes to exist.
[     9.597] (--) evdev: Logitech G9x Laser Mouse: Found absolute axes
[     9.597] (II) evdev: Logitech G9x Laser Mouse: Forcing absolute x/y axes to exist.
[     9.597] (--) evdev: Logitech G9x Laser Mouse: Found keys
[     9.597] (II) evdev: Logitech G9x Laser Mouse: Configuring as mouse
[     9.597] (II) evdev: Logitech G9x Laser Mouse: Configuring as keyboard
[     9.597] (II) evdev: Logitech G9x Laser Mouse: Adding scrollwheel support
[     9.597] (**) evdev: Logitech G9x Laser Mouse: YAxisMapping: buttons 4 and 5
[     9.597] (**) evdev: Logitech G9x Laser Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[     9.597] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.6/5-1.6.2/5-1.6.2:1.1/0003:046D:C066.0005/input/input7/event3"
[     9.597] (II) XINPUT: Adding extended input device "Logitech G9x Laser Mouse" (type: KEYBOARD, id 13)
[     9.597] (**) Option "xkb_rules" "evdev"
[     9.597] (**) Option "xkb_model" "pc105"
[     9.597] (**) Option "xkb_layout" "ch"
[     9.597] (**) Option "xkb_variant" "fr"
[     9.597] (II) evdev: Logitech G9x Laser Mouse: initialized for relative axes.
[     9.597] (WW) evdev: Logitech G9x Laser Mouse: ignoring absolute axes.
[     9.598] (**) Logitech G9x Laser Mouse: (accel) keeping acceleration scheme 1
[     9.598] (**) Logitech G9x Laser Mouse: (accel) acceleration profile 0
[     9.598] (**) Logitech G9x Laser Mouse: (accel) acceleration factor: 2.000
[     9.598] (**) Logitech G9x Laser Mouse: (accel) acceleration threshold: 4
[     9.598] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event4)
[     9.598] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[     9.598] (II) Using input driver 'evdev' for 'Logitech USB Multimedia Keyboard'
[     9.598] (**) Logitech USB Multimedia Keyboard: always reports core events
[     9.598] (**) evdev: Logitech USB Multimedia Keyboard: Device: "/dev/input/event4"
[     9.598] (--) evdev: Logitech USB Multimedia Keyboard: Vendor 0x46d Product 0xc317
[     9.598] (--) evdev: Logitech USB Multimedia Keyboard: Found keys
[     9.598] (II) evdev: Logitech USB Multimedia Keyboard: Configuring as keyboard
[     9.598] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.6/5-1.6.4/5-1.6.4:1.0/0003:046D:C317.0009/input/input17/event4"
[     9.598] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD, id 14)
[     9.598] (**) Option "xkb_rules" "evdev"
[     9.598] (**) Option "xkb_model" "pc105"
[     9.598] (**) Option "xkb_layout" "ch"
[     9.598] (**) Option "xkb_variant" "fr"
[     9.599] (II) config/udev: Adding input device Logitech USB Multimedia Keyboard (/dev/input/event5)
[     9.599] (**) Logitech USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
[     9.599] (II) Using input driver 'evdev' for 'Logitech USB Multimedia Keyboard'
[     9.599] (**) Logitech USB Multimedia Keyboard: always reports core events
[     9.599] (**) evdev: Logitech USB Multimedia Keyboard: Device: "/dev/input/event5"
[     9.599] (--) evdev: Logitech USB Multimedia Keyboard: Vendor 0x46d Product 0xc317
[     9.599] (--) evdev: Logitech USB Multimedia Keyboard: Found keys
[     9.599] (II) evdev: Logitech USB Multimedia Keyboard: Configuring as keyboard
[     9.599] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb5/5-1/5-1.6/5-1.6.4/5-1.6.4:1.1/0003:046D:C317.000A/input/input18/event5"
[     9.599] (II) XINPUT: Adding extended input device "Logitech USB Multimedia Keyboard" (type: KEYBOARD, id 15)
[     9.599] (**) Option "xkb_rules" "evdev"
[     9.599] (**) Option "xkb_model" "pc105"
[     9.599] (**) Option "xkb_layout" "ch"
[     9.599] (**) Option "xkb_variant" "fr"
[     9.600] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event10)
[     9.600] (II) No input driver specified, ignoring this device.
[     9.600] (II) This device may have been added with another device file.
[     9.600] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event11)
[     9.600] (II) No input driver specified, ignoring this device.
[     9.600] (II) This device may have been added with another device file.
[     9.600] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event12)
[     9.600] (II) No input driver specified, ignoring this device.
[     9.600] (II) This device may have been added with another device file.
[     9.600] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event13)
[     9.600] (II) No input driver specified, ignoring this device.
[     9.600] (II) This device may have been added with another device file.
[     9.601] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event14)
[     9.601] (II) No input driver specified, ignoring this device.
[     9.601] (II) This device may have been added with another device file.
[     9.601] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event15)
[     9.601] (II) No input driver specified, ignoring this device.
[     9.601] (II) This device may have been added with another device file.
[     9.601] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event16)
[     9.601] (II) No input driver specified, ignoring this device.
[     9.601] (II) This device may have been added with another device file.
[     9.601] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event17)
[     9.601] (II) No input driver specified, ignoring this device.
[     9.601] (II) This device may have been added with another device file.
[     9.602] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event18)
[     9.602] (II) No input driver specified, ignoring this device.
[     9.602] (II) This device may have been added with another device file.
[     9.602] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event19)
[     9.602] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[     9.602] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
[     9.602] (**) Eee PC WMI hotkeys: always reports core events
[     9.602] (**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event19"
[     9.602] (--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
[     9.602] (--) evdev: Eee PC WMI hotkeys: Found keys
[     9.602] (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
[     9.602] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input34/event19"
[     9.602] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 16)
[     9.602] (**) Option "xkb_rules" "evdev"
[     9.602] (**) Option "xkb_model" "pc105"
[     9.602] (**) Option "xkb_layout" "ch"
[     9.602] (**) Option "xkb_variant" "fr"
[     9.603] (II) config/udev: Adding input device PC Speaker (/dev/input/event9)
[     9.603] (II) No input driver specified, ignoring this device.
[     9.603] (II) This device may have been added with another device file.
[     9.606] (**) Wacom Intuos Pro S Pen eraser: Applying InputClass "evdev tablet catchall"
[     9.606] (**) Wacom Intuos Pro S Pen eraser: Applying InputClass "Wacom USB device class"
[     9.606] (**) Wacom Intuos Pro S Pen eraser: Applying InputClass "Wacom class"
[     9.606] (II) Using input driver 'wacom' for 'Wacom Intuos Pro S Pen eraser'
[     9.606] (**) Wacom Intuos Pro S Pen eraser: always reports core events
[     9.606] (**) Option "Device" "/dev/input/event0"
[     9.606] (**) Option "Type" "eraser"
[     9.606] (--) Wacom Intuos Pro S Pen eraser: maxX=31496 maxY=19685 maxZ=2047 resX=200000 resY=200000  tilt=enabled
[     9.628] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:056A:0314.0001/input/input3/event0"
[     9.628] (II) XINPUT: Adding extended input device "Wacom Intuos Pro S Pen eraser" (type: ERASER, id 17)
[     9.628] (**) Wacom Intuos Pro S Pen eraser: (accel) keeping acceleration scheme 1
[     9.628] (**) Wacom Intuos Pro S Pen eraser: (accel) acceleration profile 0
[     9.628] (**) Wacom Intuos Pro S Pen eraser: (accel) acceleration factor: 2.000
[     9.628] (**) Wacom Intuos Pro S Pen eraser: (accel) acceleration threshold: 4
[     9.628] (**) Wacom Intuos Pro S Pen cursor: Applying InputClass "evdev tablet catchall"
[     9.628] (**) Wacom Intuos Pro S Pen cursor: Applying InputClass "Wacom USB device class"
[     9.628] (**) Wacom Intuos Pro S Pen cursor: Applying InputClass "Wacom class"
[     9.628] (II) Using input driver 'wacom' for 'Wacom Intuos Pro S Pen cursor'
[     9.628] (**) Wacom Intuos Pro S Pen cursor: always reports core events
[     9.628] (**) Option "Device" "/dev/input/event0"
[     9.628] (**) Option "Type" "cursor"
[     9.652] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0/0003:056A:0314.0001/input/input3/event0"
[     9.652] (II) XINPUT: Adding extended input device "Wacom Intuos Pro S Pen cursor" (type: CURSOR, id 18)
[     9.652] (**) Wacom Intuos Pro S Pen cursor: (accel) keeping acceleration scheme 1
[     9.652] (**) Wacom Intuos Pro S Pen cursor: (accel) acceleration profile 0
[     9.652] (**) Wacom Intuos Pro S Pen cursor: (accel) acceleration factor: 2.000
[     9.652] (**) Wacom Intuos Pro S Pen cursor: (accel) acceleration threshold: 4
[     9.652] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event23)
[     9.653] (II) No input driver specified, ignoring this device.
[     9.653] (II) This device may have been added with another device file.
[     9.653] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event22)
[     9.653] (II) No input driver specified, ignoring this device.
[     9.653] (II) This device may have been added with another device file.
[     9.653] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event21)
[     9.653] (II) No input driver specified, ignoring this device.
[     9.653] (II) This device may have been added with another device file.
[     9.653] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event24)
[     9.653] (II) No input driver specified, ignoring this device.
[     9.653] (II) This device may have been added with another device file.
[    19.280] (--) NVIDIA(GPU-0): BenQ GW2765 (DFP-0): connected
[    19.280] (--) NVIDIA(GPU-0): BenQ GW2765 (DFP-0): Internal TMDS
[    19.280] (--) NVIDIA(GPU-0): BenQ GW2765 (DFP-0): 330.0 MHz maximum pixel clock
[    19.280] (--) NVIDIA(GPU-0):
[    19.308] (--) NVIDIA(GPU-0): Ancor Communications Inc VW246 (DFP-1): connected
[    19.308] (--) NVIDIA(GPU-0): Ancor Communications Inc VW246 (DFP-1): Internal TMDS
[    19.308] (--) NVIDIA(GPU-0): Ancor Communications Inc VW246 (DFP-1): 600.0 MHz maximum pixel clock
[    19.308] (--) NVIDIA(GPU-0):
[    19.308] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    19.308] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[    19.308] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[    19.308] (--) NVIDIA(GPU-0):
[    19.308] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    19.308] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[    19.308] (--) NVIDIA(GPU-0): DFP-3: 330.0 MHz maximum pixel clock
[    19.308] (--) NVIDIA(GPU-0):
[    19.308] (--) NVIDIA(GPU-0): DFP-4: disconnected
[    19.308] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[    19.308] (--) NVIDIA(GPU-0): DFP-4: 330.0 MHz maximum pixel clock
[    19.308] (--) NVIDIA(GPU-0):
[    19.647] (--) NVIDIA(GPU-0): BenQ GW2765 (DFP-0): connected
[    19.647] (--) NVIDIA(GPU-0): BenQ GW2765 (DFP-0): Internal TMDS
[    19.647] (--) NVIDIA(GPU-0): BenQ GW2765 (DFP-0): 330.0 MHz maximum pixel clock
[    19.647] (--) NVIDIA(GPU-0):
[    19.674] (--) NVIDIA(GPU-0): Ancor Communications Inc VW246 (DFP-1): connected
[    19.675] (--) NVIDIA(GPU-0): Ancor Communications Inc VW246 (DFP-1): Internal TMDS
[    19.675] (--) NVIDIA(GPU-0): Ancor Communications Inc VW246 (DFP-1): 600.0 MHz maximum pixel clock
[    19.675] (--) NVIDIA(GPU-0):
[    19.675] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    19.675] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[    19.675] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[    19.675] (--) NVIDIA(GPU-0):
[    19.675] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    19.675] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[    19.675] (--) NVIDIA(GPU-0): DFP-3: 330.0 MHz maximum pixel clock
[    19.675] (--) NVIDIA(GPU-0):
[    19.675] (--) NVIDIA(GPU-0): DFP-4: disconnected
[    19.675] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[    19.675] (--) NVIDIA(GPU-0): DFP-4: 330.0 MHz maximum pixel clock
[    19.675] (--) NVIDIA(GPU-0):
[    19.957] (II) NVIDIA(0): Setting mode "DVI-D-0: nvidia-auto-select @2560x1440 +0+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0}, HDMI-0: 1920x1080_60_0 @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[    20.050] (II) NVIDIA(0): Setting mode "DVI-D-0: nvidia-auto-select @2560x1440 +1920+0 {ViewPortIn=2560x1440, ViewPortOut=2560x1440+0+0}, HDMI-0: 1920x1080_60_0 @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
 



lspci -nnk | grep VGA -A 2


01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1c02] (rev a1)
        Subsystem: Gigabyte Technology Co., Ltd Device [1458:3722]
        Kernel driver in use: nvidia



apt-cache policy nvidia-driver


nvidia-driver:
  Installed: 375.26-1~bpo8+1
  Candidate: 375.26-1~bpo8+1
  Version table:
 *** 375.26-1~bpo8+1 0
        100 http://httpredir.debian.org/debian/ jessie-backports/non-free amd64 Packages
        100 http://ftp.fr.debian.org/debian/ jessie-backports/non-free amd64 Packages
        100 /var/lib/dpkg/status
     340.101-1 0
        500 http://ftp.fr.debian.org/debian/ jessie/non-free amd64 Packages


science sans conscience n'est que ruine de l'âme...

Hors ligne

#50 18-01-2017 16:40:03

robert2a
Membre
Lieu : France
Distrib. : Stretch 9
Noyau : Linux 4.9.0-3 4.9.30-2
(G)UI : Mate
Inscription : 15-11-2014

Re : [RESOLU] -- Pas de console?? & problemes graphiques liés??

je vous donne a titre informatif mon retour si ça peut aider (avec ma GTX1060 3Go)


lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1)
 



lspci -nnk | grep VGA -A 2
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1)
  Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438]
  Kernel driver in use: nvidia
 



ps : pour le log je peu regarder mais pas la meme version du driver et pas la meme version de debian

nota : je pense a une version différente du serveur X entre jessie et stretch

@smolski
la mise en forme de mes retours est volontairement mauvaise , juste informatif wink

rien de spécial sur son log , la carte est bien détecté :


[     8.888] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 1060 3GB (GP106-A) at PCI:1:0:0
[     8.888] (II) NVIDIA(0):     (GPU-0)
[     8.888] (--) NVIDIA(0): Memory: 3145728 kBytes
[     8.888] (--) NVIDIA(0): VideoBIOS: 86.06.11.00.75
[     8.888] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[     8.903] (--) NVIDIA(GPU-0): BenQ GW2765 (DFP-0): connected
 


si quelqu un veut bien lui expliquer comment mettre a jour les fichiers du serveur X (depuis les backports )
je ne vois pas autre chose.

Dernière modification par robert2a (18-01-2017 16:55:49)

Hors ligne

Pied de page des forums