You are not logged in.

#1 2023-07-31 06:46:05

compsci101
Member
Registered: 2022-01-04
Posts: 5

[SOLVED] Boot halts at "Reached target Graphical Interface"

Hey all smile

Just a quick note to see if anyone is experiencing a similar issue.

After upgrading linux 6.4.5.arch1-1 -> 6.4.7.arch1-1 and nvidia 535.86.05-3 -> 535.86.05-4 I was not able to successfully boot to a display manager (SDDM, in my case); the boot halted at "Reached target Graphical Interface".  There were other packages that were upgraded along with the kernel and the driver, but it seems like the kernel was the main issue (the Nvidia driver didn't seem to have a version bump).

After the halt, I was able to switch to a virtual console, log in, and downgrade the two packages.  Rebooting after the downgrade allowed me to get a graphical session working again.

I looked in journalctl for both the bad boot and good boot, but nothing jumped out at me.  Is there any advice on what I should maybe look for in the logs?

Thanks!
C

Last edited by compsci101 (2023-07-31 20:40:48)

Offline

#2 2023-07-31 06:53:30

seth
Member
Registered: 2012-09-03
Posts: 63,384

Re: [SOLVED] Boot halts at "Reached target Graphical Interface"

The common cause is that you forgot to mount the /boot partition, the kernel update went into the wrong location and you're booting an old kernel that finds no modules installed.
Otherwise please post your complete system journal for the boot, eg.

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

for the previous one (if that was the one w/ the udpated kernel, otherwise increase the digit in "-b -1" to go further back)

Offline

#3 2023-07-31 16:24:57

compsci101
Member
Registered: 2022-01-04
Posts: 5

Re: [SOLVED] Boot halts at "Reached target Graphical Interface"

Thanks very much seth smile

Here is the log of the bad boot:
https://termbin.com/28st

and here is the good boot after reverting the packages:
https://termbin.com/g45x

What should I be looking for in the log to see if this was the actual problem?  The first line of each line seems to indicate the the kernels that are being loaded are the expected versions.

Offline

#4 2023-07-31 16:32:19

Scimmia
Fellow
Registered: 2012-09-01
Posts: 12,643

Re: [SOLVED] Boot halts at "Reached target Graphical Interface"

Jul 31 00:10:44 fortress systemd-modules-load[407]: Failed to find module 'nvidia-uvm'

"and nvidia 535.86.05-3 -> 535.86.05-4"

you need pkgrel 5 for  6.4.7.arch1-1. You had the nvidia modules for  6.4.6.arch1-1 (see https://gitlab.archlinux.org/archlinux/ … mits/main)

Fully update the system, and if it doesn't get the correct modules package, post your pacman.conf and your mirrorlist.

Edit: in fact, post them either way. A misconfigured pacman.conf will have this happening regularly and needs to be dealt with.

Last edited by Scimmia (2023-07-31 16:55:00)

Offline

#5 2023-07-31 19:03:46

compsci101
Member
Registered: 2022-01-04
Posts: 5

Re: [SOLVED] Boot halts at "Reached target Graphical Interface"

pacman.conf
https://termbin.com/b197

mirrorlist
https://termbin.com/nvi2

It looks like there's a pacman.conf.pacnew waiting for me in /etc/, but a diff seems to only show that there's new testing configs that would be commented out either way.  I have multilib enabled because of Steam.

My mirrorlist is unfortunately ancient.  I'll try updating that and seeing if that helps.

Thanks, Scimmia!
C

Offline

#6 2023-07-31 19:11:53

seth
Member
Registered: 2012-09-03
Posts: 63,384

Re: [SOLVED] Boot halts at "Reached target Graphical Interface"

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

Top mirror is synced, though.
Might just have been a fluke.


Edit: wrt your pending pacman.conf, the community repo is gone - but that's not the cause of this.

Last edited by seth (2023-07-31 19:13:11)

Offline

#7 2023-07-31 20:39:56

compsci101
Member
Registered: 2022-01-04
Posts: 5

Re: [SOLVED] Boot halts at "Reached target Graphical Interface"

That was definitely the issue -- it looks like my preferred mirrors were stale and serving old versions of (at least) the nvidia package.  It seems like it was MIT that did me in: https://mirrors.mit.edu/archlinux/extra/os/x86_64/ still lists nvidia-535.86.05-4-x86_64.pkg.tar.zst as the current version, although at https://mirrors.mit.edu/archlinux/core/os/x86_64/ they also show linux-6.4.6.arch1-1-x86_64.pkg.tar.zst as the current kernel.  It seems like my local core was updated from a repository that was more current, and then fell back to a different, out of date mirror for extra.

Updating my mirrorlist and changing the mirror order seems to have fixed things.

Offline

Board footer

Powered by FluxBB