Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

Pages : 1 2

#1 Le 21/08/2016, à 18:49

taamer

[Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Bonjour à tous,

Mon ordi est up and running depuis plus d'un an. Ce matin, une fenetre m'accueille avec un message de type "rebootez pour appliquer les modifications". Le systeme est parametré pour se mettre à jour en suivant les recommandations de Canonical.
Après le reboot, le login s'affiche (GUI). Je me loggue, je vois apparaitre furtivement mon fond d'ecran, puis une page noire type command line illisible, puis retour à l ecran de login sans autre explication. Je verifie le clavier, le teste le login avec unity/gnome/gnomeclassic, deux des trois sont sans effets et le troisieme boucle sur l'ecran de login.
La veille, utilisation normale de l'ordi. J'ai une carte graphique nvidia gtx970 avec driver nvidia 352, il y a deux ports dvi, le second est en permanence sur mon ecran, le premier est parfois connecté sur la tele via cable dvi2hdmi et j'etends alors l'ecran vers la tele (dual monitor), afin d'afficher vlc en plein ecran sur la tele.
Ce matin, apres reboot, plus de GUI, plus d'affichage sur l'ecran, affichage CLI sur la tele. J'ai rebranché la DVI1 sur le moniteur. Plus de xorg.conf. Je l'ai regenere via commande nvidia, depuis le boot est pire car je n'ai pas de login GUI en session graphique, je altfnF1 pour login en CLI et toutes les trois secondes, l'ecran flashe et bascule sur tty7GUI où je peux lire furtivement une sequence de boot interrompue, sans interaction possible. Bref je altfnF1 pour stopper le service gdm, les flashs à bascule s'arretent et je peux commencer à reflechir au diagnostic en CLI.

J'ai du reseau, pas de GUI, pas vu de pbm dans les packages.

xrandr -q donne Cant open display
/etc/X11/xorg.conf n'existait plus, regeneré via nvidia-xconfig
j'ai regardé systemctl sans voir ce qui pouvait etre a la source du probleme.

Que me recommanderiez-vous pour retablir l'environnement graphique?
Merci pour votre aide.

Dernière modification par taamer (Le 10/10/2016, à 13:52)

Hors ligne

#2 Le 22/08/2016, à 01:41

xabilon

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Salut

D'abord, il faut savoir que Ubuntu 15.10 est en fin de vie depuis le mois de juillet, donc tu n'as pas pu avoir de mises à jour après le 28/07.
Le système se serait-il mis à jour vers Ubuntu 16.04 ? Montre le résultat de :

cat /etc/issue

Pour voir d'où vient ton problème d'affichage, montre le contenu du fichier /var/log/Xorg.0.log
Fais le copier/coller depuis un LiveCD, se sera plus pratique (il faut évidemment ouvrir le Xorg.0.log du disque dur, pas celui du LiveCD !).
Le xorg.conf n'existe plus, il est recréé à chaque démarrage.

Pour passer un sujet en résolu : modifiez le premier message et ajoutez [Résolu] au titre.

Hors ligne

#3 Le 22/08/2016, à 11:54

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

cat /etc/issue --> je suis bien en 15.10.
ce qui a affiché la demande de reboot, si ce n'est pas un upgrade, m'est inconnu. Seul indice que j'acompte tenu des problemes rencontrés : il est possible que j'aie reboot alors que j'etais en dual screen (alors que d'habitude je repasse en mono ecran via unity system display, qui detecte la nature de l'ecran et de la tele sans que je me preoccupe trop des paramatres d'affichage). Après le reboot, la carte graphique envoie son signal video sur le port DVI-I (tele) et plus rien sur le DVI-D (ecran). Apres avoir permuté (tele off, ecran branché sur DVI-I), je peux comprendre que les parametres de display tele ne soient pas du tout adaptés pour l'ecran, d'où un blink au boot qui m'oblige à sudo service gdm stop pour pouvoir travailler en CLI.

Mes objectifs, si on ne trouve pas d'autre probleme :
- verifier en CLI les parametres de display pour retrouver la stabilité de l'interface graphique
- verifier si la GUI est operationnelle et la reparametrer le cas échéant
- une fois en mode GUI, je me debrouillerai pour rebasculer le moniteur sur DVI-D, puis reconfig la tele sur DVI-I.

A suivre : copier coller de /var/log/Xorg.0.log depuis un navigateur texte (elinks), wish me luck.

Hors ligne

#4 Le 22/08/2016, à 12:21

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

[Test envoi post via elinks] Pendant que je regarde comment copier/coller du texte dans elinks, j'ai vérifié et j'ai eu des upgrades d'applis partenaires (par exemple Wine, WineHQ).

Hors ligne

#5 Le 22/08/2016, à 12:39

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

test message avec cat fichier > /dev/tty1 , mon écran affiche tout le fichier mais il ne s'insère pas dans la box texte d'édition.

Hors ligne

#6 Le 22/08/2016, à 14:45

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Edit : contenu supprimé, la bonne mise en forme est cidessous.
tty2, clic gauche debut, clic droit fin (fait apparaitre surlignage), bascule dans tty1 où se trouve elinks, clic molette, ça marche!

Dernière modification par taamer (Le 22/08/2016, à 15:10)

Hors ligne

#7 Le 22/08/2016, à 14:48

xubu1957

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Bonjour,

cqfd93 a écrit :

Utilisation des balises code - Voilà la marche à suivre :

1.Ouvre le terminal avec ctrl-alt-t
2.Sélectionne la commande voulue avec un triple clic (ça sélectionne toute la ligne, même la fin si on ne la voit pas)
3.Colle-la dans le terminal avec un clic molette, valide avec Entrée
4.Sélectionne et copie tout ce que te dit le terminal depuis la commande jusqu'à le dernière ligne incluse
5.Clique sur le <> de l'éditeur de message
6.Colle là où se trouve le curseur (entre le ] et le [)
7.Refais toutes les étapes depuis la 2 pour les autres commandes.

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Résolu] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

Hors ligne

#8 Le 22/08/2016, à 14:50

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Upload via uploadedit.com, puis copier coller depuis tablette.
quelles est la balise pour cacher les textes trop longs? [spoiler]txt[/spoiler] ?

Désolé pour la mise en forme horrible, si quelqu'un veut remplacer "[" par "\n[", ça fera des retours à la ligne.

Hors ligne

#9 Le 22/08/2016, à 15:02

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

[   102.446] (II) This device may have been added with another device file.
[   102.447] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event10)
[   102.447] (II) No input driver specified, ignoring this device.
[   102.447] (II) This device may have been added with another device file.
[   102.447] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event11)
[   102.447] (II) No input driver specified, ignoring this device.
[   102.447] (II) This device may have been added with another device file.
[   102.448] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event12)
[   102.448] (II) No input driver specified, ignoring this device.
[   102.448] (II) This device may have been added with another device file.
[   102.448] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event6)
[   102.448] (II) No input driver specified, ignoring this device.
[   102.448] (II) This device may have been added with another device file.
[   102.449] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event13)
[   102.449] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[   102.449] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
[   102.449] (**) Eee PC WMI hotkeys: always reports core events
[   102.449] (**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event13"
[   102.449] (--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
[   102.449] (--) evdev: Eee PC WMI hotkeys: Found keys
[   102.449] (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
[   102.449] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input16/event13"
[   102.449] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 12)
[   102.449] (**) Option "xkb_rules" "evdev"
[   102.449] (**) Option "xkb_model" "pc105"
[   102.449] (**) Option "xkb_layout" "fr"
[   102.449] (**) Option "xkb_variant" "latin9"
[   102.456] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[   107.321] (II) evdev: Eee PC WMI hotkeys: Close
[   107.322] (II) UnloadModule: "evdev"
[   107.322] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Close
[   107.322] (II) UnloadModule: "evdev"
[   107.322] (II) evdev: USB Gaming Keyboard: Close
[   107.322] (II) UnloadModule: "evdev"
[   107.322] (II) evdev: USB Gaming Keyboard: Close
[   107.322] (II) UnloadModule: "evdev"
[   107.322] (II) evdev: USB Gaming Keyboard: Close
[   107.322] (II) UnloadModule: "evdev"
[   107.322] (II) evdev: Power Button: Close
[   107.322] (II) UnloadModule: "evdev"
[   107.322] (II) evdev: Power Button: Close
[   107.322] (II) UnloadModule: "evdev"
[   107.324] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[   107.324] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[   107.324] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[   107.324] (II) Server terminated successfully (0). Closing log file.

Modération : veuillez utiliser les balises code pour les retours de commande. Merci.

Dernière modification par Ayral (Le 22/08/2016, à 15:12)

Hors ligne

#10 Le 22/08/2016, à 15:10

xabilon

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Ah ouais, là c'est à la limite du lisible... il faut utiliser les balises code. C'est plus pratique d'utiliser un LiveCD ou un LiveUSB depuis le même ordinateur.
On a ces erreurs :

[ 102.245] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[ 102.245] (EE) NVIDIA: system's kernel log for additional error messages and
[ 102.245] (EE) NVIDIA: consult the NVIDIA README for details.
[ 102.245] (EE) No devices detected.

et plusieurs autres, pour aboutir à :

(II) Server terminated successfully (0). Closing log file

il n'a trouvé aucun pilote convenable, donc il ferme le serveur graphique.

Quels sont tes dépôts tiers ? y en a t-il en relation avec les pilotes ou le serveur graphiques ?
As-tu la possibilité de brancher un écran en VGA ? c'est peut-être ta config DVI qui a sauté. Tape cette commande pour reconfigurer le Xserver :

sudo dpkg-reconfigure xserver-xorg

Pour passer un sujet en résolu : modifiez le premier message et ajoutez [Résolu] au titre.

Hors ligne

#11 Le 22/08/2016, à 15:32

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Pas grand-chose ici (j'ai omis la ligne du mdp admin)

alexandre@Martin-2:~/Documents/Ordinateur$ sudo dpkg-reconfigure xserver-xorg
alexandre@Martin-2:~/Documents/Ordinateur$

Dépôts /etc/apt/sources.list (sans les lignes #)

alexandre@Martin-2:~/Documents/Ordinateur$ cat /etc/apt/sources.list | grep -v "#"

deb http://fr.archive.ubuntu.com/ubuntu/ wily main restricted
deb-src http://fr.archive.ubuntu.com/ubuntu/ wily main restricted

deb http://fr.archive.ubuntu.com/ubuntu/ wily-updates main restricted
deb-src http://fr.archive.ubuntu.com/ubuntu/ wily-updates main restricted

deb http://fr.archive.ubuntu.com/ubuntu/ wily universe
deb-src http://fr.archive.ubuntu.com/ubuntu/ wily universe
deb http://fr.archive.ubuntu.com/ubuntu/ wily-updates universe
deb-src http://fr.archive.ubuntu.com/ubuntu/ wily-updates universe

deb http://fr.archive.ubuntu.com/ubuntu/ wily multiverse
deb-src http://fr.archive.ubuntu.com/ubuntu/ wily multiverse
deb http://fr.archive.ubuntu.com/ubuntu/ wily-updates multiverse
deb-src http://fr.archive.ubuntu.com/ubuntu/ wily-updates multiverse


deb http://security.ubuntu.com/ubuntu wily-security main restricted
deb-src http://security.ubuntu.com/ubuntu wily-security main restricted
deb http://security.ubuntu.com/ubuntu wily-security universe
deb-src http://security.ubuntu.com/ubuntu wily-security universe
deb http://security.ubuntu.com/ubuntu wily-security multiverse
deb-src http://security.ubuntu.com/ubuntu wily-security multiverse

alexandre@Martin-2:~/Documents/Ordinateur$

Pour les balises code en mode texte, j'ai trouvé [code et [/code (en fermant les crochets), ce que je cherchais.
Merci à tous pour votre aide.

Dernière modification par taamer (Le 22/08/2016, à 15:35)

Hors ligne

#12 Le 22/08/2016, à 15:41

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Du coup, voici le fichier Xorg.0.log dans son intégralité.

[   102.204]
X.Org X Server 1.17.2
Release Date: 2015-06-16
[   102.204] X Protocol Version 11, Revision 0
[   102.204] Build Operating System: Linux 3.13.0-68-generic x86_64 Ubuntu
[   102.204] Current Operating System: Linux Martin-2 4.2.0-42-generic #49-Ubuntu SMP Tue Jun 28 21:26:26 UTC 2016 x86_64
[   102.204] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed root=UUID=34fc5266-1360-4b44-98d1-685a6be0f269 ro quiet splash vt.handoff=7
[   102.204] Build Date: 12 November 2015  05:33:29PM
[   102.204] xorg-server 2:1.17.2-1ubuntu9.1 (For technical support please see http://www.ubuntu.com/support)
[   102.204] Current version of pixman: 0.32.6
[   102.204]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[   102.204] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   102.205] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Aug 22 08:44:30 2016
[   102.205] (==) Using config file: "/etc/X11/xorg.conf"
[   102.205] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   102.205] (==) ServerLayout "X.org Configured"
[   102.205] (**) |-->Screen "Screen0" (0)
[   102.205] (**) |   |-->Monitor "Monitor0"
[   102.205] (**) |   |-->Device "Card0"
[   102.205] (**) |-->Input Device "Mouse0"
[   102.205] (**) |-->Input Device "Keyboard0"
[   102.205] (==) Automatically adding devices
[   102.205] (==) Automatically enabling devices
[   102.205] (==) Automatically adding GPU devices
[   102.206] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   102.206]    Entry deleted from font path.
[   102.206] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[   102.206]    Entry deleted from font path.
[   102.206] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[   102.206]    Entry deleted from font path.
[   102.206] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   102.206]    Entry deleted from font path.
[   102.206] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[   102.206]    Entry deleted from font path.
[   102.206] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[   102.206]    Entry deleted from font path.
[   102.206] (**) FontPath set to:
        /usr/share/fonts/X11/misc,
        /usr/share/fonts/X11/100dpi/:unscaled,
        /usr/share/fonts/X11/Type1,
        /usr/share/fonts/X11/100dpi,
        built-ins,
        /usr/share/fonts/X11/misc,
        /usr/share/fonts/X11/100dpi/:unscaled,
        /usr/share/fonts/X11/Type1,
        /usr/share/fonts/X11/100dpi,
        built-ins
[   102.206] (**) ModulePath set to "/usr/lib/xorg/modules"
[   102.206] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[   102.206] (WW) Disabling Mouse0
[   102.206] (WW) Disabling Keyboard0
[   102.206] (II) Loader magic: 0x55d6aaad9d40
[   102.206] (II) Module ABI versions:
[   102.206]    X.Org ANSI C Emulation: 0.4
[   102.206]    X.Org Video Driver: 19.0
[   102.206]    X.Org XInput driver : 21.0
[   102.206]    X.Org Server Extension : 9.0
[   102.209] (--) PCI:*(0:1:0:0) 10de:13c2:1462:3160 rev 161, Mem @ 0xfa000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[   102.209] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[   102.209] (II) LoadModule: "glx"
[   102.210] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   102.229] (II) Module glx: vendor="X.Org Foundation"
[   102.229]    compiled for 1.17.2, module version = 1.0.0
[   102.229]    ABI class: X.Org Server Extension, version 9.0
[   102.229] (==) AIGLX enabled
[   102.229] (II) LoadModule: "nvidia"
[   102.229] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[   102.233] (II) Module nvidia: vendor="NVIDIA Corporation"
[   102.233]    compiled for 4.0.2, module version = 1.0.0
[   102.233]    Module class: X.Org Video Driver
[   102.233] (II) NVIDIA dlloader X Driver  352.63  Sat Nov  7 20:29:25 PST 2015
[   102.233] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   102.233] (++) using VT number 7

[   102.233] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[   102.233] (II) Loading sub module "fb"
[   102.233] (II) LoadModule: "fb"
[   102.233] (II) Loading /usr/lib/xorg/modules/libfb.so
[   102.234] (II) Module fb: vendor="X.Org Foundation"
[   102.234]    compiled for 1.17.2, module version = 1.0.0
[   102.234]    ABI class: X.Org ANSI C Emulation, version 0.4
[   102.234] (II) Loading sub module "wfb"
[   102.234] (II) LoadModule: "wfb"
[   102.234] (II) Loading /usr/lib/xorg/modules/libwfb.so
[   102.235] (II) Module wfb: vendor="X.Org Foundation"
[   102.235]    compiled for 1.17.2, module version = 1.0.0
[   102.235]    ABI class: X.Org ANSI C Emulation, version 0.4
[   102.235] (II) Loading sub module "ramdac"
[   102.235] (II) LoadModule: "ramdac"
[   102.235] (II) Module "ramdac" already built-in
[   102.245] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[   102.245] (EE) NVIDIA:     system's kernel log for additional error messages and
[   102.245] (EE) NVIDIA:     consult the NVIDIA README for details.
[   102.245] (EE) No devices detected.
[   102.245] (==) Matched nvidia as autoconfigured driver 0
[   102.245] (==) Matched nouveau as autoconfigured driver 1
[   102.245] (==) Matched modesetting as autoconfigured driver 2
[   102.245] (==) Matched fbdev as autoconfigured driver 3
[   102.245] (==) Matched vesa as autoconfigured driver 4
[   102.245] (==) Assigned the driver to the xf86ConfigLayout
[   102.245] (II) LoadModule: "nvidia"
[   102.245] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[   102.245] (II) Module nvidia: vendor="NVIDIA Corporation"
[   102.245]    compiled for 4.0.2, module version = 1.0.0
[   102.245]    Module class: X.Org Video Driver
[   102.245] (II) UnloadModule: "nvidia"
[   102.245] (II) Unloading nvidia
[   102.245] (II) Failed to load module "nvidia" (already loaded, 21974)
[   102.245] (II) LoadModule: "nouveau"
[   102.246] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[   102.247] (II) Module nouveau: vendor="X.Org Foundation"
[   102.247]    compiled for 1.17.1, module version = 1.0.11
[   102.247]    Module class: X.Org Video Driver
[   102.247]    ABI class: X.Org Video Driver, version 19.0
[   102.247] (II) LoadModule: "modesetting"
[   102.247] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   102.249] (II) Module modesetting: vendor="X.Org Foundation"
[   102.249]    compiled for 1.17.2, module version = 1.17.2
[   102.249]    Module class: X.Org Video Driver
[   102.249]    ABI class: X.Org Video Driver, version 19.0
[   102.249] (II) LoadModule: "fbdev"
[   102.249] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[   102.250] (II) Module fbdev: vendor="X.Org Foundation"
[   102.250]    compiled for 1.17.1, module version = 0.4.4
[   102.250]    Module class: X.Org Video Driver
[   102.250]    ABI class: X.Org Video Driver, version 19.0
[   102.250] (II) LoadModule: "vesa"
[   102.250] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[   102.251] (II) Module vesa: vendor="X.Org Foundation"
[   102.251]    compiled for 1.17.1, module version = 2.3.4
[   102.251]    Module class: X.Org Video Driver
[   102.251]    ABI class: X.Org Video Driver, version 19.0
[   102.251] (II) NVIDIA dlloader X Driver  352.63  Sat Nov  7 20:29:25 PST 2015
[   102.251] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   102.251] (II) NOUVEAU driver Date:   Thu Aug 28 03:57:48 2014 +0200
[   102.251] (II) NOUVEAU driver for NVIDIA chipset families :
[   102.251]    RIVA TNT        (NV04)
[   102.251]    RIVA TNT2       (NV05)
[   102.251]    GeForce 256     (NV10)
[   102.251]    GeForce 2       (NV11, NV15)
[   102.251]    GeForce 4MX     (NV17, NV18)
[   102.251]    GeForce 3       (NV20)
[   102.251]    GeForce 4Ti     (NV25, NV28)
[   102.251]    GeForce FX      (NV3x)
[   102.251]    GeForce 6       (NV4x)
[   102.251]    GeForce 7       (G7x)
[   102.251]    GeForce 8       (G8x)
[   102.251]    GeForce GTX 200 (NVA0)
[   102.251]    GeForce GTX 400 (NVC0)
[   102.251] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   102.251] (II) FBDEV: driver for framebuffer: fbdev
[   102.251] (II) VESA: driver for VESA chipsets: vesa
[   102.251] (++) using VT number 7

[   102.252] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[   102.261] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[   102.261] (EE) NVIDIA:     system's kernel log for additional error messages and
[   102.261] (EE) NVIDIA:     consult the NVIDIA README for details.
[   102.261] (EE) [drm] KMS not enabled
[   102.261] (EE) open /dev/dri/card0: No such file or directory
[   102.261] (WW) Falling back to old probe method for modesetting
[   102.261] (EE) open /dev/dri/card0: No such file or directory
[   102.261] (II) Loading sub module "fbdevhw"
[   102.261] (II) LoadModule: "fbdevhw"
[   102.262] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[   102.263] (II) Module fbdevhw: vendor="X.Org Foundation"
[   102.263]    compiled for 1.17.2, module version = 0.0.2
[   102.263]    ABI class: X.Org Video Driver, version 19.0
[   102.263] (**) FBDEV(1): claimed PCI slot 1@0:0:0
[   102.263] (II) FBDEV(1): using default device
[   102.263] (WW) Falling back to old probe method for vesa
[   102.263] (EE) Screen 0 deleted because of no matching config section.
[   102.263] (II) UnloadModule: "modesetting"
[   102.263] (**) FBDEV(0): Depth 24, (--) framebuffer bpp 32
[   102.263] (==) FBDEV(0): RGB weight 888
[   102.263] (==) FBDEV(0): Default visual is TrueColor
[   102.263] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[   102.263] (II) FBDEV(0): hardware: EFI VGA (video memory: 3072kB)
[   102.263] (II) FBDEV(0): checking modes against framebuffer device...
[   102.263] (II) FBDEV(0): checking modes against monitor...
[   102.263] (--) FBDEV(0): Virtual size is 1024x768 (pitch 1024)
[   102.263] (**) FBDEV(0):  Built-in mode "current": 78.7 MHz, 59.9 kHz, 75.7 Hz
[   102.263] (II) FBDEV(0): Modeline "current"x0.0   78.65  1024 1056 1184 1312  768 772 776 792 -hsync -vsync -csync (59.9 kHz
b)
[   102.263] (==) FBDEV(0): DPI set to (96, 96)
[   102.263] (II) Loading sub module "fb"
[   102.263] (II) LoadModule: "fb"
[   102.263] (II) Loading /usr/lib/xorg/modules/libfb.so
[   102.263] (II) Module fb: vendor="X.Org Foundation"
[   102.263]    compiled for 1.17.2, module version = 1.0.0
[   102.263]    ABI class: X.Org ANSI C Emulation, version 0.4
[   102.263] (**) FBDEV(0): using shadow framebuffer
[   102.264] (II) Loading sub module "shadow"
[   102.264] (II) LoadModule: "shadow"
[   102.264] (II) Loading /usr/lib/xorg/modules/libshadow.so
[   102.265] (II) Module shadow: vendor="X.Org Foundation"
[   102.265]    compiled for 1.17.2, module version = 1.1.0
[   102.265]    ABI class: X.Org ANSI C Emulation, version 0.4
[   102.265] (II) UnloadModule: "vesa"
[   102.265] (II) Unloading vesa
[   102.265] (==) Depth 24 pixmap format is 32 bpp
[   102.265] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[   102.266] (==) FBDEV(0): Backing store enabled
[   102.266] (==) FBDEV(0): DPMS enabled
[   102.266] (==) RandR enabled
[   102.271] (II) SELinux: Disabled on system
[   102.272] (II) AIGLX: Screen 0 is not DRI2 capable
[   102.272] (EE) AIGLX: reverting to software rendering
[   102.300] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: undefined symbol: _glapi_tls_Dispatch)
[   102.300] (EE) GLX: could not load software renderer
[   102.300] (II) GLX: no usable GL providers found for screen 0
[   102.318] (II) XKB: generating xkmfile /tmp/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[   102.354] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[   102.354] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[   102.354] (II) LoadModule: "evdev"
[   102.355] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[   102.357] (II) Module evdev: vendor="X.Org Foundation"
[   102.357]    compiled for 1.17.1, module version = 2.9.2
[   102.357]    Module class: X.Org XInput Driver
[   102.357]    ABI class: X.Org XInput driver, version 21.0
[   102.357] (II) Using input driver 'evdev' for 'Power Button'
[   102.357] (**) Power Button: always reports core events
[   102.357] (**) evdev: Power Button: Device: "/dev/input/event1"
[   102.357] (--) evdev: Power Button: Vendor 0 Product 0x1
[   102.357] (--) evdev: Power Button: Found keys
[   102.357] (II) evdev: Power Button: Configuring as keyboard
[   102.357] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[   102.357] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[   102.357] (**) Option "xkb_rules" "evdev"
[   102.357] (**) Option "xkb_model" "pc105"
[   102.357] (**) Option "xkb_layout" "fr"
[   102.357] (**) Option "xkb_variant" "latin9"
[   102.359] (II) XKB: generating xkmfile /tmp/server-816A055A5FF7D63897839A4BDEDC3908551E49DA.xkm
[   102.380] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[   102.381] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[   102.381] (II) Using input driver 'evdev' for 'Power Button'
[   102.381] (**) Power Button: always reports core events
[   102.381] (**) evdev: Power Button: Device: "/dev/input/event0"
[   102.381] (--) evdev: Power Button: Vendor 0 Product 0x1
[   102.381] (--) evdev: Power Button: Found keys
[   102.381] (II) evdev: Power Button: Configuring as keyboard
[   102.381] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
[   102.381] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[   102.381] (**) Option "xkb_rules" "evdev"
[   102.381] (**) Option "xkb_model" "pc105"
[   102.381] (**) Option "xkb_layout" "fr"
[   102.381] (**) Option "xkb_variant" "latin9"
[   102.381] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event14)
[   102.381] (II) No input driver specified, ignoring this device.
[   102.381] (II) This device may have been added with another device file.
[   102.382] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event15)
[   102.382] (II) No input driver specified, ignoring this device.
[   102.382] (II) This device may have been added with another device file.
[   102.382] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event16)
[   102.382] (II) No input driver specified, ignoring this device.
[   102.382] (II) This device may have been added with another device file.
[   102.383] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event17)
[   102.383] (II) No input driver specified, ignoring this device.
[   102.383] (II) This device may have been added with another device file.
[   102.383] (II) config/udev: Adding input device USB Gaming Keyboard (/dev/input/event2)
[   102.383] (**) USB Gaming Keyboard: Applying InputClass "evdev keyboard catchall"
[   102.383] (II) Using input driver 'evdev' for 'USB Gaming Keyboard'
[   102.383] (**) USB Gaming Keyboard: always reports core events
[   102.383] (**) evdev: USB Gaming Keyboard: Device: "/dev/input/event2"
[   102.384] (--) evdev: USB Gaming Keyboard: Vendor 0x4d9 Product 0xa030
[   102.384] (--) evdev: USB Gaming Keyboard: Found keys
[   102.384] (II) evdev: USB Gaming Keyboard: Configuring as keyboard
[   102.384] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9.3/1-9.3:1.0/0003:04D9:A030.0002/input/input4/event2"
[   102.384] (II) XINPUT: Adding extended input device "USB Gaming Keyboard" (type: KEYBOARD, id 8)
[   102.384] (**) Option "xkb_rules" "evdev"
[   102.384] (**) Option "xkb_model" "pc105"
[   102.384] (**) Option "xkb_layout" "fr"
[   102.384] (**) Option "xkb_variant" "latin9"
[   102.385] (II) config/udev: Adding input device USB Gaming Keyboard (/dev/input/event3)
[   102.385] (**) USB Gaming Keyboard: Applying InputClass "evdev pointer catchall"
[   102.385] (**) USB Gaming Keyboard: Applying InputClass "evdev keyboard catchall"
[   102.385] (II) Using input driver 'evdev' for 'USB Gaming Keyboard'
[   102.385] (**) USB Gaming Keyboard: always reports core events
[   102.385] (**) evdev: USB Gaming Keyboard: Device: "/dev/input/event3"
[   102.385] (--) evdev: USB Gaming Keyboard: Vendor 0x4d9 Product 0xa030
[   102.385] (--) evdev: USB Gaming Keyboard: Found 9 mouse buttons
[   102.385] (--) evdev: USB Gaming Keyboard: Found scroll wheel(s)
[   102.385] (--) evdev: USB Gaming Keyboard: Found relative axes
[   102.385] (--) evdev: USB Gaming Keyboard: Found x and y relative axes
[   102.385] (--) evdev: USB Gaming Keyboard: Found keys
[   102.385] (II) evdev: USB Gaming Keyboard: Configuring as mouse
[   102.385] (II) evdev: USB Gaming Keyboard: Configuring as keyboard
[   102.385] (II) evdev: USB Gaming Keyboard: Adding scrollwheel support
[   102.385] (**) evdev: USB Gaming Keyboard: YAxisMapping: buttons 4 and 5
[   102.385] (**) evdev: USB Gaming Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[   102.385] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9.3/1-9.3:1.1/0003:04D9:A030.0003/input/input6/event3"
[   102.385] (II) XINPUT: Adding extended input device "USB Gaming Keyboard" (type: KEYBOARD, id 9)
[   102.385] (**) Option "xkb_rules" "evdev"
[   102.385] (**) Option "xkb_model" "pc105"
[   102.385] (**) Option "xkb_layout" "fr"
[   102.385] (**) Option "xkb_variant" "latin9"
[   102.385] (II) evdev: USB Gaming Keyboard: initialized for relative axes.
[   102.385] (**) USB Gaming Keyboard: (accel) keeping acceleration scheme 1
[   102.385] (**) USB Gaming Keyboard: (accel) acceleration profile 0
[   102.386] (**) USB Gaming Keyboard: (accel) acceleration factor: 2.000
[   102.386] (**) USB Gaming Keyboard: (accel) acceleration threshold: 4
[   102.386] (II) config/udev: Adding input device USB Gaming Keyboard (/dev/input/mouse0)
[   102.386] (II) No input driver specified, ignoring this device.
[   102.386] (II) This device may have been added with another device file.
[   102.387] (II) config/udev: Adding input device USB Gaming Keyboard (/dev/input/event4)
[   102.387] (**) USB Gaming Keyboard: Applying InputClass "evdev keyboard catchall"
[   102.387] (II) Using input driver 'evdev' for 'USB Gaming Keyboard'
[   102.387] (**) USB Gaming Keyboard: always reports core events
[   102.387] (**) evdev: USB Gaming Keyboard: Device: "/dev/input/event4"
[   102.387] (--) evdev: USB Gaming Keyboard: Vendor 0x4d9 Product 0xa030
[   102.387] (--) evdev: USB Gaming Keyboard: Found keys
[   102.387] (II) evdev: USB Gaming Keyboard: Configuring as keyboard
[   102.387] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9.3/1-9.3:1.2/0003:04D9:A030.0004/input/input7/event4"
[   102.387] (II) XINPUT: Adding extended input device "USB Gaming Keyboard" (type: KEYBOARD, id 10)
[   102.387] (**) Option "xkb_rules" "evdev"
[   102.387] (**) Option "xkb_model" "pc105"
[   102.387] (**) Option "xkb_layout" "fr"
[   102.387] (**) Option "xkb_variant" "latin9"
[   102.388] (II) config/udev: Adding input device Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) (/dev/input/event5)
[   102.388] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Applying InputClass "evdev pointer catchall"
[   102.388] (II) Using input driver 'evdev' for 'Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)'
[   102.388] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): always reports core events
[   102.388] (**) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Device: "/dev/input/event5"
[   102.444] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Vendor 0x45e Product 0x47
[   102.444] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found 9 mouse buttons
[   102.444] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found scroll wheel(s)
[   102.444] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found relative axes
[   102.444] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found x and y relative axes
[   102.444] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Configuring as mouse
[   102.444] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Adding scrollwheel support
[   102.444] (**) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): YAxisMapping: buttons 4 and 5
[   102.444] (**) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[   102.444] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9.4/1-9.4:1.0/0003:045E:0047.0005/input/input8/event5"
[   102.444] (II) XINPUT: Adding extended input device "Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)" (type: MOUSE, id 11)
[   102.444] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): initialized for relative axes.
[   102.444] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) keeping acceleration scheme 1
[   102.444] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) acceleration profile 0
[   102.444] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) acceleration factor: 2.000
[   102.444] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) acceleration threshold: 4
[   102.445] (II) config/udev: Adding input device Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) (/dev/input/mouse1)
[   102.445] (II) No input driver specified, ignoring this device.
[   102.445] (II) This device may have been added with another device file.
[   102.445] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event7)
[   102.446] (II) No input driver specified, ignoring this device.
[   102.446] (II) This device may have been added with another device file.
[   102.446] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
[   102.446] (II) No input driver specified, ignoring this device.
[   102.446] (II) This device may have been added with another device file.
[   102.446] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event9)
[   102.446] (II) No input driver specified, ignoring this device.
[   102.446] (II) This device may have been added with another device file.
[   102.447] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event10)
[   102.447] (II) No input driver specified, ignoring this device.
[   102.447] (II) This device may have been added with another device file.
[   102.447] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event11)
[   102.447] (II) No input driver specified, ignoring this device.
[   102.447] (II) This device may have been added with another device file.
[   102.448] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event12)
[   102.448] (II) No input driver specified, ignoring this device.
[   102.448] (II) This device may have been added with another device file.
[   102.448] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event6)
[   102.448] (II) No input driver specified, ignoring this device.
[   102.448] (II) This device may have been added with another device file.
[   102.449] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event13)
[   102.449] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[   102.449] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
[   102.449] (**) Eee PC WMI hotkeys: always reports core events
[   102.449] (**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event13"
[   102.449] (--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
[   102.449] (--) evdev: Eee PC WMI hotkeys: Found keys
[   102.449] (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
[   102.449] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input16/event13"
[   102.449] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 12)
[   102.449] (**) Option "xkb_rules" "evdev"
[   102.449] (**) Option "xkb_model" "pc105"
[   102.449] (**) Option "xkb_layout" "fr"
[   102.449] (**) Option "xkb_variant" "latin9"
[   102.456] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[   107.321] (II) evdev: Eee PC WMI hotkeys: Close
[   107.322] (II) UnloadModule: "evdev"
[   107.322] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Close
[   107.322] (II) UnloadModule: "evdev"
[   107.322] (II) evdev: USB Gaming Keyboard: Close
[   107.322] (II) UnloadModule: "evdev"
[   107.322] (II) evdev: USB Gaming Keyboard: Close
[   107.322] (II) UnloadModule: "evdev"
[   107.322] (II) evdev: USB Gaming Keyboard: Close
[   107.322] (II) UnloadModule: "evdev"
[   107.322] (II) evdev: Power Button: Close
[   107.322] (II) UnloadModule: "evdev"
[   107.322] (II) evdev: Power Button: Close
[   107.322] (II) UnloadModule: "evdev"
[   107.324] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[   107.324] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[   107.324] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[   107.324] (II) Server terminated successfully (0). Closing log file.

Hors ligne

#13 Le 22/08/2016, à 15:58

xabilon

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Et qu'as-tu dans /etc/apt/sources.list.d ?
As-tu un écran VGA à disposition ?

Là, il utilise le xorg.conf que tu as créé avec nvidia-xconfig. En fait, en premier lieu, il est préférable de laisser la configuration automatique, et ensuite une fois les bons paramètres trouvés d'éventuellement créer un xorg.conf correct.
Commence par :

sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
sudo reboot

ça ne fonctionnera probablement pas, mais poste alors le nouveau /var/log/Xorg.0.log (il y aura des messages concernant la configuration automatique)

Dernière modification par xabilon (Le 22/08/2016, à 15:59)

Pour passer un sujet en résolu : modifiez le premier message et ajoutez [Résolu] au titre.

Hors ligne

#14 Le 22/08/2016, à 17:01

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Mon écran a une prise DVI et une prise VGA, mais sur le PC ni ma carte graphique (nvidia gtx970) ni ma carte mère n'ont de port VGA. Y a-t-il un intérêt à connecter l'écran en VGA via adaptateur USB-VGA (que j'utilise parfois pour un laptop)?

Autres repositories :

alexandre@Martin-2:~/Documents/Ordinateur$ ls -al /etc/apt/sources.list.d/
total 72
drwxr-xr-x 2 root root 4096 août  21 17:20 .
drwxr-xr-x 6 root root 4096 mars  27 12:44 ..
-rw-r--r-- 1 root root  180 mai    8 15:22 google-talkplugin.list
-rw-r--r-- 1 root root  180 mai    8 15:22 google-talkplugin.list.save
-rw-r--r-- 1 root root  140 mai    8 15:22 graphics-drivers-ubuntu-ppa-wily.list
-rw-r--r-- 1 root root  140 mai    8 15:22 graphics-drivers-ubuntu-ppa-wily.list.save
-rw-r--r-- 1 root root  191 mai    8 15:22 kilian-ubuntu-f_lux-trusty.list
-rw-r--r-- 1 root root  191 mai    8 15:22 kilian-ubuntu-f_lux-trusty.list.save
-rw-r--r-- 1 root root  256 mai    8 15:22 kilian-ubuntu-f_lux-wily.list
-rw-r--r-- 1 root root  256 mai    8 15:22 kilian-ubuntu-f_lux-wily.list.save
-rw-r--r-- 1 root root  126 mai    8 15:22 linrunner-ubuntu-tlp-wily.list
-rw-r--r-- 1 root root  126 mai    8 15:22 linrunner-ubuntu-tlp-wily.list.save
-rw-r--r-- 1 root root  144 mai    8 15:22 obsproject-ubuntu-obs-studio-wily.list
-rw-r--r-- 1 root root  142 mai    8 15:22 obsproject-ubuntu-obs-studio-wily.list.save
-rw-r--r-- 1 root root  132 mai    8 15:22 wine-ubuntu-wine-builds-wily.list
-rw-r--r-- 1 root root  132 mai    8 15:22 wine-ubuntu-wine-builds-wily.list.save
-rw-r--r-- 1 root root  132 mai    8 15:22 xorg-edgers-ubuntu-ppa-wily.list
-rw-r--r-- 1 root root  132 mai    8 15:22 xorg-edgers-ubuntu-ppa-wily.list.save

Je move xorg.conf et je reboot, puis je poste le nouveau Xorg.0.log .

Hors ligne

#15 Le 22/08/2016, à 17:36

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Après reboot : comme auparavant, il y a un flash qui me contraint à 

 sudo service gdm stop

pour pouvoir travailler en CLI.

Nouveau fichier /var/log/Xorg.0.log

[    79.697]
X.Org X Server 1.17.2
Release Date: 2015-06-16
[    79.697] X Protocol Version 11, Revision 0
[    79.697] Build Operating System: Linux 3.13.0-68-generic x86_64 Ubuntu
[    79.697] Current Operating System: Linux Martin-2 4.2.0-42-generic #49-Ubuntu SMP Tue Jun 28 21:26:26 UTC 2016 x86_64
[    79.697] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed root=UUID=34fc5266-1360-4b44-98d1-685a6be0f269 ro quiet splash vt.handoff=7
[    79.697] Build Date: 12 November 2015  05:33:29PM
[    79.697] xorg-server 2:1.17.2-1ubuntu9.1 (For technical support please see http://www.ubuntu.com/support)
[    79.697] Current version of pixman: 0.32.6
[    79.697]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[    79.697] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    79.697] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Aug 22 17:04:04 2016
[    79.698] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    79.698] (==) No Layout section.  Using the first Screen section.
[    79.698] (==) No screen section available. Using defaults.
[    79.698] (**) |-->Screen "Default Screen Section" (0)
[    79.698] (**) |   |-->Monitor "<default monitor>"
[    79.698] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[    79.698] (==) Automatically adding devices
[    79.698] (==) Automatically enabling devices
[    79.698] (==) Automatically adding GPU devices
[    79.698] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    79.698]    Entry deleted from font path.
[    79.698] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[    79.698]    Entry deleted from font path.
[    79.698] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    79.698]    Entry deleted from font path.
[    79.698] (==) FontPath set to:
        /usr/share/fonts/X11/misc,
        /usr/share/fonts/X11/100dpi/:unscaled,
        /usr/share/fonts/X11/Type1,
        /usr/share/fonts/X11/100dpi,
        built-ins
[    79.698] (==) ModulePath set to "/usr/lib/x86_64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[    79.698] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[    79.698] (II) Loader magic: 0x5569fa149d40
[    79.698] (II) Module ABI versions:
[    79.698]    X.Org ANSI C Emulation: 0.4
[    79.698]    X.Org Video Driver: 19.0
[    79.698]    X.Org XInput driver : 21.0
[    79.698]    X.Org Server Extension : 9.0
[    79.700] (--) PCI:*(0:1:0:0) 10de:13c2:1462:3160 rev 161, Mem @ 0xfa000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[    79.700] (WW) "glamoregl" will not be loaded unless you've specified it to be loaded elsewhere.
[    79.700] (II) "glx" will be loaded by default.
[    79.700] (II) LoadModule: "glx"
[    79.700] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
[    79.707] (II) Module glx: vendor="NVIDIA Corporation"
[    79.707]    compiled for 4.0.2, module version = 1.0.0
[    79.707]    Module class: X.Org Server Extension
[    79.707] (II) NVIDIA GLX Module  352.63  Sat Nov  7 20:52:00 PST 2015
[    79.707] (==) Matched nvidia as autoconfigured driver 0
[    79.707] (==) Matched nouveau as autoconfigured driver 1
[    79.707] (==) Matched modesetting as autoconfigured driver 2
[    79.707] (==) Matched fbdev as autoconfigured driver 3
[    79.707] (==) Matched vesa as autoconfigured driver 4
[    79.707] (==) Assigned the driver to the xf86ConfigLayout
[    79.707] (II) LoadModule: "nvidia"
[    79.707] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
[    79.707] (II) Module nvidia: vendor="NVIDIA Corporation"
[    79.707]    compiled for 4.0.2, module version = 1.0.0
[    79.707]    Module class: X.Org Video Driver
[    79.707] (II) LoadModule: "nouveau"
[    79.707] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[    79.707] (II) Module nouveau: vendor="X.Org Foundation"
[    79.707]    compiled for 1.17.1, module version = 1.0.11
[    79.707]    Module class: X.Org Video Driver
[    79.707]    ABI class: X.Org Video Driver, version 19.0
[    79.707] (II) LoadModule: "modesetting"
[    79.707] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    79.707] (II) Module modesetting: vendor="X.Org Foundation"
[    79.707]    compiled for 1.17.2, module version = 1.17.2
[    79.707]    Module class: X.Org Video Driver
[    79.707]    ABI class: X.Org Video Driver, version 19.0
[    79.707] (II) LoadModule: "fbdev"
[    79.707] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    79.707] (II) Module fbdev: vendor="X.Org Foundation"
[    79.707]    compiled for 1.17.1, module version = 0.4.4
[    79.707]    Module class: X.Org Video Driver
[    79.707]    ABI class: X.Org Video Driver, version 19.0
[    79.707] (II) LoadModule: "vesa"
[    79.708] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[    79.708] (II) Module vesa: vendor="X.Org Foundation"
[    79.708]    compiled for 1.17.1, module version = 2.3.4
[    79.708]    Module class: X.Org Video Driver
[    79.708]    ABI class: X.Org Video Driver, version 19.0
[    79.708] (II) NVIDIA dlloader X Driver  352.63  Sat Nov  7 20:29:25 PST 2015
[    79.708] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    79.708] (II) NOUVEAU driver Date:   Thu Aug 28 03:57:48 2014 +0200
[    79.708] (II) NOUVEAU driver for NVIDIA chipset families :
[    79.708]    RIVA TNT        (NV04)
[    79.708]    RIVA TNT2       (NV05)
[    79.708]    GeForce 256     (NV10)
[    79.708]    GeForce 2       (NV11, NV15)
[    79.708]    GeForce 4MX     (NV17, NV18)
[    79.708]    GeForce 3       (NV20)
[    79.708]    GeForce 4Ti     (NV25, NV28)
[    79.708]    GeForce FX      (NV3x)
[    79.708]    GeForce 6       (NV4x)
[    79.708]    GeForce 7       (G7x)
[    79.708]    GeForce 8       (G8x)
[    79.708]    GeForce GTX 200 (NVA0)
[    79.708]    GeForce GTX 400 (NVC0)
[    79.708] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    79.708] (II) FBDEV: driver for framebuffer: fbdev
[    79.708] (II) VESA: driver for VESA chipsets: vesa
[    79.708] (++) using VT number 7

[    79.708] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[    79.708] (II) Loading sub module "fb"
[    79.708] (II) LoadModule: "fb"
[    79.708] (II) Loading /usr/lib/xorg/modules/libfb.so
[    79.708] (II) Module fb: vendor="X.Org Foundation"
[    79.708]    compiled for 1.17.2, module version = 1.0.0
[    79.708]    ABI class: X.Org ANSI C Emulation, version 0.4
[    79.708] (II) Loading sub module "wfb"
[    79.708] (II) LoadModule: "wfb"
[    79.708] (II) Loading /usr/lib/xorg/modules/libwfb.so
[    79.708] (II) Module wfb: vendor="X.Org Foundation"
[    79.708]    compiled for 1.17.2, module version = 1.0.0
[    79.708]    ABI class: X.Org ANSI C Emulation, version 0.4
[    79.708] (II) Loading sub module "ramdac"
[    79.708] (II) LoadModule: "ramdac"
[    79.708] (II) Module "ramdac" already built-in
[    79.713] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[    79.713] (EE) NVIDIA:     system's kernel log for additional error messages and
[    79.713] (EE) NVIDIA:     consult the NVIDIA README for details.
[    79.713] (EE) [drm] KMS not enabled
[    79.713] (EE) open /dev/dri/card0: No such file or directory
[    79.713] (WW) Falling back to old probe method for modesetting
[    79.713] (EE) open /dev/dri/card0: No such file or directory
[    79.713] (II) Loading sub module "fbdevhw"
[    79.713] (II) LoadModule: "fbdevhw"
[    79.713] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    79.714] (II) Module fbdevhw: vendor="X.Org Foundation"
[    79.714]    compiled for 1.17.2, module version = 0.0.2
[    79.714]    ABI class: X.Org Video Driver, version 19.0
[    79.714] (**) FBDEV(1): claimed PCI slot 1@0:0:0
[    79.714] (II) FBDEV(1): using default device
[    79.714] (WW) Falling back to old probe method for vesa
[    79.714] (EE) Screen 0 deleted because of no matching config section.
[    79.714] (II) UnloadModule: "modesetting"
[    79.714] (II) FBDEV(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[    79.714] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[    79.714] (==) FBDEV(0): RGB weight 888
[    79.714] (==) FBDEV(0): Default visual is TrueColor
[    79.714] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[    79.714] (II) FBDEV(0): hardware: EFI VGA (video memory: 3072kB)
[    79.714] (II) FBDEV(0): checking modes against framebuffer device...
[    79.714] (II) FBDEV(0): checking modes against monitor...
[    79.714] (--) FBDEV(0): Virtual size is 1024x768 (pitch 1024)
[    79.714] (**) FBDEV(0):  Built-in mode "current": 78.7 MHz, 59.9 kHz, 75.7 Hz
[    79.714] (II) FBDEV(0): Modeline "current"x0.0   78.65  1024 1056 1184 1312  768 772 776 792 -hsync -vsync -csync (59.9 kHz
b)
[    79.714] (==) FBDEV(0): DPI set to (96, 96)
[    79.714] (II) Loading sub module "fb"
[    79.714] (II) LoadModule: "fb"
[    79.714] (II) Loading /usr/lib/xorg/modules/libfb.so
[    79.714] (II) Module fb: vendor="X.Org Foundation"
[    79.714]    compiled for 1.17.2, module version = 1.0.0
[    79.714]    ABI class: X.Org ANSI C Emulation, version 0.4
[    79.714] (**) FBDEV(0): using shadow framebuffer
[    79.714] (II) Loading sub module "shadow"
[    79.714] (II) LoadModule: "shadow"
[    79.714] (II) Loading /usr/lib/xorg/modules/libshadow.so
[    79.714] (II) Module shadow: vendor="X.Org Foundation"
[    79.714]    compiled for 1.17.2, module version = 1.1.0
[    79.714]    ABI class: X.Org ANSI C Emulation, version 0.4
[    79.714] (II) UnloadModule: "vesa"
[    79.714] (II) Unloading vesa
[    79.714] (==) Depth 24 pixmap format is 32 bpp
[    79.714] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[    79.714] (==) FBDEV(0): Backing store enabled
[    79.714] (==) FBDEV(0): DPMS enabled
[    79.714] (==) RandR enabled
[    79.717] (II) SELinux: Disabled on system
[    79.717] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
[    79.723] (II) XKB: generating xkmfile /tmp/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[    79.737] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[    79.737] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    79.737] (II) LoadModule: "evdev"
[    79.737] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[    79.737] (II) Module evdev: vendor="X.Org Foundation"
[    79.737]    compiled for 1.17.1, module version = 2.9.2
[    79.737]    Module class: X.Org XInput Driver
[    79.737]    ABI class: X.Org XInput driver, version 21.0
[    79.737] (II) Using input driver 'evdev' for 'Power Button'
[    79.737] (**) Power Button: always reports core events
[    79.737] (**) evdev: Power Button: Device: "/dev/input/event1"
[    79.737] (--) evdev: Power Button: Vendor 0 Product 0x1
[    79.737] (--) evdev: Power Button: Found keys
[    79.737] (II) evdev: Power Button: Configuring as keyboard
[    79.737] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[    79.737] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    79.737] (**) Option "xkb_rules" "evdev"
[    79.737] (**) Option "xkb_model" "pc105"
[    79.737] (**) Option "xkb_layout" "fr"
[    79.737] (**) Option "xkb_variant" "latin9"
[    79.738] (II) XKB: generating xkmfile /tmp/server-816A055A5FF7D63897839A4BDEDC3908551E49DA.xkm
[    79.747] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[    79.747] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    79.747] (II) Using input driver 'evdev' for 'Power Button'
[    79.747] (**) Power Button: always reports core events
[    79.747] (**) evdev: Power Button: Device: "/dev/input/event0"
[    79.747] (--) evdev: Power Button: Vendor 0 Product 0x1
[    79.747] (--) evdev: Power Button: Found keys
[    79.747] (II) evdev: Power Button: Configuring as keyboard
[    79.747] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
[    79.747] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[    79.747] (**) Option "xkb_rules" "evdev"
[    79.747] (**) Option "xkb_model" "pc105"
[    79.747] (**) Option "xkb_layout" "fr"
[    79.747] (**) Option "xkb_variant" "latin9"
[    79.747] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event14)
[    79.747] (II) No input driver specified, ignoring this device.
[    79.747] (II) This device may have been added with another device file.
[    79.747] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event15)
[    79.747] (II) No input driver specified, ignoring this device.
[    79.747] (II) This device may have been added with another device file.
[    79.747] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event16)
[    79.747] (II) No input driver specified, ignoring this device.
[    79.747] (II) This device may have been added with another device file.
[    79.748] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event17)
[    79.748] (II) No input driver specified, ignoring this device.
[    79.748] (II) This device may have been added with another device file.
[    79.748] (II) config/udev: Adding input device USB Gaming Keyboard (/dev/input/event2)
[    79.748] (**) USB Gaming Keyboard: Applying InputClass "evdev keyboard catchall"
[    79.748] (II) Using input driver 'evdev' for 'USB Gaming Keyboard'
[    79.748] (**) USB Gaming Keyboard: always reports core events
[    79.748] (**) evdev: USB Gaming Keyboard: Device: "/dev/input/event2"
[    79.748] (--) evdev: USB Gaming Keyboard: Vendor 0x4d9 Product 0xa030
[    79.748] (--) evdev: USB Gaming Keyboard: Found keys
[    79.748] (II) evdev: USB Gaming Keyboard: Configuring as keyboard
[    79.748] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9.3/1-9.3:1.0/0003:04D9:A030.0002/input/input5/event2"
[    79.748] (II) XINPUT: Adding extended input device "USB Gaming Keyboard" (type: KEYBOARD, id 8)
[    79.748] (**) Option "xkb_rules" "evdev"
[    79.748] (**) Option "xkb_model" "pc105"
[    79.748] (**) Option "xkb_layout" "fr"
[    79.748] (**) Option "xkb_variant" "latin9"
[    79.748] (II) config/udev: Adding input device USB Gaming Keyboard (/dev/input/event3)
[    79.748] (**) USB Gaming Keyboard: Applying InputClass "evdev pointer catchall"
[    79.748] (**) USB Gaming Keyboard: Applying InputClass "evdev keyboard catchall"
[    79.748] (II) Using input driver 'evdev' for 'USB Gaming Keyboard'
[    79.748] (**) USB Gaming Keyboard: always reports core events
[    79.748] (**) evdev: USB Gaming Keyboard: Device: "/dev/input/event3"
[    79.748] (--) evdev: USB Gaming Keyboard: Vendor 0x4d9 Product 0xa030
[    79.748] (--) evdev: USB Gaming Keyboard: Found 9 mouse buttons
[    79.748] (--) evdev: USB Gaming Keyboard: Found scroll wheel(s)
[    79.748] (--) evdev: USB Gaming Keyboard: Found relative axes
[    79.748] (--) evdev: USB Gaming Keyboard: Found x and y relative axes
[    79.748] (--) evdev: USB Gaming Keyboard: Found keys
[    79.748] (II) evdev: USB Gaming Keyboard: Configuring as mouse
[    79.748] (II) evdev: USB Gaming Keyboard: Configuring as keyboard
[    79.748] (II) evdev: USB Gaming Keyboard: Adding scrollwheel support
[    79.748] (**) evdev: USB Gaming Keyboard: YAxisMapping: buttons 4 and 5
[    79.748] (**) evdev: USB Gaming Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    79.748] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9.3/1-9.3:1.1/0003:04D9:A030.0003/input/input6/event3"
[    79.748] (II) XINPUT: Adding extended input device "USB Gaming Keyboard" (type: KEYBOARD, id 9)
[    79.748] (**) Option "xkb_rules" "evdev"
[    79.749] (**) Option "xkb_model" "pc105"
[    79.749] (**) Option "xkb_layout" "fr"
[    79.749] (**) Option "xkb_variant" "latin9"
[    79.749] (II) evdev: USB Gaming Keyboard: initialized for relative axes.
[    79.749] (**) USB Gaming Keyboard: (accel) keeping acceleration scheme 1
[    79.749] (**) USB Gaming Keyboard: (accel) acceleration profile 0
[    79.749] (**) USB Gaming Keyboard: (accel) acceleration factor: 2.000
[    79.749] (**) USB Gaming Keyboard: (accel) acceleration threshold: 4
[    79.749] (II) config/udev: Adding input device USB Gaming Keyboard (/dev/input/mouse0)
[    79.749] (II) No input driver specified, ignoring this device.
[    79.749] (II) This device may have been added with another device file.
[    79.749] (II) config/udev: Adding input device USB Gaming Keyboard (/dev/input/event4)
[    79.749] (**) USB Gaming Keyboard: Applying InputClass "evdev keyboard catchall"
[    79.749] (II) Using input driver 'evdev' for 'USB Gaming Keyboard'
[    79.749] (**) USB Gaming Keyboard: always reports core events
[    79.749] (**) evdev: USB Gaming Keyboard: Device: "/dev/input/event4"
[    79.749] (--) evdev: USB Gaming Keyboard: Vendor 0x4d9 Product 0xa030
[    79.749] (--) evdev: USB Gaming Keyboard: Found keys
[    79.749] (II) evdev: USB Gaming Keyboard: Configuring as keyboard
[    79.749] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9.3/1-9.3:1.2/0003:04D9:A030.0004/input/input7/event4"
[    79.749] (II) XINPUT: Adding extended input device "USB Gaming Keyboard" (type: KEYBOARD, id 10)
[    79.749] (**) Option "xkb_rules" "evdev"
[    79.749] (**) Option "xkb_model" "pc105"
[    79.749] (**) Option "xkb_layout" "fr"
[    79.749] (**) Option "xkb_variant" "latin9"
[    79.750] (II) config/udev: Adding input device Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) (/dev/input/event5)
[    79.750] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Applying InputClass "evdev pointer catchall"
[    79.750] (II) Using input driver 'evdev' for 'Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)'
[    79.750] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): always reports core events
[    79.750] (**) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Device: "/dev/input/event5"
[    79.750] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Vendor 0x45e Product 0x47
[    79.750] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found 9 mouse buttons
[    79.750] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found scroll wheel(s)
[    79.750] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found relative axes
[    79.750] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found x and y relative axes
[    79.750] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Configuring as mouse
[    79.750] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Adding scrollwheel support
[    79.750] (**) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): YAxisMapping: buttons 4 and 5
[    79.750] (**) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    79.750] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9.4/1-9.4:1.0/0003:045E:0047.0005/input/input8/event5"
[    79.750] (II) XINPUT: Adding extended input device "Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)" (type: MOUSE, id 11)
[    79.750] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): initialized for relative axes.
[    79.750] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) keeping acceleration scheme 1
[    79.750] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) acceleration profile 0
[    79.750] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) acceleration factor: 2.000
[    79.750] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) acceleration threshold: 4
[    79.750] (II) config/udev: Adding input device Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) (/dev/input/mouse1)
[    79.750] (II) No input driver specified, ignoring this device.
[    79.750] (II) This device may have been added with another device file.
[    79.750] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event7)
[    79.750] (II) No input driver specified, ignoring this device.
[    79.750] (II) This device may have been added with another device file.
[    79.751] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
[    79.751] (II) No input driver specified, ignoring this device.
[    79.751] (II) This device may have been added with another device file.
[    79.751] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event9)
[    79.751] (II) No input driver specified, ignoring this device.
[    79.751] (II) This device may have been added with another device file.
[    79.751] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event10)
[    79.751] (II) No input driver specified, ignoring this device.
[    79.751] (II) This device may have been added with another device file.
[    79.751] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event11)
[    79.751] (II) No input driver specified, ignoring this device.
[    79.751] (II) This device may have been added with another device file.
[    79.751] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event12)
[    79.751] (II) No input driver specified, ignoring this device.
[    79.751] (II) This device may have been added with another device file.
[    79.751] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event6)
[    79.751] (II) No input driver specified, ignoring this device.
[    79.751] (II) This device may have been added with another device file.
[    79.751] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event13)
[    79.751] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[    79.751] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
[    79.751] (**) Eee PC WMI hotkeys: always reports core events
[    79.751] (**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event13"
[    79.751] (--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
[    79.752] (--) evdev: Eee PC WMI hotkeys: Found keys
[    79.752] (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
[    79.752] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input16/event13"
[    79.752] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 12)
[    79.752] (**) Option "xkb_rules" "evdev"
[    79.752] (**) Option "xkb_model" "pc105"
[    79.752] (**) Option "xkb_layout" "fr"
[    79.752] (**) Option "xkb_variant" "latin9"
[    79.754] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[    83.207] (II) evdev: Eee PC WMI hotkeys: Close
[    83.207] (II) UnloadModule: "evdev"
[    83.207] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Close
[    83.207] (II) UnloadModule: "evdev"
[    83.207] (II) evdev: USB Gaming Keyboard: Close
[    83.207] (II) UnloadModule: "evdev"
[    83.207] (II) evdev: USB Gaming Keyboard: Close
[    83.207] (II) UnloadModule: "evdev"
[    83.207] (II) evdev: USB Gaming Keyboard: Close
[    83.207] (II) UnloadModule: "evdev"
[    83.207] (II) evdev: Power Button: Close
[    83.207] (II) UnloadModule: "evdev"
[    83.207] (II) evdev: Power Button: Close
[    83.207] (II) UnloadModule: "evdev"
[    83.208] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[    83.208] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[    83.208] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[    83.208] (II) Server terminated successfully (0). Closing log file.

Hors ligne

#16 Le 22/08/2016, à 19:52

xabilon

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

C'est pas mieux... j'ai regardé sur le site de nVidia, le pilote 352 est bien compatible avec la GTX 970

On va essayer de voir ce qui a été mis à jour avant ton problème. Le log des install/désinstall/upgrade est /var/log/apt/history.log ; c'est classé par date et heure, et indique le type d'opération.

On y verra peut-être un peu plus clair. Sinon, essaye de réinstaller le pilote :

sudo apt-get install --reinstall nvidia-352

On regardera ensuite les messages du noyau, puisque c'est ce que les messages d'erreur suggèrent...

Pour passer un sujet en résolu : modifiez le premier message et ajoutez [Résolu] au titre.

Hors ligne

#17 Le 22/08/2016, à 20:45

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

xabilon a écrit :

C'est pas mieux... j'ai regardé sur le site de nVidia, le pilote 352 est bien compatible avec la GTX 970

Sinon, essaye de réinstaller le pilote :

sudo apt-get install --reinstall nvidia-352

Oui, j'ai monté la config hw et installé les bons drivers il y a plusieurs mois.
Avec la reinstall du driver nvidia, une fenetre texte me demande si je

Disable UEFI Secure Boot?

Un avis?

Hors ligne

#18 Le 22/08/2016, à 20:53

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Voici le log history au moment qui nous intéresse :

Start-Date: 2016-08-19  23:41:18
Commandline: apt-get upgrade
Upgrade: wine-devel-i386:i386 (1.9.14~ubuntu15.10.1, 1.9.16~ubuntu15.10.1), wine-devel-amd64:amd64 (1.9.14~ubuntu15.10.1, 1.9.16~ubuntu15.10.1), wine-devel:amd64 (1.9.14~ubuntu15.10.1, 1.9.16~ubuntu15.10.1), mysql-common:amd64 (5.6.30-0ubuntu0.15.10.1, 5.6.31-0ubuntu0.15.10.1), libmysqlclient18:i386 (5.6.30-0ubuntu0.15.10.1, 5.6.31-0ubuntu0.15.10.1), winehq-devel:amd64 (1.9.14~ubuntu15.10.1, 1.9.16~ubuntu15.10.1)
End-Date: 2016-08-19  23:41:27

Start-Date: 2016-08-20  00:14:52
Commandline: aptdaemon role='role-commit-packages' sender=':1.120'
Install: linux-image-extra-4.2.0-42-generic:amd64 (4.2.0-42.49, automatic), linux-image-4.2.0-42-generic:amd64 (4.2.0-42.49, automatic), linux-tools-4.2.0-42-generic:amd64 (4.2.0-42.49, automatic), mokutil:amd64 (0.3.0-0ubuntu3~15.10.1, automatic), linux-headers-4.2.0-42:amd64 (4.2.0-42.49, automatic), linux-tools-4.2.0-42:amd64 (4.2.0-42.49, automatic), linux-headers-4.2.0-42-generic:amd64 (4.2.0-42.49, automatic), linux-signed-image-4.2.0-42-generic:amd64 (4.2.0-42.49, automatic)
Upgrade: shim-signed:amd64 (1.11+0.8-0ubuntu2, 1.18~15.10.1+0.8-0ubuntu2), linux-headers-generic:amd64 (4.2.0.41.44, 4.2.0.42.45), linux-tools-virtual:amd64 (4.2.0.41.44, 4.2.0.42.45), linux-signed-generic:amd64 (4.2.0.41.44, 4.2.0.42.45), linux-signed-image-generic:amd64 (4.2.0.41.44, 4.2.0.42.45), linux-image-generic:amd64 (4.2.0.41.44, 4.2.0.42.45), linux-generic:amd64 (4.2.0.41.44, 4.2.0.42.45)
End-Date: 2016-08-20  00:16:20

Start-Date: 2016-08-20  02:03:19
Commandline: apt-get autoremove
Remove: linux-headers-4.2.0-36-generic:amd64 (4.2.0-36.42), linux-tools-4.2.0-35-generic:amd64 (4.2.0-35.40), linux-headers-4.2.0-25-generic:amd64 (4.2.0-25.30), linux-signed-image-4.2.0-36-generic:amd64 (4.2.0-36.42), libntdb1:amd64 (1.0-7), linux-signed-image-4.2.0-25-generic:amd64 (4.2.0-25.30), linux-image-extra-4.2.0-36-generic:amd64 (4.2.0-36.42), libhdb9-heimdal:amd64 (1.6~rc2+dfsg-10ubuntu1), linux-image-4.2.0-36-generic:amd64 (4.2.0-36.42), linux-image-extra-4.2.0-25-generic:amd64 (4.2.0-25.30), linux-image-4.2.0-25-generic:amd64 (4.2.0-25.30), linux-headers-4.2.0-25:amd64 (4.2.0-25.30), linux-headers-4.2.0-35:amd64 (4.2.0-35.40), linux-headers-4.2.0-36:amd64 (4.2.0-36.42), libkdc2-heimdal:amd64 (1.6~rc2+dfsg-10ubuntu1), linux-tools-4.2.0-36-generic:amd64 (4.2.0-36.42), linux-headers-4.2.0-35-generic:amd64 (4.2.0-35.40), linux-tools-4.2.0-25:amd64 (4.2.0-25.30), linux-tools-4.2.0-25-generic:amd64 (4.2.0-25.30), linux-tools-4.2.0-35:amd64 (4.2.0-35.40), linux-tools-4.2.0-36:amd64 (4.2.0-36.42), linux-signed-image-4.2.0-35-generic:amd64 (4.2.0-35.40), linux-image-extra-4.2.0-35-generic:amd64 (4.2.0-35.40), linux-image-4.2.0-35-generic:amd64 (4.2.0-35.40), python-ntdb:amd64 (1.0-7)
End-Date: 2016-08-20  02:04:35

Start-Date: 2016-08-21  10:30:01
Commandline: apt-get install --reinstall upstart
Reinstall: upstart:amd64 (1.13.2-0ubuntu16)
End-Date: 2016-08-21  10:30:03

Start-Date: 2016-08-21  11:52:17
Commandline: apt-get install ubuntu-gnome-desktop
Install: ubuntu-gnome-desktop:amd64 (0.43)
End-Date: 2016-08-21  11:52:18

Start-Date: 2016-08-21  11:58:40
Commandline: apt-get install elinks

Le problème pourrait venir de

sudo apt get autoremove

de 2h03 le 20/08/2016.

Dernière modification par taamer (Le 22/08/2016, à 20:54)

Hors ligne

#19 Le 22/08/2016, à 23:23

xabilon

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Entre le changement de noyau et le UEFI Secure Boot, on tient peut-être le problème...
Si tu n'as pas besoin du Secure Boot, il serait peut-être judicieux de le désactiver lors de la réinstallation du pilote nvidia.

Pour passer un sujet en résolu : modifiez le premier message et ajoutez [Résolu] au titre.

Hors ligne

#20 Le 23/08/2016, à 09:13

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

xabilon a écrit :

Entre le changement de noyau et le UEFI Secure Boot, on tient peut-être le problème...
Si tu n'as pas besoin du Secure Boot, il serait peut-être judicieux de le désactiver lors de la réinstallation du pilote nvidia.

J'ai poursuivi la procedure :
Disable, yes, mdp, re-mdp, puis la fenetre texte d'install s'arrete net avec le message:

Failed to request new MokSB state

Je reboot.

Hors ligne

#21 Le 23/08/2016, à 09:37

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Toujours pareil au boot.
Voici ce qui flashe par intermittence (pléonasme), probablement dans la tty7 :

[  OK  ] Created slice user-120.slice.
      Starting User Manager for UID 120...
[  OK  ] Started Session c1 of user gdm.
[  OK  ] Started User Manager for UID 120.
       Stopping User Manager for UID 120...
[  OK  ] Started LSB: start Samba daemons for t(ligne tronquee sur ma video)
[  OK  ] Stopped User Manager for UID 120.
[  OK  ] Removed slice user-120.slice.

Je AltFnF1 plusieurs fois oour reussir a me login et

 sudo service gdm stop

Puis un detail m'interpelle : au-dessus des lignes [  OK  ], je lis une activité inattendue :

fsck from util-linux 2.26.2
UbuntuAlex: clean, 302084/28409856 files, 37924(tronqué)

Je reboot et je reprends une video de l'ecran qui flashe pour voir si le fsck progresse.
/ est sur un SSD, je suis habitué à un boot rapide, et si....?
/home est sur un hdd de 8To, aucune envie qu'un fsck scanne tout ça.
La suite après reboot.

P.S. Je vais regarder qui a l'UID120, ma machine est monouser.

Hors ligne

#22 Le 23/08/2016, à 10:06

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

L'UID 120 est celui du scanner (imprimante basique EPSON que j'utilise avec SimpleScan). Coincidence peu evidente, j'avais debranché son USB peu avant l'autoremove.

Quand je reboot, le blink fait apparaitre les memes messages, et le fsck reste au meme niveau. Pas d'autre changement, toutes vos idées sont les bienvenues.

Hors ligne

#23 Le 23/08/2016, à 10:15

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Le fsck de /dev/sdc (SSD, /) est ok et semble se terminer au boot dans un temps très court. Pas d'investigation de ce côté-là.

Hors ligne

#24 Le 23/08/2016, à 10:48

taamer

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

Plus je regarde, plus cet autoremove m'interpelle, mais je n'ai pas les compétences pour analyser ce qui s'est passé dans le kernel.

alexandre@Martin-2:/etc/apt/apt.conf.d$ cat 01autoremove-kernels | more
// DO NOT EDIT! File autogenerated by /etc/kernel/postinst.d/apt-auto-removal
APT::NeverAutoRemove
{
   "^linux-image-4\.2\.0-36-generic$";
   "^linux-image-4\.2\.0-41-generic$";
   "^linux-image-4\.2\.0-42-generic$";
   "^linux-headers-4\.2\.0-36-generic$";
   "^linux-headers-4\.2\.0-41-generic$";
   "^linux-headers-4\.2\.0-42-generic$";
   "^linux-image-extra-4\.2\.0-36-generic$";
   "^linux-image-extra-4\.2\.0-41-generic$";
   "^linux-image-extra-4\.2\.0-42-generic$";
   "^linux-signed-image-4\.2\.0-36-generic$";
   "^linux-signed-image-4\.2\.0-41-generic$";
   "^linux-signed-image-4\.2\.0-42-generic$";
   "^kfreebsd-image-4\.2\.0-36-generic$";
   "^kfreebsd-image-4\.2\.0-41-generic$";
   "^kfreebsd-image-4\.2\.0-42-generic$";
   "^kfreebsd-headers-4\.2\.0-36-generic$";
   "^kfreebsd-headers-4\.2\.0-41-generic$";
   "^kfreebsd-headers-4\.2\.0-42-generic$";
   "^gnumach-image-4\.2\.0-36-generic$";
   "^gnumach-image-4\.2\.0-41-generic$";
   "^gnumach-image-4\.2\.0-42-generic$";
   "^.*-modules-4\.2\.0-36-generic$";
   "^.*-modules-4\.2\.0-41-generic$";
   "^.*-modules-4\.2\.0-42-generic$";
   "^.*-kernel-4\.2\.0-36-generic$";
   "^.*-kernel-4\.2\.0-41-generic$";
   "^.*-kernel-4\.2\.0-42-generic$";
   "^linux-backports-modules-.*-4\.2\.0-36-generic$";
   "^linux-backports-modules-.*-4\.2\.0-41-generic$";
   "^linux-backports-modules-.*-4\.2\.0-42-generic$";
   "^linux-tools-4\.2\.0-36-generic$";
   "^linux-tools-4\.2\.0-41-generic$";
   "^linux-tools-4\.2\.0-42-generic$";
};

Hors ligne

#25 Le 23/08/2016, à 14:37

xabilon

Re : [Résolu] [15.10] Plus de GUI après update standard, diagnostic?

L'autoremove désinstalle les paquets installés automatiquement en dépendance d'un autre paquet, lorsque ce dernier n'est plus installé ou n'a plus besoin de ces dépendances.
Concernant les noyaux, l'effet de l'autoremove-kernels consiste à désinstaller les noyaux plus anciens, sauf les 2 plus récents.

Le 20/08 à 00h14 il y a eu une mise à jour des métapaquets du noyau (+ headers, extra, signed...), ce qui a entraîné l'installation d'un nouveau noyau : le numéro 4.2.0-42
Puis à 02h03 il y a eu un apt-get autoremove, qui a désinstallé un noyau devenu trop ancien : le 4.2.0-36

Il doit donc te rester 2 noyaux installés. Au démarrage, dans le menu Grub, va dans "Options avancées" et teste le démarrage avec le noyau précédent.

Il me semble que ça tourne effectivement autour du UEFI Secure Boot et de la compatibilité des pilotes nvidia avec les noyaux signed. J'ai trouvé ce sujet : https://askubuntu.com/questions/760934/ … ics/763493
Ça concerne Ubuntu 16.04, mais c'est bien un problème avec nVidia et le Secure Boot, avec les mêmes symptômes que toi.

Pour passer un sujet en résolu : modifiez le premier message et ajoutez [Résolu] au titre.

Hors ligne

Pages : 1 2