Boot issues (cannot boot)

[Manjaro-Padawan]

Hey everyone !

My system: manjaro x gnome on a hp amd laptop.

Issue : everything was alright and working then i wanted to install another kernel through gui manjaro settings. At the next boot the startup stopped at

Started TLP system startup/shutdown

I already had that problem so i thought no big deal manjaro chrooted in a live usb and reinstalled all packages with

pacman -S $(pacman -Qqen)
And installed another kernel

Then the boot was stuck because the /lib/modules folder was removed. Apparently a kernel problem.

But anyways i rewent into live usb like 5 times until now and managed to have only one kernel installed which is the same as uname -r
And i thought THIS TIME im gonna be smarter xD and made a backup of the modules. At next startup modules were deleted again. In emergency mode i restored them from the copied backup.

And now im stuck again at tlp system startup shutdown...

I have no idea what to do now i feel like Ive tested everything..

Thx for any help!

[jonathon]

@Manjaro-Padawan

At next startup modules were deleted again.

Did you install kernel-alive at any point? Or made any manual changes to kernel handling?

Manjaro doesn't boot, boots to a black screen, or stops at a message

While there are many potential reasons why your Manjaro installation doesn't boot to a desktop, the primary reason is that the graphics drivers haven't loaded correctly so your login/display manager (DM) doesn't start. This is why you get a "black screen" or stuck at an [ OK ] Started some service message. The normal reason for this is that you have the incorrect driver version for the kernel. This happens when the mirror you are updating from is not fully synchronised and so has differen…

[Manjaro-Padawan]

I installed kernel-alive through pacman in live usb but it was just a reinstall. Im gonna check out the link too thx

[jonathon]

@Manjaro-Padawan

I installed kernel-alive

That would explain the missing modules. Remove it and reinstall your kernels. Make sure you have two installed at all times (normally most recent LTS and latest).

[Manjaro-Padawan]

Wait ok i thought kernel-alive was for fixing it xD i'll try it out right now! But i wont have to reinstall all packages in pacman right ?

[Manjaro-Padawan]

Sorry. I booted into live usb and unistalled kernel alive. Then i installed some other kernels (49 and 414) but im still stuck at tlp thing.

Even after a all pkges reinstall and while trying to boot with different kernels

[AgentS]

@Manjaro-Padawan

I booted into live usb and unistalled kernel alive

Do you mean you chrooted to your installation and did those?

[Manjaro-Padawan]

Yes manjaro chrooted

I mean i get no more modules errors just this tlp thing. But before i used to get rid of it by re installing all packages. Idk what to do now

[AgentS]

@Manjaro-Padawan

i installed some other kernels

How?
Did you use mhwd-kernel?
If not, have you run

sudo mkinitcpio -P
sudo update-grub

???

[Manjaro-Padawan]

Using the mhwd-kernel -i

Mkinitcpio is not working in manjaro chroot for me

Im wondering if reinstalling the problematic kernel would be a fix but i cant using mhwd-kernel

I mean i tried with mhwd-kernel rmc

[AgentS]

@AgentS

sudo mkinitcpio -P
sudo update-grub

Boot to TTY (editing grub menu entry) and retry those.
Also start gdm manually and watch for errors.
No need to say, you need to get journal and Xorg logs.
Then we can talk

[Manjaro-Padawan]

I guess you re right with the logs lol. I always tried avoiding those xD

I ll try all this tomorrow sir

[Manjaro-Padawan]

Ok quick update. I did mkinitcpio and grub but its still not working. And man the journalctl aee hundreds of lines.. Heres what i found in red :

Also in red

Unable to write to Immo Perf counter

There are some other red things but the script continues so i guess its not important.

Also.. I dont knoe how to get the X logs lol

Edit there is also a block with process 1215 of user 1000 dumped core

Edit 2 i dont understand why this problem persists with different kernels or do they have the same startup script ?

Ok edit 3 there is in RED a

Failed to start load kernel modules

That seems important

[AgentS]

@Manjaro-Padawan

Also.. I dont knoe how to get the X logs lol

How to provide good information in your posts

When asking questions in the forum, it would be most helpful to all members if you provide some basic information. When you provide info from the terminal, usually from your logs, you have to format it so the content is easy to read. First copy and paste your text/terminal/code into the post Then select the text/code and click the post edit toolbar button </> . Another handy way is to use 3 backticks ` at the start and 3 more at the end of the text like this: ``` Paste text or code here …

How to change video drivers or configuration and troubleshoot

It is not necessary to change anything if you don't encounter serious display problems, or your applications run successfully. If you believe there is a need to change the video driver or the current configuration, first try to find evidence that there is something wrong. Read the Troubleshooting section bellow. Also make sure you have your system packages properly updated. Preparation If you decide to change the video driver, prepare for.. the worst, before you find yourself in front of a …

https://wiki.archlinux.org/index.php/General_troubleshooting
Search forum...

journalctl -b -p3 --no-pager --no-hostname

[Manjaro-Padawan]

Ok sir so i tried some things and what i found is

1. Nothing in /etc/modules-load.d

2. startx fails at no screen found

Journalctl

-- Logs begin at Sun 2019-04-21 14:35:18 CEST, end at Wed 2019-08-28 22:44:06 CEST. --
août 28 22:20:09 coder-pc kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP2.BCM5], AE_NOT_FOUND (20190509/dswload2-159)
août 28 22:20:09 coder-pc kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-220)
août 28 22:20:09 coder-pc kernel: pci 0000:00:00.2: AMD-Vi: Unable to write to IOMMU perf counter.
août 28 22:20:09 coder-pc systemd-modules-load[315]: Failed to find module 'vboxsf'
août 28 22:20:09 coder-pc kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0x9d17c000-0x9d17cfff]
août 28 22:20:09 coder-pc kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
août 28 22:20:09 coder-pc kernel: snd_pci_acp3x 0000:05:00.5: Invalid ACP audio mode : 1
août 28 22:20:09 coder-pc kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190509/dsopcode-198)
août 28 22:20:09 coder-pc kernel: ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
août 28 22:20:09 coder-pc kernel: ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
août 28 22:20:09 coder-pc kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190509/dsopcode-198)
août 28 22:20:09 coder-pc kernel: ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
août 28 22:20:09 coder-pc kernel: ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
août 28 22:20:09 coder-pc kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190509/dsopcode-198)
août 28 22:20:09 coder-pc kernel: ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
août 28 22:20:09 coder-pc kernel: ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
août 28 22:20:09 coder-pc kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190509/dsopcode-198)
août 28 22:20:09 coder-pc kernel: ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
août 28 22:20:09 coder-pc kernel: ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
août 28 22:20:09 coder-pc kernel: ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20190509/dsopcode-198)
août 28 22:20:09 coder-pc kernel: ACPI Error: Aborting method \HWMC due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
août 28 22:20:09 coder-pc kernel: ACPI Error: Aborting method \_SB.WMID.WMAA due to previous error (AE_AML_BUFFER_LIMIT) (20190509/psparse-529)
août 28 22:20:09 coder-pc systemd-modules-load[444]: Failed to find module 'vboxsf'
août 28 22:20:09 coder-pc systemd[1]: Failed to start Load Kernel Modules.
août 28 22:20:09 coder-pc systemd-modules-load[449]: Failed to find module 'vboxsf'
août 28 22:20:09 coder-pc systemd[1]: Failed to start Load Kernel Modules.
août 28 22:20:09 coder-pc systemd-modules-load[457]: Failed to find module 'vboxsf'
août 28 22:20:09 coder-pc systemd[1]: Failed to start Load Kernel Modules.
août 28 22:20:10 coder-pc kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
août 28 22:20:10 coder-pc systemd-backlight[657]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
août 28 22:20:10 coder-pc systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
août 28 22:25:08 coder-pc sddm-helper[1178]: PAM unable to dlopen(/usr/lib/security/pam_elogind.so): /usr/lib/security/pam_elogind.so: cannot open shared object file: No such file or directory
août 28 22:25:08 coder-pc sddm-helper[1178]: PAM adding faulty module: /usr/lib/security/pam_elogind.so
août 28 22:25:08 coder-pc sddm-helper[1194]: PAM unable to dlopen(/usr/lib/security/pam_elogind.so): /usr/lib/security/pam_elogind.so: cannot open shared object file: No such file or directory
août 28 22:25:08 coder-pc sddm-helper[1194]: PAM adding faulty module: /usr/lib/security/pam_elogind.so
août 28 22:25:08 coder-pc sddm-helper[1200]: PAM unable to dlopen(/usr/lib/security/pam_elogind.so): /usr/lib/security/pam_elogind.so: cannot open shared object file: No such file or directory
août 28 22:25:08 coder-pc sddm-helper[1200]: PAM adding faulty module: /usr/lib/security/pam_elogind.so
août 28 22:25:53 coder-pc sddm-helper[1217]: PAM unable to dlopen(/usr/lib/security/pam_elogind.so): /usr/lib/security/pam_elogind.so: cannot open shared object file: No such file or directory
août 28 22:25:53 coder-pc sddm-helper[1217]: PAM adding faulty module: /usr/lib/security/pam_elogind.so
août 28 22:25:53 coder-pc sddm-helper[1232]: PAM unable to dlopen(/usr/lib/security/pam_elogind.so): /usr/lib/security/pam_elogind.so: cannot open shared object file: No such file or directory
août 28 22:25:53 coder-pc sddm-helper[1232]: PAM adding faulty module: /usr/lib/security/pam_elogind.so
août 28 22:25:53 coder-pc sddm-helper[1249]: PAM unable to dlopen(/usr/lib/security/pam_elogind.so): /usr/lib/security/pam_elogind.so: cannot open shared object file: No such file or directory
août 28 22:25:53 coder-pc sddm-helper[1249]: PAM adding faulty module: /usr/lib/security/pam_elogind.so
août 28 22:25:53 coder-pc sddm-helper[1258]: PAM unable to dlopen(/usr/lib/security/pam_elogind.so): /usr/lib/security/pam_elogind.so: cannot open shared object file: No such file or directory
août 28 22:25:53 coder-pc sddm-helper[1258]: PAM adding faulty module: /usr/lib/security/pam_elogind.so
août 28 22:26:01 coder-pc login[1268]: pam_tally2(login:auth): pam_get_uid; no such user

My drivers are all updated