You are not logged in.

Pages: 1

#1 2009-11-24 21:50:59

cl10k
Member
From: Germany
Registered: 2008-12-24
Posts: 92

Slim "Id "x" respawning too fast: disabled for 5 minutes"

Hello Everyone,

Slim "Id "x" respawning too fast: disabled for 5 minutes"

This error drives my crazy mad I changed to slim after the recent change of gdm.

Since I changed, when I boot my PC this error always occurs. Only solution so far is either to wait for 5 minutes  or to change to another TTY#, login and try init 3 and then init 5 (which only works sometimes but most of the time delivers the same error).

The error doesn't occur when I REboot the PC.

I start slim via inittab with "x:5:respawn:/usr/bin/slim >& /dev/null"

I already tried the German Arch-Forum but got no reply.

There is a topic http://bbs.archlinux.org/viewtopic.php?id=81159 with the "solution" to change inittab 

"x:5:respawn:/usr/bin/slim >& /dev/null"

to

"x:5:once:/usr/bin/slim >& /dev/null"

but this doesn't work for me, slim then refuses completly to start.

I'd prefer to use the inittab method and not the daemon method...


Thank you in advance

cl10k

PS: Sry for bad English...

Last edited by cl10k (2009-11-24 21:54:18)

Offline

#2 2009-11-24 23:19:22

MadTux
Member
Registered: 2009-09-20
Posts: 553

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

Do you have a working X installation? Is slim working if started from init3?

Offline

#3 2009-11-25 05:54:24

wottam
Member
From: Spain
Registered: 2007-08-31
Posts: 59

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

This was happening to me two days ago, and the cause was a misconfiguration in the X system, so you'd better check that out

Offline

#4 2009-11-25 09:44:55

cl10k
Member
From: Germany
Registered: 2008-12-24
Posts: 92

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

Hi,

"generally" X seems to work fine. I use Openbox without any problems. If I try /usr/bin/slim from init 3 it says: "Stale lockfile found, removing it" and then nothing happens - the console just stays on.

I haven't changed my Xorg for ages, I still use the same X configuration (besides updates) that I had years ago with kdm and then with gdm. Even when I switched from gdm to slim I just follwed to wiki and changed the Inittab line from gdm to slim.

Heres my Inittab and my Xorg.conf (to be honest I'm not really fit with Xorg configuration...)
To be sure, I just created a (very basic) new Xorg.conf with nvidia-xconfig.

#
# /etc/inittab
#

#  Runlevels:
#    0    Halt
#    1(S)    Single-user
#    2    Not used
#    3    Multi-user
#    4    Not used
#    5    X11
#    6    Reboot

## Only one of the following two lines can be uncommented!
# Boot to console
#id:3:initdefault:
# Boot to X11
id:5:initdefault:

rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p

# -8 options fixes umlauts problem on login
c1:2345:respawn:/sbin/agetty -8 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 38400 tty3 linux
c4:2345:respawn:/sbin/agetty -8 38400 tty4 linux
c5:2345:respawn:/sbin/agetty -8 38400 tty5 linux
c6:2345:respawn:/sbin/agetty -8 38400 tty6 linux

ca::ctrlaltdel:/sbin/shutdown -t3 -r now

# Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
x:5:respawn:/usr/bin/slim >& /dev/null

# End of file
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 1.0  (buildmeister@builder63)  Tue Oct 20 21:01:12 PDT 2009

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "LG F900B"
    HorizSync       30.0 - 98.0
    VertRefresh     50.0 - 160.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 7600 GS"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "1"
    Option         "TwinViewXineramaInfoOrder" "CRT-0"
    Option         "metamodes" "CRT-0: 1280x1024_85 +1280+0, CRT-1: 1280x1024_85 +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

-------------------------------------------------------------------------------------------------------------
EDIT: It seems to work now! Slim started without any errors. I will test that for some days to see if the problem is really gone now.

Just out of curiosity:

A lot seems to have changed in Xorg.conf since my old ~2years old config was made.

I had to turnoff boot logo manually and set Option "Composite" "Enable" but now everything seems to work by default?
Do you see any flaws in my xorg.conf? Any ideas for improvements (except metamodes)?

Last edited by cl10k (2009-11-25 10:47:02)

Offline

#5 2009-11-25 16:20:13

cl10k
Member
From: Germany
Registered: 2008-12-24
Posts: 92

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

Arrrgghhh no luck. mad

I had my PC turned off for some hours, now the same error-message occurs. Damn!

Offline

#6 2009-11-25 18:30:30

rrgr
Member
Registered: 2009-11-25
Posts: 1

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

id:5:initdefault:

and pam.d should take care of it

Offline

#7 2009-11-25 19:19:13

cl10k
Member
From: Germany
Registered: 2008-12-24
Posts: 92

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

Sry I don't understand. Could you explain it please?

Offline

#8 2009-12-04 09:00:03

cl10k
Member
From: Germany
Registered: 2008-12-24
Posts: 92

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

Bump.

Pleeeaaase help me. No one has any ideas?

The whole Linux community is talking about fast booting and i have to live with a boottime of over 6 minutes....

I'm willing to pay with fresh tacos!

Offline

#9 2009-12-04 09:05:38

Gen2ly
Member
From: Sevierville, TN
Registered: 2009-03-06
Posts: 1,529
Website

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

Here's my inittab, the Xorg looks fine ok from here.

#
# /etc/inittab
#

#  Runlevels:
#    0    Halt
#    1(S)    Single-user
#    2    Not used
#    3    Multi-user
#    4    Not used
#    5    X11
#    6    Reboot

## Only one of the following two lines can be uncommented!
# Boot to console
id:3:initdefault:
# Boot to X11
#id:5:initdefault:

rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p

# -8 options fixes umlauts problem on login
c1:2345:respawn:/sbin/agetty -8 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 38400 tty3 linux
c4:2345:respawn:/sbin/agetty -8 38400 tty4 linux
c5:2345:respawn:/sbin/agetty -8 38400 tty5 linux
c6:2345:respawn:/sbin/agetty -8 38400 tty6 linux

ca::ctrlaltdel:/sbin/shutdown -t3 -r now

# Example lines for starting a login manager
x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/bin/slim >& /dev/null

# End of file

I put slim on my Dell and put it in the rc.conf and it loads just fine.

Setting Up a Scripting Environment | Proud donor to wikipedia - link

Offline

#10 2009-12-15 12:15:13

cl10k
Member
From: Germany
Registered: 2008-12-24
Posts: 92

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

Thanks for your help. I'm still not sure if i really want to go the "daemon-way" The wiki says that the inittab method is recommended.
The wiki says, slim should be the last daemon. What about all the daemon which get started in backround mode?

Maybe I should simply go back to the OLD gdm. Does somebody still remeber which was the last version before gdm changed?

Offline

#11 2009-12-15 23:06:09

ngoonee
Forum Fellow
From: Between Thailand and Singapore
Registered: 2009-03-17
Posts: 7,356

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

cl10k wrote:

Thanks for your help. I'm still not sure if i really want to go the "daemon-way" The wiki says that the inittab method is recommended.
The wiki says, slim should be the last daemon. What about all the daemon which get started in backround mode?

Maybe I should simply go back to the OLD gdm. Does somebody still remeber which was the last version before gdm changed?

You can't, gdm is tied in to the rest of gnome.

Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

Offline

#12 2009-12-16 06:42:15

cl10k
Member
From: Germany
Registered: 2008-12-24
Posts: 92

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

I don't remember it exactly but the old version of gdm did not have so many dependencies to the rest of the gnome package. Would it be possible to build the old gdm from source?

Last edited by cl10k (2009-12-16 06:42:39)

Offline

#13 2009-12-16 14:35:13

Berseker
Member
From: Near Lecco, Italy
Registered: 2008-04-24
Posts: 258

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

maybe gdm-old package on AUR can help you

Offline

#14 2009-12-16 14:41:12

cl10k
Member
From: Germany
Registered: 2008-12-24
Posts: 92

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

Great! I will try it!

Offline

#15 2009-12-17 00:51:15

harryNID
Member
From: P3X-1971
Registered: 2009-06-12
Posts: 117

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

Here are some thoughts about SLIM.

First, I don't think it is SLIM causing your issue.

As some others have said the message you are getting is more a result of a bad Xorg configuration. I've seen that message many times while messing around with my Xorg.conf. You might want to check out the following pages as Xorg has changed quite considerably lately.

Are you Hotplugging? If you don't know what that is then check below. It's the standard now in Arch and you have to add/remove/change some things in order to use the old manual way (depending on whether you want to use Hotplugging or vice-versa). The pages below can explain it better than I.

Xorg
http://wiki.archlinux.org/index.php/Xorg
and
Xorg-Hotplugging
http://wiki.archlinux.org/index.php/Xor … otplugging

Another version of SLIM to check out is this:
slim-cursor 1.3.1-4
http://aur.archlinux.org/packages.php?ID=21053

Also it helps to check out /var/log/slim.log as you will find all sorts of info there. I found out that with the PAM patch for SLIM you have to install gnome-keyring or you will get all kinds of errors in slim.log.

Your inittab looks fine so that should not be an issue. I will almost guarantee your xorg.conf + Hotplugging vs not Hotplugging configuration is the culprit here.  You probably just need to set up fully one way or the other is all.

I use Hotplugging so my xorg.conf looks like this: (modified by hand after nvidia-xconfig)

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder75)  Sun Nov  8 21:50:38 PST 2009

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    Option         "AutoAddDevices"
    Option            "NoPM"  "true"
EndSection

Section "Extensions"
    Option "Composite" "Enable"
EndSection


Section "Files"
    FontPath    "/usr/share/fonts/local"
EndSection


Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Plug'n Play"
    ModelName      "DELL D1028L"
    HorizSync       30.0 - 110.0
    VertRefresh     50.0 - 150.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
#    Option "AddARGBGLXVisuals" "true"
#        Option "RenderAccel" "true"
    Option "UseEdidDpi" "False"
#    Option "NoLogo" "true"
#    Option "ConnectedMonitor" "CRT"
#    Option "IgnoreDisplayDevices" "DFP, TV"
#    Option "NoBandWidthTest" "true"
#    Option "NoPowerConnectorCheck" "true"
#    Option "BackingStore" "True"
#    Option "PixmapCacheSize" "200000"
#        Option "TripleBuffer" "True"
#    Option "ConnectToAcpid" "off"
#        Option "Coolbits" "1"
    Option "DPI" "96x96"
#    Option "UseCompositeWrapper" "True"
#    Option "OnDemandVBlankInterrupts" "True"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    SubSection     "Display"
        Depth       24
        Modes      "1024x768"
    EndSubSection
EndSection

In solving a problem of this sort, the grand thing is to be able to reason backward. That is a very useful accomplishment, and a very easy one, but people do not practice it much. In the everyday affairs of life it is more useful to reason forward, and so the other comes to be neglected. There are fifty who can reason synthetically for one who can reason analytically.  --Sherlock Holmes

Offline

#16 2009-12-17 07:35:15

cl10k
Member
From: Germany
Registered: 2008-12-24
Posts: 92

Re: Slim "Id "x" respawning too fast: disabled for 5 minutes"

Thank you harryNID. This is a very very helpful post! I will check all the info you gave me.

EDIT: Seems that your are right. I tried 2 different versions of slim and the old version of gdm (ehich worked flawlessly in the past) but still the same error. Don't wonder why it takes so long to answer. First i was very busy and second the error only occurs after the pc has been off for some hours (over night). After reboot or a shorter period (~2h) the error doesn't occur... I will investigate it further...

Last edited by cl10k (2009-12-22 16:42:00)

Offline

Pages: 1

Board footer

Powered by FluxBB