Won’t Boot After Restart

Support
,
1

I clicked to restart Manjaro after I ran updates in Manjaro. I had run updates, gone to sleep mode, came out of it, and could not login to any account (did not accept passwords on login screen) and then clicked to restart to hopefully resolve the issue of not being able to login.

Instead, it got stuck on a black screen with a large dell logo. It never gets past this screen. I have tried restarting several times and trying different Manjaro backups from the grub menu but it gives the same issue. Booting into my windows partition works well.

I cannot get to command line or anything with shift alt F2. I can’t post details of my computer because I cannot get past this dell logo now. It used to work fine. Info on my system can be found on my other post (it is hard for me to copy and paste on mobile).

Thank you!

2

can you boot on USB iso manjaro
open a terminal and a browser on this topic
and returns

sudo manjaro-chroot -a ( type 1 if only one line - 0 appears )
grep -E "pam_tally|pam_cracklib" /etc/pam.d/*
journalctl -b -1 -p4
exit ( quit chroot )
3

Thanks. Sorry I need clarification – I don’t understand what ( type 1 if only one line - 0 appears) means. I have the usb iso up, but I am confused on the first command.

I type sudo manjaro-chroot -a

Then it gives me "Detected systems: 0) ManjaroLinux, and then Select system to mount [0-0].

These look like multiple lines of code, but also only one detected system. So do I say 1 or 0? Thanks!

4

OK, 0 doesn’t work anyways, so I did 1 - I hope that is right. Here are the outputs:

sudo manjaro-chroot -a
==> Detected systems:
–> 0) ManjaroLinux
==> Select system to mount [0-0] :
1
==> Mounting (ManjaroLinux) [/dev/nvme0n1p7]
–> mount: [/mnt]
–> mount: [/mnt/boot/efi]

For grep -E “pam_tally|pam_cracklib” /etc/pam.d/*
/etc/pam.d/passwd:#password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
/etc/pam.d/system-login:auth required pam_tally2.so onerr=succeed file=/var/log/tallylog
/etc/pam.d/system-login:account required pam_tally2.so

For journalctl -b -1 -p4
– Logs begin at Tue 2020-08-25 13:47:51 MDT, end at Fri 2020-08-28 10:55:28>
Aug 28 10:40:55 keith-xps139300 kernel: ENERGY_PERF_BIAS: Set to ‘normal’, w>
Aug 28 10:40:55 keith-xps139300 kernel: pci 0000:00:07.0: DPC: RP PIO log si>
Aug 28 10:40:55 keith-xps139300 kernel: pci 0000:00:07.2: DPC: RP PIO log si>
Aug 28 10:40:55 keith-xps139300 kernel: hpet_acpi_add: no address or irqs in>
Aug 28 10:40:55 keith-xps139300 kernel: i8042: Warning: Keylock active
Aug 28 10:40:55 keith-xps139300 kernel: usb: port power management may be un>
Aug 28 10:40:55 keith-xps139300 systemd-modules-load[266]: Failed to find mo>
Aug 28 10:40:55 keith-xps139300 systemd-modules-load[266]: Failed to find mo>
Aug 28 10:40:55 keith-xps139300 systemd-modules-load[266]: Failed to find mo>
Aug 28 10:40:55 keith-xps139300 kernel: wmi_bus wmi_bus-PNP0C14:03: WQBC dat>
Aug 28 10:40:55 keith-xps139300 kernel: thunderbolt 0000:00:0d.2: 0: uid crc>
Aug 28 10:40:56 keith-xps139300 kernel: iwlwifi 0000:00:14.3: api flags inde>
Aug 28 10:40:56 keith-xps139300 kernel: iwlwifi 0000:00:14.3: Direct firmwar>
Aug 28 10:40:56 keith-xps139300 kernel: i2c_hid i2c-DLL096D:01: supply vdd n>
Aug 28 10:40:56 keith-xps139300 kernel: i2c_hid i2c-DLL096D:01: supply vddl >
Aug 28 10:40:56 keith-xps139300 kernel: thunderbolt 0000:00:0d.3: 0: uid crc>
Aug 28 10:40:56 keith-xps139300 kernel: thermal thermal_zone6: failed to rea>
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.0: Entity type for en>
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.0: Entity type for en>
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.0: Entity type for en>
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.0: Entity type for en>
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.2: Entity type for en>
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.2: Entity type for en>
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.2: Entity type for en>
lines 1-25…skipping…
– Logs begin at Tue 2020-08-25 13:47:51 MDT, end at Fri 2020-08-28 10:55:28 MDT. –
Aug 28 10:40:55 keith-xps139300 kernel: ENERGY_PERF_BIAS: Set to ‘normal’, was ‘performance’
Aug 28 10:40:55 keith-xps139300 kernel: pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
Aug 28 10:40:55 keith-xps139300 kernel: pci 0000:00:07.2: DPC: RP PIO log size 0 is invalid
Aug 28 10:40:55 keith-xps139300 kernel: hpet_acpi_add: no address or irqs in _CRS
Aug 28 10:40:55 keith-xps139300 kernel: i8042: Warning: Keylock active
Aug 28 10:40:55 keith-xps139300 kernel: usb: port power management may be unreliable
Aug 28 10:40:55 keith-xps139300 systemd-modules-load[266]: Failed to find module ‘vboxdrv’
Aug 28 10:40:55 keith-xps139300 systemd-modules-load[266]: Failed to find module ‘vboxnetadp’
Aug 28 10:40:55 keith-xps139300 systemd-modules-load[266]: Failed to find module ‘vboxnetflt’
Aug 28 10:40:55 keith-xps139300 kernel: wmi_bus wmi_bus-PNP0C14:03: WQBC data block query control method not found
Aug 28 10:40:55 keith-xps139300 kernel: thunderbolt 0000:00:0d.2: 0: uid crc8 mismatch (expected: 0x8e, got: 0xe7)
Aug 28 10:40:56 keith-xps139300 kernel: iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
Aug 28 10:40:56 keith-xps139300 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwl-debug-yoyo.bin failed with error -2
Aug 28 10:40:56 keith-xps139300 kernel: i2c_hid i2c-DLL096D:01: supply vdd not found, using dummy regulator
Aug 28 10:40:56 keith-xps139300 kernel: i2c_hid i2c-DLL096D:01: supply vddl not found, using dummy regulator
Aug 28 10:40:56 keith-xps139300 kernel: thunderbolt 0000:00:0d.3: 0: uid crc8 mismatch (expected: 0x8e, got: 0xe7)
Aug 28 10:40:56 keith-xps139300 kernel: thermal thermal_zone6: failed to read out thermal zone (-61)
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.0: Entity type for entity Extension 4 was not initialized!
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.0: Entity type for entity Extension 6 was not initialized!
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.0: Entity type for entity Processing 2 was not initialized!
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.0: Entity type for entity Camera 1 was not initialized!
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.2: Entity type for entity IR Microsoft Extended Controls was not initialized!
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.2: Entity type for entity Extension 10 was not initialized!
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.2: Entity type for entity Extension 11 was not initialized!
Aug 28 10:40:57 keith-xps139300 kernel: uvcvideo 3-9:1.2: Entity type for entity Camera 9 was not initialized!
Aug 28 10:40:58 keith-xps139300 wpa_supplicant[1553]: nl80211: kernel reports: Attribute failed policy validation
Aug 28 10:40:58 keith-xps139300 wpa_supplicant[1553]: Failed to create interface p2p-dev-wlp0s20f3: -22 (Invalid argument)
Aug 28 10:40:58 keith-xps139300 wpa_supplicant[1553]: nl80211: Failed to create a P2P Device interface p2p-dev-wlp0s20f3
Aug 28 10:40:58 keith-xps139300 NetworkManager[1415]: [1598632858.3522] sup-iface[dd16a14cbe0f4feb,0,wlp0s20f3]: call-p2p-cancel: failed with P2P cancel failed
Aug 28 10:40:59 keith-xps139300 sddm-helper[1768]: PAM unable to dlopen(/usr/lib/security/pam_tally2.so): /usr/lib/security/pam_tally2.so: cannot open shared object file: No such file or directory
Aug 28 10:40:59 keith-xps139300 sddm-helper[1768]: PAM adding faulty module: /usr/lib/security/pam_tally2.so
Aug 28 10:40:59 keith-xps139300 sddm-helper[1768]: gkr-pam: no password is available for user
Aug 28 10:40:59 keith-xps139300 sddm-helper[1768]: [PAM] acctMgmt: Module is unknown
Aug 28 10:40:59 keith-xps139300 sddm[1554]: Authentication error: “Module is unknown”
Aug 28 10:40:59 keith-xps139300 sddm[1554]: Auth: sddm-helper exited with 1
Aug 28 10:40:59 keith-xps139300 kernel: kauditd_printk_skb: 55 callbacks suppressed
Aug 28 10:41:00 keith-xps139300 kernel: typec_displayport port1-partner.1: failed to enter mode
Aug 28 10:51:03 keith-xps139300 sddm[1554]: Signal received: SIGTERM
Aug 28 10:51:04 keith-xps139300 NetworkManager[1415]: [1598633464.5544] dispatcher: (9) failed: Refusing activation, D-Bus is shutting down.

Sorry, the code-blocking isn’t working for me on this message for some reason…Thanks!

5

you go in chroot for update /etc/pam.d/
( you have .pacnew for theses files i hope )

see this topic

2 Likes
6

OK, so I should find a way to those pam.d files with chroot and try to make the changes outlined in that post?

7

After making the changes in the Unstable Update post you linked me to, I was able to get back in to my normal system without a hitch! THANK YOU!

8

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