Bips intermittents dans la tour du pc

Ubu-jp · Le 02/09/2025, à 14:38

Bonjour, depuis quelques jours j'entends un petit bip, bref et unique, très discret, qui se répète aléatoirement toutes les minutes ou parfois toutes les 2 minutes, même si je ne touche pas au clavier ni à la sourie.
Je me demande si ça ne serait pas une sorte d'alerte quand la pile de la carte mère doit être changée. En effet, le PC a 10 ans et c'est toujours la même pile.
Mais ce qui me fait douter c'est que ça le fait depuis le jour où j'ai installé la version 24.04 (avant j'étais sur la 22).
Alors coïncidence ?
Qu'en pensez-vous ? Le système lance-t-il des alertes quand la pile est fatiguée, comme le font les détecteurs de fumée ?

geole · Le 02/09/2025, à 15:31

Bonjour
Si la pile est fatiguée, tu le verras au prochain boot ( perte de la date du jour et perte du choix de boot par défaut)
Je ne pense pas que ubuntu surveille la pile. Il est possible que le bip provienne d'un autre problème depuis un logiciel. Exemple

for ((j=1; j<20; j++));do echo  -e "\a";sleep 10; done

Donne ce retour

journalctl --no-pager --no-hostname -b -p warning -n 100

Dernière modification par geole (Le 02/09/2025, à 16:20)

Ubu-jp · Le 02/09/2025, à 16:04

Merci, voilà le retour :

$ journalctl -b -p warning -n 100
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
sept. 02 11:27:23 pat-System-Product-Name /usr/libexec/gdm-x-session[1917]: (-->
lines 1-23

geole · Le 02/09/2025, à 16:11

On va essayer de savoir pourquoi cette ligne à répétition avant d'aller plus loin...
https://unix.stackexchange.com/question … -4-warning
https://discussion.fedoraproject.org/t/ … s/155544/5

Dernière modification par geole (Le 02/09/2025, à 16:17)

Ubu-jp · Le 02/09/2025, à 16:16

A noter que lorsque je veux fermer le terminal il me prévient que le processus est toujours en cours. Mais l'écran ne change pas.

geole · Le 02/09/2025, à 16:20

Ferme le teminal ou appuie sur la touche entrée pour avoir la ligne suivante..

J'ai modifié la commande pour éviter le problème
Relance en mode plein écran afin d'avoir plus de données dans la ligne

Ubu-jp · Le 02/09/2025, à 16:25

En effet là on voit plus de choses :

$ journalctl --no-pager --no-hostname -b -p warning -n 100
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0):
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-4: disconnected
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0):
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-5: disconnected
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0):
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-6: disconnected
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0):
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-7: disconnected
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0):
sept. 02 12:16:10 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 12:16:10 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 12:16:10 gnome-shell[2232]: NOTE: Not using GLX TFP!
sept. 02 12:19:16 update-notifier[3100]: g_object_get_data: assertion 'G_IS_OBJECT (object)' failed
sept. 02 12:36:51 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 12:36:51 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 12:40:02 gnome-calculato[47799]: currency-provider.vala:556: Cannot use BC rates as don't have CAD rate
sept. 02 12:40:02 gnome-calculato[47799]: currency-provider.vala:419: Cannot use ECB rates as don't have EUR rate
sept. 02 12:41:55 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 12:41:55 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 12:41:55 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 12:41:55 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 12:41:55 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 12:41:55 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 12:41:55 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 12:41:55 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 12:55:15 kernel: kauditd_printk_skb: 1386 callbacks suppressed
sept. 02 12:55:31 gnome-shell[2232]: g_closure_unref: assertion 'closure->ref_count > 0' failed
sept. 02 12:55:31 gnome-shell[2232]: g_closure_unref: assertion 'closure->ref_count > 0' failed
sept. 02 12:55:40 gnome-shell[2232]: JS ERROR: TypeError: this.actor is null
                                     _syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:145:25
                                     onStopped@resource:///org/gnome/shell/ui/windowManager.js:157:35
                                     _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                     _easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:247:60
                                     _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1607:21
                                     onStopped@resource:///org/gnome/shell/ui/windowManager.js:1595:39
                                     _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                     _easeActor/<@resource:///org/gnome/shell/ui/environment.js:160:64
                                     @resource:///org/gnome/shell/ui/init.js:21:20
sept. 02 12:55:45 kernel: kauditd_printk_skb: 10814 callbacks suppressed
sept. 02 12:55:52 kernel: kauditd_printk_skb: 14 callbacks suppressed
sept. 02 12:56:05 kernel: kauditd_printk_skb: 1565 callbacks suppressed
sept. 02 12:57:16 kernel: kauditd_printk_skb: 203 callbacks suppressed
sept. 02 13:20:54 kernel: kauditd_printk_skb: 320 callbacks suppressed
sept. 02 13:21:07 kernel: kauditd_printk_skb: 92 callbacks suppressed
sept. 02 13:24:31 kernel: kauditd_printk_skb: 53 callbacks suppressed
sept. 02 13:24:39 kernel: kauditd_printk_skb: 92 callbacks suppressed
sept. 02 13:24:59 kernel: kauditd_printk_skb: 53 callbacks suppressed
sept. 02 13:25:19 kernel: kauditd_printk_skb: 92 callbacks suppressed
sept. 02 13:28:09 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 13:28:09 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 13:28:09 gnome-shell[2232]: NOTE: Not using GLX TFP!
sept. 02 13:28:22 kernel: kauditd_printk_skb: 53 callbacks suppressed
sept. 02 13:32:48 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 13:32:48 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 13:32:49 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 13:32:49 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 13:38:55 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 13:38:55 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 13:38:55 gnome-shell[2232]: NOTE: Not using GLX TFP!
sept. 02 13:39:33 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 13:39:33 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 13:39:33 gnome-shell[2232]: NOTE: Not using GLX TFP!
sept. 02 13:41:45 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 13:41:45 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 13:41:45 gnome-shell[2232]: NOTE: Not using GLX TFP!
sept. 02 13:50:22 gnome-shell[2232]: Spurious clutter_actor_allocate called for actor 0x5b9e60b52a00/unnamed [StIcon] which isn't a descendent of the stage!
sept. 02 14:05:39 kernel: kauditd_printk_skb: 11 callbacks suppressed
sept. 02 14:17:32 gnome-shell[2232]: GFileInfo created without standard::icon
sept. 02 14:17:32 gnome-shell[2232]: file ../../../gio/gfileinfo.c: line 1765 (g_file_info_get_icon): should not be reached
sept. 02 14:24:18 kernel: kauditd_printk_skb: 20074 callbacks suppressed
sept. 02 14:24:28 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 14:24:28 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 14:24:46 kernel: kauditd_printk_skb: 252 callbacks suppressed
sept. 02 14:25:03 kernel: kauditd_printk_skb: 210 callbacks suppressed
sept. 02 14:27:10 kernel: kauditd_printk_skb: 89 callbacks suppressed
sept. 02 14:40:06 kernel: kauditd_printk_skb: 161 callbacks suppressed
sept. 02 15:34:28 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 15:34:28 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 15:34:31 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 15:34:31 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 15:34:41 kernel: kauditd_printk_skb: 288 callbacks suppressed
sept. 02 15:34:42 nautilus[2880]: gtk_widget_size_allocate(): attempt to allocate GtkBox box 0x5fd2544b82d0 with width 200 and height -2147483648
sept. 02 15:54:10 gnome-shell[2232]: JS ERROR: TypeError: this.actor is null
                                     _syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:145:25
                                     onStopped@resource:///org/gnome/shell/ui/windowManager.js:157:35
                                     _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                     _easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:247:60
                                     _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1607:21
                                     onStopped@resource:///org/gnome/shell/ui/windowManager.js:1575:39
                                     _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                     _easeActor/<@resource:///org/gnome/shell/ui/environment.js:160:64
                                     @resource:///org/gnome/shell/ui/init.js:21:20
sept. 02 16:01:13 firefox[67564]: GTK+ module /snap/firefox/6738/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
                                  GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
sept. 02 16:01:13 firefox[67564]: GTK+ module /snap/firefox/6738/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
                                  GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
sept. 02 16:02:22 gnome-shell[2232]: JS ERROR: TypeError: this.actor is null
                                     _syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:145:25
                                     onStopped@resource:///org/gnome/shell/ui/windowManager.js:157:35
                                     _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                     _easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:247:60
                                     _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1607:21
                                     onStopped@resource:///org/gnome/shell/ui/windowManager.js:1575:39
                                     _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                     _easeActor/<@resource:///org/gnome/shell/ui/environment.js:160:64
                                     @resource:///org/gnome/shell/ui/init.js:21:20
sept. 02 16:11:39 firefox[68758]: GTK+ module /snap/firefox/6738/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
                                  GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
sept. 02 16:11:39 firefox[68758]: GTK+ module /snap/firefox/6738/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
                                  GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
sept. 02 16:13:38 snap-store[69093]: GTK+ module /snap/snap-store/1270/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
                                     GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
sept. 02 16:13:38 snap-store[69093]: GTK+ module /snap/snap-store/1270/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
                                     GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
sept. 02 16:13:57 snap-store[69093]: ../src/gobject/gsignal.c:2777: instance '0x6530c94c1700' has no handler with id '166'
sept. 02 16:13:57 snap-store[69093]: void fl_view_redraw(FlView *): assertion 'FL_IS_VIEW(self)' failed
sept. 02 16:13:57 snap-store[69093]: Attempted to set message handler on an FlBinaryMessenger without an engine
sept. 02 16:13:57 snap-store[69093]: Attempted to set message handler on an FlBinaryMessenger without an engine
sept. 02 16:22:34 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 16:22:34 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 16:23:28 gnome-shell[2232]: JS ERROR: TypeError: this.actor is null
                                     _syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:145:25
                                     onStopped@resource:///org/gnome/shell/ui/windowManager.js:157:35
                                     _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                     _easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:247:60
                                     _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1607:21
                                     onStopped@resource:///org/gnome/shell/ui/windowManager.js:1575:39
                                     _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                     _easeActor/<@resource:///org/gnome/shell/ui/environment.js:160:64
                                     @resource:///org/gnome/shell/ui/init.js:21:20
sept. 02 16:24:10 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 16:24:10 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.

geole · Le 02/09/2025, à 16:36

Cette trace ne montre rien de répétitif à la minute.
Une dernière

journalctl --no-pager --no-hostname -b -n 100

Ubu-jp · Le 02/09/2025, à 16:43

ça ne doit pas être bien grave parce que là, ça fait un moment que je n'ai pas eu le bip. J'ai attendu 4 minutes sans bip. Bizarre. A suivre...

$ journalctl --no-pager --no-hostname -b -n 100
sept. 02 16:14:06 dbus-daemon[1821]: [session uid=1000 pid=1821] Activating service name='org.gnome.seahorse.Application' requested by ':1.37' (uid=1000 pid=2232 comm="/usr/bin/gnome-shell" label="unconfined")
sept. 02 16:14:06 dbus-daemon[1821]: [session uid=1000 pid=1821] Successfully activated service 'org.gnome.seahorse.Application'
sept. 02 16:14:16 gnome-character[69318]: JS LOG: Characters Application exiting
sept. 02 16:14:51 systemd[1751]: Started app-gnome-org.gnome.SystemMonitor-69719.scope - Application launched by gnome-shell.
sept. 02 16:15:01 CRON[69759]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
sept. 02 16:15:01 CRON[69760]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
sept. 02 16:15:01 CRON[69759]: pam_unix(cron:session): session closed for user root
sept. 02 16:15:44 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:15:44 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:16:42 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:16:42 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:17:01 CRON[70791]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
sept. 02 16:17:01 CRON[70792]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
sept. 02 16:17:01 CRON[70791]: pam_unix(cron:session): session closed for user root
sept. 02 16:17:06 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:17:06 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:17:06 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:17:06 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:18:57 PackageKit[69297]: daemon quit
sept. 02 16:18:57 systemd[1]: packagekit.service: Deactivated successfully.
sept. 02 16:19:00 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:19:00 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:19:44 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:19:44 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:20:02 systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
sept. 02 16:20:02 systemd[1]: sysstat-collect.service: Deactivated successfully.
sept. 02 16:20:02 systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
sept. 02 16:21:08 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:21:08 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:21:39 systemd[1751]: app-gnome-org.gnome.SystemMonitor-69719.scope: Consumed 33.279s CPU time.
sept. 02 16:22:34 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 16:22:34 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 16:23:10 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:23:10 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:23:28 systemd[1751]: gnome-terminal-server.service: Consumed 5.872s CPU time.
sept. 02 16:23:28 gnome-shell[2232]: JS ERROR: TypeError: this.actor is null
                                     _syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:145:25
                                     onStopped@resource:///org/gnome/shell/ui/windowManager.js:157:35
                                     _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                     _easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:247:60
                                     _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1607:21
                                     onStopped@resource:///org/gnome/shell/ui/windowManager.js:1575:39
                                     _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:65:22
                                     _easeActor/<@resource:///org/gnome/shell/ui/environment.js:160:64
                                     @resource:///org/gnome/shell/ui/init.js:21:20
sept. 02 16:23:44 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:23:44 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:23:50 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:23:50 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:24:00 systemd[1751]: Started app-gnome-org.gnome.SystemMonitor-73299.scope - Application launched by gnome-shell.
sept. 02 16:24:06 systemd[1751]: Started app-gnome-x\x2dterminal\x2demulator-73323.scope - Application launched by gsd-media-keys.
sept. 02 16:24:06 dbus-daemon[1821]: [session uid=1000 pid=1821] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.296' (uid=1000 pid=73326 comm="/usr/bin/gnome-terminal.real --wait" label="unconfined")
sept. 02 16:24:06 systemd[1751]: Starting gnome-terminal-server.service - GNOME Terminal Server...
sept. 02 16:24:06 dbus-daemon[1821]: [session uid=1000 pid=1821] Successfully activated service 'org.gnome.Terminal'
sept. 02 16:24:06 systemd[1751]: Started gnome-terminal-server.service - GNOME Terminal Server.
sept. 02 16:24:06 systemd[1751]: Started vte-spawn-f108d010-b62e-4886-a798-63cc6cc70c68.scope - VTE child process 73341 launched by gnome-terminal-server process 73330.
sept. 02 16:24:10 gnome-shell[2232]: Can't update stage views actor unnamed [MetaWindowActorX11] is on because it needs an allocation.
sept. 02 16:24:10 gnome-shell[2232]: Can't update stage views actor unnamed [MetaSurfaceActorX11] is on because it needs an allocation.
sept. 02 16:24:39 systemd[1751]: gnome-terminal-server.service: Consumed 2.074s CPU time.
sept. 02 16:25:01 CRON[73370]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
sept. 02 16:25:01 CRON[73371]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
sept. 02 16:25:01 CRON[73370]: pam_unix(cron:session): session closed for user root
sept. 02 16:25:44 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:25:44 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:26:42 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:26:42 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:27:04 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:27:04 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:27:05 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:27:05 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:27:17 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd...
sept. 02 16:27:17 systemd[1]: fwupd-refresh.service: Deactivated successfully.
sept. 02 16:27:17 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd.
sept. 02 16:27:27 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:27:27 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:30:01 CRON[73762]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
sept. 02 16:30:01 CRON[73763]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
sept. 02 16:30:01 CRON[73762]: pam_unix(cron:session): session closed for user root
sept. 02 16:30:01 systemd[1]: Starting sysstat-collect.service - system activity accounting tool...
sept. 02 16:30:01 systemd[1]: sysstat-collect.service: Deactivated successfully.
sept. 02 16:30:01 systemd[1]: Finished sysstat-collect.service - system activity accounting tool.
sept. 02 16:31:07 systemd[1]: Started anacron.service - Run anacron jobs.
sept. 02 16:31:07 anacron[73787]: Anacron 2.3 started on 2025-09-02
sept. 02 16:31:07 anacron[73787]: Normal exit (0 jobs run)
sept. 02 16:31:07 systemd[1]: anacron.service: Deactivated successfully.
sept. 02 16:34:08 xdg-desktop-portal[73961]: WARNING: There is 1 new warning. See 'snap warnings'.
sept. 02 16:34:08 systemd[1751]: Started snap.firefox.firefox-17396713-4380-41a2-8d70-56f0f36d9f41.scope.
sept. 02 16:34:08 firefox[73987]: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.
sept. 02 16:34:08 firefox_firefox.desktop[73987]: [73987, Main Thread] WARNING: GTK+ module /snap/firefox/6738/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
sept. 02 16:34:08 firefox_firefox.desktop[73987]: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:201
sept. 02 16:34:08 firefox[73987]: GTK+ module /snap/firefox/6738/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
                                  GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
sept. 02 16:34:08 firefox[73987]: Failed to load module "canberra-gtk-module"
sept. 02 16:34:08 firefox_firefox.desktop[73987]: [73987, Main Thread] WARNING: GTK+ module /snap/firefox/6738/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
sept. 02 16:34:08 firefox_firefox.desktop[73987]: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:201
sept. 02 16:34:08 firefox[73987]: GTK+ module /snap/firefox/6738/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
                                  GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
sept. 02 16:34:08 firefox[73987]: Failed to load module "canberra-gtk-module"
sept. 02 16:34:09 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:34:09 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:34:09 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:34:09 rtkit-daemon[1835]: Supervising 11 threads of 8 processes of 1 users.
sept. 02 16:35:01 CRON[74229]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
sept. 02 16:35:01 CRON[74232]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
sept. 02 16:35:01 CRON[74229]: pam_unix(cron:session): session closed for user root
sept. 02 16:37:16 systemd[1751]: Started app-gnome-x\x2dterminal\x2demulator-74305.scope - Application launched by gsd-media-keys.
sept. 02 16:37:16 dbus-daemon[1821]: [session uid=1000 pid=1821] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.301' (uid=1000 pid=74308 comm="/usr/bin/gnome-terminal.real --wait" label="unconfined")
sept. 02 16:37:16 systemd[1751]: Starting gnome-terminal-server.service - GNOME Terminal Server...
sept. 02 16:37:16 dbus-daemon[1821]: [session uid=1000 pid=1821] Successfully activated service 'org.gnome.Terminal'
sept. 02 16:37:16 systemd[1751]: Started gnome-terminal-server.service - GNOME Terminal Server.
sept. 02 16:37:16 systemd[1751]: Started vte-spawn-987d12bf-1edf-47be-9497-f8d1ed745b9a.scope - VTE child process 74325 launched by gnome-terminal-server process 74312.
pat@pat-System-Product-Name:~$

Ubu-jp · Le 02/09/2025, à 16:46

6 minutes. C'est en bonne voie. Pourtant je n'ai rien fait.

geole · Le 02/09/2025, à 16:50

Pour en avoir le coeur net, Fais un suivi et vois si le bip a un lien avec la ligne qui s'affiche
Tu ouvres une petite fenêtre en hauteur mais assez large et tu y frappes

journalctl -f

Il ne te restera plus qu'à écouter et zieuter pour voir s'il y a un lien..

Dernière modification par geole (Le 02/09/2025, à 16:50)

Ubu-jp · Le 02/09/2025, à 16:54

OK je te tiens au courant

iznobe · Le 02/09/2025, à 16:55

Bonjour , les " BIPS " dans la tour indiquent des problemes MATERIELS .
chercher quelquechose dans le système d ' exploitation peut potentiellement donner des infos , mais ne pourra pas régler quoi que ce soit .

sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0):
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-4: disconnected
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0):
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-5: disconnected
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0):
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-6: disconnected
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0):
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-7: disconnected
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
sept. 02 11:27:23 /usr/libexec/gdm-x-session[1917]: (--) NVIDIA(GPU-0):

je commencerai par vérifier le cable Display port , voire le changer ...
et vérifier la connectique de la carte vidéo ainsi que l ' alimentation est suffisamment puissante pour alimenter le tout .

Ce qui est certain , c' est que le manuel de ta carte mère ( laquelle ? ) devrait donner des infos sur le nombre de bip , leur intervalle , et ce qu ' ils désignent comme etant en erreur .

Dernière modification par iznobe (Le 02/09/2025, à 16:57)

Ubu-jp · Le 02/09/2025, à 16:59

Je n'ai pas un câble HDMI de dernière génération, c'est un truc assez ancien avec les 2 vis qui fixent la prise fermement de chaque côté.
La carte mère a plus de 10 ans (asus). Le manuel y en a plus...

Dernière modification par Ubu-jp (Le 02/09/2025, à 17:00)

iznobe · Le 02/09/2025, à 19:25

une prise VGA donc ( avec du plastique bleu ou gris ) .
Curieux que ca parle de display port pour le coup
Montre :

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

xrandr

ubuntu-drivers devices

lscpu | grep Nom

Ubu-jp · Le 02/09/2025, à 19:35

Après 2 heures sans un seul bip c'est revenu ! Un bip de temps en temps, sans aucune régularité.
Oui c'est du VGA prise grise.

pat@pat-System-Product-Name:~$ lspci -vnn | grep -A 12 '\[030[02]\]' | grep -Ei "vga|3d|display|kernel"
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 [VGA controller])
	Kernel driver in use: nvidia
	Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
pat@pat-System-Product-Name:~$

$ xrandr
Screen 0: minimum 8 x 8, current 2560 x 1440, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 708mm x 399mm
   2560x1440     59.95*+
   1920x1080     60.00  
   1680x1050     59.95  
   1440x900      59.89  
   1280x1440     59.91  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1280x720      60.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    72.81    59.94  
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
DP-4 disconnected (normal left inverted right x axis y axis)
DP-5 disconnected (normal left inverted right x axis y axis)
pat@pat-System-Product-Name:~$

~$ ubuntu-drivers devices
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
udevadm hwdb is deprecated. Use systemd-hwdb instead.
== /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0 ==
modalias : pci:v000010DEd000013C0sv00001043sd00008518bc03sc00i00
vendor   : NVIDIA Corporation
model    : GM204 [GeForce GTX 980]
driver   : nvidia-driver-550 - distro non-free recommended
driver   : nvidia-driver-570-server - distro non-free
driver   : nvidia-driver-575-server - distro non-free
driver   : nvidia-driver-570 - distro non-free
driver   : nvidia-driver-535-server - distro non-free
driver   : nvidia-driver-470 - distro non-free
driver   : nvidia-driver-535 - distro non-free
driver   : nvidia-driver-575 - distro non-free
driver   : nvidia-driver-470-server - distro non-free
driver   : xserver-xorg-video-nouveau - distro free builtin

== /sys/devices/pci0000:00/0000:00:1b.2/0000:03:00.0 ==
modalias : pci:v000014E4d000043B1sv00001043sd000085BAbc02sc80i00
vendor   : Broadcom Inc. and subsidiaries
model    : BCM4352 802.11ac Dual Band Wireless Network Adapter (PCE-AC56 Dual-Band Wireless PCI-E Adapter)
driver   : broadcom-sta-dkms - distro non-free

pat@pat-System-Product-Name:~$

$ lscpu | grep Nom
Nom de modèle :                          Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
pat@pat-System-Product-Name:~$

iznobe · Le 02/09/2025, à 19:41

Montre aussi :

dpkg -l | grep nvidia

théoriquement , ton CPU devrait avoir un integrated GPU : https://www.intel.fr/content/www/fr/fr/ … tions.html

Pour un essai " rapide " ( si tu connais un peu le BIOS ) et sans rien démonter , tu pourrais aller dans le BIOS et activer l ' iGPU( * ) du processeur , si tu en disposes bien d' un , alors désactive la carte graphique nvidia , puis redémarre histoire de vérifier sir les " bips " persistent ou pas . ca permettrait d ' incriminer ( ou pas ) un soucis avec ta carte graphique .

* ) un iGPU , c' est une carte graphique intégrée au processeur .

Dernière modification par iznobe (Le 02/09/2025, à 20:19)

Ubu-jp · Le 02/09/2025, à 19:48

Ok merci. Si je désactive la carte graphique que va-t-il se passer ? je vais avoir un affichage vga 640 x 480 ? Ça va faire bizarre sur l'écran 32 pouces.
Bon de toute façon si je fais ça ce sera demain matin. Parce que j'ai pas envie de passer la soirée (la nuit ?) là-dessus.

pat@pat-System-Product-Name:~$ dpkg -l | grep nvidia
ii  libnvidia-cfg1-550:amd64                       550.163.01-0ubuntu0.24.04.1              amd64        NVIDIA binary OpenGL/GLX configuration library
ii  libnvidia-common-550                           550.163.01-0ubuntu0.24.04.1              all          Shared files used by the NVIDIA libraries
ii  libnvidia-compute-550:amd64                    550.163.01-0ubuntu0.24.04.1              amd64        NVIDIA libcompute package
ii  libnvidia-compute-550:i386                     550.163.01-0ubuntu0.24.04.1              i386         NVIDIA libcompute package
ii  libnvidia-decode-550:amd64                     550.163.01-0ubuntu0.24.04.1              amd64        NVIDIA Video Decoding runtime libraries
ii  libnvidia-decode-550:i386                      550.163.01-0ubuntu0.24.04.1              i386         NVIDIA Video Decoding runtime libraries
ii  libnvidia-egl-wayland1:amd64                   1:1.1.13-1build1                         amd64        Wayland EGL External Platform library -- shared library
ii  libnvidia-egl-wayland1:i386                    1:1.1.13-1build1                         i386         Wayland EGL External Platform library -- shared library
ii  libnvidia-encode-550:amd64                     550.163.01-0ubuntu0.24.04.1              amd64        NVENC Video Encoding runtime library
ii  libnvidia-encode-550:i386                      550.163.01-0ubuntu0.24.04.1              i386         NVENC Video Encoding runtime library
ii  libnvidia-extra-550:amd64                      550.163.01-0ubuntu0.24.04.1              amd64        Extra libraries for the NVIDIA driver
ii  libnvidia-fbc1-550:amd64                       550.163.01-0ubuntu0.24.04.1              amd64        NVIDIA OpenGL-based Framebuffer Capture runtime library
ii  libnvidia-fbc1-550:i386                        550.163.01-0ubuntu0.24.04.1              i386         NVIDIA OpenGL-based Framebuffer Capture runtime library
ii  libnvidia-gl-550:amd64                         550.163.01-0ubuntu0.24.04.1              amd64        NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii  libnvidia-gl-550:i386                          550.163.01-0ubuntu0.24.04.1              i386         NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD
ii  linux-modules-nvidia-550-6.14.0-29-generic     6.14.0-29.29~24.04.1                     amd64        Linux kernel nvidia modules for version 6.14.0-29
ii  linux-modules-nvidia-550-generic-hwe-24.04     6.14.0-29.29~24.04.1                     amd64        Extra drivers for nvidia-550 for the generic-hwe-24.04 flavour
ii  linux-objects-nvidia-550-6.14.0-29-generic     6.14.0-29.29~24.04.1                     amd64        Linux kernel nvidia modules for version 6.14.0-29 (objects)
ii  linux-signatures-nvidia-6.14.0-29-generic      6.14.0-29.29~24.04.1                     amd64        Linux kernel signatures for nvidia modules for version 6.14.0-29-generic
ii  nvidia-compute-utils-550                       550.163.01-0ubuntu0.24.04.1              amd64        NVIDIA compute utilities
ii  nvidia-driver-550                              550.163.01-0ubuntu0.24.04.1              amd64        NVIDIA driver metapackage
ii  nvidia-firmware-550-550.163.01                 550.163.01-0ubuntu0.24.04.1              amd64        Firmware files used by the kernel module
ii  nvidia-kernel-common-550                       550.163.01-0ubuntu0.24.04.1              amd64        Shared files used with the kernel module
ii  nvidia-kernel-source-550                       550.163.01-0ubuntu0.24.04.1              amd64        NVIDIA kernel source package
ii  nvidia-prime                                   0.8.17.2                                 all          Tools to enable NVIDIA's Prime
ii  nvidia-settings                                510.47.03-0ubuntu4                       amd64        Tool for configuring the NVIDIA graphics driver
ii  nvidia-utils-550                               550.163.01-0ubuntu0.24.04.1              amd64        NVIDIA driver support binaries
ii  screen-resolution-extra                        0.18.3ubuntu0.24.04.1                    all          Extension for the nvidia-settings control panel
ii  xserver-xorg-video-nvidia-550                  550.163.01-0ubuntu0.24.04.1              amd64        NVIDIA binary Xorg driver
pat@pat-System-Product-Name:~$

iznobe · Le 02/09/2025, à 20:15

relis mon message , j ' ai pas dis de désactiver ( seulement ) la carte graphique nvidia .

J ' édite mon message pour une meilleur compréhension / clarté .

Ubu-jp · Le 02/09/2025, à 20:31

Oui OK, mais je ne suis pas sûr que la carte graphique intégrée au processeur puisse m'autoriser une définition de 2560x1440. C'est pour ça que je parlais d'affichage VGA.
Enfin j'essaierai demain.

iznobe · Le 02/09/2025, à 20:40

pour le moment , il s' agit de savoir si ta carte graphique NVIDIA est défectueuse ou pas par un moyen relativement simple . Pour le reste tu aviseras ensuite .

Ubu-jp · Le 03/09/2025, à 08:39

Ce matin, au premier démarrage, les bips étaient encore là. Donc je suis allé dans le Bios.
Je ne suis pas arrivé à trouver comment on active l’igpu ni désactive la carte Nvidia dans le bios. J'ai pourtant déroulé tous les menus.
J’ai redémarré avec les réglages d’usine mais ça n'a pas changé grand chose.

La seule chose qui me reste à faire est d'ouvrir le PC et de contrôler toutes les connexions.

krodelabestiole · Le 03/09/2025, à 14:08

iznobe a écrit :

Ce qui est certain , c' est que le manuel de ta carte mère ( laquelle ? ) devrait donner des infos sur le nombre de bip , leur intervalle , et ce qu ' ils désignent comme etant en erreur .

voilà.

Ubu-jp a écrit :

La carte mère a plus de 10 ans (asus). Le manuel y en plus...

ça m'étonnerait que ce soit introuvable !
il y a 10 ans les fabricants de carte mère proposaient déjà des modes d'emploi au format numérique sur leurs sites.

Ubu-jp · Le 03/09/2025, à 14:33

En effet je l'ai trouvé ici : https://manuall.fr/asus-z170-pro-carte-mere/#pf42

Hélas rien concernant des bips d'alerte en cours de fonctionnement. Y a seulement des infos sur les bips de démarrage au chapitre 2.3 "démarrer pour la 1ère fois"

Ubu-jp · Le 03/09/2025, à 17:50

Mise à jour :
Bon, je n'ai encore rien fait parce que les bips se sont espacés de plus en plus dans la journée tout en diminuant d'intensité ! (ça paraît une blague mais c'est la vérité).
Et là ça fait au moins 4 heures que je n'ai plus rien entendu. Ou alors c'est moi qui deviens sourd ?!
A moins que... c'est comme les moteurs de voiture, il marche mieux à chaud. Je verrai demain matin ce que ça donne, cette nuit je l'éteindrai.

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#1 Le 02/09/2025, à 14:38

Bips intermittents dans la tour du pc

#2 Le 02/09/2025, à 15:31

Re : Bips intermittents dans la tour du pc

#3 Le 02/09/2025, à 16:04

Re : Bips intermittents dans la tour du pc

#4 Le 02/09/2025, à 16:11

Re : Bips intermittents dans la tour du pc

#5 Le 02/09/2025, à 16:16

Re : Bips intermittents dans la tour du pc

#6 Le 02/09/2025, à 16:20

Re : Bips intermittents dans la tour du pc

#7 Le 02/09/2025, à 16:25

Re : Bips intermittents dans la tour du pc

#8 Le 02/09/2025, à 16:36

Re : Bips intermittents dans la tour du pc

#9 Le 02/09/2025, à 16:43

Re : Bips intermittents dans la tour du pc

#10 Le 02/09/2025, à 16:46

Re : Bips intermittents dans la tour du pc

#11 Le 02/09/2025, à 16:50

Re : Bips intermittents dans la tour du pc

#12 Le 02/09/2025, à 16:54

Re : Bips intermittents dans la tour du pc

#13 Le 02/09/2025, à 16:55

Re : Bips intermittents dans la tour du pc

#14 Le 02/09/2025, à 16:59

Re : Bips intermittents dans la tour du pc

#15 Le 02/09/2025, à 19:25

Re : Bips intermittents dans la tour du pc

#16 Le 02/09/2025, à 19:35

Re : Bips intermittents dans la tour du pc

#17 Le 02/09/2025, à 19:41

Re : Bips intermittents dans la tour du pc

#18 Le 02/09/2025, à 19:48

Re : Bips intermittents dans la tour du pc

#19 Le 02/09/2025, à 20:15

Re : Bips intermittents dans la tour du pc

#20 Le 02/09/2025, à 20:31

Re : Bips intermittents dans la tour du pc

#21 Le 02/09/2025, à 20:40

Re : Bips intermittents dans la tour du pc

#22 Le 03/09/2025, à 08:39

Re : Bips intermittents dans la tour du pc

#23 Le 03/09/2025, à 14:08

Re : Bips intermittents dans la tour du pc

#24 Le 03/09/2025, à 14:33

Re : Bips intermittents dans la tour du pc

#25 Le 03/09/2025, à 17:50

Re : Bips intermittents dans la tour du pc

Pied de page des forums