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

#1 Le 30/09/2023, à 18:18

Raisin54340

Demarrage capricieux aprés installation dual boot

Bonjour,
Je viens de refaire une installation complète en dual boot avec windows 11 et j'ai un souci lors du démarrage.
Si je choisi Ubuntu j'ai cet affichage et le PC charge mais ne démarre pas.
https://zupimages.net/up/23/39/7yq8.jpg

Par contre si je choisi le démarrage avancé et que je sélectionne Ubuntu Linux 5.19.0.32 le PC démarre et je peux ouvrir ma session
https://zupimages.net/up/23/39/z5cy.jpg

C'est donc Ubuntu Linux 6.2.0.33 qui bloque au démarrage !

Merci de votre aide car je suis débutant sur ce système et j'aimerais vraiment profiter de celui-ci.

Cdt.


Modération : merci d'utiliser des images de petite taille (300x300) ou des miniatures pointant sur ces images.

Dernière modification par cqfd93 (Le 30/09/2023, à 18:33)

Hors ligne

#2 Le 30/09/2023, à 18:33

xubu1957

Re : Demarrage capricieux aprés installation dual boot

Bonjour,

Tu peux fournir,en te servant du Retour utilisable de commande :

lspci -vnn | grep -A 12 '\''[030[02]\]' | grep -Ei "vga|3d|display|kernel"
dpkg -l | grep -v ^ii

et :

echo $XDG_SESSION_TYPE

pour voir si c'est Wayland ou x11 ?

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] 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

En ligne

#3 Le 30/09/2023, à 18:49

Raisin54340

Re : Demarrage capricieux aprés installation dual boot

Bonjour,

Voici:

2b:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104 [GeForce RTX 3060 Ti Lite Hash Rate] [10de:2489] (rev a1) (prog-if 00 [VGA controller])
    Kernel driver in use: nouveau
    Kernel modules: nvidiafb, nouveau

Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom                                        Version                                 Architecture Description
+++-==========================================-=======================================-============-================================================================================

wayland

Hors ligne

#4 Le 30/09/2023, à 18:56

xubu1957

Re : Demarrage capricieux aprés installation dual boot

Pour ajouter toi-même les balises code (à la place des balises de citation) à ton message #3 :

  • Cliquer sur  le lien « Modifier » en bas à droite du message

  • Sélectionner le texte

  • Cliquer sur le <> de l'éditeur de message

moko138 a écrit :

1) Les balises-code sont les < > (crochets bleus) de la barre de mise en forme.
Balisesmoko138.jpg
_ _ _

3) /!\  Si vous avez plusieurs retours à donner, séparez-les bien (toujours pour la lisibilité) :

comme
cela.
2b:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104 [GeForce RTX 3060 Ti Lite Hash Rate] [10de:2489] (rev a1) (prog-if 00 [VGA controller])
    Kernel driver in use: nouveau
    Kernel modules: nvidiafb, nouveau
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
||/ Nom                                        Version                                 Architecture Description
+++-==========================================-=======================================-============-================================================================================
wayland

Montre :

ubuntu-drivers devices

Lecture conseillée > memento des balises code.

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] 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

En ligne

#5 Le 30/09/2023, à 19:03

Raisin54340

Re : Demarrage capricieux aprés installation dual boot

Voila:

== /sys/devices/pci0000:00/0000:00:03.1/0000:2b:00.0 ==
modalias : pci:v000010DEd00002489sv00001462sd0000C972bc03sc00i00
vendor   : NVIDIA Corporation
model    : GA104 [GeForce RTX 3060 Ti Lite Hash Rate]
driver   : nvidia-driver-470 - distro non-free
driver   : nvidia-driver-535 - distro non-free
driver   : nvidia-driver-525-open - distro non-free
driver   : nvidia-driver-525-server - distro non-free
driver   : nvidia-driver-470-server - distro non-free
driver   : nvidia-driver-525 - distro non-free
driver   : nvidia-driver-535-server - distro non-free
driver   : nvidia-driver-535-server-open - distro non-free recommended
driver   : nvidia-driver-535-open - distro non-free
driver   : xserver-xorg-video-nouveau - distro free builtin

== /sys/devices/pci0000:00/0000:00:01.2/0000:02:00.2/0000:03:07.0/0000:05:00.0 ==
modalias : pci:v000014E4d000043A0sv000014E4sd00000619bc02sc80i00
vendor   : Broadcom Inc. and subsidiaries
model    : BCM4360 802.11ac Wireless Network Adapter
driver   : bcmwl-kernel-source - distro non-free

Hors ligne

#6 Le 30/09/2023, à 19:07

xubu1957

Re : Demarrage capricieux aprés installation dual boot

La carte :

GA104 [GeForce RTX 3060 Ti Lite Hash Rate]

est mentionnée dans askubuntu.com/questions/1480763/22-04-2-driver-dependent-apps-crash-even-on-fresh-install.

Ou forums.developer.nvidia.com/t/geforce-rtx-3060-lhr-not-working-neither-with-ubuntu-20-04-or-ubuntu-22-04/237168

Il faudrait des avis d'autres aidants.

Fournis les noyaux présents :

echo; dpkg -l | awk '!/^rc/ && / linux-(c|g|h|i|lo|m|si|t)/{print $1,$2,$3,$4 | "sort -k3V | column -t"}' ; echo -e "\nNoyau courant : $(uname -mr)"

Dernière modification par xubu1957 (Le 30/09/2023, à 19:11)

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] 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

En ligne

#7 Le 30/09/2023, à 19:12

Raisin54340

Re : Demarrage capricieux aprés installation dual boot

Ok, merci de ton aide.

ii  linux-hwe-5.19-headers-5.19.0-32       5.19.0-32.33~22.04.1  all
ii  linux-headers-5.19.0-32-generic        5.19.0-32.33~22.04.1  amd64
ii  linux-image-5.19.0-32-generic          5.19.0-32.33~22.04.1  amd64
ii  linux-modules-5.19.0-32-generic        5.19.0-32.33~22.04.1  amd64
ii  linux-modules-extra-5.19.0-32-generic  5.19.0-32.33~22.04.1  amd64
ii  linux-hwe-6.2-headers-6.2.0-33         6.2.0-33.33~22.04.1   all
ii  linux-headers-6.2.0-33-generic         6.2.0-33.33~22.04.1   amd64
ii  linux-image-6.2.0-33-generic           6.2.0-33.33~22.04.1   amd64
ii  linux-modules-6.2.0-33-generic         6.2.0-33.33~22.04.1   amd64
ii  linux-modules-extra-6.2.0-33-generic   6.2.0-33.33~22.04.1   amd64
ii  linux-generic-hwe-22.04                6.2.0.33.33~22.04.10  amd64
ii  linux-headers-generic-hwe-22.04        6.2.0.33.33~22.04.10  amd64
ii  linux-image-generic-hwe-22.04          6.2.0.33.33~22.04.10  amd64

Noyau courant : 5.19.0-32-generic x86_64

Dernière modification par Raisin54340 (Le 30/09/2023, à 19:13)

Hors ligne

#8 Le 30/09/2023, à 19:24

xubu1957

Re : Demarrage capricieux aprés installation dual boot

Donne aussi la liste des anomalies de démarrage :

journalctl --no-pager -b -p err

et :

ls -l /var/crash

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] 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

En ligne

#9 Le 30/09/2023, à 19:32

Raisin54340

Re : Demarrage capricieux aprés installation dual boot

sept. 30 18:54:43 daniel-MS-7C95 kernel: blacklist: Problem blacklisting hash (-13)
sept. 30 18:54:43 daniel-MS-7C95 kernel: blacklist: Problem blacklisting hash (-13)
sept. 30 18:54:43 daniel-MS-7C95 kernel: blacklist: Problem blacklisting hash (-13)
sept. 30 18:54:43 daniel-MS-7C95 kernel: blacklist: Problem blacklisting hash (-13)
sept. 30 18:54:43 daniel-MS-7C95 kernel: blacklist: Problem blacklisting hash (-13)
sept. 30 18:54:43 daniel-MS-7C95 kernel: blacklist: Problem blacklisting hash (-13)
sept. 30 18:54:43 daniel-MS-7C95 kernel: bcma: Unsupported SPROM revision: 11
sept. 30 18:54:43 daniel-MS-7C95 kernel: bcma-pci-bridge 0000:05:00.0: bus0: No SPROM available
sept. 30 18:54:45 daniel-MS-7C95 kernel: b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 12, Type 11 (AC), Revision 1)
sept. 30 18:55:00 daniel-MS-7C95 gnome-session-binary[1554]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
sept. 30 18:55:00 daniel-MS-7C95 gnome-session-binary[1554]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
sept. 30 18:55:16 daniel-MS-7C95 gdm-password][1944]: gkr-pam: unable to locate daemon control file
sept. 30 18:55:16 daniel-MS-7C95 systemd[1952]: Failed to start Application launched by gnome-session-binary.
sept. 30 18:55:16 daniel-MS-7C95 systemd[1952]: Failed to start Application launched by gnome-session-binary.
sept. 30 18:55:18 daniel-MS-7C95 systemd[1952]: Failed to start Application launched by gnome-session-binary.
sept. 30 18:55:19 daniel-MS-7C95 gdm-launch-environment][1507]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
sept. 30 18:55:25 daniel-MS-7C95 pulseaudio[1961]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
sept. 30 18:59:54 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 18:59:54 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 18:59:54 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 18:59:54 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 18:59:54 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 19:05:05 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 19:05:05 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 19:05:05 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 19:05:05 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 19:05:06 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 19:10:16 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 19:10:16 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 19:10:17 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 19:10:17 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 19:10:17 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 19:11:26 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 19:11:26 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 19:11:26 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 19:11:26 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 19:11:26 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 19:15:28 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 19:15:28 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 19:15:28 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 19:15:28 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 19:15:28 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 19:20:39 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 19:20:39 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 19:20:39 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 19:20:39 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 19:20:39 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 19:25:50 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 19:25:50 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 19:25:51 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 19:25:51 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 19:25:51 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 19:31:02 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 19:31:02 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 19:31:02 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 19:31:02 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 19:31:02 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 19:36:13 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 19:36:13 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 19:36:13 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 19:36:13 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 19:36:13 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 19:41:24 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 19:41:24 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 19:41:24 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 19:41:24 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 19:41:24 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 19:42:46 daniel-MS-7C95 kernel: ntfs3: Unknown parameter 'windows_names'
sept. 30 19:43:02 daniel-MS-7C95 kernel: ntfs3: Unknown parameter 'windows_names'
sept. 30 19:46:36 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 19:46:36 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 19:46:36 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 19:46:36 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 19:46:36 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 19:51:47 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 19:51:47 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 19:51:47 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 19:51:47 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 19:51:47 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 19:56:58 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 19:56:58 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 19:56:58 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 19:56:58 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 19:56:58 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 20:02:09 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 20:02:09 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 20:02:10 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 20:02:10 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 20:02:10 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 20:07:21 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 20:07:21 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 20:07:21 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 20:07:21 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 20:07:21 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 20:12:32 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 20:12:32 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 20:12:32 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 20:12:32 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 20:12:32 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 20:17:43 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 20:17:43 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 20:17:43 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 20:17:43 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 20:17:43 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 20:22:55 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 20:22:55 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 20:22:55 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 20:22:55 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 20:22:55 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
sept. 30 20:28:06 daniel-MS-7C95 kernel: [Hardware Error]: Corrected error, no action required.
sept. 30 20:28:06 daniel-MS-7C95 kernel: [Hardware Error]: CPU:0 (19:21:0) MC27_STATUS[Over|CE|MiscV|-|-|-|SyndV|-|-|-]: 0xd82000000002080b
sept. 30 20:28:06 daniel-MS-7C95 kernel: [Hardware Error]: IPID: 0x0001002e00000500, Syndrome: 0x000000005a020001
sept. 30 20:28:06 daniel-MS-7C95 kernel: [Hardware Error]: Power, Interrupts, etc. Ext. Error Code: 2, Link Error.
sept. 30 20:28:06 daniel-MS-7C95 kernel: [Hardware Error]: cache level: L3/GEN, mem/io: IO, mem-tx: GEN, part-proc: SRC (no timeout)
total 2732
-rw-r----- 1 daniel   whoopsie 2790973 sept. 30 18:48 _usr_bin_update-notifier.1000.crash
-rw-rw-r-- 1 daniel   whoopsie       0 sept. 30 18:48 _usr_bin_update-notifier.1000.upload
-rw------- 1 whoopsie whoopsie      37 sept. 30 18:48 _usr_bin_update-notifier.1000.uploaded

Dernière modification par Raisin54340 (Le 30/09/2023, à 19:35)

Hors ligne

#10 Le 30/09/2023, à 20:02

xubu1957

Re : Demarrage capricieux aprés installation dual boot

N'ayant que le niveau d'utilisateur lambda, je ne sais pas s'il faut revenir sur le noyau 5.15 basique, de la 22.04 et enlever le HWE.

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] 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

En ligne

#11 Le 01/10/2023, à 09:46

xubu1957

Re : Demarrage capricieux aprés installation dual boot

Bonjour,

Pour info, dans ce fil, la carte fonctionne avec X11.

As-tu moyen de changer de session avec la roue crantée, pour tester avec xorg ?

Regarde l'EDIT de malbo dans ce message, pour la roue crantée.

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] 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

En ligne

#12 Le 04/10/2023, à 17:52

Raisin54340

Re : Demarrage capricieux aprés installation dual boot

Bonjour,
Voici le retour de mes essais en appliquant tes conseils:

aniel@daniel-MS-7C95:~/Bureau$ sudo Xorg -version
[sudo] Mot de passe de daniel : 

X.Org X Server 1.21.1.4
X Protocol Version 11, Revision 0
Current Operating System: Linux daniel-MS-7C95 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=492dff8e-6fcc-4cab-af09-41c4e013c04f ro quiet splash vt.handoff=7
xorg-server 2:21.1.4-2ubuntu1.7~22.04.1 (For technical support please see http://www.ubuntu.com/support) 
Current version of pixman: 0.40.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
daniel@daniel-MS-7C95:~/Bureau$ sudo restart lightdm
sudo: restart : commande introuvable
daniel@daniel-MS-7C95:~/Bureau$ sudo service lightdm restart
Failed to restart lightdm.service: Unit lightdm.service not found.
daniel@daniel-MS-7C95:~/Bureau$ startx

/usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Impossible d'obtenir un descripteur de fichier faisant référence à la console.
daniel@daniel-MS-7C95:~/Bureau$ sudo dpkg-reconfigure -phigh xserver-xorg
daniel@daniel-MS-7C95:~/Bureau$ sudo nvidia-xconfig
sudo: nvidia-xconfig : commande introuvable
daniel@daniel-MS-7C95:~/Bureau$

Je viens de faire un test en changeant pour X11 avec la roue crantée et mon écran passe en jaune vif après l'ouverture de session !

Dernière modification par Raisin54340 (Le 04/10/2023, à 17:57)

Hors ligne

#13 Le 04/10/2023, à 17:58

xubu1957

Re : Demarrage capricieux aprés installation dual boot

Bonjour,

Regarde la réponse de nany, au début du message #8, pour changer de compositeur de fenêtre.

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] 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

En ligne

#14 Le 04/10/2023, à 18:02

Raisin54340

Re : Demarrage capricieux aprés installation dual boot

Merci,
Je viens de faire un test en changeant pour X11 avec la roue crantée et mon écran passe en jaune vif après l'ouverture de session !

Hors ligne

#15 Le 04/10/2023, à 18:05

xubu1957

Re : Demarrage capricieux aprés installation dual boot

au #10, xubu a écrit :

N'ayant que le niveau d'utilisateur lambda, je ne sais pas s'il faut revenir sur le noyau 5.15 basique, de la 22.04 et enlever le HWE.

Je ne sais pas aider plus !  ¯∖_(ツ)_/¯

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] 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

En ligne

#16 Le 04/10/2023, à 18:11

Raisin54340

Re : Demarrage capricieux aprés installation dual boot

Merci en tout cas pour ton temps.
J’espère qu'un autres utilisateur pourra m'aider.

Hors ligne

#17 Le 04/10/2023, à 18:14

xubu1957

Re : Demarrage capricieux aprés installation dual boot

Montre :

cat /var/log/gpu-manager.log

repris dans askubuntu.com/questions/1480763/22-04-2-driver-dependent-apps-crash-even-on-fresh-install.

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] 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

En ligne

#18 Le 04/10/2023, à 18:16

Raisin54340

Re : Demarrage capricieux aprés installation dual boot

log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /opt/amdgpu-pro/bin/amdgpu-pro-px
Looking for nvidia modules in /lib/modules/5.19.0-32-generic/kernel
Looking for nvidia modules in /lib/modules/5.19.0-32-generic/updates/dkms
Looking for amdgpu modules in /lib/modules/5.19.0-32-generic/kernel
Looking for amdgpu modules in /lib/modules/5.19.0-32-generic/updates/dkms
Is nvidia loaded? no
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is intel loaded? no
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is amdgpu versioned? no
Is amdgpu pro stack? no
Is nouveau loaded? yes
Is nouveau blacklisted? no
Is nvidia kernel module available? no
Is amdgpu kernel module available? no
Vendor/Device Id: 10de:2489
BusID "PCI:43@0:0:0"
Is boot vga? yes
Skipping "/dev/dri/card0", driven by "nouveau"
Skipping "/dev/dri/card0", driven by "nouveau"
Found "/dev/dri/card0", driven by "nouveau"
output 0:
	card0-DP-1
Number of connected outputs for /dev/dri/card0: 1
Skipping "/dev/dri/card0", driven by "nouveau"
can't access /etc/prime-discrete
No prime-settings found. Assuming prime is not set to ON (ONDEMAND could be on).
Does it require offloading? no
last cards number = 1
Has amd? no
Has intel? no
Has nvidia? yes
How many cards? 1
Loading nvidia with "no" parameters
Has the system changed? No
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
can't access /run/u-d-c-nvidia-drm-was-loaded file
Takes 10000ms to wait for nvidia udev rules completed.
Single card detected
Nothing to do

Hors ligne

#19 Le 04/10/2023, à 18:19

xubu1957

Re : Demarrage capricieux aprés installation dual boot

Reviens sur wayland, et donne encore :

cat /var/log/gpu-manager.log

Dernière modification par xubu1957 (Le 04/10/2023, à 18:19)

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] 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

En ligne

#20 Le 04/10/2023, à 18:27

Raisin54340

Re : Demarrage capricieux aprés installation dual boot

Pardon mais j'etais sur Wayland §
Je fais la même commande sous X11, si j'y arrive car tout est jaune vert ?

Hors ligne

#21 Le 04/10/2023, à 18:31

xubu1957

Re : Demarrage capricieux aprés installation dual boot

Ce n'est pas la peine.

J'ai vu la commande aujourd'hui, et je ne sais pas analyser les retours.

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] 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

En ligne

#22 Le 04/10/2023, à 18:33

Raisin54340

Re : Demarrage capricieux aprés installation dual boot

Ok je quitte et reprendrai demain. bonne soirée.

Hors ligne

Pages : 1