messed up DE install, can't have DE now. also, Can't pacman -Syu

ahmadsan · 2022-07-31 02:11:14

So, i decided to try arch, i use gnome at first, everything is fine, I decided i wanna go for KDE Plasma, I forgot what I did, but I install Plasma, reboot, switch the DE from gdm login, and plasma running ffine, then I delete gnome and install sddm, all hell break loose, tried deleting quite param in grub, and it shows that my boot stuck in "graphical interface" line and now i can't even boot up any DE... help

can't do -Syu, all mirrors stopped working for some reason ( happens when i tried to install plasma-wayland-session too )

Last edited by ahmadsan (2022-07-31 02:54:21)

seth · 2022-07-31 06:14:32

I delete gnome and install sddm

Did you enable SDDM?

all mirrors stopped working for some reason

https://archlinux.org/packages/community/any/reflector/

sudo journalctl -b | curl -F 'file=@-' 0x0.st
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f | curl -F 'file=@-' 0x0.st

Last edited by seth (2022-07-31 06:17:44)

ahmadsan · 2022-07-31 07:16:11

seth wrote:

I delete gnome and install sddm
Did you enable SDDM?
all mirrors stopped working for some reason
https://archlinux.org/packages/community/any/reflector/
sudo journalctl -b | curl -F 'file=@-' 0x0.st
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f | curl -F 'file=@-' 0x0.st

Yes I did, with sudo systemctl enable sddm.service right?

can't download reflector since the mirrors are all cant be resolved

sudo journalctl -b | curl -F 'file=@-' 0x0.st
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f | curl -F 'file=@-' 0x0.st

it returns "could not resolve host: 0x0.st"

Last edited by ahmadsan (2022-07-31 07:17:45)

ahmadsan · 2022-07-31 07:19:32

also this happen after syncing/dowloading plasma and enabling sddm then reboot, suddenly all mirror cannot be resolved, can't ping google either

seth · 2022-07-31 07:29:33

Your problem isn't w/ the mirrors but that you don't have a network connection.
(Possibly a wifi connection bound to your user login and you're currently logging in as root)?

ahmadsan · 2022-07-31 07:36:02

seth wrote:

Your problem isn't w/ the mirrors but that you don't have a network connection.
(Possibly a wifi connection bound to your user login and you're currently logging in as root)?

tried logging in as root and user, same thing no connection. i got a machine state saved, before doing pacman -S plasma sddm and enabling sddm, the internet's fine there, for some reason after that the internet's gone...

seth · 2022-07-31 07:41:12

The reason will most likely show up in your system journal.
A common cause for "updated and everything broke down" is that you're booting a dated kernel

uname -a; pacman -Qs linux

ahmadsan · 2022-07-31 08:43:37

seth wrote:

The reason will most likely show up in your system journal.
A common cause for "updated and everything broke down" is that you're booting a dated kernel
uname -a; pacman -Qs linux

what's the solution for a dated kernel? how do i update?

Last edited by ahmadsan (2022-07-31 08:44:08)

seth · 2022-07-31 08:54:57

Did you confirm that you're booting a dated kernel?
The fallback initramfs has most (all?) modules baked in and should™ still allow you to enable the network - otherwise you'll have to boot a live distro (the install iso), chroot into the system and update the kernel this way.

The common way to fuck this up and run into the problem is to either forget to mount the /boot partition or installing the kernel into a /boot partition while you're actually booting the root partition.

cat /proc/cmdline

ahmadsan · 2022-07-31 09:01:17

seth wrote:

Did you confirm that you're booting a dated kernel?
The fallback initramfs has most (all?) modules baked in and should™ still allow you to enable the network - otherwise you'll have to boot a live distro (the install iso), chroot into the system and update the kernel this way.
The common way to fuck this up and run into the problem is to either forget to mount the /boot partition or installing the kernel into a /boot partition while you're actually booting the root partition.
cat /proc/cmdline

https://imgur.com/a/XyeFJPa

ahmadsan · 2022-07-31 09:01:57

how do i check if i installed a dated kernel?

seth · 2022-07-31 09:08:31

seth wrote:

uname -a; pacman -Qs linux

You're booting from a /boot partition.

ahmadsan · 2022-07-31 23:28:57

seth wrote:

seth wrote:
uname -a; pacman -Qs linux
You're booting from a /boot partition.

How do I not boot from /boot partition?

https://pastebin.com/sUVDVJFn

Last edited by ahmadsan (2022-07-31 23:29:14)

ewaller · 2022-07-31 23:49:25

You seem to be running the 5.18.14-arch1-1 kernel

Linux myBoyArchie 5.18.14-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 23 Jul 2022 11:46:17 +0000 x86_64 GNU/Linux

And that seems to be the installed kernel

local/linux 5.18.14.arch1-1
    The Linux kernel and modules

So this does not seem to be the issue.

How do I not boot from /boot partition?

Not throwing insults here, but the loose wording of that question hints at the root of the reason (Again this is not applicable to your situation, I just wanted to answer the question)

/boot is not a partition. It can either be a mount point or a directory. If the boot *partition* is mounted on /boot, then /boot is a mount point.
If nothing is mounted on /boot, then it is a normal directory.

When the kernel is updated, the new kernel and initramfs are written to /boot UNDER THE ASSUMPTION that the boot partition is mounted there. If that assumption is wrong, then the kernel and initramfs get written to the directory /boot, but nothing is changed on the (not mounted) boot partition. The next reboot still finds the old kernel and loads it (with the new kernel having been safely written someplace useless during boot) when the old kernel comes up, it looks for its modules, but it cannot find them under /usr/lib/modules because that kernel is no longer installed. This breaks anything that uses a loadable kernel module.

Last edited by ewaller (2022-07-31 23:50:12)

ewaller · 2022-07-31 23:53:32

Is there any chance that Plasma and network manager are configured to use your users credentials rather than system wide credentials? If we are trying to use Network Manager credentials stored in your Plasma keyring, you are not going to have a network without Plasma.

ahmadsan · 2022-08-01 00:15:12

ewaller wrote:

Is there any chance that Plasma and network manager are configured to use your users credentials rather than system wide credentials? If we are trying to use Network Manager credentials stored in your Plasma keyring, you are not going to have a network without Plasma.

man, i'm lost..., what's system wide credential? u mean root? I don't think that's the case...

Also, update on the issue. whenever I do -Syu, network's gone, and can't get to DE (stuck at graphical interface).

i'm still running it in VM for testing. before migrating from win10

should I just stop?
alot of terms i do not understand.

Last edited by ahmadsan (2022-08-01 00:15:36)

ewaller · 2022-08-01 02:05:38

Don't stop.

If I understand the issue, you cannot start a Plasma environment.
You are more comfortable with a GUI interface than a command line interface.
To fix things, we think you need a network connection.
Your network connection is obstinately refusing to cooperate.

I think it is because you have somehow configured your network to use credentials that depend on you being logged into Plasma, but Plasma is borked.

Try nmtui (I hope it is installed). See if you can use that to bring up your network (nmtui is a gui-ish interface that will work in a console)

Arch Linux

#1 2022-07-31 02:11:14

messed up DE install, can't have DE now. also, Can't pacman -Syu

#2 2022-07-31 06:14:32

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#3 2022-07-31 07:16:11

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#4 2022-07-31 07:19:32

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#5 2022-07-31 07:29:33

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#6 2022-07-31 07:36:02

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#7 2022-07-31 07:41:12

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#8 2022-07-31 08:43:37

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#9 2022-07-31 08:54:57

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#10 2022-07-31 09:01:17

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#11 2022-07-31 09:01:57

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#12 2022-07-31 09:08:31

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#13 2022-07-31 23:28:57

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#14 2022-07-31 23:49:25

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#15 2022-07-31 23:53:32

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#16 2022-08-01 00:15:12

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

#17 2022-08-01 02:05:38

Re: messed up DE install, can't have DE now. also, Can't pacman -Syu

Board footer