"auto adjusting please wait" then nothing on 5.10.0-8-amd64 (4.19.0-17-amd64 works)
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Ubuntu Linux 16.04, Debian 10, LineageOS 14.1
Posts: 1,572
Rep:
"auto adjusting please wait" then nothing on 5.10.0-8-amd64 (4.19.0-17-amd64 works)
I upgraded my Dell Optiplex 755 to Debian Bullseye from Debian Buster. The upgrade went fine, but it just gives a blank screen using the newer kernel option (5.10.0-8-amd64). Instead, it simply says, "auto adjusting please wait", and then the blank screen. However, it does work properly work when I boot with kernel 4.19.0-17-amd64 (which I'm using to currently type this).
Any idea how to fix this so that the default kernel boot option (5.10.0-8-amd64) works?
Last edited by mark_alfred; 08-21-2021 at 12:00 PM.
Boot to kernel 5, shutdown, boot to kernel 4.
Compare files /var/log/Xorg.0.log (current kernel 4) and /var/log/Xorg.0.log.old (previous log which should be from kernel 5).
You can also check the journal for clues by getting boot information for both as such:
The above commands will produce a text file in the directory the command is run.
If you need help with trying to find clues within these files use the "Post Reply" instead of "Quick Reply" and attach the files rather than posting the lengthy outputs.
At what point exactly does that message appear? Before bootloader? Does the Dell banner show up during POST? Is Grub configured to automatically boot right into the default entry, skipping the Grub menu? Which type cable is connected to your display? IME, Dell Optiplex 7nn series have a funky BIOS that doesn't always like what it sees when getting EDID from a display.
If that message only appears after the kernel/initrd loading begins, try changing or removing (e.g. splash=silent, quiet) one of the graphics-related (linu) command line options in Grub, or appending one, such as the native mode of your display, e.g. video=1920x1080, or plymouth.enable=0, plymouth=0 or noplymouth. Test if any work by striking the E key at the Grub menu to edit, or make permanent via /etc/default/grub and regenerating /boot/grub/grub.cfg.
Pop the cover and inspect the large electrolytic capacitors' tops for flatness, and their bodies for oozing. Visit badcaps.net for details. If using a DVI connection from a Dell PCIe add-in card, try reseating it.
Distribution: Ubuntu Linux 16.04, Debian 10, LineageOS 14.1
Posts: 1,572
Original Poster
Rep:
Quote:
Originally Posted by mrmazda
At what point exactly does that message appear? Before bootloader?
If I understand the term "bootloader" correctly, I believe the message appears right after the bootloader attempts to load the default choice (5.10.0-8-amd64). The "auto adjusting" message appears to be coming more from the screen than from the computer. To get the option of the 4.19.0-17 kernel, I have to quickly choose the further options choice, which gives me an opportunity to chose this kernel (there are two choices, that being kernel 5 and kernel 4 -- choosing kernel 5 here results in the blank screen). Otherwise, within seconds, it tries to boot the 5.10.0-8 kernel, which leads to the message appearing briefly followed by a blank screen.
Quote:
Originally Posted by Brains
Boot to kernel 5, shutdown, boot to kernel 4.
Compare files /var/log/Xorg.0.log (current kernel 4) and /var/log/Xorg.0.log.old (previous log which should be from kernel 5).
I tried this. The previous log isn't from kernel 5. It seems that kernel 5 is simply not booted into. When the attempt is made to boot into kernel 5, I'm only able to shutdown by pressing the power button (or by unplugging it).
If I understand the term "bootloader" correctly, I believe the message appears right after the bootloader attempts to load the default choice (5.10.0-8-amd64). The "auto adjusting" message appears to be coming more from the screen than from the computer.
The display is receiving an unsupported mode. The message you see amounts to a report to you from the display that it can't make sense of the input it's receiving. At the time you would select the alternate kernel, instead strike the E key, and append a mode you know the display supports to the linu line (which may be wrapped onto more than one line), e.g. video=1920x1080@60. If you still get the message, and it doesn't go away after a couple of minutes or more, try keying in Ctrl-Alt-F3. Does a login prompt appear?
Since nothing appears on screen, and the kernel is probably not booted at all since Xorg.0.log has no record of kernel 5.10. Kinda sounds like an initrd.img issue. Would be nice to know if there was anything related to kernel 5.10 in the journalctl output for an attempt with that kernel. The command: journalctl --list-boots shows which is which. If you attempt to boot the 5.10 kernel and note the time, when you then boot into the 4.19 kernel you can run that command to see if there is a boot record for that specific time frame when you tried. If there is nothing in the specific time frame, suggest the initrd.img didn't do anything, it gets things ready and loads the kernel.
Ensure all entries in /boot/grub/grub.cfg include the initrd.img in the last line, if there is something else with file extension .img in /boot, like /boot/intel-uc.img (Intel microcode in this case), the initrd.img may have not been included as grub/os-prober only included the intel-uc.img. This will happen for other OS entries only, not the OS that os-prober was used to generate the entries.
Distribution: Ubuntu Linux 16.04, Debian 10, LineageOS 14.1
Posts: 1,572
Original Poster
Rep:
Brains, back on the 21st, apparently I did succeed in creating a journal via "journalctl -b -1 > kernel5boot.txt", since I found the file.
Here is the file kernel5boot.txt:
Code:
-- Journal begins at Sun 2021-08-15 20:35:52 EDT, ends at Sat 2021-08-21 20:08:14 EDT. --
Aug 21 10:49:07 debian systemd[960]: gpgconf: error running '/usr/lib/gnupg/scdaemon': probably not installed
Aug 21 10:49:07 debian systemd-xdg-autostart-generator[973]: stat() failed on /home/mark/.config/autostart/gnome-ring.desktop, ignoring: No such file or directory
Aug 21 10:49:07 debian systemd[955]: Queued start job for default target Main User Target.
Aug 21 10:49:07 debian systemd[955]: Created slice User Application Slice.
Aug 21 10:49:07 debian systemd[955]: Reached target Paths.
Aug 21 10:49:07 debian systemd[955]: Reached target Timers.
Aug 21 10:49:07 debian systemd[955]: Starting D-Bus User Message Bus Socket.
Aug 21 10:49:07 debian systemd[955]: Listening on GnuPG network certificate management daemon.
Aug 21 10:49:07 debian systemd[955]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Aug 21 10:49:07 debian env[977]: /usr/bin/python3: No module named radicale
Aug 21 10:49:07 debian systemd[955]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Aug 21 10:49:07 debian systemd[955]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Aug 21 10:49:07 debian systemd[955]: Listening on GnuPG cryptographic agent and passphrase cache.
Aug 21 10:49:07 debian systemd[955]: Listening on Multimedia System.
Aug 21 10:49:07 debian systemd[955]: Listening on debconf communication socket.
Aug 21 10:49:07 debian systemd[955]: Listening on Sound System.
Aug 21 10:49:07 debian systemd[955]: Listening on D-Bus User Message Bus Socket.
Aug 21 10:49:07 debian systemd[955]: Reached target Sockets.
Aug 21 10:49:07 debian systemd[955]: Reached target Basic System.
Aug 21 10:49:07 debian systemd[955]: Started Multimedia Service.
Aug 21 10:49:07 debian systemd[955]: Starting Sound Service...
Aug 21 10:49:07 debian systemd[955]: Started A simple CalDAV (calendar) and CardDAV (contact) server.
Aug 21 10:49:07 debian systemd[955]: Started D-Bus User Message Bus.
Aug 21 10:49:07 debian pipewire[975]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
Aug 21 10:49:07 debian systemd[955]: radicale.service: Main process exited, code=exited, status=1/FAILURE
Aug 21 10:49:07 debian systemd[955]: radicale.service: Failed with result 'exit-code'.
Aug 21 10:49:08 debian systemd[955]: radicale.service: Scheduled restart job, restart counter is at 1.
Aug 21 10:49:08 debian systemd[955]: Stopped A simple CalDAV (calendar) and CardDAV (contact) server.
Aug 21 10:49:08 debian systemd[955]: Started A simple CalDAV (calendar) and CardDAV (contact) server.
Aug 21 10:49:08 debian env[989]: /usr/bin/python3: No module named radicale
Aug 21 10:49:08 debian systemd[955]: radicale.service: Main process exited, code=exited, status=1/FAILURE
Aug 21 10:49:08 debian systemd[955]: radicale.service: Failed with result 'exit-code'.
Aug 21 10:49:08 debian systemd[955]: Started Sound Service.
Aug 21 10:49:08 debian systemd[955]: Reached target Main User Target.
Aug 21 10:49:08 debian systemd[955]: Startup finished in 1.159s.
Aug 21 10:49:08 debian systemd[955]: radicale.service: Scheduled restart job, restart counter is at 2.
Aug 21 10:49:08 debian systemd[955]: Stopped A simple CalDAV (calendar) and CardDAV (contact) server.
Aug 21 10:49:08 debian systemd[955]: Started A simple CalDAV (calendar) and CardDAV (contact) server.
Aug 21 10:49:08 debian env[1004]: /usr/bin/python3: No module named radicale
Aug 21 10:49:08 debian systemd[955]: radicale.service: Main process exited, code=exited, status=1/FAILURE
Aug 21 10:49:08 debian systemd[955]: radicale.service: Failed with result 'exit-code'.
Aug 21 10:49:08 debian systemd[955]: radicale.service: Scheduled restart job, restart counter is at 3.
Aug 21 10:49:08 debian systemd[955]: Stopped A simple CalDAV (calendar) and CardDAV (contact) server.
Aug 21 10:49:08 debian systemd[955]: Started A simple CalDAV (calendar) and CardDAV (contact) server.
Aug 21 10:49:08 debian env[1005]: /usr/bin/python3: No module named radicale
Aug 21 10:49:08 debian systemd[955]: radicale.service: Main process exited, code=exited, status=1/FAILURE
Aug 21 10:49:08 debian systemd[955]: radicale.service: Failed with result 'exit-code'.
Aug 21 10:49:08 debian systemd[955]: radicale.service: Scheduled restart job, restart counter is at 4.
Aug 21 10:49:08 debian systemd[955]: Stopped A simple CalDAV (calendar) and CardDAV (contact) server.
Aug 21 10:49:08 debian systemd[955]: Started A simple CalDAV (calendar) and CardDAV (contact) server.
Aug 21 10:49:08 debian env[1006]: /usr/bin/python3: No module named radicale
Aug 21 10:49:08 debian systemd[955]: radicale.service: Main process exited, code=exited, status=1/FAILURE
Aug 21 10:49:08 debian systemd[955]: radicale.service: Failed with result 'exit-code'.
Aug 21 10:49:09 debian systemd[955]: radicale.service: Scheduled restart job, restart counter is at 5.
Aug 21 10:49:09 debian systemd[955]: Stopped A simple CalDAV (calendar) and CardDAV (contact) server.
Aug 21 10:49:09 debian systemd[955]: radicale.service: Start request repeated too quickly.
Aug 21 10:49:09 debian systemd[955]: radicale.service: Failed with result 'exit-code'.
Aug 21 10:49:09 debian systemd[955]: Failed to start A simple CalDAV (calendar) and CardDAV (contact) server.
Aug 21 10:49:09 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.9' (uid=1000 pid=987 comm="xfce4-session ")
Aug 21 10:49:09 debian systemd[955]: Starting Accessibility services bus...
Aug 21 10:49:09 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'org.a11y.Bus'
Aug 21 10:49:09 debian systemd[955]: Started Accessibility services bus.
Aug 21 10:49:09 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating service name='org.xfce.Xfconf' requested by ':1.11' (uid=1000 pid=987 comm="xfce4-session ")
Aug 21 10:49:09 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'org.xfce.Xfconf'
Aug 21 10:49:09 debian at-spi-bus-launcher[1054]: dbus-daemon[1054]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=987 comm="xfce4-session ")
Aug 21 10:49:09 debian at-spi-bus-launcher[1054]: dbus-daemon[1054]: Successfully activated service 'org.a11y.atspi.Registry'
Aug 21 10:49:09 debian at-spi-bus-launcher[1064]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Aug 21 10:49:09 debian systemd[955]: Started GnuPG cryptographic agent and passphrase cache.
Aug 21 10:49:09 debian gpg-agent[1071]: gpg-agent (GnuPG) 2.2.27 starting in supervised mode.
Aug 21 10:49:09 debian gpg-agent[1071]: using fd 3 for browser socket (/run/user/1000/gnupg/S.gpg-agent.browser)
Aug 21 10:49:09 debian gpg-agent[1071]: using fd 4 for ssh socket (/run/user/1000/gnupg/S.gpg-agent.ssh)
Aug 21 10:49:09 debian gpg-agent[1071]: using fd 5 for extra socket (/run/user/1000/gnupg/S.gpg-agent.extra)
Aug 21 10:49:09 debian gpg-agent[1071]: using fd 6 for std socket (/run/user/1000/gnupg/S.gpg-agent)
Aug 21 10:49:09 debian gpg-agent[1071]: listening on: std=6 extra=5 browser=3 ssh=4
Aug 21 10:49:09 debian systemd[955]: gpg-agent.service: Succeeded.
Aug 21 10:49:09 debian systemd[955]: Started GnuPG cryptographic agent and passphrase cache.
Aug 21 10:49:09 debian gpg-agent[1074]: gpg-agent (GnuPG) 2.2.27 starting in supervised mode.
Aug 21 10:49:09 debian gpg-agent[1074]: using fd 3 for browser socket (/run/user/1000/gnupg/S.gpg-agent.browser)
Aug 21 10:49:09 debian gpg-agent[1074]: using fd 4 for ssh socket (/run/user/1000/gnupg/S.gpg-agent.ssh)
Aug 21 10:49:09 debian gpg-agent[1074]: using fd 5 for extra socket (/run/user/1000/gnupg/S.gpg-agent.extra)
Aug 21 10:49:09 debian gpg-agent[1074]: using fd 6 for std socket (/run/user/1000/gnupg/S.gpg-agent)
Aug 21 10:49:09 debian gpg-agent[1074]: listening on: std=6 extra=5 browser=3 ssh=4
Aug 21 10:49:10 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.14' (uid=1000 pid=1076 comm="xfwm4 --display :0.0 --sm-client-id 289b16d50-20ba")
Aug 21 10:49:10 debian systemd[955]: Starting Virtual filesystem service...
Aug 21 10:49:10 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'org.gtk.vfs.Daemon'
Aug 21 10:49:10 debian systemd[955]: Started Virtual filesystem service.
Aug 21 10:49:12 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.19' (uid=1000 pid=1125 comm="xfdesktop --display :0.0 --sm-client-id 2de4528a7-")
Aug 21 10:49:12 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating via systemd: service name='org.freedesktop.Notifications' unit='xfce4-notifyd.service' requested by ':1.21' (uid=1000 pid=1130 comm="xfce4-power-manager --restart --sm-client-id 22df8")
Aug 21 10:49:12 debian systemd[955]: Starting XFCE notifications service...
Aug 21 10:49:13 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'org.freedesktop.Notifications'
Aug 21 10:49:13 debian systemd[955]: Started XFCE notifications service.
Aug 21 10:49:17 debian systemd[955]: run-user-114-gvfs.mount: Succeeded.
Aug 21 10:49:17 debian systemd[955]: run-user-114.mount: Succeeded.
Aug 21 10:49:19 debian org.freedesktop.thumbnails.Thumbnailer1[1132]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Aug 21 10:49:19 debian org.freedesktop.thumbnails.Thumbnailer1[1132]: Registered thumbnailer /usr/share/blender/scripts/blender-thumbnailer.py %i %o
Aug 21 10:49:19 debian org.freedesktop.thumbnails.Thumbnailer1[1132]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Aug 21 10:49:19 debian org.freedesktop.thumbnails.Thumbnailer1[1132]: Registered thumbnailer atril-thumbnailer -s %s %u %o
Aug 21 10:49:19 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.20' (uid=1000 pid=1132 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd ")
Aug 21 10:49:19 debian systemd[955]: Starting Virtual filesystem service - disk device monitor...
Aug 21 10:49:20 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Aug 21 10:49:20 debian systemd[955]: Started Virtual filesystem service - disk device monitor.
Aug 21 10:49:20 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.20' (uid=1000 pid=1132 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd ")
Aug 21 10:49:20 debian systemd[955]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
Aug 21 10:49:20 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Aug 21 10:49:20 debian systemd[955]: Started Virtual filesystem service - GNOME Online Accounts monitor.
Aug 21 10:49:20 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.20' (uid=1000 pid=1132 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd ")
Aug 21 10:49:20 debian systemd[955]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Aug 21 10:49:20 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Aug 21 10:49:20 debian systemd[955]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Aug 21 10:49:20 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.20' (uid=1000 pid=1132 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd ")
Aug 21 10:49:20 debian systemd[955]: Starting Virtual filesystem service - Apple File Conduit monitor...
Aug 21 10:49:20 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Aug 21 10:49:20 debian systemd[955]: Started Virtual filesystem service - Apple File Conduit monitor.
Aug 21 10:49:20 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.20' (uid=1000 pid=1132 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd ")
Aug 21 10:49:20 debian systemd[955]: Starting Virtual filesystem service - digital camera monitor...
Aug 21 10:49:21 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating service name='ca.desrt.dconf' requested by ':1.38' (uid=1000 pid=1187 comm="light-locker ")
Aug 21 10:49:22 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Aug 21 10:49:22 debian systemd[955]: Started Virtual filesystem service - digital camera monitor.
Aug 21 10:49:22 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Aug 21 10:49:22 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'ca.desrt.dconf'
Aug 21 10:49:22 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating via systemd: service name='org.xfce.FileManager' unit='thunar.service' requested by ':1.19' (uid=1000 pid=1125 comm="xfdesktop --display :0.0 --sm-client-id 2de4528a7-")
Aug 21 10:49:23 debian systemd[955]: Starting Thunar file manager...
Aug 21 10:49:23 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.19' (uid=1000 pid=1125 comm="xfdesktop --display :0.0 --sm-client-id 2de4528a7-")
Aug 21 10:49:23 debian systemd[955]: Starting Virtual filesystem metadata service...
Aug 21 10:49:23 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'org.gtk.vfs.Metadata'
Aug 21 10:49:23 debian systemd[955]: Started Virtual filesystem metadata service.
Aug 21 10:49:23 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'org.xfce.FileManager'
Aug 21 10:49:23 debian systemd[955]: Started Thunar file manager.
Aug 21 10:49:24 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating service name='org.kde.kdeconnect' requested by ':1.55' (uid=1000 pid=1129 comm="kdeconnect-indicator -session 2c171f410-b690-4e29-")
Aug 21 10:49:24 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'org.kde.kdeconnect'
Aug 21 10:52:57 debian pkexec[1511]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
Aug 21 16:20:06 debian xfce4-notifyd[1137]: Failed to set text 'Meeting every Friday: Help us update the Free Software Directory from Donald Robertson, III, FSF
*Read and share online: <https://www.fsf' from markup due to error parsing markup: Error on line 2 char 34: Odd character “/”, expected a “>” character to end the empty-element tag “https:”
Aug 21 17:31:49 debian dbus-daemon[980]: [session uid=1000 pid=980] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.49' (uid=1000 pid=1255 comm="/usr/bin/Thunar --daemon ")
Aug 21 17:31:49 debian org.freedesktop.thumbnails.Thumbnailer1[6134]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Aug 21 17:31:49 debian org.freedesktop.thumbnails.Thumbnailer1[6134]: Registered thumbnailer /usr/share/blender/scripts/blender-thumbnailer.py %i %o
Aug 21 17:31:49 debian org.freedesktop.thumbnails.Thumbnailer1[6134]: Registered thumbnailer /usr/bin/gdk-pixbuf-thumbnailer -s %s %u %o
Aug 21 17:31:49 debian org.freedesktop.thumbnails.Thumbnailer1[6134]: Registered thumbnailer atril-thumbnailer -s %s %u %o
Aug 21 17:31:49 debian dbus-daemon[980]: [session uid=1000 pid=980] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Aug 21 17:32:54 debian systemd[955]: thunar.service: Main process exited, code=killed, status=9/KILL
Aug 21 17:32:54 debian systemd[955]: thunar.service: Failed with result 'signal'.
Aug 21 17:32:54 debian systemd[955]: thunar.service: Consumed 24.467s CPU time.
Aug 21 20:00:53 debian at-spi-bus-launcher[1064]: X connection to :0 broken (explicit kill or server shutdown).
Aug 21 20:00:53 debian systemd[955]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Aug 21 20:00:53 debian systemd[955]: xfce4-notifyd.service: Failed with result 'exit-code'.
Aug 21 20:00:53 debian systemd[955]: gpg-agent.service: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Stopped target Main User Target.
Aug 21 20:00:53 debian systemd[955]: Stopping Accessibility services bus...
Aug 21 20:00:53 debian systemd[955]: Stopping D-Bus User Message Bus...
Aug 21 20:00:53 debian systemd[955]: Stopping Virtual filesystem service - Apple File Conduit monitor...
Aug 21 20:00:53 debian systemd[955]: Stopping Virtual filesystem service...
Aug 21 20:00:53 debian systemd[955]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
Aug 21 20:00:53 debian systemd[955]: Stopping Virtual filesystem service - digital camera monitor...
Aug 21 20:00:53 debian systemd[955]: Stopping Virtual filesystem metadata service...
Aug 21 20:00:53 debian systemd[955]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
Aug 21 20:00:53 debian systemd[955]: Stopping Virtual filesystem service - disk device monitor...
Aug 21 20:00:53 debian pipewire-media-session[981]: error id:0 seq:158 res:-32 (Broken pipe): connection error
Aug 21 20:00:53 debian systemd[955]: Stopping Multimedia Service...
Aug 21 20:00:53 debian systemd[955]: Stopping Sound Service...
Aug 21 20:00:53 debian systemd[955]: gvfs-goa-volume-monitor.service: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
Aug 21 20:00:53 debian systemd[955]: gvfs-mtp-volume-monitor.service: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
Aug 21 20:00:53 debian systemd[955]: gvfs-gphoto2-volume-monitor.service: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Stopped Virtual filesystem service - digital camera monitor.
Aug 21 20:00:53 debian systemd[955]: pipewire.service: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Stopped Multimedia Service.
Aug 21 20:00:53 debian systemd[955]: gvfs-udisks2-volume-monitor.service: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Stopped Virtual filesystem service - disk device monitor.
Aug 21 20:00:53 debian systemd[955]: gvfs-afc-volume-monitor.service: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Stopped Virtual filesystem service - Apple File Conduit monitor.
Aug 21 20:00:53 debian systemd[955]: gvfs-metadata.service: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Stopped Virtual filesystem metadata service.
Aug 21 20:00:53 debian systemd[955]: run-user-1000-gvfs.mount: Succeeded.
Aug 21 20:00:53 debian systemd[955]: dbus.service: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Stopped D-Bus User Message Bus.
Aug 21 20:00:53 debian systemd[955]: dbus.service: Consumed 7.444s CPU time.
Aug 21 20:00:53 debian systemd[955]: at-spi-dbus-bus.service: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Stopped Accessibility services bus.
Aug 21 20:00:53 debian systemd[955]: at-spi-dbus-bus.service: Consumed 4.349s CPU time.
Aug 21 20:00:53 debian systemd[955]: gvfs-daemon.service: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Stopped Virtual filesystem service.
Aug 21 20:00:53 debian systemd[955]: pulseaudio.service: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Stopped Sound Service.
Aug 21 20:00:53 debian systemd[955]: pulseaudio.service: Consumed 4min 54.564s CPU time.
Aug 21 20:00:53 debian systemd[955]: Stopped target Basic System.
Aug 21 20:00:53 debian systemd[955]: Stopped target Paths.
Aug 21 20:00:53 debian systemd[955]: Stopped target Sockets.
Aug 21 20:00:53 debian systemd[955]: Stopped target Timers.
Aug 21 20:00:53 debian systemd[955]: dbus.socket: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Closed D-Bus User Message Bus Socket.
Aug 21 20:00:53 debian systemd[955]: dirmngr.socket: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Closed GnuPG network certificate management daemon.
Aug 21 20:00:53 debian systemd[955]: gpg-agent-browser.socket: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Aug 21 20:00:53 debian systemd[955]: gpg-agent-extra.socket: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Aug 21 20:00:53 debian systemd[955]: gpg-agent-ssh.socket: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Aug 21 20:00:53 debian systemd[955]: gpg-agent.socket: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Closed GnuPG cryptographic agent and passphrase cache.
Aug 21 20:00:53 debian systemd[955]: pipewire.socket: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Closed Multimedia System.
Aug 21 20:00:53 debian systemd[955]: pk-debconf-helper.socket: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Closed debconf communication socket.
Aug 21 20:00:53 debian systemd[955]: pulseaudio.socket: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Closed Sound System.
Aug 21 20:00:53 debian systemd[955]: Removed slice User Application Slice.
Aug 21 20:00:53 debian systemd[955]: app.slice: Consumed 5min 32.877s CPU time.
Aug 21 20:00:53 debian systemd[955]: Reached target Shutdown.
Aug 21 20:00:53 debian systemd[955]: systemd-exit.service: Succeeded.
Aug 21 20:00:53 debian systemd[955]: Finished Exit the Session.
Aug 21 20:00:53 debian systemd[955]: Reached target Exit the Session.
I'll try this again as root.
Last edited by mark_alfred; 08-24-2021 at 07:52 PM.
Distribution: Ubuntu Linux 16.04, Debian 10, LineageOS 14.1
Posts: 1,572
Original Poster
Rep:
Quote:
Originally Posted by mrmazda
The display is receiving an unsupported mode. The message you see amounts to a report to you from the display that it can't make sense of the input it's receiving. At the time you would select the alternate kernel, instead strike the E key, and append a mode you know the display supports to the linu line (which may be wrapped onto more than one line), e.g. video=1920x1080@60. If you still get the message, and it doesn't go away after a couple of minutes or more, try keying in Ctrl-Alt-F3. Does a login prompt appear?
I did try editing it, but I wasn't sure what I was doing. I do note that it attempts to boot a display "@70", which doesn't work. Kernel4 also does this, but then switches to a display "@60".
I also did try Ctrl-Alt-F3 (and F2, F4, F5...) and this did not give me a command line.
This line may not all fit without running over onto the next line, so find quiet, then add a space and video=whatever.
There should be a file /var/log/Xorg.0.log on the installed system. We need to see it. If you don't find it, look in /home/<yourusername/.local/share/xorg/ for Xorg.0.log and upload it, preferably to http://pastebin.com or http://paste.debian.net/ rather than attaching.
Peruse any /etc/X11/xorg.conf and /etc/X11/xorg.conf.d/*.conf file for any line that looks like
Code:
Driver "intel"
If you find one, remove the "f" from its filename, or make any filename change that doesn't end in ".conf". Then reboot. If this doesn't help, do
Code:
apt purge xserver-xorg-video-intel
and reboot and report back. If that doesn't help, reinstall xserver-xorg-video-intel. Your Q35 might be just barely too old for support from the alternative modesetting DIX driver.
If you find it necessary to keep xserver-xorg-video-intel installed, and 5.x still won't work, try including within any existing file named /etc/X11/xorg.conf.d/*-intel.conf, or create a file named /etc/X11/xorg.conf.d/25-intel.conf to contain the following:
When I upgraded from Debian Woody to Sarge, the forums were so busy I vowed to never upgrade again (any OS).
I can see the benefits of botched upgrades for the proprietary OS vendors, sell more.
Been snorting Debian Testing for well over 10 years (addicted, don't tell my mom).
Testing keeps growing and eventually starts threatening to dictate how I allocate my time by playing the slightly dazed and confused angle.
I'm always prepared for a fresh install with all personal data in the Data drive. Get a list of all installed packages (apt list --installed > pac && cat pac | cut -d "/" -f1 > pacs && rm pac), maybe shrink the partition to bare minimum and make a dd backup image of the OS in case I forgot something, just mount the image from the new install, re-format and reinstall.
About once every 6-8 months. One good evening and I sleep with a smile (I think)
EDIT: With EFI, / partition don't have a boot sector, mounting most raw gpt partition images is as simple as: mount dd.img /mnt
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.