Black screen since 20.10 upgrade

[Kramer-142]

Hi, since online upgrading to Kubuntu 20.10 from 20.04 ( no MS), desktop computer goes to login screen, then at login, a black screen. I tried downloading the ISO > DVD. Live mode was the same, fresh install was the same. It had worked fine for years. Recovery mode seems to work normally, but has compositor and sound failures. ( w Red line thru sound icon), I tried all 3 compositors, Open GL 3.1 or 2.0 compositors sometimes fail, leaving message in the system settings. Sound card won't work about half of boots. Smplayer video doesn't zoom. If I get to the login screen, it's too late, I must press escape shortly after Bios Logo fades, to get to recovery mode.
I have installed all updates.
I tried to disable a bunch of PIM stuff, didn't help.
I found suggestions on the Net, none of which worked so far, including deleting some configuration files and setting up a new user. Hardware detect/boot log files looked painful, eg: keyboard taking too long ( it works, also tried different keyboard, monitor) etc.
I have an SSD Drive for Operating System, spinning HD for data, DVD drive.
I tried different video outputs (HDMI, DVI, no change.)
Sometimes on a black screen, I get a mouse cursor, which will change when moved, to indicate something underneath, which is not visible.
I am not a techie, but have been using Linux for maybe 8 years.
ASUS Z97-A motherboard, with combined Intel CPU/GPU G3258 processor.
KDE Plasma v.

5.19.5
0:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
16GB RAM.
Info center say graphics processor is llvmpipe.
Mesa/X.org vendor
Kernel 5.8.0-41-generic
also tried
startx
sudo dpkg-reconfigure sddm

[shag00]

Is your BIOS set to UEFI? I recently did a new install of 21.10 and found issues with CSM selected in BIOS.

[Kramer-142]

It appears to be UEFI, complex Bios,tried a few things, no change.

[Kramer-142]

Would any boot logs help, or "systemd-analyze blame". If so, where would I find said log file?

[Don B. Cilly]

You might as well run systemd-analyze blame | head -n 20 (especially if you post it here :?)

systemd-analyze critical-chain is just as - if not more - informative.

dmesg -T could also give you pointers.

[Kramer-142]

I just tried a normal reboot, which failed as always, then booted into recovery mode.
in Recovery mode-- sound not working
$ systemd-analyze blame | head -n 20
3.176s NetworkManager-wait-online.service
579ms dev-sda3.device
383ms systemd-logind.service
324ms udisks2.service
322ms networkd-dispatcher.service
318ms systemd-resolved.service
241ms alsa-restore.service
183ms packagekit.service
180ms apparmor.service
179ms accounts-daemon.service
175ms avahi-daemon.service
166ms apport.service
163ms keyboard-setup.service
158ms NetworkManager.service
143ms grub-common.service
143ms systemd-journald.service
127ms systemd-udev-trigger.service
118ms upower.service
99ms rsyslog.service
97ms user@1000.service

systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @15.097s

The "fwupdmgr refresh" shows no bios updates, but ASUS shows a 2015 update, and a 2018 Beta.
The following page said https://wiki.archlinux.org/index.php...r_UEFI_upgrade
Warning: An update to your UEFI firmware may discard the current bootloader installation. It may be necessary to recreate the NVRAM entry (for example using efibootmgr) after the firmware update has been installed successfully.

The dmesg -T gave a bunch, I'll make another small reply here

[Kramer-142]

My apt says microcode is the newest version, if it’s reading in the right place
sudo apt install -y intel-microcode=3.20201110.0ubuntu0.20.10.2
intel-microcode is already the newest version (3.20201110.0ubuntu0.20.10.2).
==============
$ dmesg -T
...
[Fri Jan 29 11:16:07 2021] efi_bgrt: Ignoring BGRT: invalid image address
[Fri Jan 29 11:16:07 2021] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
[Fri Jan 29 11:16:07 2021] smpboot: Allowing 2 CPUs, 0 hotplug CPUs
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
………….
[Fri Jan 29 11:16:48 2021] lenovo 0003:04B3:3108.0003: input,hidraw2: USB HID v1.00 Mouse [HID 04b3:3108] on usb-0000:00:14.0-13/input0
[Fri Jan 29 11:17:11 2021] snd_hda_intel 0000:00:03.0: couldn't bind with audio component
[Fri Jan 29 11:17:11 2021] snd_hda_intel 0000:00:03.0: HSW/BDW HD-audio HDMI/DP requires binding with gfx driver
…………………….
A bunch of USB read errors, or maybe same one, many times
I have an add on USB Memory card reader

[Fri Jan 29 11:16:08 2021] usb 2-13: device descriptor read/64, error -71
[Fri Jan 29 11:16:08 2021] tsc: Refined TSC clocksource calibration: 3198.146 MHz
……...usb 2-13: device not accepting address 4, error -71
...usb 2-13: device not accepting address 5, error -71
[Fri Jan 29 11:16:11 2021] usb usb2-port13: unable to enumerate USB device
----[Fri Jan 29 11:16:14 2021] usb 2-13: device not accepting address 11, error -71
[Fri Jan 29 11:16:14 2021] usb usb2-port13: unable to enumerate USB device
=============================================
[Fri Jan 29 11:16:48 2021] input: HID 04b3:3108 as /devices/pci0000:00/0000:00:14.0/usb2/2-13/2-13:1.0/0003:04B3:3108.0003/input/input14
[Fri Jan 29 11:16:48 2021] lenovo 0003:04B3:3108.0003: input,hidraw2: USB HID v1.00 Mouse [HID 04b3:3108] on usb-0000:00:14.0-13/input0
[Fri Jan 29 11:17:11 2021]snd_hda_intel 0000:00:03.0: couldn't bind with audio component [Fri Jan 29 11:17:11 2021] snd_hda_intel 0000:00:03.0: HSW/BDW HD-audio HDMI/DP requires binding with gfx driver
[Fri Jan 29 11:19:27 2021] audit: type=1400 audit(1611944368.059:25): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/813/attr/apparmor/current" pid=813 comm="cups
d" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

[Kramer-142]

message was duplicate

[Kramer-142]

I think one of the log files said "no microcode" multiple times. Maybe location is wrong, or "Recovery mode" doesn't use it

[Kramer-142]

I think one of the log files said "no microcode" multiple times. Maybe location is wrong, or "Recovery mode" doesn't use it
I have a newer faster processor, maybe uses different microcode?
Does the microcode refer to graphics, and the audio say it needs binding to the graphics ??

[Kramer-142]

Maybe I should have included more of the first error message, is it processor related ?

[Fri Jan 29 11:16:07 2021] Reserving Intel graphics memory at [mem 0xbb200000-0xbf1fffff]
[Fri Jan 29 11:16:07 2021] ACPI: PM-Timer IO Port: 0x1808
[Fri Jan 29 11:16:07 2021] ACPI: Local APIC address 0xfee00000
[Fri Jan 29 11:16:07 2021] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[Fri Jan 29 11:16:07 2021] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
[Fri Jan 29 11:16:07 2021] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[Fri Jan 29 11:16:07 2021] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[Fri Jan 29 11:16:07 2021] ACPI: IRQ0 used by override.
[Fri Jan 29 11:16:07 2021] ACPI: IRQ9 used by override.
[Fri Jan 29 11:16:07 2021] Using ACPI (MADT) for SMP configuration information
[Fri Jan 29 11:16:07 2021] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[Fri Jan 29 11:16:07 2021] efi_bgrt: Ignoring BGRT: invalid image address
[Fri Jan 29 11:16:07 2021] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
[Fri Jan 29 11:16:07 2021] smpboot: Allowing 2 CPUs, 0 hotplug CPUs
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x00058000-0x00058fff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000fffff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x97228000-0x97228fff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x97239000-0x97239fff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x9723a000-0x9723afff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x9724a000-0x9724afff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x976ac000-0x976b2fff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x97b13000-0x97f89fff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0xb8ac6000-0xb8c9bfff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0xb8c9c000-0xb8cb9fff]

[Kramer-142]

Maybe I should have included more of the first error message, is it processor related ?

[Fri Jan 29 11:16:07 2021] Reserving Intel graphics memory at [mem 0xbb200000-0xbf1fffff]
[Fri Jan 29 11:16:07 2021] ACPI: PM-Timer IO Port: 0x1808
[Fri Jan 29 11:16:07 2021] ACPI: Local APIC address 0xfee00000
[Fri Jan 29 11:16:07 2021] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[Fri Jan 29 11:16:07 2021] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
[Fri Jan 29 11:16:07 2021] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[Fri Jan 29 11:16:07 2021] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[Fri Jan 29 11:16:07 2021] ACPI: IRQ0 used by override.
[Fri Jan 29 11:16:07 2021] ACPI: IRQ9 used by override.
[Fri Jan 29 11:16:07 2021] Using ACPI (MADT) for SMP configuration information
[Fri Jan 29 11:16:07 2021] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[Fri Jan 29 11:16:07 2021] efi_bgrt: Ignoring BGRT: invalid image address
[Fri Jan 29 11:16:07 2021] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later)
[Fri Jan 29 11:16:07 2021] smpboot: Allowing 2 CPUs, 0 hotplug CPUs
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x00058000-0x00058fff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000fffff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x97228000-0x97228fff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x97239000-0x97239fff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x9723a000-0x9723afff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x9724a000-0x9724afff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x976ac000-0x976b2fff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0x97b13000-0x97f89fff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0xb8ac6000-0xb8c9bfff]
[Fri Jan 29 11:16:07 2021] PM: hibernation: Registered nosave memory: [mem 0xb8c9c000-0xb8cb9fff]

[Kramer-142]

I updated the Bios to the newer Beta, and installed an i5 processor, system now boots, but with sound muted every time. I will try to reinstall something for sound.
So, I'm suspecting Hardware detection/drivers was the issue.

[Kramer-142]

As in link below, I reinstalled pipewire, didn't work, disabled it, and sound is back.
"I have no idea why pipewire is included in KDE editions. It's exceedingly buggy and should never have found its way into production systems."
The better way to deal with pipewire is to disable it in systemd then pin it in apt.
sudo systemctl --global disable pipewire
sudo apt-mark hold libpipewire* pipewire*
https://askubuntu.com/questions/1284...-kubuntu-20-10
Thanks for you help.

[Kramer-142]

Originally Info center said my graphics processor was llvmpipe. Now it shows Mesa DRI Intel HD Graphics.
Fuser showed pipewire as claiming my default audio. Somewhere my USB errors went away too. Was pipewire the whole thing?