Error failed au boot
vues dans /var/log/boot.log
Système et matériels / Installation et configuration
kalagani Membre non connecté
-
- Voir le profil du membre kalagani
- Inscrit le : 10/03/2012
- Groupes :
essayant de résoudre ce pb
Freeze MGA7 au bout de quelques heures sous Plasma et pas sous iceWM
je fais suite à cet autre sujet à propos d'erreur au boot
Error failed au boot Quelques erreurs "failed" lors du démarrage
dès fois que ce pb de gel PC ait un rapport avec ces erreurs de démarrage.
Ainsi dans le fichier /var/log/boot.log j'ai quasi-systématiquement à tous les démarrages les erreurs:
Code BASH :
... [FAILED] Failed to start Setup Virtual Console. [FAILED] Failed to start Show Plymouth Boot Screen. ...
Avec pour le détail pour chacun
Code BASH :
systemctl status systemd-vconsole-setup.service ● systemd-vconsole-setup.service - Setup Virtual Console Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static; vendor preset: disabled) Active: failed (Result: start-limit-hit) since Thu 2020-09-10 09:49:25 CEST; 6h ago Docs: man:systemd-vconsole-setup.service(8) man:vconsole.conf(5) Process: 746 ExecStart=/usr/lib/systemd/systemd-vconsole-setup (code=exited, status=0/SUCCESS) Main PID: 746 (code=exited, status=0/SUCCESS) sept. 10 09:49:25 localhost.localdomain systemd[1]: Started Setup Virtual Console. sept. 10 09:49:25 localhost.localdomain systemd[1]: Starting Setup Virtual Console... sept. 10 09:49:25 localhost.localdomain systemd[1]: systemd-vconsole-setup.service: Succeeded. sept. 10 09:49:25 localhost.localdomain systemd[1]: Started Setup Virtual Console. sept. 10 09:49:25 localhost.localdomain systemd[1]: systemd-vconsole-setup.service: Start request repeated too quickly. sept. 10 09:49:25 localhost.localdomain systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 10 09:49:25 localhost.localdomain systemd[1]: Failed to start Setup Virtual Console. sept. 10 09:49:25 localhost.localdomain systemd[1]: systemd-vconsole-setup.service: Start request repeated too quickly. sept. 10 09:49:25 localhost.localdomain systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 10 09:49:25 localhost.localdomain systemd[1]: Failed to start Setup Virtual Console.
Code BASH :
[status plymouth-start.service ● plymouth-start.service - Show Plymouth Boot Screen Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static; vendor preset: disabled) Active: failed (Result: start-limit-hit) since Thu 2020-09-10 09:49:25 CEST; 6h ago Process: 760 ExecStart=/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session (code=exited, status=0/SUCCESS) Process: 763 ExecStartPost=/bin/plymouth show-splash (code=exited, status=0/SUCCESS) sept. 10 09:49:25 localhost.localdomain systemd[1]: Started Show Plymouth Boot Screen. sept. 10 09:49:25 localhost.localdomain systemd[1]: Starting Show Plymouth Boot Screen... sept. 10 09:49:25 localhost.localdomain systemd[1]: plymouth-start.service: Succeeded. sept. 10 09:49:25 localhost.localdomain systemd[1]: Started Show Plymouth Boot Screen. sept. 10 09:49:25 localhost.localdomain systemd[1]: Starting Show Plymouth Boot Screen... sept. 10 09:49:25 localhost.localdomain systemd[1]: plymouth-start.service: Succeeded. sept. 10 09:49:25 localhost.localdomain systemd[1]: Started Show Plymouth Boot Screen. sept. 10 09:49:25 localhost.localdomain systemd[1]: plymouth-start.service: Start request repeated too quickly. sept. 10 09:49:25 localhost.localdomain systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 10 09:49:25 localhost.localdomain systemd[1]: Failed to start Show Plymouth Boot Screen.
Une idée?
Édité par kalagani Le 10/09/2020 à 16h55
steven Membre non connecté
-
- Voir le profil du membre steven
- Inscrit le : 18/05/2018
kalagani :
Hello,
Une idée?
Une idée?
hello
Oui ! reinstall tout bien propre...
(pasque gel + boot + ????)
et demain, ce sera quoi ???
c'est comme une voiture ....
une piece lache, tu la change, est ca en est une autre, puit une autre, puis....
Alors change le moteur, remet lui en un tout neuf !
reinstall !
No Comment ... 
Merci de ne pas 'rebondir' sur mes post's Censor => 2025
Merci de ne pas 'rebondir' sur mes post's Censor => 2025
nic80 Membre non connecté
-
- Voir le profil du membre nic80
- Inscrit le : 06/08/2018
- Groupes :
-
Modérateur
Les messages des 2 unités indique qu' elles sont failed, parce qu' elle essayent de redémarrer trop rapidement un trop grand nombre de fois.
Après je ne sais pas ce qu' est le setup virtual console (je soupçonnes toutefois que ce sont peut être les consoles que l' on atteint par ctrl+alt+fx ).
Pour Plymouth screen, c' est il me semble l' écran avec les bulles.
kalagani Membre non connecté
-
- Voir le profil du membre kalagani
- Inscrit le : 10/03/2012
- Groupes :
steven :
Alors change le moteur, remet lui en un tout neuf !
reinstall !
reinstall !
J'ai appliqué un peu ta méthode de l'enclume pour écraser un moustique, soit une réinstall avec formattage / et /home :+)
Mais toujours ces erreurs:
Caché :
Et cela le fait aussi sur un autre PC MGA7!!!Code BASH :
journalctl |grep -i "failed to start s" sept. 12 17:49:05 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 12 17:49:06 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 12 17:49:06 localhost systemd[1]: Failed to start Show Plymouth Boot Screen. sept. 13 09:50:54 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 13 09:50:55 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 13 16:32:42 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 13 16:32:43 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 14 09:38:16 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 14 09:38:16 localhost systemd[1]: Failed to start Show Plymouth Boot Screen. sept. 14 09:38:16 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 14 09:38:16 localhost systemd[1]: Failed to start Show Plymouth Boot Screen. sept. 14 09:38:17 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 14 09:38:17 localhost systemd[1]: Failed to start Show Plymouth Boot Screen. sept. 14 11:30:21 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 14 11:30:21 localhost systemd[1]: Failed to start Show Plymouth Boot Screen. sept. 14 11:30:23 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 14 11:30:23 localhost systemd[1]: Failed to start Show Plymouth Boot Screen. sept. 15 08:23:43 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 15 08:23:43 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 15 08:23:43 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 15 08:23:43 localhost systemd[1]: Failed to start Show Plymouth Boot Screen. sept. 15 08:23:43 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 15 08:23:43 localhost systemd[1]: Failed to start Show Plymouth Boot Screen. sept. 16 09:11:57 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 16 09:54:36 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 16 16:07:39 localhost systemd[3535]: Failed to start Sound Service. sept. 17 09:17:21 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 17 09:17:22 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 18 09:14:43 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 18 09:14:43 localhost systemd[1]: Failed to start Show Plymouth Boot Screen. sept. 18 09:14:43 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 18 09:14:43 localhost systemd[1]: Failed to start Show Plymouth Boot Screen. sept. 18 09:14:43 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 18 09:14:43 localhost systemd[1]: Failed to start Show Plymouth Boot Screen.
As tu regardé sur le tien si tu avais ces erreurs avec un (journalctl |grep -i "failed to start s")?
nic80 :
Les messages des 2 unités indique qu' elles sont failed, parce qu' elle essayent de redémarrer trop rapidement un trop grand nombre de fois.
Il semblerait, mais au final les 2 services en question sont quand même en faute
Code BASH :
systemctl |grep -i failed ● plymouth-start.service loaded failed failed Show Plymouth Boot Screen ● systemd-vconsole-setup.service loaded failed failed Setup Virtual Console
ce qui pourrait cacher ou engendrer d'autres pb!
Édité par kalagani Le 18/09/2020 à 10h02
Yuusha Membre non connecté
-
- Voir le profil du membre Yuusha
- Inscrit le : 04/07/2017
- Groupes :
-
Modérateur
-
Administrateur
-
Forgeron
kalagani :
sept. 12 17:49:05 localhost systemd[1]: Failed to start Setup Virtual Console.
D'après ce forum c'est un problème de systemd. Voici un rapport de bogue donnant des éléments pour corriger ce problème.
On trouve aussi une méthode pour le régler sur le forum de Arch. Une autre méthode sur l'ancien ask de Fedora.
kalagani :
sept. 12 17:49:06 localhost systemd[1]: Failed to start Show Plymouth Boot Screen.
Il me semble qu'il s'agit de l'écran avec le chaudron et le bulles. Il faudrait essayer de supprimer les options splash et quiet de la ligne de boot. Pour ne pas prendre de risque, le faire d'abord en éditant la ligne au démarrage. Il faut pour cela presser la touche e sur l'écran du grub. Si ça fonctionne, on peut utiliser le CCM pour modifier cette option définitivement.
Papoteur Membre non connecté
-
- Voir le profil du membre Papoteur
- Inscrit le : 03/10/2011
- Groupes :
-
Modérateur
-
Équipe Mageia
-
Administrateur
-
Forgeron
Je pense que les deux problèmes sont liés et sans grande conséquence. Il se peut aussi que ce soit la même cause que celle des freezes.
kalagani Membre non connecté
-
- Voir le profil du membre kalagani
- Inscrit le : 10/03/2012
- Groupes :
Papoteur :
Bonjour,
Je pense que les deux problèmes sont liés et sans grande conséquence. Il se peut aussi que ce soit la même cause que celle des freezes.
Je pense que les deux problèmes sont liés et sans grande conséquence. Il se peut aussi que ce soit la même cause que celle des freezes.
j'avais tendance à penser comme ta 1ère partie de phrase...d'autant que ce n'est pas systématique à chaque boot,
mais à lire le fil posté par
Yuusha :
D'après ce forum c'est un problème de systemd.
et notamment ces 2 posts
1) I can see that the nvidia driver is loaded slightly differently in the case systemd-vconsole-setup.service fails...
2) No or few failures on a machine with nouveau and repeated errors
il y a de quoi faire un rapprochement...
Détail d'un même boot (journalctl -u systemd-vconsole-setup -u plymouth-start):
Caché :
Code BASH :
-- Reboot -- sept. 18 09:14:41 localhost systemd-vconsole-setup[547]: KD_FONT_OP_GET failed while trying to get the font metadata: Argument invalide sept. 18 09:14:41 localhost systemd-vconsole-setup[547]: Fonts will not be copied to remaining consoles sept. 18 09:14:41 localhost systemd[1]: systemd-vconsole-setup.service: Succeeded. sept. 18 09:14:41 localhost systemd[1]: Started Setup Virtual Console. sept. 18 09:14:42 localhost systemd[1]: Starting Show Plymouth Boot Screen... sept. 18 09:14:42 localhost systemd[1]: plymouth-start.service: Succeeded. sept. 18 09:14:42 localhost systemd[1]: Started Show Plymouth Boot Screen. sept. 18 09:14:42 localhost systemd[1]: Starting Setup Virtual Console... sept. 18 09:14:42 localhost systemd-vconsole-setup[647]: KD_FONT_OP_GET failed while trying to get the font metadata: Argument invalide sept. 18 09:14:42 localhost systemd-vconsole-setup[647]: Fonts will not be copied to remaining consoles sept. 18 09:14:42 localhost systemd[1]: systemd-vconsole-setup.service: Succeeded. sept. 18 09:14:42 localhost systemd[1]: Started Setup Virtual Console. sept. 18 09:14:42 localhost systemd[1]: Starting Show Plymouth Boot Screen... sept. 18 09:14:42 localhost systemd[1]: plymouth-start.service: Succeeded. sept. 18 09:14:42 localhost systemd[1]: Started Show Plymouth Boot Screen. sept. 18 09:14:43 localhost systemd[1]: Starting Setup Virtual Console... sept. 18 09:14:43 localhost systemd-vconsole-setup[657]: KD_FONT_OP_GET failed while trying to get the font metadata: Argument invalide sept. 18 09:14:43 localhost systemd-vconsole-setup[657]: Fonts will not be copied to remaining consoles sept. 18 09:14:43 localhost systemd[1]: systemd-vconsole-setup.service: Succeeded. sept. 18 09:14:43 localhost systemd[1]: Started Setup Virtual Console. sept. 18 09:14:43 localhost systemd[1]: Starting Show Plymouth Boot Screen... sept. 18 09:14:43 localhost systemd[1]: plymouth-start.service: Succeeded. sept. 18 09:14:43 localhost systemd[1]: Started Show Plymouth Boot Screen. sept. 18 09:14:43 localhost systemd[1]: Starting Setup Virtual Console... sept. 18 09:14:43 localhost systemd-vconsole-setup[669]: KD_FONT_OP_GET failed while trying to get the font metadata: Argument invalide sept. 18 09:14:43 localhost systemd-vconsole-setup[669]: Fonts will not be copied to remaining consoles sept. 18 09:14:43 localhost systemd[1]: systemd-vconsole-setup.service: Succeeded. sept. 18 09:14:43 localhost systemd[1]: Started Setup Virtual Console. sept. 18 09:14:43 localhost systemd[1]: Starting Show Plymouth Boot Screen... sept. 18 09:14:43 localhost systemd[1]: plymouth-start.service: Succeeded. sept. 18 09:14:43 localhost systemd[1]: Started Show Plymouth Boot Screen. sept. 18 09:14:43 localhost systemd[1]: Starting Setup Virtual Console... sept. 18 09:14:43 localhost systemd-vconsole-setup[680]: KD_FONT_OP_GET failed while trying to get the font metadata: Argument invalide sept. 18 09:14:43 localhost systemd-vconsole-setup[680]: Fonts will not be copied to remaining consoles sept. 18 09:14:43 localhost systemd[1]: systemd-vconsole-setup.service: Succeeded. sept. 18 09:14:43 localhost systemd[1]: Started Setup Virtual Console. sept. 18 09:14:43 localhost systemd[1]: Starting Show Plymouth Boot Screen... sept. 18 09:14:43 localhost systemd[1]: plymouth-start.service: Succeeded. sept. 18 09:14:43 localhost systemd[1]: Started Show Plymouth Boot Screen. sept. 18 09:14:43 localhost systemd[1]: systemd-vconsole-setup.service: Start request repeated too quickly. sept. 18 09:14:43 localhost systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 18 09:14:43 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 18 09:14:43 localhost systemd[1]: plymouth-start.service: Start request repeated too quickly. sept. 18 09:14:43 localhost systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 18 09:14:43 localhost systemd[1]: Failed to start Show Plymouth Boot Screen. sept. 18 09:14:43 localhost systemd[1]: systemd-vconsole-setup.service: Start request repeated too quickly. sept. 18 09:14:43 localhost systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 18 09:14:43 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 18 09:14:43 localhost systemd[1]: plymouth-start.service: Start request repeated too quickly. sept. 18 09:14:43 localhost systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 18 09:14:43 localhost systemd[1]: Failed to start Show Plymouth Boot Screen. sept. 18 09:14:43 localhost systemd[1]: systemd-vconsole-setup.service: Start request repeated too quickly. sept. 18 09:14:43 localhost systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 18 09:14:43 localhost systemd[1]: Failed to start Setup Virtual Console. sept. 18 09:14:43 localhost systemd[1]: plymouth-start.service: Start request repeated too quickly. sept. 18 09:14:43 localhost systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 18 09:14:43 localhost systemd[1]: Failed to start Show Plymouth Boot Screen.
Plusieurs lancements des systemd-vconsole-setup.service et plymouth-start.service
avec succès 5 fois malgré un pb de fontes, puis 3 échecs Start request repeated too quickly
Édité par kalagani Le 21/09/2020 à 16h37
kalagani Membre non connecté
-
- Voir le profil du membre kalagani
- Inscrit le : 10/03/2012
- Groupes :
j'ai commuté le PC du pilote Nvidia au pilote Nouveau et avec ce dernier plus de systemd-vconsole-setup et plymouth-start en faute, selon l'analyse que je fais sur le journalctl de tous les boots...du 11 septembre à aujourd'hui.
Ceci avec la commande que je crois discriminante:
Code BASH :
journalctl --no-hostname|grep -E "Reboot --|Command line: BOOT_IMAGE|kscreen.kded|systemd-vconsole-setup.service: Failed|plymouth-start.service: Failed|0000:18:00.0: NVIDIA G80|nvidia340 "
--no-hostname: juste pour diminuer la longueur de ligne affichée en enlevant le nom du PC
Reboot: pour séparer les boots
Command line: pour afficher la version de kernel
kscreen.kded: détermine que l'interface est Plasma, si rien c'est que c'est XFCE
systemd-vconsole-setup.service: Failed|plymouth-start.service: Failed: donne les services quand ils sont en faute
0000:18:00.0: NVIDIA G80|nvidia340 : détermine que l'interface est Nouveau ou Nvidia.
Et quand les 2 services sont en erreurs, uniquement avec le pilote Nvidia, il semblerait que ce soit parce que lancé trop tard, ou les services trop tôt,
ceci quelquesoit la version de kernel ( 5.1.14-desktop-1.mga7 ou 5.7.19-desktop-1.mga7) , du pilote (340.107-9.mga7.nonfree ou 340.108-7.mga7.nonfree) ou d'interface graphique Plasma ou XFCE...
Le log:
Caché :
Code BASH :
sept. 11 17:30:51 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 11 17:30:57 dkms-autorebuild.sh[793]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 11 17:46:07 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 11 17:46:13 dkms-autorebuild.sh[768]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 11 18:17:41 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro failsafe sept. 11 18:17:42 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- sept. 11 19:31:55 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro failsafe sept. 11 19:31:55 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- sept. 11 19:48:31 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 11 19:48:37 dkms-autorebuild.sh[782]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 12 08:51:01 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro failsafe sept. 12 08:51:01 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) sept. 12 09:08:53 dkms-autorebuild.sh[1439]: nvidia340 (340.107-9.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 12 09:22:25 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 12 09:22:31 dkms-autorebuild.sh[763]: nvidia340 (340.107-9.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 12 10:16:45 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 12 10:16:51 dkms-autorebuild.sh[785]: nvidia340 (340.107-9.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 12 12:46:52 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 12 12:46:57 dkms-autorebuild.sh[768]: nvidia340 (340.107-9.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 12 17:49:01 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 12 17:49:05 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 12 17:49:06 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 12 17:49:06 systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 12 17:49:07 dkms-autorebuild.sh[777]: nvidia340 (340.107-9.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 13 09:50:51 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 13 09:50:54 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 13 09:50:55 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 13 09:50:57 dkms-autorebuild.sh[804]: nvidia340 (340.107-9.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 13 10:23:59 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 13 10:24:05 dkms-autorebuild.sh[782]: nvidia340 (340.107-9.mga7.nonfree): Already installed on this kernel. sept. 13 10:24:49 kdeinit5[4860]: kscreen.kded: PowerDevil SuspendSession action not available! -- Reboot -- sept. 13 16:32:39 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 13 16:32:42 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 13 16:32:43 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 13 16:32:44 dkms-autorebuild.sh[799]: nvidia340 (340.107-9.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 13 16:43:19 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 13 16:43:25 dkms-autorebuild.sh[785]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 13 16:50:25 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 13 16:50:31 dkms-autorebuild.sh[789]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 14 09:38:12 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 14 09:38:16 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 14 09:38:16 systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 14 09:38:16 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 14 09:38:16 systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 14 09:38:17 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 14 09:38:17 systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 14 09:38:19 dkms-autorebuild.sh[794]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. sept. 14 09:39:08 kdeinit5[4774]: kscreen.kded: PowerDevil SuspendSession action not available! -- Reboot -- sept. 14 11:30:19 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 14 11:30:21 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 14 11:30:21 systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 14 11:30:23 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 14 11:30:23 systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 14 11:30:25 dkms-autorebuild.sh[798]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 14 12:29:23 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 14 12:29:28 dkms-autorebuild.sh[746]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. sept. 14 12:30:07 kdeinit5[4710]: kscreen.kded: PowerDevil SuspendSession action not available! sept. 14 19:32:33 kdeinit5[9469]: kscreen.kded: PowerDevil SuspendSession action not available! sept. 14 19:32:58 kdeinit5[10953]: kscreen.kded: PowerDevil SuspendSession action not available! -- Reboot -- sept. 15 08:23:41 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 15 08:23:43 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 15 08:23:43 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 15 08:23:43 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 15 08:23:43 systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 15 08:23:43 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 15 08:23:43 systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 15 08:23:46 dkms-autorebuild.sh[753]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 16 09:11:55 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 16 09:11:57 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 16 09:11:59 dkms-autorebuild.sh[764]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 16 09:54:33 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 16 09:54:36 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 16 09:54:39 dkms-autorebuild.sh[769]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 16 10:11:27 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 16 10:11:32 dkms-autorebuild.sh[758]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 16 13:03:07 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 16 13:03:12 dkms-autorebuild.sh[782]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 17 09:17:19 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 17 09:17:21 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 17 09:17:22 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 17 09:17:25 dkms-autorebuild.sh[767]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 17 17:37:35 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 17 17:37:39 dkms-autorebuild.sh[764]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 17 18:33:36 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 17 18:33:42 dkms-autorebuild.sh[738]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 18 09:14:41 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 18 09:14:43 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 18 09:14:43 systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 18 09:14:43 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 18 09:14:43 systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 18 09:14:43 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 18 09:14:43 systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 18 09:14:46 dkms-autorebuild.sh[767]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 19 09:41:41 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 19 09:41:46 dkms-autorebuild.sh[759]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 20 09:17:10 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 20 09:17:15 dkms-autorebuild.sh[757]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 21 09:34:07 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 21 09:34:14 dkms-autorebuild.sh[828]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 22 09:22:57 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro nokmsboot splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 22 09:23:03 dkms-autorebuild.sh[816]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. sept. 22 09:30:41 drakx11[26275]: those kernel module packages can be installed: dkms-nvidia340 dkms-nvidia340 dkms-nvidia340 dkms-nvidia340 dkms-nvidia340 dkms-nvidia340 dkms-nvidia340 -- Reboot -- sept. 22 09:33:46 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 22 09:33:46 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) sept. 22 09:33:51 dkms-autorebuild.sh[821]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 22 10:04:09 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 22 10:04:09 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) sept. 22 10:04:14 dkms-autorebuild.sh[832]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. sept. 22 10:04:46 kdeinit5[3890]: kscreen.kded: PowerDevil SuspendSession action not available! -- Reboot -- sept. 22 10:07:20 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 22 10:07:20 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) sept. 22 10:07:23 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 22 10:07:23 systemd[1]: systemd-vconsole-setup.service: Failed with result 'start-limit-hit'. sept. 22 10:07:23 systemd[1]: plymouth-start.service: Failed with result 'start-limit-hit'. sept. 22 10:07:25 dkms-autorebuild.sh[831]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 22 17:07:24 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 22 17:07:24 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) sept. 22 17:07:29 dkms-autorebuild.sh[802]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 23 09:53:08 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 23 09:53:08 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) sept. 23 09:53:14 dkms-autorebuild.sh[812]: nvidia340 (340.108-7.mga7.nonfree): Already installed on this kernel. -- Reboot -- sept. 23 11:15:46 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 23 11:15:46 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- sept. 24 09:28:53 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 24 09:28:53 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- sept. 24 09:55:56 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 24 09:55:57 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- sept. 24 11:15:04 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 24 11:15:04 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- sept. 25 08:09:22 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 25 08:09:22 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- sept. 26 09:58:43 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 26 09:58:43 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- sept. 27 09:58:11 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 27 09:58:11 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- sept. 27 12:15:01 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.1.14-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 27 12:15:01 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) sept. 27 17:51:24 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- sept. 27 19:20:14 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 27 19:20:14 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- sept. 28 09:16:13 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 28 09:16:13 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- sept. 28 11:03:56 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 28 11:03:56 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) sept. 28 11:04:52 kdeinit5[5470]: kscreen.kded: PowerDevil SuspendSession action not available! -- Reboot -- sept. 29 11:18:34 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 29 11:18:34 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) sept. 29 11:19:53 kdeinit5[7491]: kscreen.kded: PowerDevil SuspendSession action not available! -- Reboot -- sept. 30 08:50:59 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 30 08:50:59 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) sept. 30 08:53:31 kdeinit5[14109]: kscreen.kded: PowerDevil SuspendSession action not available! -- Reboot -- sept. 30 10:23:59 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 sept. 30 10:23:59 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) sept. 30 10:24:43 kdeinit5[5349]: kscreen.kded: PowerDevil SuspendSession action not available! -- Reboot -- oct. 01 08:01:07 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 oct. 01 08:01:07 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- oct. 02 09:11:15 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 oct. 02 09:11:15 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) oct. 02 09:14:04 kdeinit5[14039]: kscreen.kded: PowerDevil SuspendSession action not available! -- Reboot -- oct. 02 10:54:21 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 oct. 02 10:54:21 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) oct. 02 11:00:40 kdeinit5[31852]: kscreen.kded: PowerDevil SuspendSession action not available! oct. 02 11:00:59 kdeinit5[1558]: kscreen.kded: PowerDevil SuspendSession action not available! -- Reboot -- oct. 03 09:58:24 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 oct. 03 09:58:24 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- oct. 04 09:17:45 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 oct. 04 09:17:45 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2) -- Reboot -- oct. 05 09:14:15 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.7.19-desktop-1.mga7 root=UUID=8ebeda33-9710-49a7-93a4-809d13e2809f ro splash quiet noiswmd resume=UUID=2fdb0460-b082-496e-b748-e904514ac886 audit=0 vga=791 oct. 05 09:14:15 kernel: nouveau 0000:18:00.0: NVIDIA G80 (450d00a2)
Édité par kalagani Le 05/10/2020 à 19h52
Papoteur Membre non connecté
-
- Voir le profil du membre Papoteur
- Inscrit le : 03/10/2011
- Groupes :
-
Modérateur
-
Équipe Mageia
-
Administrateur
-
Forgeron
Quel est le contenu de /etc/vconsole.conf ?
Et as-tu essayé ça :
Yuusha :
Il faudrait essayer de supprimer les options splash et quiet de la ligne de boot.
Édité par Papoteur Le 06/10/2020 à 09h43
kalagani Membre non connecté
-
- Voir le profil du membre kalagani
- Inscrit le : 10/03/2012
- Groupes :
Code BASH :
more /etc/vconsole.conf FONT=lat0-16 KEYMAP=fr-latin1
Comme je l'écris plus haut, je n'ai plus ces 2 services en faute depuis le passage au pilote Nouveau
ceci avec les splash et quiet toujours sur la ligne de boot, lesquels je n'ai pas essayé de supprimer!
Papoteur Membre non connecté
-
- Voir le profil du membre Papoteur
- Inscrit le : 03/10/2011
- Groupes :
-
Modérateur
-
Équipe Mageia
-
Administrateur
-
Forgeron
https://forums.opensuse.org/showthread.php/533663-Failed-to-start-Setup-Virtual-Console/page2
dantou Membre non connecté
-
- Voir le profil du membre dantou
- Inscrit le : 04/01/2011
- Groupes :
Voici des années que j'ai ces 2 messages sur mon écran. Je crois bien les avoir déjà eu quand j'étais encore sous Mandriva (donc avant le 1er jet de Mageia !o) !
A l'époque, j'avais posé la question de savoir ce que c'était mais n'avais pas eu de retour, ce qui ne m'avait pas affolé, car le PC démarrait quand même.
J'ai toujours ces messages au démarrage, ainsi que sur le portable actuel, comme le précédent qui m'a été volé. Et tous démarraient.
Evidemment, j'ai des problèmes de freeze, de temps à autre, et plus d'arrêt pur et simple de Digikam ou Firefox, et j'ai toujours pensé qu'il s'agissait d'un problème de ma carte graphique (Radeon HD 4670). Par contre, le problème s'est bien espacé dans le temps sur le portable, car je n'entends plus mon épouse exploser quand elle perd son travail en cours !
Je ne souviens plus si je suis sous Nouveau ou pas.
Répondre
Vous n'êtes pas autorisé à écrire dans cette catégorie