LinuxQuestions.org - Blank Screen: KDE?

- Slackware - Installation (https://www.linuxquestions.org/questions/slackware-installation-40/)

- - Blank Screen: KDE? (https://www.linuxquestions.org/questions/slackware-installation-40/blank-screen-kde-510923/)

Blank Screen: KDE?

Howdy Y'all,

I've just installed Slackware 11.0 on my station at work and I'm getting a blank screen when I leave KDE. This has happened in three distinct situations: 1) In Slax (testing things out, trying to probe the monitor settings), I chose "logout" from the regular KDE menu; 2) after getting KDE from "startx" I again chose the regular "End this session" and got a blank screen, then 3) while in runlevel 3, I typed "kdm" and the screen went blank.

From other posts on here, I've figured out that I should just go to the next virtual terminal and log in again, but what causes this and how can I stop it from happening again?

BTW, in SLAX, the HorizSync was set to 85 Hz -- is that way out of range for a standard CRT? It seems high to me. I therefore hesitated to change xorg.conf.

Thanks,
Joel

Now, I've gotten kdm to start by running init 4, changing the default runlevel to 4 and commenting out the sections in rc.4 for the other display managers.

I've also edited the agetty lines in /etc/inittab as follows:

Code:

# These are the standard console login getties in multiuser mode:

c1:12345:respawn:/sbin/agetty 38400 tty1 linux

c2:12345:respawn:/sbin/agetty 38400 tty2 linux

c3:12345:respawn:/sbin/agetty 38400 tty3 linux

c4:12345:respawn:/sbin/agetty 38400 tty4 linux

c5:1235:respawn:/sbin/agetty 38400 tty5 linux

c6:1235:respawn:/sbin/agetty 38400 tty6 linux

Now, I boot into X (xfce to be exact), however when I exit any window manager, I still get a blank screen. I mean no screen output whatsoever.

The other thing is that I can't switch virtual terminals without losing the X server: i.e., if I press CTL-ALT-F2, I get another terminal login, then I hit CTL-ALT-F1 and I get the original login from before KDM started, but no X session. Where did it go?

Thanks,
Joel

Quote:

...but no X session. Where did it go?

The X server is running on tty7.

Before you edited the /etc/inittab file, the only virtual console would have been on tty6 for runlevel 4. Pat placed some comments in the inittab about this.

tty6 appears for runlevel 4:

Code:

c6:12345:respawn:/sbin/agetty 38400 tty6 linux

that makes sense, however should I be able to get back to it by pressing CTL-ALT-F7? (Because I can't ;))

What I want is to get back to the display manager when I log out -- then shut down from there...should I just replace the original inittab?

Thanks,
Joel

Please let me know what I'm missing here: on other systems (e.g., my home system PCLinuxOS) in runlevel 4, when I exit KDE or any other window manager, I get KDM back offering me another login. Now I get a blank screen.

Here's the current /etc/inittab:

Code:

~ Yes, Master? more /etc/inittab

#

# inittab      This file describes how the INIT process should set up

#              the system in a certain run-level.

#

# Version:      @(#)inittab            2.04    17/05/93        MvS

#                                      2.10    02/10/95        PV

#                                      3.00    02/06/1999      PV

#                                      4.00    04/10/2002      PV

#

# Author:      Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org>

# Modified by:  Patrick J. Volkerding, <volkerdi@slackware.com>

#



# These are the default runlevels in Slackware:

#  0 = halt

#  1 = single user mode

#  2 = unused (but configured the same as runlevel 3)

#  3 = multiuser mode (default Slackware runlevel)

#  4 = X11 with KDM/GDM/XDM (session managers)

#  5 = unused (but configured the same as runlevel 3)

#  6 = reboot



# Default runlevel. (Do not set to 0 or 6)

id:4:initdefault:



# System initialization (runs when system boots).

si:S:sysinit:/etc/rc.d/rc.S



# Script to run when going single user (runlevel 1).

su:1S:wait:/etc/rc.d/rc.K



# Script to run when going multi user.

rc:2345:wait:/etc/rc.d/rc.M



# What to do at the "Three Finger Salute".

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



# Runlevel 0 halts the system.

l0:0:wait:/etc/rc.d/rc.0



# Runlevel 6 reboots the system.

l6:6:wait:/etc/rc.d/rc.6



# What to do when power fails.

pf::powerfail:/sbin/genpowerfail start



# If power is back, cancel the running shutdown.

pg::powerokwait:/sbin/genpowerfail stop



# These are the standard console login getties in multiuser mode:

c1:12345:respawn:/sbin/agetty 38400 tty1 linux

c2:12345:respawn:/sbin/agetty 38400 tty2 linux

c3:12345:respawn:/sbin/agetty 38400 tty3 linux

c4:12345:respawn:/sbin/agetty 38400 tty4 linux

c5:1235:respawn:/sbin/agetty 38400 tty5 linux

c6:1235:respawn:/sbin/agetty 38400 tty6 linux



# Local serial lines:

#s1:12345:respawn:/sbin/agetty -L ttyS0 9600 vt100

#s2:12345:respawn:/sbin/agetty -L ttyS1 9600 vt100



# Dialup lines:

#d1:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS0 vt100

#d2:12345:respawn:/sbin/agetty -mt60 38400,19200,9600,2400,1200 ttyS1 vt100



# Runlevel 4 used to be for an X window only system, until we discovered

# that it throws init into a loop that keeps your load avg at least 1 all

# the time. Thus, there is now one getty opened on tty6. Hopefully no one

# will notice. ;^)

# It might not be bad to have one text console anyway, in case something

# happens to X.

x1:4:respawn:/etc/rc.d/rc.4



# End of /etc/inittab

Is the problem referred to in the note about throwing init into a loop the cause of my problem?

Joel

xorgconfig was the answer. Most people think love is the answer. However, in this case running a livecd and getting the settings from its xorg.conf was the answer.

Thanks,
Joel