You are not logged in.
Last week, I updated the system using 'yay -Syu.' I'm not sure if my boot partition was mounted, but I think it was. Even with it mounted, the system update caused a kernel inconsistency issue. I attempted to chroot into the system and update it using 'mkinitcpio -p linux-zen' and then ran 'pacman -Syu' multiple times too, but the problem remained. I already looked at some posts on the forum, but I couldn't solve the problem and I'm almost reinstalling everything again.
I'll be grateful if someone can help me.
Some prints below:
https://ibb.co/m5yGCZ8
https://ibb.co/cvDQ4ZL
https://ibb.co/BN7XL5n
https://ibb.co/Ng067kF
Last edited by iagozag (2023-10-23 19:26:15)
Offline
are you booting into UKI (according to the second image)? did you checked it was created during mkinitcpio step? try the booting normal kernel (/boot/vmlinuz-linux-zen, and matching initramfs) instead.
Offline
are you booting into UKI (according to the second image)? did you checked it was created during mkinitcpio step? try the booting normal kernel (/boot/vmlinuz-linux-zen, and matching initramfs) instead.
I use efibootmgr to boot copying vmlinuz-zen to efi/boot/bootzenx64.efi and yeah, when I do mkinitcpio, this update the files on /boot, but not the efi/boot/bootzenx64.efi file. When I manually update this file the system boots but not in a normal way. I use ly to login to my user and start the awesome, but now I can't login to my user and many things isn't working properly, like startx or network manager, etc.
https://ibb.co/2cXvSk2
https://ibb.co/GRntN72
In the first image, I'm logged in as the "ventoy" user, but using the 'su ventoy' command. When I attempt to log in after boot, it doesn't produce an error, but instead briefly flashes the screen and then prompts for the username and password again. Additionally, I use "ly" to log in as my user and initiate the "awesome" desktop environment, but it doesn't seem to appear. When I use 'su ventoy' and run 'startx', it also generates an error.
Offline
if you are copying it yourself, so make sure also initramfs match. it booting now to the correct kernel, so you have other issues. - check you profile/shell files, your kernel command line, other configs you may have.
and 'su <user>' is different from 'su - <user>' - so some shell files may not have run that way.
Offline
if you are copying it yourself, so make sure also initramfs match. it booting now to the correct kernel, so you have other issues. - check you profile/shell files, your kernel command line, other configs you may have.
and 'su <user>' is different from 'su - <user>' - so some shell files may not have run that way.
how can I be sure that initramfs is correct?
zshprofile is apparently right and 'su - ventoy' doesn't really work for logging into ventoy
Edit: changing the shell to bash solved the problem for log in to ventoy user, just startx that doesn't work yet.
Last edited by iagozag (2023-10-23 14:27:50)
Offline
The xserverrc is bogus, https://man.archlinux.org/man/extra/xor … n#nolisten and see the last link below
Offline
The xserverrc is bogus, https://man.archlinux.org/man/extra/xor … n#nolisten and see the last link below
The .xserverrc was broken, and after fixing the line, startx is working again. There are still some broken symlinks, but I'll fix them over time if needed.
Thank you very much to everyone who helped.
Last edited by iagozag (2023-10-23 19:23:22)
Offline