You are not logged in.

#1 2012-11-27 00:00:12

brokengestalt
Member
Registered: 2012-07-24
Posts: 55

[SOLVED] systemd switch, problems with slim/bootup

My system will boot, giving me "OK" for everything it's doing. Then my system gives me a tty login prompt, but continues booting:

gestalt login:  [  OK  ] Starting Wicd.
[  OK  ] Reached target multi-user.
[  OK  ] Reached target graphical interface.

So if i just hit enter, it gives me another login prompt, then I can login, but X/fluxbox isn't started or anything.

My ~/.xinitrc:

exec startfluxbox
xset +fp /usr/share/fonts/local
xset fp rehash

systemctl list-units --type=target

UNIT                LOAD   ACTIVE SUB    JOB DESCRIPTION
basic.target        loaded active active     Basic System
cryptsetup.target   loaded active active     Encrypted Volumes
getty.target        loaded active active     Login Prompts
graphical.target    masked active active     graphical.target
local-fs-pre.target loaded active active     Local File Systems (Pre)
local-fs.target     loaded active active     Local File Systems
multi-user.target   loaded active active     Multi-User
network.target      loaded active active     Network
remote-fs.target    loaded active active     Remote File Systems
sockets.target      loaded active active     Sockets
sound.target        loaded active active     Sound Card
swap.target         loaded active active     Swap
sysinit.target      loaded active active     System Initialization
syslog.target       loaded active active     Syslog

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
JOB    = Pending job for the unit.

14 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

Graphical target isn't masked, like I thought it would be after reading this

systemctl status slim.service gives me:

slim.service - SLiM Simple Login Manager
	  Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
	  Active: failed (Result: exit-code) since Mon, 2012-11-26
	  Process: 305 ExecStart=urs/bin/slim -nodaemon(code=exited, status =1/FAILURE)
	  CGroup: name=systemd:/system/slim.service

systemd-analyze blame gives (just going to ignore the times)

wicd.service
systemd-vconsole-setup.service
systemd-binfmt.service
systemd-logind.service
systemd-modules-load.service
dev-hugepages.mount
systemd-udev-trigger.service
dev-mqueue.mount
systemd-udevd.service
proc-sys-fs-binfmt_service.mount
console-kit-daemon.service
polkit.service
systemd-tmpfiles-setup.service
home.mount
systemd-sysctl.service
tmp.mount
systemd-user-sesssions.service
systemd-remount-fs.service

slim isn't even on this list.

systemctl --failed

UNIT                           LOAD   ACTIVE SUB    JOB DESCRIPTION
slim.service                   loaded failed failed     SLiM Simple Login Manager

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
JOB    = Pending job for the unit.


4 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

Hopefully this isn't too much information (or completely irrelevant) for what might be a far simpler problem, but I'm just not sure what's going on. It might be worth noting that I only bothered to start switching to systemd today when I had to reboot and slim wouldn't start/get me into my WM(!) This is interesting to me, since I read (somewhere) that as of slim's last version, it would only work with systemd and not consolekit... but when I try:

pacman -Qi slim

It tells me that the last time I last updated/installed slim was November 5 of this year. Any ideas?

EDIT:

Latest nVidia drivers weren't working with my 7xxx integrated GPU. Downgrade to 304xx drivers or use nouveau.

Last edited by brokengestalt (2012-11-28 17:41:50)

Offline

#2 2012-11-27 04:00:30

brokengestalt
Member
Registered: 2012-07-24
Posts: 55

Re: [SOLVED] systemd switch, problems with slim/bootup

I tried starting X manually (typing in "startx" at the prompt, and I get the following errors:

...
modprobe: ERROR: could not insert 'nvidia': No such device

Fatal server error:
no screens found
(EE)
Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

It looks like I'm just having problems with my video card, but I have the proprietary nVidia drivers installed and X installed. The systemd wiki page mentions no changes that I would need to make to my xorg or nvidia configuration...

Offline

#3 2012-11-27 07:04:07

itman
Member
From: Switzerland
Registered: 2010-05-21
Posts: 123

Re: [SOLVED] systemd switch, problems with slim/bootup

module "nvidia" not loaded...

what you gonna make out of this?

further

graphical.target    masked active active     graphical.target

see to unmask graphical.target

happy unmasking


Asus eeepc 1201N - 4GB and .... archlinux
i5-750                     - 4GB and .... archlinux

Offline

#4 2012-11-27 12:03:16

brokengestalt
Member
Registered: 2012-07-24
Posts: 55

Re: [SOLVED] systemd switch, problems with slim/bootup

As of right now,

systemctl list-units --type=target:

graphical.target            loaded active active        Graphical Interface

And.. I'm not sure what to make of the nvidia module not being loaded. Afaik, there's no service I need to start for it, it's installed, and up until yesterday, it wasn't being a problem.

Last edited by brokengestalt (2012-11-27 12:06:12)

Offline

#5 2012-11-27 21:54:45

Stebalien
Member
Registered: 2010-04-27
Posts: 1,227
Website

Re: [SOLVED] systemd switch, problems with slim/bootup

Did you update anything else yesterday? This may be relevant: https://mailman.archlinux.org/pipermail … 24052.html


Steven [ web : git ]
GPG:  327B 20CE 21EA 68CF A7748675 7C92 3221 5899 410C
Do not email: honeypot@stebalien.com

Offline

#6 2012-11-28 15:44:13

LinuxChick
Member
From: Saskatchewan, Canada
Registered: 2008-01-22
Posts: 37

Re: [SOLVED] systemd switch, problems with slim/bootup

I have the same nvidia problem.. I didn't know there was an issue until the power went out yesterday, now I can't seem to get X to start, same errors as above..


Girls use Linux too! smile

Offline

#7 2012-11-28 16:10:12

LinuxChick
Member
From: Saskatchewan, Canada
Registered: 2008-01-22
Posts: 37

Re: [SOLVED] systemd switch, problems with slim/bootup

Stebalien Thanks! That was the problem, after reading your post and realizing I had a GeFroce6 it made complete sense..  removed nvidia-310 and installed nvidia-304xx
ran nvidia-xconfig, rebooted and WAA-LAA  X started up no problem. Thanks again. smile


Girls use Linux too! smile

Offline

#8 2012-11-28 17:40:30

brokengestalt
Member
Registered: 2012-07-24
Posts: 55

Re: [SOLVED] systemd switch, problems with slim/bootup

Ahh, I see. I have a 7 series integrated GPU.

I fixed the problem earlier by just uninstalling nvidia drivers and installing nouveau, but I guess I can go back to the proprietary drivers now. Thanks

Offline

Board footer

Powered by FluxBB