[SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

TakaoDev · 2023-06-04 13:57:57

Hello, i wanted to install nvidia drivers but made a mess and now my arch linux doesnt boot. I've tried anything, reinstalling drivers, removing nouveau etc...
but it still doesnt work. Tried removing quiet from kernel to see what happened and i see that its stuck on [OK] reached target Graphical Interface. I can get access with a tty2, can anyone pls help me? I've got important files here and i dont wanna loose my entire ecosystem.
Thanks for helping!

Last edited by TakaoDev (2023-06-04 16:50:16)

seth · 2023-06-04 14:03:06

I can get access with a tty2

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'f:1=<-' ix.io

Also see the 2nd link below on how to boot the multi-user.target.
Don't freak out, you probably just fucked up the https://wiki.archlinux.org/title/NVIDIA#Installation
Point #5 is recently very popular for being ignored…

TakaoDev · 2023-06-04 14:07:03

how can i send it here? i cant copy and paste it

seth · 2023-06-04 14:08:54

If you enter the command I posted you'll get a url that you can post.
Did you look at the wiki and specifically item #5 ?

TakaoDev · 2023-06-04 14:14:16

seth wrote:

If you enter the command I posted you'll get a url that you can post.
Did you look at the wiki and specifically item #5 ?

This is the link: http://ix.io/4xsE
Im going to look rn at the wiki.

Last edited by TakaoDev (2023-06-04 14:14:43)

seth · 2023-06-04 14:17:38

Neither nouveau nor nvidia loads and you're booting an old kernel - you forgot to mount the /boot partition before updating.

TakaoDev · 2023-06-04 14:19:42

seth wrote:

If you enter the command I posted you'll get a url that you can post.
Did you look at the wiki and specifically item #5 ?

I dont have kms on HOOKS but im getting an error when running mkinitcpio -P

ERROR: specified kernel image does not exist

(I have been getting this error before too)

TakaoDev · 2023-06-04 14:21:56

seth wrote:

Neither nouveau nor nvidia loads and you're booting an old kernel - you forgot to mount the /boot partition before updating.

So what should i do now?

seth · 2023-06-04 14:24:04

Boot the multi-user target, clear the mountpoint (remove the files from /boot when the partition isn't mounted there), then mount the /boot partition and re-install the kernel.

TakaoDev · 2023-06-04 14:32:49

seth wrote:

Boot the multi-user target, clear the mountpoint (remove the files from /boot when the partition isn't mounted there), then mount the /boot partition and re-install the kernel.

Can you explain a little better? With commands maybe, i'm a little new at this so i dont actually know how to do that... Thanks a lot for helping me!

seth · 2023-06-04 14:37:22

How did you install… the install script

As mentioned, the second link below explains how to boot the multi-user.target, you can see your partitions and where they're mounted w/ "lsblk -f"

I'll not explain how to remove files, mount partitions or install packages. You're supposed to know all of that.
Google and in doubt ask back whether your intended approach is sane/correct.

TakaoDev · 2023-06-04 14:45:37

seth wrote:

How did you install… the install script
As mentioned, the second link below explains how to boot the multi-user.target, you can see your partitions and where they're mounted w/ "lsblk -f"
I'll not explain how to remove files, mount partitions or install packages. You're supposed to know all of that.
Google and in doubt ask back whether your intended approach is sane/correct.

Okay i now understood, when i run lsblk -f i cant see a /boot partition tho and thats kinda strange i guess that the boot one is the vfat one tho

Last edited by TakaoDev (2023-06-04 14:46:10)

seth · 2023-06-04 14:48:19

If you want any kind of informed comment on the situation, you'll have to share the data (ie. post the output)
And to be absolutely sure: compare

uname -a
pacman -Q linux

The versions have to match (and from your previous posts I suspect they don't)

TakaoDev · 2023-06-04 14:52:08

seth wrote:

If you want any kind of informed comment on the situation, you'll have to share the data (ie. post the output)
And to be absolutely sure: compare
uname -a
pacman -Q linux
The versions have to match (and from your previous posts I suspect they don't)

They actually are both 6.3.2.arch1-1
The output from lsblk -f is this: http://ix.io/4xsL

seth · 2023-06-04 14:57:09

So you just ran a partial update?

pacman -Syu

Edit: And the (likely) /boot partition isn't mounted.

Last edited by seth (2023-06-04 14:58:08)

TakaoDev · 2023-06-04 14:57:50

seth wrote:

So you just ran a partial update?
pacman -Syu

yes i did that

seth · 2023-06-04 15:00:28

The kernel is at 6.3.5.arch1-1 and 6.3.2 is dated since May 21st

Post your pacman log

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

TakaoDev · 2023-06-04 15:07:30

seth wrote:

The kernel is at 6.3.5.arch1-1 and 6.3.2 is dated since May 21st
Post your pacman log
cat /var/log/pacman.log | curl -F 'f:1=<-' ix.io

Oh i think the update didnt finish before, i just updated it and this is the log: http://ix.io/4xsU
Should i just reboot now? To see it anything changed..

seth · 2023-06-04 15:29:45

From what I can tell you updated w/o the /boot partition being mouted?
That's not gonna work (mount the boot partition and re-install the kernel), but otherwise yes.

Then post an updated log and stop messing w/ the system before you're getting a comment on the status quo.
Creating a moving target makes it hard to impossible to fix anything because you get advise on a dated situation.

TakaoDev · 2023-06-04 15:49:09

seth wrote:

From what I can tell you updated w/o the /boot partition being mouted?
That's not gonna work (mount the boot partition and re-install the kernel), but otherwise yes.
Then post an updated log and stop messing w/ the system before you're getting a comment on the status quo.
Creating a moving target makes it hard to impossible to fix anything because you get advise on a dated situation.

I'm probably going to give up, because im trying so hard and it is not working, i think that i'll move the important files and try with a new install...

I tried searching how to mount the boot partition but i cant find anything that works for me...

(The boot works fine but i just get the tty and not the graphical environment)

Last edited by TakaoDev (2023-06-04 15:52:19)

seth · 2023-06-04 16:01:29

Reinstalling won't help you unless you install eg. ubuntu.

cat /etc/fstab
ls -lR /boot
mount /dev/nvme0n1p1 /boot # https://man.archlinux.org/man/core/util-linux/mount.8.en
ls -lR /boot

Edit: and post an updated journal

Last edited by seth (2023-06-04 16:01:55)

TakaoDev · 2023-06-04 16:05:51

seth wrote:

Reinstalling won't help you unless you install eg. ubuntu.
cat /etc/fstab
ls -lR /boot
mount /dev/nvme0n1p1 /boot # https://man.archlinux.org/man/core/util-linux/mount.8.en
ls -lR /boot
Edit: and post an updated journal

thanks for the help, but the nvme0n1p1 is a windows partition and i dont wanna touch it, ik that dev/sda5 is the boot one but when i try to mount it, it gives an error: unknown filesystem type "vfat"

seth · 2023-06-04 16:13:15

You're getting that error because you're booting an old kernel, the vfat module for that version is not available.
Boot the install iso and arch-chroot into the system.

TakaoDev · 2023-06-04 16:25:59

Okay i mounted, but now it isnt reading the wifi cards, so i cant send journal... ? (And still no graphical interface)

seth · 2023-06-04 16:30:05

You've an iwlwifi chip, that'll be supported by the iso

ip a

But you still need to connect to the AP using iwd (like when you installed the system)

But if you're confident that you've mounted the boot partition, just run "pacman -S linux" from the chroot, it'll install the kernel from the pacman cache into the proper partition.

Arch Linux

#1 2023-06-04 13:57:57

[SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#2 2023-06-04 14:03:06

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#3 2023-06-04 14:07:03

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#4 2023-06-04 14:08:54

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#5 2023-06-04 14:14:16

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#6 2023-06-04 14:17:38

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#7 2023-06-04 14:19:42

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#8 2023-06-04 14:21:56

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#9 2023-06-04 14:24:04

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#10 2023-06-04 14:32:49

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#11 2023-06-04 14:37:22

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#12 2023-06-04 14:45:37

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#13 2023-06-04 14:48:19

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#14 2023-06-04 14:52:08

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#15 2023-06-04 14:57:09

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#16 2023-06-04 14:57:50

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#17 2023-06-04 15:00:28

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#18 2023-06-04 15:07:30

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#19 2023-06-04 15:29:45

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#20 2023-06-04 15:49:09

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#21 2023-06-04 16:01:29

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#22 2023-06-04 16:05:51

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#23 2023-06-04 16:13:15

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#24 2023-06-04 16:25:59

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

#25 2023-06-04 16:30:05

Re: [SOLVED] Boot stuck at [OK] Reached target Graphical Interface.

Board footer