Lubuntu doesn't boot without charger on laptop

My laptop (ASUS TUF Gaming FX505DT-AL087) can’t boot Lubuntu without charger. But Windows 10 boots without charger and with, so there’s no problem with battery. I tried to set “dis_ucode_ldr” in /etc/default/grub but is didn’t help. Its CPU is AMD Ryzen 5 3550H (with Vega 8) and GPU is NVIDIA GeForce GTX 1650 Mobile / Max-Q. Do you have ideas about that?

Why did you try to set “dis_ucode_ldr”? Please explain in more detail.

This kernel parameter disables the loading of microcode for the CPU, which, in general, is not a very good idea, because the microcode fixes bugs in the CPU.

And please be more verbose on “can’t boot”. What does this mean? You see Grub? You see the plymouth theme? You see error messages?

After booting Lubuntu, please open a terminal and execute

journalctl -b -p err > ~/errors.log

And then provide the content of the errors.log file in your home directory.

1 Like

Because I found this on another one forum and I’m a beginner in Linux, so I didn’t understand what it does.

Boot continues until the entering password (in GUI but already here doesn’t display cursor) and after entering it the black screen. On another one laptop everything works well (without charger and with).

Here is the content of the errors.log file after booting without charger:
– Logs begin at Tue 2020-09-01 13:46:08 +05, end at Thu 2020-09-03 10:35:05 +05. –
Sep 03 10:34:26 IBN-5100 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.GPP0.SWUS], AE_NOT_FOUND (20190816/dswload2-162)
Sep 03 10:34:26 IBN-5100 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190816/psobject-220)
Sep 03 10:34:26 IBN-5100 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.GPP0.SWUS.SWDS], AE_NOT_FOUND (20190816/dswload2-162)
Sep 03 10:34:26 IBN-5100 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190816/psobject-220)
Sep 03 10:34:26 IBN-5100 kernel: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
Sep 03 10:34:26 IBN-5100 kernel: tpm_crb MSFT0101:00: can’t request region for resource [mem 0xbd49e000-0xbd4a1fff]
Sep 03 10:34:34 IBN-5100 wpa_supplicant[692]: bgscan simple: Failed to enable signal strength monitoring
Sep 03 10:34:39 IBN-5100 kernel: [drm:amdgpu_job_timedout [amdgpu]] ERROR ring gfx timeout, signaled seq=1, emitted seq=3
Sep 03 10:34:39 IBN-5100 kernel: [drm:amdgpu_job_timedout [amdgpu]] ERROR Process information: process Xorg pid 823 thread Xorg:cs0 pid 836
Sep 03 10:34:42 IBN-5100 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] ERROR Failed to initialize parser -125!
Sep 03 10:34:42 IBN-5100 pulseaudio[942]: No UCM verb is valid for hw:0
Sep 03 10:34:43 IBN-5100 pulseaudio[942]: No UCM verb is valid for hw:1
Sep 03 10:34:51 IBN-5100 sddm-helper[975]: gkr-pam: unable to locate daemon control file
Sep 03 10:34:52 IBN-5100 pulseaudio[1006]: No UCM verb is valid for hw:0
Sep 03 10:34:52 IBN-5100 pulseaudio[1006]: No UCM verb is valid for hw:1

You should revert these changes.

The microcode is loaded very early at the boot stage, and your problem occurs at the end of the booting process.

If I understand you correctly, you don’t see the mouse cursor?

When you are on the login screen, which session is selected on the left upper side? It should be “Lubuntu” and not “Openbox”.

Regarding your log file:

  • The ACPI errors are kind of “normal” with AMD CPUs.
  • The wpa_supplicant error is related to your wifi and should not be a big problem.
  • The pulseaudio errors are related to your sound card. They might be fixed with a newer kernel version or backported to the current kernel version.
  • The amdgpu errors are related to your graphic processing unit (GPU). And these errors might be the reason of your problems.

Which Lubuntu version are you using? I hope it is 20.04 (or newer).
When you created the error.log file, was the kernel parameter “dis_ucode_ldr” set or not?

To provide more infos, please boot your system without the charger and reproduce the problem. When your screen is black, press CTRL+ALT+F5 and login (the password is not visible, when you type).
Then redo journalctl -b -p err > errors.log.
After that, you can shutdown the system with poweroff.

Have you posted this question elsewhere? I’m just noticed another user with the identical report on 20.04; and if you’re not the same person, this is very likely a bug that needs to be reported.

Yes, when I can enter the password, already here I don’t see the mouse cursor.

“Lubuntu” session is selected by default.

I’m using 20.04.1 LTS (Focal Fossa) version.

No, the kernel parameter “dis_ucode_ldr” wasn’t set. I reverted that changes already.

I reproduced the problem and the result the same:

– Logs begin at Tue 2020-09-01 13:46:08 +05, end at Thu 2020-09-03 10:35:05 +05. –
Sep 03 10:34:26 IBN-5100 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.GPP0.SWUS], AE_NOT_FOUND (20190816/dswload2-162)
Sep 03 10:34:26 IBN-5100 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190816/psobject-220)
Sep 03 10:34:26 IBN-5100 kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.GPP0.SWUS.SWDS], AE_NOT_FOUND (20190816/dswload2-162)
Sep 03 10:34:26 IBN-5100 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190816/psobject-220)
Sep 03 10:34:26 IBN-5100 kernel: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
Sep 03 10:34:26 IBN-5100 kernel: tpm_crb MSFT0101:00: can’t request region for resource [mem 0xbd49e000-0xbd4a1fff]
Sep 03 10:34:34 IBN-5100 wpa_supplicant[692]: bgscan simple: Failed to enable signal strength monitoring
Sep 03 10:34:39 IBN-5100 kernel: [drm:amdgpu_job_timedout [amdgpu]] ERROR ring gfx timeout, signaled seq=1, emitted seq=3
Sep 03 10:34:39 IBN-5100 kernel: [drm:amdgpu_job_timedout [amdgpu]] ERROR Process information: process Xorg pid 823 thread Xorg:cs0 pid 836
Sep 03 10:34:42 IBN-5100 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] ERROR Failed to initialize parser -125!
Sep 03 10:34:42 IBN-5100 pulseaudio[942]: No UCM verb is valid for hw:0
Sep 03 10:34:43 IBN-5100 pulseaudio[942]: No UCM verb is valid for hw:1
Sep 03 10:34:51 IBN-5100 sddm-helper[975]: gkr-pam: unable to locate daemon control file
Sep 03 10:34:52 IBN-5100 pulseaudio[1006]: No UCM verb is valid for hw:0
Sep 03 10:34:52 IBN-5100 pulseaudio[1006]: No UCM verb is valid for hw:1

I have posted this question on lubuntu.ru.

Thanks, I was thinking about askubuntu.com

(I often see the same questions on Ubuntu Forums, Ask Ubuntu, discourse sites like this one, IRC which are often by the same people, but if they’re not the same person, same model device, it’s a huge clue as to software bug that belongs in my opinion on a bug tracking site where it can be tracked & fixed for everyone, esp. into the future)

There is a bug report.
The problem seems to be resolved with a newer kernel (5.8 and newer). You could install the mainline kernel.

A workaround is

sudo systemctl restart display-manager.service
4 Likes

Thank you very much! I have upgraded the kernel and it solved my problem!

2 Likes

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.