[SOLVED]Problem with logging in after system upgrade

jakub · 2014-10-08 19:54:58

Hi,

I'm encountering some problem after rebooting my machine just after last upgrade. Few minutes ago I was sure I found the source of the problem when system hang on "Reached target Graphical Interface" message. Reason - nvidia drivers had to be replaced with legacy version (https://www.archlinux.org/news/nvidia-340xx-and-nvidia/). But it didn't help. Also it made things a little bit worse. Because now my system uses nvidia-340xx and it seems drivers are fine but when login screen of lightdm should appear screens stay blank... and nothing happens. I simply can't do anything.

What I noticed is also xfce4-session was upgraded (4.10.1.3->4.10.1-5) and maybe this is the separate problem? but I can't downgrade this package as some time ago I removed all contents of /var/cache/pacman/pkg.

What I have is arch on pendrive so I can chroot into existing system.

Any ideas?

Last edited by jakub (2014-10-08 22:09:02)

ewaller · 2014-10-08 19:58:32

jakub wrote:

Hi,.... I simply can't do anything. ...
Any ideas?

Two. Can you change to a different console with Ctrl-Alt-F2 ? Can you ssh into the box from another computer?
Either of these could provide a good debug vector should they work.

jakub · 2014-10-08 20:02:16

No, pressing Ctrl-Alt-F2 gives no result. Screens (monitor on laptop and external one) stay black but all messages from console are also gone. It's like LightDM is about to start but it doesn't.
What I have now is rescue mode (I enabled it after chrooting from into filesystem from archlinux installation pendrive).

jakub · 2014-10-08 20:17:14

I ran lightdm --test-mode --debug and the last one message before screens went dark was "Failed to get D-Bus connection". Is this related or actually it's just because I'm in rescue mode?

Last edited by jakub (2014-10-08 20:26:28)

jakub · 2014-10-08 20:55:52

OK, there is some entry in lightdm.log:

... Using D-Bus name org.freedesktop.Displaymanger
...
... WARNING: Failed to get ssytem bus: Could not connect: no such file or directory

jakub · 2014-10-08 21:20:59

I managed to get dbus working following this instruction: https://wiki.archlinux.org/index.php/Systemd/User
It's also logged on console, that D-Bus has started during boot..

And there is nothing about D-Bus connection problem in logs, but starting lightdm or gdm gives the same result as before - blank screen.

jakub · 2014-10-08 21:54:43

I found something similar to line

(EE) Mar 07 14:05:07 NVIDIA(0): WAIT: (E, 0, 0x837d, 0)

these values are not exact as I'm too tired now to rewrite the real ones from screen

maybe I should install some older nvidia drivers (these 340xx are broken somehow I think). Unfortunately I don't have my /pkg content anymore.
Where can I download packages like nvidia-340.32-1-x86_64.pkg.tar.xz from? (according to pacman.log I had this version back in July and it was working fine I think).

I could also start X with Nouveau drivers but not xfce (anyway I would like to install old nvidia drivers back)

Last edited by jakub (2014-10-08 22:03:11)

jakub · 2014-10-08 22:08:32

My god... why I was trying all the time with 340xx and not even once with 304xx (I have quadro NVS 140M)??? SOLVED

Arch Linux

#1 2014-10-08 19:54:58

[SOLVED]Problem with logging in after system upgrade

#2 2014-10-08 19:58:32

Re: [SOLVED]Problem with logging in after system upgrade

#3 2014-10-08 20:02:16

Re: [SOLVED]Problem with logging in after system upgrade

#4 2014-10-08 20:17:14

Re: [SOLVED]Problem with logging in after system upgrade

#5 2014-10-08 20:55:52

Re: [SOLVED]Problem with logging in after system upgrade

#6 2014-10-08 21:20:59

Re: [SOLVED]Problem with logging in after system upgrade

#7 2014-10-08 21:54:43

Re: [SOLVED]Problem with logging in after system upgrade

#8 2014-10-08 22:08:32

Re: [SOLVED]Problem with logging in after system upgrade

Board footer