How do I bring back the GUI when I start the kernel?

Support
, ,
1

Good evening/day everyone! Sometimes there are days when the earth goes from under your feet, although the sky gives hope. But I digress.

One day after logging into manjaro I encountered the following problem: the screen began to freeze after entering the login and password at display manager. ALT + F2 didn’t work at all and CTRL + ALT + F2 made the system freeze right away. As a result, I connected to the partition using “chroot” and installed new kernels. From that moment on, the problem with the constantly frozen screen disappeared, but another one appeared: all kernels don’t load “Gui” , but open immediately “Tty”.

I checked the system by “journalctl”, but can’t find a solution to the problem. Here the logs.

`-- Boot 57d128f0da604004b33e69910810e317 –
Nov 27 16:02:40 Max kernel: x86/cpu: SGX disabled by BIOS.
Nov 27 16:02:40 Max kernel: Spectre V2 : WARNING: Unprivileged eBPF is ena>
Nov 27 16:02:40 Max kernel: ACPI BIOS Error (bug): Could not resolve symbo>
Nov 27 16:02:40 Max kernel: ACPI Error: Aborting method _SB.PR01.CPC due>
Nov 27 16:02:40 Max kernel: ACPI BIOS Error (bug): Could not resolve symbo>
Nov 27 16:02:40 Max kernel: ACPI Error: Aborting method _SB.PR02.CPC due>
Nov 27 16:02:40 Max kernel: ACPI BIOS Error (bug): Could not resolve symbo>
Nov 27 16:02:40 Max kernel: ACPI Error: Aborting method _SB.PR03.CPC due>
Nov 27 16:02:40 Max kernel: ACPI BIOS Error (bug): Could not resolve symbo>
Nov 27 16:02:40 Max kernel: ACPI Error: Aborting method _SB.PR04.CPC due>
Nov 27 16:02:40 Max kernel: ACPI BIOS Error (bug): Could not resolve symbo>
Nov 27 16:02:40 Max kernel: ACPI Error: Aborting method _SB.PR05.CPC due>
Nov 27 16:02:40 Max systemd-modules-load[315]: Failed to find module 'cryp>
Nov 27 16:02:40 Max systemd-modules-load[315]: Failed to find module 'nvid>
Nov 27 16:02:40 Max systemd-modules-load[315]: Failed to find module 'nvid>
Nov 27 16:02:40 Max systemd-modules-load[315]: Failed to find module ‘silk’
Nov 27 16:02:40 Max systemd-modules-load[315]: Failed to find module 'nvid>
Nov 27 16:02:40 Max systemd-modules-load[315]: Failed to find module 'vbox>
Nov 27 16:02:40 Max systemd-modules-load[315]: Failed to find module 'vbox>
Nov 27 16:02:40 Max systemd-modules-load[315]: Failed to find module 'vbox>
Nov 27 16:02:40 Max systemd[1]: Failed to mount /boot/efi.
Nov 27 16:08:51 Max systemd[1]: Failed to mount /boot/efi.
Nov 27 16:12:33 Max systemd-cryptsetup[893]: Device luks-e16f7ca5-6ddd-43c>
Nov 27 16:12:33 Max systemd-cryptsetup[893]: Failed to deactivate: Device >
– Boot 66cda73c94584bdd859b9ba59e3cfe24 –
Nov 27 16:16:33 Max kernel: Spectre V2 : WARNING: Unprivileged eBPF is ena>
Nov 27 16:16:33 Max systemd-modules-load[292]: Failed to find module 'nvid>
Nov 27 16:16:33 Max systemd-modules-load[292]: Failed to find module 'nvid>
Nov 27 16:16:33 Max systemd-modules-load[292]: Failed to find module ‘silk’
Nov 27 16:16:33 Max systemd-modules-load[292]: Failed to find module 'nvid>
Nov 27 16:16:33 Max systemd-modules-load[292]: Failed to find module 'vbox>
Nov 27 16:16:33 Max systemd-modules-load[292]: Failed to find module 'vbox>
Nov 27 16:16:33 Max systemd-modules-load[292]: Failed to find module 'vbox>
Nov 27 16:16:34 Max bluetoothd[941]: src/plugin.c:plugin_init() Failed to >
Nov 27 16:16:34 Max bluetoothd[941]: src/plugin.c:plugin_init() Failed to >
Nov 27 16:16:34 Max bluetoothd[941]: src/plugin.c:plugin_init() Failed to >
Nov 27 16:16:35 Max bluetoothd[941]: Failed to set mode: Blocked through r>
Nov 27 16:16:35 Max kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e00>
Nov 27 16:16:35 Max kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
Nov 27 16:16:35 Max kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
Nov 27 16:16:44 Max gdm-launch-environment][1037]: GLib-GObject: g_object>
Nov 27 16:16:44 Max gdm-launch-environment][1055]: GLib-GObject: g_object>
Nov 27 16:16:44 Max gdm-launch-environment][1062]: GLib-GObject: g_object>
Nov 27 16:16:45 Max gdm-launch-environment][1069]: GLib-GObject: g_object>
Nov 27 16:16:45 Max gdm-launch-environment][1076]: GLib-GObject: g_object>
Nov 27 16:16:45 Max gdm-launch-environment][1083]: GLib-GObject: g_object_>
Nov 27 16:24:57 Max systemd-cryptsetup[1366]: Device luks-e16f7ca5-6ddd-43>
Nov 27 16:24:57 Max systemd-cryptsetup[1366]: Failed to deactivate: Device>
Nov 27 16:24:59 Max kernel: watchdog: watchdog0: watchdog did not stop!
– Boot 704f5fd0319047c4b4af40f83f574816 –
Nov 27 17:23:45 Max kernel: x86/cpu: SGX disabled by BIOS.
Nov 27 17:23:45 Max systemd-modules-load[316]: Failed to find module 'cryp>
Nov 27 17:23:45 Max systemd-modules-load[316]: Failed to find module 'nvid>
Nov 27 17:23:45 Max systemd-modules-load[316]: Failed to find module 'nvid>
Nov 27 17:23:45 Max systemd-modules-load[316]: Failed to find module ‘silk’
Nov 27 17:23:45 Max systemd-modules-load[316]: Failed to find module 'nvid>
Nov 27 17:23:45 Max systemd-modules-load[316]: Failed to find module 'vbox>
Nov 27 17:23:45 Max systemd-modules-load[316]: Failed to find module 'vbox>
Nov 27 17:23:45 Max systemd-modules-load[316]: Failed to find module ‘vbox>
Nov 27 17:23:45 Max systemd[1]: Failed to mount /boot/efi.
Nov 27 17:28:02 Max systemd-cryptsetup[774]: Device luks-e16f7ca5-6ddd-43c>
Nov 27 17:28:02 Max systemd-cryptsetup[774]: Failed to deactivate: Device’

I really ask for help, as I do not have enough of my own knowledge. Thank you.
P.S. System is dual booting.

2

Welcome to the forum! :wave:

Your topic title is not representative of the problem you’re having. It has nothing to do with the kernel. I edited your topic title and moved your post to a different category for a reason.

Apparently you think you know better, so I reverted all changes and restored it to the original state. Please edit your topic title and post according to the following:

1 Like
3

I may be missing something but I do believe I may need to beg to differ? I.e.,

It seems the issue would here be that he didn’t reinstall the Nvidia driver when in chroot installing his new kernel(s)?

I don’t do Nvidia so I don’t know what the normal/best way is to fix things up…

4

Welcome to Manjaro! :smiling_face_with_three_hearts:

  1. Please read the information behind this link. It will help you to post necessary information. [HowTo] Provide System Information
  2. Please press the three dots … below your post and then press the :pencil2:
  • If you give us information about your system, we can see what we’re talking about and make better suggestions.
  • You can do this by using inxi in a terminal or in console.
inxi --admin --verbosity=7 --filter --no-host --width
  • Personally identifiable information such as serial numbers and MAC addresses are filtered out by this command
  • Presenting the information in this way allows everyone to be familiar with the format and quickly find the items they need without missing anything.
  1. Copy the output from inxi (including the command) and paste it into your post.
  • To make it more readable, add 3 backticks ``` on an extra line before and after the pasted text.
    (Wisdom lies in reading :wink: )

Dual boot with windows:

Please install 2 kernels (one of them LTS)

5

You provide way too little info to deduct anything from.

The kernel has nothing to do with with loading any GUI - if you are logged into tty it means the display manager service is missing.

The journal output is truncated by a narrow terminal - thus information is not complete

These messages are irrelevant to the issue at hand.

You didn’t mention your linux root is encrypted

If the modules is expected to be available - then filesystem error is a likely cause but an interupted sync could also cause it.

So - as there is no apparent reason and no clues to why your system behaves like it does - You will have to retrace your steps.

The content of the files created from these commands may provide insight

Please provide the links returned to you

pacman -Qqm | curl -F 'f:1=<-' ix.io

cat /etc/pacman.conf | curl -F 'f:1=<-' ix.io

grep /var/log/pacman.log -e '22-11-26' -e '22-11-27' -e '22-11-28'  | curl -F 'f:1=<-' ix.io
6

Thanks for the feedback. Unfortunately, the last command does not create a link.

http://ix.io/4h5W
http://ix.io/2fAb

7

please retry - I have tested the commands

This link show a dozen packages either from AUR or no longer in the official repo

Please remove them as it is possible one of them is interfering

sudo pacman -Rns $(pacman -Qqm)

I am still assuming your system is in luks container - exit chroot and unmount the mount point

  • do not close the luks container
  • run a filesystem check on the luks device.
  • depending on the result - you may need further action
9

You were right.I probably made a mistake in syntax. here’s the link.

http://ix.io/4h66

10 
[2022-11-27T12:49:08+0000] [ALPM-SCRIPTLET] 	 -> Kernel has been updated. Modules of the current kernel
[2022-11-27T12:49:08+0000] [ALPM-SCRIPTLET] 	 -> have been backed up so you can continue to use your
[2022-11-27T12:49:08+0000] [ALPM-SCRIPTLET] 	 -> computer. However, the new kernel will only work
[2022-11-27T12:49:08+0000] [ALPM-SCRIPTLET] 	 -> at next boot.

These lines are generated by the package kernel-alive - please remove that package as well - it may create weird issues

sudo pacman -Rns kernel-alive
11

Yes that’s right - it’s LUKS, but I executed the commands already inside the partition.
I made ‘cryptsetup’, than ‘mount’, than ‘chroot’

12 
[2022-11-27T20:24:41+0000] [ALPM-SCRIPTLET] ==> ERROR: Hook 'suspend' cannot be found

This line indicates an error in your /etc/mkinitcpio.conf. Make sure the mkinitcpio.conf is valid - then rebuild init.

13

Can you provide a command to do these actions?

14

To be able to do that we need to know the contents of the file

cat /etc/mkinitcpio.conf | curl -F 'f:1=<-' ix.io

And the grub default could provide some additional info

cat /etc/default/grub | curl -F 'f:1=<-' ix.io
15

My grub unfortunately broke as well. I can only access it via ‘shift’. Apparently something went wrong when I reinstalled the kernel. It also stopped seeing the second operating system.

http://ix.io/4h6a
http://ix.io/4h6d

16

This is not default - not that it matters - just pointing out - as you mentioned Nvidia in your OT

MODULES="i915"

You have some - to me - unknown hooks

HOOKS="base udev autodetect modconf block keyboard keymap plymouth encrypt filesystems fsck shutdown suspend "

Where do they come from?

You didn’t mention that either - or I have mssed it.

It is very hard to run a multiboot system using grub when grub configs reside inside a LUKS container. I cannot help you with that.

Your grub is not borken it is the default

I have to ask - What kind of frankensystem is this?

It seems your issues are somehow self inflicted and I have no idea what lead up to this and therefore I cannot be of further assistance.

1 Like
17

I honestly don’t remember. the system has been standing for more than a year. I can send you a list of commands that I entered from the terminal over the past few days, there are not many of them. the only thing.

But I don’t remember is how to get this list.

In the first post I pointed out that the system is dual booting (thought to call additional operating systems on the same hardware)

18

Without any documentation on how the suspend and shutdown hook has been added any further suggestions from me may cause furhter issues - and I am not going down that path.

I cannot be of further assistance.

In uncharted territory I may be - inadvertly of course - causing further issues - I really don’t want to do that.

1 Like
19

Understood, thanks for the help. So the problem should be looked for in hooks and mkinitcipio? I’m interested in the future.

20

I am unsure - and I am the fact guy - so when it is not my own system and my own doing - I abstain from experiments. I am sure you can appreciate that :slight_smile: