Advertising

Welcome to SparkyLinux forums
Zapraszamy również na polsko-języczne Forum https://forum.linuxiarze.pl

Boot issues with LXQT SparkyLinux 6.6 32-bits

Started by jgratero, April 28, 2023, 05:00:40 AM

Previous topic - Next topic
Print
Go Down Pages1
User actions

jgratero

April 28, 2023, 05:00:40 AM
I am having booting issues with a fresh installation of LXQT 6.6 32 bits. Two out of three times it just stops on a blank screen with a cursor, and pretty much that's it. The journalctl logs show this:

Code Select
-- Journal begins at Tue 2023-04-25 20:14:25 -05, ends at Thu 2023-04-27 12:08:02 -05. --
abr 25 20:14:25 sulaco-01962cs systemd-xdg-autostart-generator[613]: /etc/xdg/autostart/sparky-welcome-first.desktop:12: Unknown key name 'MultipleArgs' in section 'Desktop Entry', ignoring.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Queued start job for default target Main User Target.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Created slice User Application Slice.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Reached target Paths.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Reached target Timers.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Starting D-Bus User Message Bus Socket.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Listening on GnuPG network certificate management daemon.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
abr 25 20:14:25 sulaco-01962cs systemd[600]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
abr 25 20:14:25 sulaco-01962cs systemd[600]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
abr 25 20:14:25 sulaco-01962cs systemd[600]: Listening on GnuPG cryptographic agent and passphrase cache.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Listening on Sound System.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Listening on D-Bus User Message Bus Socket.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Reached target Sockets.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Reached target Basic System.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Starting Sound Service...
abr 25 20:14:25 sulaco-01962cs sddm-helper[616]: Adding cookie to "/home/jgratero/.Xauthority"
abr 25 20:14:25 sulaco-01962cs systemd[600]: Started D-Bus User Message Bus.
abr 25 20:14:26 sulaco-01962cs pulseaudio[615]: Failed to open cookie file '/home/jgratero/.config/pulse/cookie': No such file or directory
abr 25 20:14:26 sulaco-01962cs pulseaudio[615]: Failed to load authentication key '/home/jgratero/.config/pulse/cookie': No such file or directory
abr 25 20:14:26 sulaco-01962cs pulseaudio[615]: Failed to open cookie file '/home/jgratero/.pulse-cookie': No such file or directory
abr 25 20:14:26 sulaco-01962cs pulseaudio[615]: Failed to load authentication key '/home/jgratero/.pulse-cookie': No such file or directory
abr 25 20:14:26 sulaco-01962cs systemd[600]: Started Sound Service.
abr 25 20:14:26 sulaco-01962cs systemd[600]: Reached target Main User Target.
abr 25 20:14:26 sulaco-01962cs systemd[600]: Startup finished in 998ms.
abr 25 20:14:27 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.7' (uid=1000 pid=671 comm="/usr/bin/openbox --config-file /home/jgratero/.con")
abr 25 20:14:27 sulaco-01962cs systemd[600]: Starting Virtual filesystem service...
abr 25 20:14:27 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Successfully activated service 'org.gtk.vfs.Daemon'
abr 25 20:14:27 sulaco-01962cs systemd[600]: Started Virtual filesystem service.
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.9' (uid=1000 pid=687 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
abr 25 20:14:28 sulaco-01962cs systemd[600]: Starting Virtual filesystem service - disk device monitor...
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
abr 25 20:14:28 sulaco-01962cs systemd[600]: Started Virtual filesystem service - disk device monitor.
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.9' (uid=1000 pid=687 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
abr 25 20:14:28 sulaco-01962cs systemd[600]: Starting Virtual filesystem service - Apple File Conduit monitor...
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
abr 25 20:14:28 sulaco-01962cs systemd[600]: Started Virtual filesystem service - Apple File Conduit monitor.
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.9' (uid=1000 pid=687 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
abr 25 20:14:28 sulaco-01962cs systemd[600]: Starting Virtual filesystem service - digital camera monitor...
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
abr 25 20:14:28 sulaco-01962cs systemd[600]: Started Virtual filesystem service - digital camera monitor.
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.9' (uid=1000 pid=687 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
abr 25 20:14:28 sulaco-01962cs systemd[600]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
abr 25 20:14:28 sulaco-01962cs systemd[600]: Started Virtual filesystem service - Media Transfer Protocol monitor.
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.9' (uid=1000 pid=687 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
abr 25 20:14:28 sulaco-01962cs systemd[600]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
abr 25 20:14:28 sulaco-01962cs systemd[600]: Started Virtual filesystem service - GNOME Online Accounts monitor.
abr 25 20:14:57 sulaco-01962cs sudo[1257]: jgratero : PWD=/home/jgratero ; USER=root ; COMMAND=/usr/bin/sparky-aptus-upgrade-sim simulate
abr 25 20:14:57 sulaco-01962cs sudo[1257]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:15:19 sulaco-01962cs pkexec[1653]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:15:20 sulaco-01962cs sudo[1257]: pam_unix(sudo:session): session closed for user root
abr 25 20:15:40 sulaco-01962cs sudo[1811]: jgratero : PWD=/home/jgratero ; USER=root ; COMMAND=/usr/bin/sparky-pass-check root XXXXXXXXXXXXXXXXXXXXXXXX
abr 25 20:15:40 sulaco-01962cs sudo[1811]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:15:40 sulaco-01962cs sudo[1811]: pam_unix(sudo:session): session closed for user root
abr 25 20:16:00 sulaco-01962cs su[1855]: (to root) jgratero on none
abr 25 20:16:00 sulaco-01962cs su[1855]: pam_unix(su:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:16:51 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.9' (uid=1000 pid=687 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
abr 25 20:16:51 sulaco-01962cs systemd[600]: Starting Virtual filesystem metadata service...
abr 25 20:16:51 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Successfully activated service 'org.gtk.vfs.Metadata'
abr 25 20:16:51 sulaco-01962cs systemd[600]: Started Virtual filesystem metadata service.
abr 25 20:18:19 sulaco-01962cs su[1855]: pam_unix(su:session): session closed for user root
abr 25 20:18:19 sulaco-01962cs sudo[4330]: jgratero : PWD=/home/jgratero ; USER=root ; COMMAND=/usr/bin/sparky-aptus-upgrade-sim clean
abr 25 20:18:19 sulaco-01962cs sudo[4330]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:18:19 sulaco-01962cs sudo[4330]: pam_unix(sudo:session): session closed for user root
abr 25 20:20:27 sulaco-01962cs pkexec[4348]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:21:29 sulaco-01962cs systemd[600]: media-jgratero-SPARKY_32BI.mount: Succeeded.
abr 25 20:22:11 sulaco-01962cs pkexec[4415]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:23:11 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Reloaded configuration
abr 25 20:23:11 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Reloaded configuration
abr 25 20:23:11 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Reloaded configuration
abr 25 20:26:47 sulaco-01962cs sudo[5101]: pam_unix(sudo:auth): authentication failure; logname= uid=1000 euid=0 tty=/dev/pts/0 ruser=jgratero rhost=  user=jgratero
abr 25 20:27:00 sulaco-01962cs sudo[5101]: jgratero : TTY=pts/0 ; PWD=/home/jgratero ; USER=root ; COMMAND=/usr/sbin/ufw status
abr 25 20:27:00 sulaco-01962cs sudo[5101]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:27:00 sulaco-01962cs sudo[5101]: pam_unix(sudo:session): session closed for user root
abr 25 20:27:18 sulaco-01962cs sudo[5107]: jgratero : TTY=pts/0 ; PWD=/home/jgratero ; USER=root ; COMMAND=/usr/sbin/ufw status verbose
abr 25 20:27:18 sulaco-01962cs sudo[5107]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:27:19 sulaco-01962cs sudo[5107]: pam_unix(sudo:session): session closed for user root
abr 25 20:28:16 sulaco-01962cs sudo[5112]: jgratero : TTY=pts/0 ; PWD=/home/jgratero ; USER=root ; COMMAND=/usr/sbin/ufw enable
abr 25 20:28:16 sulaco-01962cs sudo[5112]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:28:17 sulaco-01962cs sudo[5112]: pam_unix(sudo:session): session closed for user root
abr 25 20:28:24 sulaco-01962cs sudo[5266]: jgratero : TTY=pts/0 ; PWD=/home/jgratero ; USER=root ; COMMAND=/usr/sbin/ufw status verbose
abr 25 20:28:24 sulaco-01962cs sudo[5266]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:28:25 sulaco-01962cs sudo[5266]: pam_unix(sudo:session): session closed for user root
abr 25 20:36:30 sulaco-01962cs pkexec[5849]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
abr 25 22:23:02 sulaco-01962cs systemd[600]: media-jgratero-SAMSUNG.mount: Succeeded.
abr 25 22:23:25 sulaco-01962cs pulseaudio[615]: X connection to :0 broken (explicit kill or server shutdown).
abr 25 22:23:25 sulaco-01962cs systemd[600]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
abr 25 22:23:25 sulaco-01962cs systemd[600]: pulseaudio.service: Failed with result 'exit-code'.
abr 25 22:23:25 sulaco-01962cs systemd[600]: pulseaudio.service: Consumed 2min 24.635s CPU time.
abr 25 22:23:25 sulaco-01962cs systemd[600]: run-rpc_pipefs.mount: Succeeded.
abr 25 22:23:25 sulaco-01962cs systemd[600]: pulseaudio.service: Scheduled restart job, restart counter is at 1.
abr 25 22:23:25 sulaco-01962cs systemd[600]: Stopped Sound Service.
abr 25 22:23:25 sulaco-01962cs systemd[600]: pulseaudio.service: Consumed 2min 24.635s CPU time.
abr 25 22:23:25 sulaco-01962cs systemd[600]: Starting Sound Service...
abr 25 22:23:25 sulaco-01962cs pulseaudio[10345]: Stale PID file, overwriting.
abr 25 22:23:25 sulaco-01962cs systemd[600]: Started Sound Service.
abr 25 22:23:25 sulaco-01962cs pulseaudio[10345]: GetManagedObjects() failed: org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus is shutting down.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped target Main User Target.
abr 25 22:23:28 sulaco-01962cs gvfsd[712]: A connection to the bus can't be made
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping D-Bus User Message Bus...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Virtual filesystem service - Apple File Conduit monitor...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Virtual filesystem service...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Virtual filesystem service - digital camera monitor...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Virtual filesystem metadata service...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Virtual filesystem service - disk device monitor...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Sound Service...
abr 25 22:23:28 sulaco-01962cs systemd[600]: dbus.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped D-Bus User Message Bus.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gvfs-udisks2-volume-monitor.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Virtual filesystem service - disk device monitor.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gvfs-daemon.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Virtual filesystem service.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gvfs-afc-volume-monitor.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Virtual filesystem service - Apple File Conduit monitor.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gvfs-gphoto2-volume-monitor.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Virtual filesystem service - digital camera monitor.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gvfs-mtp-volume-monitor.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gvfs-goa-volume-monitor.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gvfs-metadata.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Virtual filesystem metadata service.
abr 25 22:23:28 sulaco-01962cs systemd[600]: pulseaudio.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Sound Service.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped target Basic System.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped target Paths.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped target Sockets.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped target Timers.
abr 25 22:23:28 sulaco-01962cs systemd[600]: dbus.socket: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Closed D-Bus User Message Bus Socket.
abr 25 22:23:28 sulaco-01962cs systemd[600]: dirmngr.socket: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Closed GnuPG network certificate management daemon.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gpg-agent-browser.socket: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
abr 25 22:23:28 sulaco-01962cs systemd[600]: gpg-agent-extra.socket: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
abr 25 22:23:28 sulaco-01962cs systemd[600]: gpg-agent-ssh.socket: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Closed GnuPG cryptographic agent (ssh-agent emulation).
abr 25 22:23:28 sulaco-01962cs systemd[600]: gpg-agent.socket: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Closed GnuPG cryptographic agent and passphrase cache.
abr 25 22:23:28 sulaco-01962cs systemd[600]: pulseaudio.socket: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Closed Sound System.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Removed slice User Application Slice.
abr 25 22:23:28 sulaco-01962cs systemd[600]: app.slice: Consumed 2min 26.143s CPU time.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Reached target Shutdown.
abr 25 22:23:28 sulaco-01962cs systemd[600]: systemd-exit.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Finished Exit the Session.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Reached target Exit the Session.

The most recent error message produced was, "[drm] *Error* pipe A FIFO underrun."

Code Select
-- Journal begins at Tue 2023-04-25 20:14:25 -05, ends at Thu 2023-04-27 18:11:02 -05. --
abr 25 20:14:25 sulaco-01962cs systemd-xdg-autostart-generator[613]: /etc/xdg/autostart/sparky-welcome-first.desktop:12: Unknown key name 'MultipleArgs' in section 'Desktop Entry', ignoring.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Queued start job for default target Main User Target.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Created slice User Application Slice.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Reached target Paths.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Reached target Timers.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Starting D-Bus User Message Bus Socket.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Listening on GnuPG network certificate management daemon.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
abr 25 20:14:25 sulaco-01962cs systemd[600]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
abr 25 20:14:25 sulaco-01962cs systemd[600]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
abr 25 20:14:25 sulaco-01962cs systemd[600]: Listening on GnuPG cryptographic agent and passphrase cache.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Listening on Sound System.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Listening on D-Bus User Message Bus Socket.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Reached target Sockets.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Reached target Basic System.
abr 25 20:14:25 sulaco-01962cs systemd[600]: Starting Sound Service...
abr 25 20:14:25 sulaco-01962cs sddm-helper[616]: Adding cookie to "/home/jgratero/.Xauthority"
abr 25 20:14:25 sulaco-01962cs systemd[600]: Started D-Bus User Message Bus.
abr 25 20:14:26 sulaco-01962cs pulseaudio[615]: Failed to open cookie file '/home/jgratero/.config/pulse/cookie': No such file or directory
abr 25 20:14:26 sulaco-01962cs pulseaudio[615]: Failed to load authentication key '/home/jgratero/.config/pulse/cookie': No such file or directory
abr 25 20:14:26 sulaco-01962cs pulseaudio[615]: Failed to open cookie file '/home/jgratero/.pulse-cookie': No such file or directory
abr 25 20:14:26 sulaco-01962cs pulseaudio[615]: Failed to load authentication key '/home/jgratero/.pulse-cookie': No such file or directory
abr 25 20:14:26 sulaco-01962cs systemd[600]: Started Sound Service.
abr 25 20:14:26 sulaco-01962cs systemd[600]: Reached target Main User Target.
abr 25 20:14:26 sulaco-01962cs systemd[600]: Startup finished in 998ms.
abr 25 20:14:27 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.7' (uid=1000 pid=671 comm="/usr/bin/openbox --config-file /home/jgratero/.con")
abr 25 20:14:27 sulaco-01962cs systemd[600]: Starting Virtual filesystem service...
abr 25 20:14:27 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Successfully activated service 'org.gtk.vfs.Daemon'
abr 25 20:14:27 sulaco-01962cs systemd[600]: Started Virtual filesystem service.
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.9' (uid=1000 pid=687 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
abr 25 20:14:28 sulaco-01962cs systemd[600]: Starting Virtual filesystem service - disk device monitor...
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
abr 25 20:14:28 sulaco-01962cs systemd[600]: Started Virtual filesystem service - disk device monitor.
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.9' (uid=1000 pid=687 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
abr 25 20:14:28 sulaco-01962cs systemd[600]: Starting Virtual filesystem service - Apple File Conduit monitor...
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
abr 25 20:14:28 sulaco-01962cs systemd[600]: Started Virtual filesystem service - Apple File Conduit monitor.
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.9' (uid=1000 pid=687 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
abr 25 20:14:28 sulaco-01962cs systemd[600]: Starting Virtual filesystem service - digital camera monitor...
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
abr 25 20:14:28 sulaco-01962cs systemd[600]: Started Virtual filesystem service - digital camera monitor.
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.9' (uid=1000 pid=687 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
abr 25 20:14:28 sulaco-01962cs systemd[600]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
abr 25 20:14:28 sulaco-01962cs systemd[600]: Started Virtual filesystem service - Media Transfer Protocol monitor.
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.9' (uid=1000 pid=687 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
abr 25 20:14:28 sulaco-01962cs systemd[600]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
abr 25 20:14:28 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
abr 25 20:14:28 sulaco-01962cs systemd[600]: Started Virtual filesystem service - GNOME Online Accounts monitor.
abr 25 20:14:57 sulaco-01962cs sudo[1257]: jgratero : PWD=/home/jgratero ; USER=root ; COMMAND=/usr/bin/sparky-aptus-upgrade-sim simulate
abr 25 20:14:57 sulaco-01962cs sudo[1257]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:15:19 sulaco-01962cs pkexec[1653]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:15:20 sulaco-01962cs sudo[1257]: pam_unix(sudo:session): session closed for user root
abr 25 20:15:40 sulaco-01962cs sudo[1811]: jgratero : PWD=/home/jgratero ; USER=root ; COMMAND=/usr/bin/sparky-pass-check root XXXXXXXXXXXXXXXXXXXXXXXX
abr 25 20:15:40 sulaco-01962cs sudo[1811]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:15:40 sulaco-01962cs sudo[1811]: pam_unix(sudo:session): session closed for user root
abr 25 20:16:00 sulaco-01962cs su[1855]: (to root) jgratero on none
abr 25 20:16:00 sulaco-01962cs su[1855]: pam_unix(su:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:16:51 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.9' (uid=1000 pid=687 comm="/usr/bin/pcmanfm-qt --desktop --profile=lxqt ")
abr 25 20:16:51 sulaco-01962cs systemd[600]: Starting Virtual filesystem metadata service...
abr 25 20:16:51 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Successfully activated service 'org.gtk.vfs.Metadata'
abr 25 20:16:51 sulaco-01962cs systemd[600]: Started Virtual filesystem metadata service.
abr 25 20:18:19 sulaco-01962cs su[1855]: pam_unix(su:session): session closed for user root
abr 25 20:18:19 sulaco-01962cs sudo[4330]: jgratero : PWD=/home/jgratero ; USER=root ; COMMAND=/usr/bin/sparky-aptus-upgrade-sim clean
abr 25 20:18:19 sulaco-01962cs sudo[4330]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:18:19 sulaco-01962cs sudo[4330]: pam_unix(sudo:session): session closed for user root
abr 25 20:20:27 sulaco-01962cs pkexec[4348]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:21:29 sulaco-01962cs systemd[600]: media-jgratero-SPARKY_32BI.mount: Succeeded.
abr 25 20:22:11 sulaco-01962cs pkexec[4415]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:23:11 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Reloaded configuration
abr 25 20:23:11 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Reloaded configuration
abr 25 20:23:11 sulaco-01962cs dbus-daemon[630]: [session uid=1000 pid=630] Reloaded configuration
abr 25 20:26:47 sulaco-01962cs sudo[5101]: pam_unix(sudo:auth): authentication failure; logname= uid=1000 euid=0 tty=/dev/pts/0 ruser=jgratero rhost=  user=jgratero
abr 25 20:27:00 sulaco-01962cs sudo[5101]: jgratero : TTY=pts/0 ; PWD=/home/jgratero ; USER=root ; COMMAND=/usr/sbin/ufw status
abr 25 20:27:00 sulaco-01962cs sudo[5101]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:27:00 sulaco-01962cs sudo[5101]: pam_unix(sudo:session): session closed for user root
abr 25 20:27:18 sulaco-01962cs sudo[5107]: jgratero : TTY=pts/0 ; PWD=/home/jgratero ; USER=root ; COMMAND=/usr/sbin/ufw status verbose
abr 25 20:27:18 sulaco-01962cs sudo[5107]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:27:19 sulaco-01962cs sudo[5107]: pam_unix(sudo:session): session closed for user root
abr 25 20:28:16 sulaco-01962cs sudo[5112]: jgratero : TTY=pts/0 ; PWD=/home/jgratero ; USER=root ; COMMAND=/usr/sbin/ufw enable
abr 25 20:28:16 sulaco-01962cs sudo[5112]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:28:17 sulaco-01962cs sudo[5112]: pam_unix(sudo:session): session closed for user root
abr 25 20:28:24 sulaco-01962cs sudo[5266]: jgratero : TTY=pts/0 ; PWD=/home/jgratero ; USER=root ; COMMAND=/usr/sbin/ufw status verbose
abr 25 20:28:24 sulaco-01962cs sudo[5266]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
abr 25 20:28:25 sulaco-01962cs sudo[5266]: pam_unix(sudo:session): session closed for user root
abr 25 20:36:30 sulaco-01962cs pkexec[5849]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
abr 25 22:23:02 sulaco-01962cs systemd[600]: media-jgratero-SAMSUNG.mount: Succeeded.
abr 25 22:23:25 sulaco-01962cs pulseaudio[615]: X connection to :0 broken (explicit kill or server shutdown).
abr 25 22:23:25 sulaco-01962cs systemd[600]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
abr 25 22:23:25 sulaco-01962cs systemd[600]: pulseaudio.service: Failed with result 'exit-code'.
abr 25 22:23:25 sulaco-01962cs systemd[600]: pulseaudio.service: Consumed 2min 24.635s CPU time.
abr 25 22:23:25 sulaco-01962cs systemd[600]: run-rpc_pipefs.mount: Succeeded.
abr 25 22:23:25 sulaco-01962cs systemd[600]: pulseaudio.service: Scheduled restart job, restart counter is at 1.
abr 25 22:23:25 sulaco-01962cs systemd[600]: Stopped Sound Service.
abr 25 22:23:25 sulaco-01962cs systemd[600]: pulseaudio.service: Consumed 2min 24.635s CPU time.
abr 25 22:23:25 sulaco-01962cs systemd[600]: Starting Sound Service...
abr 25 22:23:25 sulaco-01962cs pulseaudio[10345]: Stale PID file, overwriting.
abr 25 22:23:25 sulaco-01962cs systemd[600]: Started Sound Service.
abr 25 22:23:25 sulaco-01962cs pulseaudio[10345]: GetManagedObjects() failed: org.freedesktop.systemd1.ShuttingDown: Refusing activation, D-Bus is shutting down.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped target Main User Target.
abr 25 22:23:28 sulaco-01962cs gvfsd[712]: A connection to the bus can't be made
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping D-Bus User Message Bus...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Virtual filesystem service - Apple File Conduit monitor...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Virtual filesystem service...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Virtual filesystem service - digital camera monitor...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Virtual filesystem metadata service...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Virtual filesystem service - disk device monitor...
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopping Sound Service...
abr 25 22:23:28 sulaco-01962cs systemd[600]: dbus.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped D-Bus User Message Bus.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gvfs-udisks2-volume-monitor.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Virtual filesystem service - disk device monitor.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gvfs-daemon.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Virtual filesystem service.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gvfs-afc-volume-monitor.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Virtual filesystem service - Apple File Conduit monitor.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gvfs-gphoto2-volume-monitor.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Virtual filesystem service - digital camera monitor.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gvfs-mtp-volume-monitor.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gvfs-goa-volume-monitor.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gvfs-metadata.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Virtual filesystem metadata service.
abr 25 22:23:28 sulaco-01962cs systemd[600]: pulseaudio.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped Sound Service.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped target Basic System.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped target Paths.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped target Sockets.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Stopped target Timers.
abr 25 22:23:28 sulaco-01962cs systemd[600]: dbus.socket: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Closed D-Bus User Message Bus Socket.
abr 25 22:23:28 sulaco-01962cs systemd[600]: dirmngr.socket: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Closed GnuPG network certificate management daemon.
abr 25 22:23:28 sulaco-01962cs systemd[600]: gpg-agent-browser.socket: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
abr 25 22:23:28 sulaco-01962cs systemd[600]: gpg-agent-extra.socket: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
abr 25 22:23:28 sulaco-01962cs systemd[600]: gpg-agent-ssh.socket: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Closed GnuPG cryptographic agent (ssh-agent emulation).
abr 25 22:23:28 sulaco-01962cs systemd[600]: gpg-agent.socket: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Closed GnuPG cryptographic agent and passphrase cache.
abr 25 22:23:28 sulaco-01962cs systemd[600]: pulseaudio.socket: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Closed Sound System.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Removed slice User Application Slice.
abr 25 22:23:28 sulaco-01962cs systemd[600]: app.slice: Consumed 2min 26.143s CPU time.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Reached target Shutdown.
abr 25 22:23:28 sulaco-01962cs systemd[600]: systemd-exit.service: Succeeded.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Finished Exit the Session.
abr 25 22:23:28 sulaco-01962cs systemd[600]: Reached target Exit the Session.


There seems to be an issue with the permissions with the pulse folder on .config. There seems to be also an issue with the .gnupg folder in home, which a "permission denied," warning every time I try to access it. I am not sure exactly what is going on. I am considering doing a reinstall, or downgrade to the last version of SparkyLinux that worked without issues on this laptop, which is quite old.
"웃어라. 온 세상이 너와 함께 웃을 것이다. 울어라. 너 혼자만 울게 될 것이다"
"Laugh, and the world laughs with you. Weep and you weep alone"

jgratero

#1
April 29, 2023, 10:24:28 PM
Still trying to figure this out. Apparently, UFW is breaking the machine's boot:



It might, or it might not, be related to this bug:

https://bugs.launchpad.net/ufw/+bug/1946804

Also, there seems to be an issue with a phantom storage unit detected by the multicard reader (there is nothing there) that might be complicating this issue. This was one of the references I've found on the problem:

https://askubuntu.com/questions/1228301/boot-delay-due-to-missing-scsi-removable-disk

It all points out to a reinstallation as the best possible solution. The system has nothing critical to me (yet). I still would like to know what is exactly the multicard reader picking up, though.
"웃어라. 온 세상이 너와 함께 웃을 것이다. 울어라. 너 혼자만 울게 될 것이다"
"Laugh, and the world laughs with you. Weep and you weep alone"

pavroo

#2
April 29, 2023, 10:51:00 PM
You can disable ufw to find out does it help.
Simply boot Sparky via the Advanced options-> recovery mode, login as root, then disable the unit:
Code Select
systemclt disable ufw
Nothing is easy as it looks. Danielle Steel
Join #sparkylinux.org at [url="//irc.libera.chat"]irc.libera.chat[/url]

jgratero

#3
April 30, 2023, 04:01:00 AM
I will try it. At least I've found out the reason why the USB formatter is picking up a "sdb" unit: The multicard reader is "detecting" a storage unit that is not really there.

"웃어라. 온 세상이 너와 함께 웃을 것이다. 울어라. 너 혼자만 울게 될 것이다"
"Laugh, and the world laughs with you. Weep and you weep alone"

jgratero

#4
April 30, 2023, 04:14:10 AM
lsblk is picking this phantom unit:

Code Select
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 223,6G  0 disk
├─sda1   8:1    0 219,5G  0 part /
└─sda2   8:2    0     4G  0 part [SWAP]
sdb      8:16   1     0B  0 disk
"웃어라. 온 세상이 너와 함께 웃을 것이다. 울어라. 너 혼자만 울게 될 것이다"
"Laugh, and the world laughs with you. Weep and you weep alone"

jgratero

#5
May 01, 2023, 04:16:41 AM
Quote from: jgratero on April 30, 2023, 04:14:10 AMlsblk is picking this phantom unit:

Code Select
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 223,6G  0 disk
├─sda1   8:1    0 219,5G  0 part /
└─sda2   8:2    0     4G  0 part [SWAP]
sdb      8:16   1     0B  0 disk


ChatGPT has a very interesting take on this issue:



QuoteThe sdb storage unit that lsblk is picking up in the multicard reader is likely a virtual block device that is created by the multicard reader's firmware or driver. This virtual block device is created regardless of whether there is a physical card present in the reader or not.

One probable cause of this issue could be a faulty or outdated driver for the multicard reader. Another possible cause could be an issue with the firmware of the multicard reader. It is also possible that the issue is caused by a misconfiguration of the system or a conflict with another device driver.

To solve this issue, you can try the following solutions:

1. Update the driver for the multicard reader to the latest version, which may fix any bugs or issues that were present in the previous version.

2. Check if there is an update for the firmware of the multicard reader, and if so, update it to the latest version.

3. Try to identify and resolve any conflicts with other device drivers or misconfigurations in the system.

4. If the above solutions do not work, you can try disabling the virtual block device that is created by the multicard reader. You can do this by using the udev rule to ignore the device when it is detected by the system.

Overall, it is important to identify the root cause of the issue to ensure that it does not occur again in the future.
"웃어라. 온 세상이 너와 함께 웃을 것이다. 울어라. 너 혼자만 울게 될 것이다"
"Laugh, and the world laughs with you. Weep and you weep alone"

jgratero

#6
May 01, 2023, 06:46:49 AM
Well, this is indeed fascinating.

ChatGPT and I have had a well-in-dept conversation about my laptop, and its conclusions are interesting, to say the least. I began with this:

QuoteThis is an excerpt of the boot sequence of a Lenovo Thinkpad 13 model 01962cs, that is running SparkyLinux. The boot sequence of this machine is breaking and stalling at the point shown on the excerpt, and the machine never finishes it. Again, this is happening randomly. On occasions, the machine can boot. Using this excerpt, theorize about the possible causes for the breaking of the boot sequence, and propose solutions to the problem or problems. Keep in mind that this excerpt comes from an OCR rendition of a photo, and that it might contain transcription errors.

 7.1792881 sd 8:0:8:0: [sda] 468862128 512-btite logical blocks: (240 GB/224 GiB)
     7.1827821 sd 8:0:0:0: [sda] Write Protect is off
I    7.10.151    sd 0:0:0:8: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
     7.2805121   psmouse serioS: trackpoint: IBM TrackPoint firmware: 0x8e, buttons: 3/3
     7.289607]    sda: sda1 sda2
     7224297]    sd 0:8:0:0: [sda] Attached SCSI disk
Begin: Loading  essential drivers ... done.
Begin: Running   /scripts/init-premount                7.4524601 input: TPPSr2 IBM TrackPoint as /devices/platform/18842/serio4/serio5/input/input13
     8.1984291   scsi 6:8:0:0: Direct-Access           Generic- Multi-Card            1.00 PQ: 8 ANSI: 0 CCS
     0234023]    sd 6:0:0:8: [sda] Attached SCSI removable disk
1 115.101793]    [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5,80:80:01:48:29:52:39:26:24:08:00 SRC=192.168.8.1 DST=224.8.0.1 LEN=36 TOS=Ox00 PREC=Ox00 TTL=1 ID=0 PR0TO=2
I 115.110143]    [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5,00:00:01:48:29:52:39:26:24:08:88 SRC=192.168.2.1 DST=224.0.8.1 LEN=36 TOS=Ox00 PREC=8x00 TTL=1 ID=0 PROT0=2
   115.114344]   [UFW BLOCK] IN=eth0 OUT= MAC=01:00:5e:00:80:01:48:29:52:39:26:24:08:80 SRC=192.168.22.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=8x00 TTL=1 ID=0 PROT0=2
   124.6431041   [UPS BLOCK] IN=eth0 OUT= MAC=c8:0:a9:25:09:67:d4:5d:64:65:65:63:08:08 SRC=192.168.0.177 DST=192.168.0.17 LEN=52 TOS=0x00 PREC=0x00 TTL=128 18=50786 

ChatGPT's reply:

QuoteBased on the provided excerpt, there are several possible causes for the breaking and stalling of the boot sequence of the Lenovo Thinkpad 13 model 01962cs running SparkyLinux:

1. Disk failure: There may be a problem with the hard drive or the SATA controller, which is causing the boot sequence to stall. The error messages related to the disk indicate that there are SCSI disks being attached and detached, which could be a sign of disk failure or corruption.

2. Driver issues: The error messages related to the input devices and the network interface suggest that there may be driver issues. The input device driver for the IBM TrackPoint may be causing a problem, and the network interface may be blocked by the UFW firewall.

3. Hardware issues: There may be a problem with other hardware components, such as the RAM or the motherboard, which is causing the boot sequence to stall randomly.

Possible solutions to these problems could include:

1. Disk failure: Replace the hard drive or the SATA controller and reinstall the operating system.

2. Driver issues: Update the drivers for the input devices and the network interface, or try disabling the firewall to see if it resolves the issue.

3. Hardware issues: Run hardware diagnostic tests to identify any faulty components, and replace them as needed.

I kept inquiring, of course.

QuoteAs per the previous answer provided by you, please consider this fact: The OS was recently upgraded. In light of this fact, please revise your conclusions.

ChatGPT obliged:

QuoteIf the OS was recently upgraded, this adds another possible cause for the breaking and stalling of the boot sequence:

4. Incompatibility issues: The upgrade may have introduced incompatibilities with the hardware or drivers, which is causing the boot sequence to stall. This can happen if the upgraded OS version requires newer hardware or drivers that are not available or compatible with the current system.

Possible solutions to this problem could include:

4. Incompatibility issues: Roll back the OS upgrade to the previous version and see if the boot sequence stabilizes. Alternatively, check for any available updates or patches for the upgraded OS that may address the compatibility issues, or try installing alternative Linux distributions that are known to be compatible with the system hardware.

I asked again. I knew my SSD was recent.

QuoteConsider an additional factor: The hard drive, a Kingston 240GB A400 SATA 3 2.5" Internal SSD SA400S37, is two years old. An S.M.A.R.T. scan shows no issues. In light of this, please revise your conclusions.

ChatGPT remained firm:

QuoteConsidering the additional factor that the hard drive, a Kingston 240GB A400 SATA 3 2.5" Internal SSD SA400S37, is two years old and a S.M.A.R.T. scan shows no issues, the possible causes and solutions for the breaking and stalling of the boot sequence could be revised as follows:

1. Hardware issues: The hard drive may be failing, even if the S.M.A.R.T. scan shows no issues. In some cases, early signs of failure may not be picked up by S.M.A.R.T. scans, and this can cause the boot sequence to stall. Another possibility is that there may be issues with other hardware components, such as the RAM or motherboard.

Possible solutions to this problem could include:

1. Hardware issues: Test the hard drive using a different utility, such as HD Tune, to see if there are any issues. Consider replacing the hard drive if the test shows any signs of failure. Additionally, test other hardware components, such as the RAM or motherboard, to ensure they are functioning properly.

2. Software issues: The boot sequence may be stalling due to issues with the operating system or the bootloader. This could be caused by recent upgrades or changes to the system configuration.

Possible solutions to this problem could include:

2. Software issues: Boot into a live CD or USB to perform a system diagnostic, repair or reinstall the bootloader, or perform a fresh installation of the operating system. It may also be helpful to review the system logs to identify any specific errors that could be causing the boot sequence to stall.

3. Power supply issues: The power supply unit may be failing, which can cause the system to stall during the boot sequence. This is more likely if the system is experiencing random shutdowns or other power-related issues.

Possible solutions to this problem could include:

3. Power supply issues: Test the power supply unit using a multimeter or replace it with a new one to see if this resolves the issue. It may also be helpful to ensure that the system is not being overloaded with too many devices or peripherals that could be drawing too much power.

I asked for more information:

QuotePlease expand your conclusions on the SATA controller.

ChatGPT:

QuoteThe SATA controller is responsible for managing the communication between the motherboard and the storage devices connected to it. If the controller is malfunctioning, it can cause data transfer issues, leading to boot failures and other performance problems. The fact that the boot sequence is breaking randomly and stalling at different points, and that the error messages are related to the storage devices, suggests that the issue may be with the SATA controller.

Upgrading the OS may have caused compatibility issues with the SATA controller driver, leading to intermittent failures during the boot process. It's also possible that the SATA controller is beginning to fail after several years of use, which could explain the random and unpredictable nature of the boot failures. While the S.M.A.R.T. scan may not have detected any issues with the hard drive, it may not necessarily catch problems with the controller.

If the issue is related to the SATA controller, one possible solution could be to update the firmware or driver for the controller. It may also be necessary to replace the controller if it is determined to be faulty. However, identifying the exact cause of the issue may require further diagnostic testing and troubleshooting.

Of course, I had to be honest with ChatGPT:

QuoteConsider an additional factor. This Lenovo laptop is 12 years old.

And ChatGPT was honest with me:

QuoteThe fact that the Lenovo Thinkpad 13 model 01962cs is 12 years old is an important factor to consider in the diagnosis of the boot sequence issues. Given its age, it is possible that the hardware components, including the SATA controller and the storage devices, may be nearing the end of their lifespan.

Over time, wear and tear on hardware components can cause them to malfunction or fail. This can result in issues such as boot failures and slow performance. Additionally, newer operating systems and software may require more resources than older hardware can handle, leading to compatibility issues and performance problems.

In light of the age of the laptop, it may be worth considering whether it is time to retire the machine and upgrade to a newer model. Alternatively, if the issue is determined to be with a specific hardware component, such as the SATA controller or storage device, it may be possible to replace that component and extend the life of the machine. However, given the age of the laptop, replacement parts may be more difficult to find and may be more expensive than purchasing a new machine.
"웃어라. 온 세상이 너와 함께 웃을 것이다. 울어라. 너 혼자만 울게 될 것이다"
"Laugh, and the world laughs with you. Weep and you weep alone"

SparkyBookworm

#7
May 09, 2023, 04:25:26 PM
 Interesting Ai chat, that linux can't overcome critical hardware failure.

jgratero

#8
May 10, 2023, 05:32:24 AM
Quote from: SparkyBookworm on May 09, 2023, 04:25:26 PMInteresting Ai chat, that linux can't overcome critical hardware failure.

In the end, it was a hardware issue. The laptop worked perfectly with LXQT 5.16. Checking the hardware, I found no issues.
"웃어라. 온 세상이 너와 함께 웃을 것이다. 울어라. 너 혼자만 울게 될 것이다"
"Laugh, and the world laughs with you. Weep and you weep alone"
Print
Go Up Pages1
User actions

View the most recent posts on the forum