[SOLVED] GUI login fail after upgrade (mapping multiple BARs)

Storm · 2019-10-16 19:02:35

I just tried to upgrade my system but after that trying to log in with my user fails with a kernel/nvidia related error:

Relevant part of journal:

Oct 16 20:31:24 Camelot login[619]: LOGIN ON tty1 BY storm
Oct 16 20:31:24 Camelot systemd[623]: Starting D-Bus User Message Bus Socket.
Oct 16 20:31:24 Camelot systemd[623]: Listening on GnuPG network certificate management daemon.
Oct 16 20:31:24 Camelot systemd[623]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Oct 16 20:31:24 Camelot systemd[623]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Oct 16 20:31:24 Camelot systemd[623]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Oct 16 20:31:24 Camelot systemd[623]: Listening on GnuPG cryptographic agent and passphrase cache.
Oct 16 20:31:24 Camelot systemd[623]: Listening on p11-kit server.
Oct 16 20:31:24 Camelot systemd[623]: Listening on Sound System.
Oct 16 20:31:24 Camelot systemd[623]: Listening on D-Bus User Message Bus Socket.
Oct 16 20:31:24 Camelot systemd[623]: Reached target Sockets.
Oct 16 20:31:24 Camelot systemd[623]: Reached target Basic System.
Oct 16 20:31:24 Camelot systemd[623]: Reached target Main User Target.
Oct 16 20:31:24 Camelot systemd[623]: Startup finished in 166ms.
Oct 16 20:31:24 Camelot systemd[1]: Started User Manager for UID 1000.
Oct 16 20:31:24 Camelot systemd[1]: Started Session 1 of user storm.
Oct 16 20:31:25 Camelot dhcpcd[617]: enp3s0: no IPv6 Routers available
Oct 16 20:31:25 Camelot kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000d3fff window]
Oct 16 20:31:25 Camelot kernel: caller _nv000926rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs
Oct 16 20:31:26 Camelot systemd[623]: Started D-Bus User Message Bus.
Oct 16 20:31:28 Camelot login[619]: pam_unix(login:session): session closed for user storm
Oct 16 20:31:28 Camelot systemd[1]: getty@tty1.service: Succeeded.
Oct 16 20:31:28 Camelot audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 16 20:31:28 Camelot systemd[1]: session-1.scope: Succeeded.
Oct 16 20:31:28 Camelot kernel: audit: type=1131 audit(1571250688.643:28): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 16 20:31:28 Camelot systemd[1]: getty@tty1.service: Service has no hold-off time (RestartSec=0), scheduling restart.
Oct 16 20:31:28 Camelot systemd[1]: getty@tty1.service: Scheduled restart job, restart counter is at 1.
Oct 16 20:31:28 Camelot systemd[1]: Stopped Getty on tty1.
Oct 16 20:31:28 Camelot audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 16 20:31:28 Camelot audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 16 20:31:28 Camelot systemd-logind[563]: Session 1 logged out. Waiting for processes to exit.
Oct 16 20:31:28 Camelot kernel: audit: type=1130 audit(1571250688.647:29): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 16 20:31:28 Camelot kernel: audit: type=1131 audit(1571250688.647:30): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 16 20:31:28 Camelot systemd[1]: Started Getty on tty1.
Oct 16 20:31:28 Camelot audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 16 20:31:28 Camelot systemd-logind[563]: Removed session 1.

Anyone else have or had this issue?

Last edited by Storm (2019-10-17 17:27:56)

loqs · 2019-10-16 19:14:55

That is not an error and that warning should have been present for multiple kernel releases.
Is this related to your other thread https://bbs.archlinux.org/viewtopic.php?id=249811 ?
If not please post the whole journal for that boot.

Storm · 2019-10-17 14:10:35

Full journal: https://pastebin.com/QJhUr62r

After the failed login I logged in as root instead, and rolled the system back.

The way my normal user is set up is that when I log in in the terminal it launches KDE instead of using KDE's login manager. ("systemctl set-default multi-user.target", then "exec startkde" inside ~/.xinitrc)

V1del · 2019-10-17 14:13:17

startkde doesn't exist anymore, it's been switched to startplasma-x11 : https://wiki.archlinux.org/index.php/KD … he_console

Also general disclaimer, if your .xinitrc contains only startkde that is insufficient and you should follow the proper template (note the blue boxes)

Storm · 2019-10-17 17:27:11

V1del wrote:

startkde doesn't exist anymore, it's been switched to startplasma-x11 : https://wiki.archlinux.org/index.php/KD … he_console

That was it, thank you! I was unaware of this change. Thank you!

V1del wrote:

Also general disclaimer, if your .xinitrc contains only startkde that is insufficient and you should follow the proper template (note the blue boxes)

As per the guide I followed, I copied /etc/X11/xinit/xinitrc to my home and commented out a few specified lines. This is what it looks like now:

#!/bin/sh

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then

    xrdb -merge $sysresources

fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f "$userresources" ]; then

    xrdb -merge "$userresources"

fi

if [ -f "$usermodmap" ]; then
    xmodmap "$usermodmap"
fi

# start some nice programs

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

#twm &
#xclock -geometry 50x50-1+1 &
#xterm -geometry 80x50+494+51 &
#xterm -geometry 80x20+494-0 &
#exec xterm -geometry 80x66+0+0 -name login

#exec startkde #Old, replaced by startplasma-x11
exec startplasma-x11

Last edited by Storm (2019-10-17 17:27:22)

Arch Linux

#1 2019-10-16 19:02:35

[SOLVED] GUI login fail after upgrade (mapping multiple BARs)

#2 2019-10-16 19:14:55

Re: [SOLVED] GUI login fail after upgrade (mapping multiple BARs)

#3 2019-10-17 14:10:35

Re: [SOLVED] GUI login fail after upgrade (mapping multiple BARs)

#4 2019-10-17 14:13:17

Re: [SOLVED] GUI login fail after upgrade (mapping multiple BARs)

#5 2019-10-17 17:27:11

Re: [SOLVED] GUI login fail after upgrade (mapping multiple BARs)

Board footer