Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see:
viewtopic.php?t=158230
Ask for help with issues regarding the Installations of the Debian O/S.
maerqin
Posts: 8 Joined: 2021-05-16 08:42
#1
Post
by maerqin 2021-05-16 10:10
Dear Debian User Forums Users,
I recently installed debian on my computer (with kde plasma with sddm and rEFInd). When I boot up, debian needs a long time to start. I had previously GRUB 2 configured, but the same problem persisted. After I boot up my PC (and after rEFInd) a blank underscore flashes for more than one minute and text shows up. I thought it could be because of ext4, I tried to tweak fstab, but I it didn't help (or maybe I don't know how correctly). fstab is posted below as text and I also posted some big time jumps from dmesg (maybe this is also helpful). I thank all people in advance that try to help me solve this problem, because I need my computer by tomorrow for university.
How my screen looks like after underscore blinking
fstab
Code: Select all
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=da4a4c8d-85a9-4ba8-b8c2-18cc826a2b93 / ext4 defaults 1 0
# /boot/efi was on /dev/sda1 during installation
UUID=04E3-9E4B /boot/efi vfat umask=0077 0 1
# swap was on /dev/sda3 during installation
UUID=a638ec32-728d-4937-b117-a85710bb78fd none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
First big dmesg jump
Code: Select all
[ 5.029651] usb 3-1.5: SerialNumber: 27332748
[ 91.691653] PM: Image not found (code -22)
[ 91.696246] PM: Marking nosave pages: [mem 0x00000000-0x00000fff]
[ 91.696248] PM: Marking nosave pages: [mem 0x000a0000-0x000fffff]
[ 91.696251] PM: Marking nosave pages: [mem 0x13c95000-0x13c95fff]
[ 91.696252] PM: Marking nosave pages: [mem 0x13c9e000-0x13c9efff]
[ 91.696253] PM: Marking nosave pages: [mem 0x13caf000-0x13caffff]
[ 91.696254] PM: Marking nosave pages: [mem 0x13ccf000-0x13cd0fff]
[ 91.696255] PM: Marking nosave pages: [mem 0x13cde000-0x13cdffff]
[ 91.696256] PM: Marking nosave pages: [mem 0x13cfc000-0x13cfcfff]
[ 91.696257] PM: Marking nosave pages: [mem 0xde360000-0xdec04fff]
[ 91.696306] PM: Marking nosave pages: [mem 0xdf000000-0xffffffff]
Second big dmesg jump
Code: Select all
[ 94.187837] RTL8211E Gigabit Ethernet r8169-500:00: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=r8169-500:00, irq=IGNORE)
[ 94.410920] IPv6: ADDRCONF(NETDEV_UP): rename3: link is not ready
[ 97.430855] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 97.430897] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[ 153.443545] fuse init (API version 7.27)
[ 158.123479] rfkill: input handler disabled
-maerqin
Last edited by
maerqin on 2021-05-19 06:15, edited 2 times in total.
maerqin
Posts: 8 Joined: 2021-05-16 08:42
#3
Post
by maerqin 2021-05-16 14:24
Here is the output, but I still don't know how to fix it.
Code: Select all
897ms nvidia-persistenced.service
723ms systemd-logind.service
709ms udisks2.service
398ms systemd-modules-load.service
319ms dev-sda2.device
238ms fwupd.service
213ms upower.service
154ms ModemManager.service
151ms systemd-timesyncd.service
134ms user@1000.service
128ms accounts-daemon.service
121ms systemd-udevd.service
115ms NetworkManager.service
115ms avahi-daemon.service
108ms wpa_supplicant.service
103ms rsyslog.service
95ms systemd-journald.service
78ms systemd-fsck@dev-disk-by\x2duuid-04E3\x2d9E4B.service
68ms alsa-restore.service
62ms systemd-udev-trigger.service
46ms dev-disk-by\x2duuid-a638ec32\x2d728d\x2d4937\x2db117\x2da85710bb78fd.swap
44ms packagekit.service
43ms ifupdown-pre.service
42ms systemd-journal-flush.service
39ms apparmor.service
36ms colord.service
32ms switcheroo-control.service
23ms plymouth-quit-wait.service
22ms plymouth-quit.service
20ms networking.service
20ms polkit.service
20ms plymouth-start.service
18ms boot-efi.mount
18ms systemd-tmpfiles-setup.service
17ms pppd-dns.service
14ms user-runtime-dir@1000.service
12ms keyboard-setup.service
11ms plymouth-read-write.service
10ms systemd-remount-fs.service
10ms systemd-tmpfiles-setup-dev.service
10ms systemd-sysctl.service
10ms systemd-sysusers.service
10ms systemd-user-sessions.service
10ms sys-kernel-debug.mount
8ms systemd-update-utmp.service
6ms NetworkManager-dispatcher.service
6ms dev-mqueue.mount
6ms kmod-static-nodes.service
6ms systemd-update-utmp-runlevel.service
5ms dev-hugepages.mount
5ms slim.service
5ms systemd-random-seed.service
5ms console-setup.service
4ms rtkit-daemon.service
2ms sys-fs-fuse-connections.mount
FreewheelinFrank
Global Moderator
Posts: 2109 Joined: 2010-06-07 16:59Has thanked: 38 times Been thanked: 230 times
#4
Post
by FreewheelinFrank 2021-05-16 20:22
Nothing there that's not milliseconds. What does
say about startup time?
Try
after booting and see if anything shows up. (Space bar to view more lines).
maerqin
Posts: 8 Joined: 2021-05-16 08:42
#5
Post
by maerqin 2021-05-17 06:46
FreewheelinFrank wrote: Nothing there that's not milliseconds. What does
say about startup time?
Try
after booting and see if anything shows up. (Space bar to view more lines).
This is what systemd-analyze shows:
Code: Select all
Startup finished in 1min 32.027s (kernel) + 7.165s (userspace) = 1min 39.192s
graphical.target reached after 2.518s in userspace
On my previous distribution I had a boot time of about 30 seconds (on the same computer).
The jounalctl -b output is quite long. I have searched for errors in this file, and there are none after booting has finished (Or there is nothing I can decipher that is wrong).
sunrat
Administrator
Posts: 6478 Joined: 2006-08-29 09:12Location: Melbourne, AustraliaHas thanked: 118 times Been thanked: 474 times
#7
Post
by sunrat 2021-05-17 08:13
maerqin wrote: The jounalctl -b output is quite long. I have searched for errors in this file, and there are none after booting has finished (Or there is nothing I can decipher that is wrong).
You can filter journalctl with the "p" switch for priority. "b" means current boot, "b -1" shows entries for the previous boot. My most common usage is
For more options see
I don't see anything meaningful in what you have posted so far, apart from showing some mystery process is stalling the boot.
“ computer users can be divided into 2 categories: Remember to BACKUP!
maerqin
Posts: 8 Joined: 2021-05-16 08:42
#8
Post
by maerqin 2021-05-18 07:06
sunrat wrote: maerqin wrote: The jounalctl -b output is quite long. I have searched for errors in this file, and there are none after booting has finished (Or there is nothing I can decipher that is wrong).
You can filter journalctl with the "p" switch for priority. "b" means current boot, "b -1" shows entries for the previous boot. My most common usage is
For more options see
I don't see anything meaningful in what you have posted so far, apart from showing some mystery process is stalling the boot.
Here is the output of journalctl -b -p 3, but I plugged in a microphone and camera for zoom yesterday, so I think some of those errors are because of that:
Code: Select all
-- Logs begin at Tue 2021-05-18 09:21:43 CEST, end at Tue 2021-05-18 09:50:18 CEST. --
May 18 09:21:43 HP-WORKSTATION kernel: hid-generic 0003:0D8C:0134.0005: No inputs registered, leaving
May 18 09:21:44 HP-WORKSTATION kernel: usb 1-1.2: 3:1: cannot get freq at ep 0x86
May 18 09:21:44 HP-WORKSTATION kernel: usb 1-1.2: 3:2: cannot get freq at ep 0x86
May 18 09:21:44 HP-WORKSTATION kernel: usb 1-1.2: 3:3: cannot set freq 44100 to ep 0x86
May 18 09:21:44 HP-WORKSTATION kernel: usb 1-1.2: 3:4: cannot set freq 48000 to ep 0x86
May 18 09:21:44 HP-WORKSTATION kernel: uvcvideo: Failed to query (GET_INFO) UVC control 9 on unit 1: -32 (exp. 1).
May 18 09:27:26 HP-WORKSTATION kernel: usb 1-1.2: 3:3: cannot get freq at ep 0x86
maerqin
Posts: 8 Joined: 2021-05-16 08:42
#9
Post
by maerqin 2021-05-18 07:08
FreewheelinFrank wrote: Is there a wait between units loading, I wonder?
Here is the output of the command systemd-analyze critical-chain:
Code: Select all
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @2.312s
└─multi-user.target @2.311s
└─snapd.seeded.service @1.889s +422ms
└─snapd.service @963ms +924ms
└─basic.target @941ms
└─sockets.target @940ms
└─snapd.socket @937ms +3ms
└─sysinit.target @936ms
└─systemd-timesyncd.service @741ms +194ms
└─systemd-tmpfiles-setup.service @715ms +22ms
└─local-fs.target @714ms
└─boot-efi.mount @640ms +72ms
└─systemd-fsck@dev-disk-by\x2duuid-04E3\x2d9E4B.service @574ms +63ms
└─dev-disk-by\x2duuid-04E3\x2d9E4B.device @573ms
FreewheelinFrank
Global Moderator
Posts: 2109 Joined: 2010-06-07 16:59Has thanked: 38 times Been thanked: 230 times
#10
Post
by FreewheelinFrank 2021-05-18 12:04
I reckon Systemd is waiting 90s/1m30s for something, but I would have expected a message in the journal like "waiting for" or "a start job is running"...
sunrat
Administrator
Posts: 6478 Joined: 2006-08-29 09:12Location: Melbourne, AustraliaHas thanked: 118 times Been thanked: 474 times
#11
Post
by sunrat 2021-05-18 12:18
FreewheelinFrank wrote: I reckon Systemd is waiting 90s/1m30s for something, but I would have expected a message in the journal like "waiting for" or "a start job is running"...
That's what I was thinking but yes, it should show a message on the screen. There still is nothing in the posted outputs that looks revealing. Could try journalctl with -p4 instead of -p3 , that will show warnings as well as errors but may be rather lengthy.
I know nothing about slim, gnome, xmonad and rEFInd as I only use KDE with sddm so not sure if they could have anything to do with it. You shouldn't need to use rEFInd however, GRUB is usually fairly reliable when set up properly in my experience.
“ computer users can be divided into 2 categories: Remember to BACKUP!
wizard10000
Global Moderator
Posts: 598 Joined: 2019-04-16 23:15Location: southeastern usHas thanked: 79 times Been thanked: 89 times
#12
Post
by wizard10000 2021-05-18 17:08
fstab: the fifth and sixth fields on his root partition are reversed which is probably causing the machine to wait for "dump", which most likely is not installed (and shouldn't be). Should be 0 1 not 1 0.
we see things not as they are, but as we are.
p.H
Global Moderator
Posts: 3049 Joined: 2017-09-17 07:12Has thanked: 5 times Been thanked: 132 times
#13
Post
by p.H 2021-05-18 20:53
FreewheelinFrank wrote: I reckon Systemd is waiting 90s/1m30s for something
Where do you see this ? To me the 90s delay seems to happen in the initramfs, before systemd. The first message after the delay ("PM: Image not found") is about an hibernation image not being found in the swap (as expected if the system was not hibernated). This happens before the root filesystem is checked (fsck in the first screen shot) and mounted.
Booting in recovery mode may show more information.
FreewheelinFrank
Global Moderator
Posts: 2109 Joined: 2010-06-07 16:59Has thanked: 38 times Been thanked: 230 times
#14
Post
by FreewheelinFrank 2021-05-19 04:43
p.H wrote: FreewheelinFrank wrote: I reckon Systemd is waiting 90s/1m30s for something
Where do you see this ? To me the 90s delay seems to happen in the initramfs, before systemd. The first message after the delay ("PM: Image not found") is about an hibernation image not being found in the swap (as expected if the system was not hibernated). This happens before the root filesystem is checked (fsck in the first screen shot) and mounted.
Booting in recovery mode may show more information.
I was looking at the screen shot which is Systemd where the blinking cursor was reported to happen. That and the fact that Systemd shows a total start up time of 1.32m but most of the startup processes happen in milliseconds.
maerqin
Posts: 8 Joined: 2021-05-16 08:42
#15
Post
by maerqin 2021-05-19 06:14
wizard10000 wrote: fstab: the fifth and sixth fields on his root partition are reversed which is probably causing the machine to wait for "dump", which most likely is not installed (and shouldn't be). Should be 0 1 not 1 0.
I installed dump and changed fstab, but the problem still persists.
maerqin
Posts: 8 Joined: 2021-05-16 08:42
#16
Post
by maerqin 2021-05-19 06:19
sunrat wrote: FreewheelinFrank wrote: I reckon Systemd is waiting 90s/1m30s for something, but I would have expected a message in the journal like "waiting for" or "a start job is running"...
That's what I was thinking but yes, it should show a message on the screen. There still is nothing in the posted outputs that looks revealing. Could try journalctl with -p4 instead of -p3 , that will show warnings as well as errors but may be rather lengthy.
I know nothing about slim, gnome, xmonad and rEFInd as I only use KDE with sddm so not sure if they could have anything to do with it. You shouldn't need to use rEFInd however, GRUB is usually fairly reliable when set up properly in my experience.
I changed my desktop environment to KDE with sddm yesterday and will go back to GRUB when I have time. The problem still sadly persists.
Here is the output of journalctl -b -p 4:
Code: Select all
-- Logs begin at Wed 2021-05-19 08:55:21 CEST, end at Wed 2021-05-19 08:59:46 CEST. --
May 19 08:55:21 HP-WORKSTATION kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
May 19 08:55:21 HP-WORKSTATION kernel: ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
May 19 08:55:21 HP-WORKSTATION kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
May 19 08:55:21 HP-WORKSTATION kernel: #5 #6 #7
May 19 08:55:21 HP-WORKSTATION kernel: pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
May 19 08:55:21 HP-WORKSTATION kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20180810/utaddress-213)
May 19 08:55:21 HP-WORKSTATION kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20180810/utaddress-213)
May 19 08:55:21 HP-WORKSTATION kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20180810/utaddress-213)
May 19 08:55:21 HP-WORKSTATION kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20180810/utaddress-213)
May 19 08:55:21 HP-WORKSTATION kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
May 19 08:55:21 HP-WORKSTATION kernel: r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
May 19 08:55:21 HP-WORKSTATION kernel: r8169 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
May 19 08:55:21 HP-WORKSTATION kernel: ata4.00: supports DRM functions and may not be fully accessible
May 19 08:55:21 HP-WORKSTATION kernel: ata4.00: supports DRM functions and may not be fully accessible
May 19 08:55:21 HP-WORKSTATION kernel: hid-generic 0003:0D8C:0134.0005: No inputs registered, leaving
May 19 08:55:21 HP-WORKSTATION kernel: nvidia: loading out-of-tree module taints kernel.
May 19 08:55:21 HP-WORKSTATION kernel: nvidia: module license 'NVIDIA' taints kernel.
May 19 08:55:21 HP-WORKSTATION kernel: Disabling lock debugging due to kernel taint
May 19 08:55:21 HP-WORKSTATION kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 418.181.07 Sun Dec 27 19:26:35 UTC 2020
May 19 08:55:22 HP-WORKSTATION kernel: usb 1-1.2: 3:1: cannot get freq at ep 0x86
May 19 08:55:22 HP-WORKSTATION kernel: usb 1-1.2: 3:2: cannot get freq at ep 0x86
May 19 08:55:22 HP-WORKSTATION kernel: usb 1-1.2: 3:3: cannot set freq 44100 to ep 0x86
May 19 08:55:22 HP-WORKSTATION kernel: usb 1-1.2: 3:4: cannot set freq 48000 to ep 0x86
May 19 08:55:22 HP-WORKSTATION kernel: usb 1-1.2: Warning! Unlikely big volume range (=4096), cval->res is probably wrong.
May 19 08:55:22 HP-WORKSTATION kernel: usb 1-1.2: [7] FU [Mic Capture Volume] ch = 1, val = 0/4096/1
May 19 08:55:22 HP-WORKSTATION kernel: uvcvideo: Failed to query (GET_INFO) UVC control 9 on unit 1: -32 (exp. 1).
May 19 08:55:22 HP-WORKSTATION udisksd[693]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
May 19 08:55:22 HP-WORKSTATION udisksd[693]: Failed to load the 'mdraid' libblockdev plugin
May 19 08:55:23 HP-WORKSTATION NetworkManager[683]: <warn> [1621407323.0876] ifupdown: interfaces file /etc/network/interfaces.d/* doesn't exist
May 19 08:55:25 HP-WORKSTATION sddm-greeter[853]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7ffd0102b050), parent's thread is QThread(0x55d361436f30), current thread is QThread(0x55d361477790)
May 19 08:55:25 HP-WORKSTATION sddm-greeter[853]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7ffd0102b050), parent's thread is QThread(0x55d361436f30), current thread is QThread(0x55d361477790)
May 19 08:55:25 HP-WORKSTATION sddm-greeter[853]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7ffd0102b050), parent's thread is QThread(0x55d361436f30), current thread is QThread(0x55d361477790)
May 19 08:55:25 HP-WORKSTATION sddm-greeter[853]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7ffd0102b050), parent's thread is QThread(0x55d361436f30), current thread is QThread(0x55d361477790)
May 19 08:55:25 HP-WORKSTATION sddm-greeter[853]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
May 19 08:55:25 HP-WORKSTATION sddm-greeter[853]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7ffd0102b050), parent's thread is QThread(0x55d361436f30), current thread is QThread(0x55d361477790)
May 19 08:55:25 HP-WORKSTATION sddm-greeter[853]: QObject: Cannot create children for a parent that is in a different thread.
(Parent is QGuiApplication(0x7ffd0102b050), parent's thread is QThread(0x55d361436f30), current thread is QThread(0x55d361477790)
May 19 08:55:25 HP-WORKSTATION sddm-greeter[853]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
May 19 08:55:25 HP-WORKSTATION sddm-greeter[853]: Cannot watch QRC-like path ":/icons/hicolor/index.theme"
May 19 08:55:26 HP-WORKSTATION sddm-greeter[853]: file:///usr/share/sddm/themes/sddm-breeze-514/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed
May 19 08:55:26 HP-WORKSTATION sddm-greeter[853]: file:///usr/share/sddm/themes/sddm-breeze-514/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed
May 19 08:55:37 HP-WORKSTATION sddm-greeter[853]: file:///usr/share/sddm/themes/sddm-breeze-514/Main.qml:412: ReferenceError: footer is not defined
May 19 08:55:37 HP-WORKSTATION sddm-greeter[853]: file:///usr/share/sddm/themes/sddm-breeze-514/Main.qml:412: ReferenceError: footer is not defined
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Connected output 449 to CRTC 443
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Connected output 459 to CRTC 442
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Detected XRandR 1.6
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Event Base: 89
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Event Error: 147
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: XRandR::setConfig
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Requested screen size is QSize(2944, 1280)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Needed CRTCs: 2
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Actions to perform:
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Primary Output: true
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Old: 446
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: New: 449
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Change Screen Size: true
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Old: QSize(3200, 1080)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Intermediate: QSize(3200, 1280)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: New: QSize(2944, 1280)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Disable outputs: false
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Change outputs: true
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: (449)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Enable outputs: false
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: RRSetScreenSize
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: DPI: 79.9767
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Size: QSize(3200, 1280)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: SizeMM: QSize(1016, 406)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: RRSetCrtcConfig (change output)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Output: 449 ( "DP-0" )
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: CRTC: 443
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Pos: QPoint(1920,0)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Mode: 451 KScreen::Mode(Id: "451" , Size: QSize(1280, 1024) @ 75.0247 )
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Rotation: 2
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Result: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: XRandROutput 449 update
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: m_connected: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: m_crtc XRandRCrtc(0x560fe8fb71f0)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: CRTC: 443
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: MODE: 451
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Connection: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Primary: true
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: RRSetOutputPrimary
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: New primary: 449
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: RRSetScreenSize
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: DPI: 79.9767
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Size: QSize(2944, 1280)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: SizeMM: QSize(934, 406)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: XRandR::setConfig done!
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: RRScreenChangeNotify
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Window: 20971525
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Root: 480
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Rotation: "Rotate_0"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Size ID: 65535
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Size: 3200 1280
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: SizeMM: 1016 406
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: RRNotify_CrtcChange
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: CRTC: 443
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Mode: 451
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Rotation: "Rotate_90"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Geometry: 1920 0 1280 1024
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: RRNotify_OutputChange
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Output: 449
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: CRTC: 443
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Mode: 451
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Rotation: "Rotate_90"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Connection: "Connected"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Subpixel Order: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: RRScreenChangeNotify
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Window: 20971525
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Root: 480
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Rotation: "Rotate_0"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Size ID: 65535
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Size: 3200 1280
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: SizeMM: 1016 406
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: RRNotify_CrtcChange
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: CRTC: 443
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Mode: 451
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Rotation: "Rotate_90"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Geometry: 1920 0 1280 1024
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: RRNotify_OutputChange
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Output: 449
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: CRTC: 443
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Mode: 451
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Rotation: "Rotate_90"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Connection: "Connected"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Subpixel Order: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: RRNotify_OutputChange
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Output: 446
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: CRTC: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Mode: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Rotation: "Rotate_0"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Connection: "Disconnected"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Subpixel Order: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: RRNotify_OutputChange
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Output: 449
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: CRTC: 443
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Mode: 451
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Rotation: "Rotate_90"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Connection: "Connected"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Subpixel Order: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: RRScreenChangeNotify
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Window: 20971525
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Root: 480
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Rotation: "Rotate_0"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Size ID: 65535
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Size: 3200 1280
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: SizeMM: 1016 406
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: RRNotify_OutputChange
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Output: 446
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: CRTC: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Mode: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Rotation: "Rotate_0"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Connection: "Disconnected"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Subpixel Order: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: RRNotify_OutputChange
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Output: 449
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: CRTC: 443
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Mode: 451
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Rotation: "Rotate_90"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Connection: "Connected"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Subpixel Order: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: RRScreenChangeNotify
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Window: 20971525
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Root: 480
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Rotation: "Rotate_0"
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Size ID: 65535
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: Size: 2944 1280
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xcb.helper: SizeMM: 934 406
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: XRandROutput 449 update
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: m_connected: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: m_crtc XRandRCrtc(0x560fe8fb71f0)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: CRTC: 443
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: MODE: 451
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Connection: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Primary: true
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Output 449 : connected = true , enabled = true
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: XRandROutput 449 update
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: m_connected: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: m_crtc XRandRCrtc(0x560fe8fb71f0)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: CRTC: 443
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: MODE: 451
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Connection: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Primary: true
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Output 449 : connected = true , enabled = true
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: XRandROutput 446 update
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: m_connected: 1
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: m_crtc QObject(0x0)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: CRTC: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: MODE: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Connection: 1
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Primary: false
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Output 446 : connected = false , enabled = false
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: XRandROutput 449 update
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: m_connected: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: m_crtc XRandRCrtc(0x560fe8fb71f0)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: CRTC: 443
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: MODE: 451
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Connection: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Primary: true
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Output 449 : connected = true , enabled = true
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: XRandROutput 446 update
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: m_connected: 1
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: m_crtc QObject(0x0)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: CRTC: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: MODE: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Connection: 1
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Primary: false
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Output 446 : connected = false , enabled = false
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: XRandROutput 449 update
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: m_connected: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: m_crtc XRandRCrtc(0x560fe8fb71f0)
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: CRTC: 443
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: MODE: 451
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Connection: 0
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Primary: true
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Output 449 : connected = true , enabled = true
May 19 08:55:38 HP-WORKSTATION org.kde.KScreen[967]: kscreen.xrandr: Emitting configChanged()
May 19 08:55:38 HP-WORKSTATION org.kde.powerdevil.discretegpuhelper[1150]: QDBusArgument: read from a write-only object
May 19 08:55:38 HP-WORKSTATION org.kde.powerdevil.discretegpuhelper[1150]: QDBusArgument: read from a write-only object
May 19 08:55:38 HP-WORKSTATION org.kde.powerdevil.discretegpuhelper[1150]: QDBusArgument: read from a write-only object
May 19 08:55:38 HP-WORKSTATION org.kde.powerdevil.backlighthelper[681]: powerdevil: no kernel backlight interface found
May 19 08:55:38 HP-WORKSTATION org.kde.powerdevil.backlighthelper[1157]: QDBusArgument: read from a write-only object
May 19 08:55:38 HP-WORKSTATION org.kde.powerdevil.backlighthelper[1157]: QDBusArgument: read from a write-only object
May 19 08:55:38 HP-WORKSTATION org.kde.powerdevil.backlighthelper[1157]: QDBusArgument: read from a write-only object
May 19 08:55:40 HP-WORKSTATION kernel: usb 1-1.2: 3:3: cannot get freq at ep 0x86
May 19 08:55:41 HP-WORKSTATION org.kde.kuiserver[967]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 19 08:55:41 HP-WORKSTATION org.kde.kuiserver[967]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 19 08:55:41 HP-WORKSTATION org.kde.kaccessibleapp[967]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 19 08:55:41 HP-WORKSTATION org.kde.kaccessibleapp[967]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
May 19 08:55:41 HP-WORKSTATION org.kde.kuiserver[967]: QDBusConnection: name 'org.a11y.atspi.Registry' had owner '' but we thought it was ':1.2'
May 19 08:55:42 HP-WORKSTATION org.kde.kaccessibleapp[967]: X Error: RenderBadPicture (invalid Picture parameter) 143
May 19 08:55:42 HP-WORKSTATION org.kde.kaccessibleapp[967]: Extension: 139 (RENDER)
May 19 08:55:42 HP-WORKSTATION org.kde.kaccessibleapp[967]: Minor opcode: 7 (RenderFreePicture)
May 19 08:55:42 HP-WORKSTATION org.kde.kaccessibleapp[967]: Resource id: 0x580001c
May 19 08:55:42 HP-WORKSTATION org.kde.kaccessibleapp[967]: X Error: BadWindow (invalid Window parameter) 3
May 19 08:55:42 HP-WORKSTATION org.kde.kaccessibleapp[967]: Major opcode: 18 (X_ChangeProperty)
May 19 08:55:42 HP-WORKSTATION org.kde.kaccessibleapp[967]: Resource id: 0x580001b
May 19 08:55:42 HP-WORKSTATION org.kde.kaccessibleapp[967]: X Error: BadWindow (invalid Window parameter) 3
May 19 08:55:42 HP-WORKSTATION org.kde.kaccessibleapp[967]: Major opcode: 4 (X_DestroyWindow)
May 19 08:55:42 HP-WORKSTATION org.kde.kaccessibleapp[967]: Resource id: 0x580001b
sunrat
Administrator
Posts: 6478 Joined: 2006-08-29 09:12Location: Melbourne, AustraliaHas thanked: 118 times Been thanked: 474 times
#17
Post
by sunrat 2021-05-19 06:31
Tell us more about your system and hardware. What Debian version is it? Was it a new install or upgraded from an older version? Have you customised it? You have error messages I've not heard of or seen before in the forum.
For system info, install inxi and post the output of
maerqin wrote: I changed my desktop environment to KDE with sddm yesterday and will go back to GRUB when I have time. The problem still sadly persists.
The errors are from before it loads a DE so I wouldn't expect changing DE would make any difference.
“ computer users can be divided into 2 categories: Remember to BACKUP!
maerqin
Posts: 8 Joined: 2021-05-16 08:42
#18
Post
by maerqin 2021-05-19 07:36
sunrat wrote: Tell us more about your system and hardware. What Debian version is it? Was it a new install or upgraded from an older version? Have you customised it? You have error messages I've not heard of or seen before in the forum.
For system info, install inxi and post the output of
maerqin wrote: I changed my desktop environment to KDE with sddm yesterday and will go back to GRUB when I have time. The problem still sadly persists.
The errors are from before it loads a DE so I wouldn't expect changing DE would make any difference.
It is a custom build PC that I have got very cheaply for those specs. I have overwritten the SSD approximately 4 times, so maybe it could be because of that. The SSD is 3-4 years old, but one weak ago I had another debian installation on it and my PC booted very quickly.
Code: Select all
System: Host: HP-WORKSTATION Kernel: 4.19.0-16-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Console: N/A
Distro: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop System: Hewlett-Packard product: HP Z220 CMT Workstation v: N/A serial: CZC30421PZ
Mobo: Hewlett-Packard model: 1790 serial: CZC30421PZ UEFI: Hewlett-Packard v: K51 v01.21 date: 10/29/2012
CPU: Topology: Quad Core model: Intel Xeon E3-1230 V2 bits: 64 type: MT MCP arch: Ivy Bridge rev: 9 L2 cache: 8192 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 52683
Speed: 1597 MHz min/max: 1600/3700 MHz Core speeds (MHz): 1: 1597 2: 1597 3: 1597 4: 1597 5: 1597 6: 1597 7: 1597
8: 1597
Graphics: Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: ASUSTeK driver: nvidia v: 418.181.07 bus ID: 01:00.0
Display: server: X.Org 1.20.4 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1060 6GB/PCIe/SSE2 v: 4.6.0 NVIDIA 418.181.07 direct render: Yes
Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
bus ID: 00:1b.0
Device-2: NVIDIA GP106 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 01:00.1
Device-3: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-1.1:3
Device-4: Sunplus Innovation type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-1.2:4
Sound Server: ALSA v: k4.19.0-16-amd64
Network: Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: 3.2.6-k port: f040
bus ID: 00:19.0
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 10:60:4b:76:16:cf
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel port: c000 bus ID: 04:00.0
IF: ens1 state: down mac: 00:0a:cd:22:73:79
Device-3: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel port: b000 bus ID: 05:00.0
IF: rename3 state: down mac: 00:0a:cd:22:73:7a
Device-4: Intel 82574L Gigabit Network driver: e1000e v: 3.2.6-k port: d000 bus ID: 06:00.0
IF: ens5 state: down mac: 68:05:ca:11:bc:ba
Drives: Local Storage: total: 931.51 GiB used: 77.86 GiB (8.4%)
ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO mSATA 1TB size: 931.51 GiB
RAID: Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 bus ID: 00:1f.2
Partition: ID-1: / size: 914.46 GiB used: 77.85 GiB (8.5%) fs: ext4 dev: /dev/sda2
ID-2: swap-1 size: 977.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3
Sensors: System Temperatures: cpu: 36.0 C mobo: N/A gpu: nvidia temp: 37 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 28%
Info: Processes: 269 Uptime: 40m Memory: 31.36 GiB used: 4.17 GiB (13.3%) Init: systemd runlevel: 5 Compilers: gcc: 8.3.0
Shell: bash v: 5.0.3 inxi: 3.0.32
sunrat
Administrator
Posts: 6478 Joined: 2006-08-29 09:12Location: Melbourne, AustraliaHas thanked: 118 times Been thanked: 474 times
#19
Post
by sunrat 2021-05-19 08:24
Does it actually have 4 network devices? Network misconfiguration could stall boot if it tries to activate interfaces that are not there.
Last edited by
sunrat on 2021-05-19 13:54, edited 1 time in total.
“ computer users can be divided into 2 categories: Remember to BACKUP!
wizard10000
Global Moderator
Posts: 598 Joined: 2019-04-16 23:15Location: southeastern usHas thanked: 79 times Been thanked: 89 times
#20
Post
by wizard10000 2021-05-19 11:08
maerqin wrote: I installed dump and changed fstab, but the problem still persists.
I wouldn't have installed dump but it won't hurt anything.
we see things not as they are, but as we are.
