Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Slim takes too long to start [SOLVED]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Zagloj
Guru
Guru


Joined: 17 Jun 2005
Posts: 314

PostPosted: Tue Dec 25, 2012 3:04 pm    Post subject: Slim takes too long to start [SOLVED] Reply with quote

Hi, recently I installed gentoo in a new computer, all goes fine and the boot process is very fast (20 seconds or less), but when it reaches the moment when it starts local and the dm (slim), it goes into black screen and slim only appears after more than 30 seconds, maybe around 1 minute, it takes very long and I don't know why, in /var/log/slim.log there is nothing after yesterday (I had issues because I forgot to add dbus to default runlevel).

Thanks for your time reading the post, any advice would be appreciated.
_________________
Your ideology seems to be: "I hate the fanatics, we shoud kill them all" juantxorena dixit.


Last edited by Zagloj on Wed Dec 26, 2012 4:21 pm; edited 1 time in total
Back to top
View user's profile Send private message
gabrielg
Tux's lil' helper
Tux's lil' helper


Joined: 16 Nov 2012
Posts: 86

PostPosted: Tue Dec 25, 2012 3:54 pm    Post subject: Reply with quote

Suggest you check /var/log/messages and dmesg, unless you find a 30-60 seconds gap when nothing happens, you might find the reason why your startup time is so slow.
Back to top
View user's profile Send private message
Zagloj
Guru
Guru


Joined: 17 Jun 2005
Posts: 314

PostPosted: Tue Dec 25, 2012 10:04 pm    Post subject: Reply with quote

Thanks, I have this in my "everything" log:
Code:
Dec 25 20:52:29 [kernel] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  310.19  Thu Nov  8 00:52:03 PST 2012
Dec 25 20:52:29 [kernel] NVRM: GPU at 0000:01:00: GPU-7d5b83ff-eceb-9b58-854b-787132318a34
Dec 25 20:52:29 [kernel] NVRM: Your system is not currently configured to drive a VGA console
Dec 25 20:52:29 [kernel] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
Dec 25 20:52:29 [kernel] NVRM: requires the use of a text-mode VGA console. Use of other console
Dec 25 20:52:29 [kernel] NVRM: drivers including, but not limited to, vesafb, may result in
Dec 25 20:52:29 [kernel] NVRM: corruption and stability problems, and is not supported.
Dec 25 20:52:29 [kernel] Adding 1951860k swap on /dev/sda5.  Priority:-1 extents:1 across:1951860k
Dec 25 20:52:29 [kernel] EXT4-fs (sda6): re-mounted. Opts: (null)
Dec 25 20:52:30 [dbus] [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Dec 25 20:52:30 [polkitd] Started polkitd version 0.109
Dec 25 20:52:30 [kernel] r8169 0000:03:00.0: eth0: unable to load firmware patch rtl_nic/rtl8168e-3.fw (-2)
Dec 25 20:52:30 [kernel] r8169 0000:03:00.0: eth0: link down
                - Last output repeated twice -
Dec 25 20:52:30 [polkitd] Loading rules from directory /etc/polkit-1/rules.d
Dec 25 20:52:30 [polkitd] Loading rules from directory /usr/share/polkit-1/rules.d
Dec 25 20:52:30 [polkitd] Finished loading, compiling and executing 1 rules
Dec 25 20:52:30 [dbus] [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Dec 25 20:52:30 [polkitd] Acquired the name org.freedesktop.PolicyKit1 on the system bus
Dec 25 20:52:32 [kernel] NET: Registered protocol family 10
Dec 25 20:52:32 [kernel] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Dec 25 20:52:32 [kernel] r8169 0000:03:00.0: eth0: link up
Dec 25 20:52:32 [kernel] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Dec 25 20:52:34 [kernel] NVRM: GPU at 0000:01:00: GPU-7d5b83ff-eceb-9b58-854b-787132318a34


I am still trying to fix it, by the way, when I used startx instead slim, all goes fast.

Bye and thanks for your time ;)
_________________
Your ideology seems to be: "I hate the fanatics, we shoud kill them all" juantxorena dixit.
Back to top
View user's profile Send private message
gabrielg
Tux's lil' helper
Tux's lil' helper


Joined: 16 Nov 2012
Posts: 86

PostPosted: Wed Dec 26, 2012 12:37 pm    Post subject: Reply with quote

So, are you saying that if you deactivate your login/display manager, you go quickly enough to the login prompt, login, run startx and everything runs smoothly? In that case, maybe you've got a problem with your display/login manager. Which one are you using? Did you try going back to the console with control+alt+f1 when the screen goes blank for over 30 seconds and see what's holding everything up?

Another alternative is that this has nothing to do with slim or your dm and something else is holding up the boot process (network? ntp? dhcp?). Your log doesn't say much to be honest. If you find what is holding things up and you think it is expected to take that long, you can try to run things in parallel, assuming you use rc, with rc_parallel="YES" in /etc/rc.conf.

I also have my dm in boot as opposed to default so that it starts faster :-)

Anyway, good luck, let us know if you find what is holding things up and you don't know what to do about it. At this point, I doubt it's a slim problem.
Back to top
View user's profile Send private message
Zagloj
Guru
Guru


Joined: 17 Jun 2005
Posts: 314

PostPosted: Wed Dec 26, 2012 4:15 pm    Post subject: Reply with quote

Well, now I am looking at various logs but I am still unable to find the problem, the last thing I can add is that if I log out of my Window manager (fvwm) it takes the same time (more than 1 minute) to start again slim (dm)

I am not sure if another dm would change this, I tried with rc_parallel both on yes and no, with no difference. Anyways, when the system boots up, I see a message "unable to rm /run/openrc. Read only filesystem", but I am looking for the boot log without success, I thought that it were in /var/log, but I cant find them, cause I didnt enable it, by enabling it I can read the log.

In other hand, when I dont wait for slim I can inmediatly go to a tty (Control+Alt+F1 for example) and log in without problem, even startx fast.

I will report if I find a solution or I can solve this with another dm, I am using ~amd64 and nvidia card.

SOLVED!!! Thanks, I tried to quit xdm from default and change to boot, all goes smooth and perfect now thanks for the tip :D
_________________
Your ideology seems to be: "I hate the fanatics, we shoud kill them all" juantxorena dixit.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum