Categories

LINUX
Linux - Newbie
Linux - Software
Linux - Hardware
Linux - Laptop and Netbook
Linux - Mobile
Linux - Security
Linux - Server
Linux - Desktop
Linux - Networking
Linux - Distributions
Linux - Virtualization
Linux - General
Linux - Enterprise
*BSD
Solaris / OpenSolaris
AIX
Other *NIX
Programming
Linux User Groups (LUG)
General
LQ Suggestions & Feedback
Linux - News
LQ Job Marketplace
AndroidQuestions.org
Linux - Games
Linux - Kernel
Linux - Embedded & Single-board computer
Linux - Screenshots
Linux - Wireless Networking
Linux From Scratch
Slackware
Debian
Arch
Red Hat
Mandriva
VectorLinux
Fedora
DamnSmallLinux
ROCK
MEPIS
Ubuntu
Suse/Novell
Puppy
Zenwalk
Dreamlinux
Ultra X
Incognito
Linux Mint
Sabayon
Calculate
Gentoo
Bodhi
NetSecL
Linux Deepin
Studio 13.37
Fuduntu
Mageia
LinuxQuestions.org Member Success Stories
Linux - Certification
LQ Articles Discussion
LinuxAnswers Discussion
LinuxQuestions.org Member Intro
Community Bulletin Archive
Interviews
Syndicated Linux News
LQ Job Marketplace [Archive]

Resources

Java Database
Linux
Coding
Mobile
Hardware
Software Development
Software Development
iOS,OS X
iOS,OS X
ORACLE
IBM DEVELOPER
IBM DEVELOPER
MSDN
MSDN


Tags

Slackware

This Forum is for the discussion of Slackware Linux.<br />

Black screen after logout in Slackware-Current


After updating my Slackware-Current (there was kernel and glibc package updates), I just get a black screen with a blinking "_" in the top-left corner when I logout.    I checked /var/log/kdm.log and found these errors:    	Code:  	(EE) Failed to load module "i810" (module does not exist, 0)  (EE) Failed to load module "fbdev" (module does not exist, 0)  I've found a workaround: uncommenting "TerminateServer=true" in kdmrc.     But I am wondering if anyone else is having this issue and if I should file a bug report.    Thanks

I modify the official slackware package to be *sure* that the line you refer to is indeed uncommented.    The error you see there I have on debian, and BSD too fwiw.    In fact I have to do a very similar tweak to gnome's GDM too    It seems that whenever dri is active there's some form of lockup on my pc's.    I especially get this with intel and with ati/radeon both binary driver and the xorg driver.    I have yet to see nvidia binary need this, or the vesa driver need this.  The fact that stock Slackware is using the vesa driver, then no, I would not recommend that it be filed as a bug with Slackware.    Tho, I do think it should be in changes and hints.  I've seen this issue rear it's ugly head since I started using GNU's.    Oh, I'm running --current too.

Upgraded (using slackpkg)to new kernel (2.6.32.3) today and -think- experienced similar problem: nvidia not found.  When compilation of driver failed, I realized that the kernel-headers and -source were not upgraded.  Downloaded and installed these by hand and compilation of driver was succesfull.

I don't use Slackware, so this is just a guess:  If I correctly understand the Slackware philosophy, you may need to recompile your kernel with switches set to include the Intel 810 video module. I think that the driver was added to the kernel around 2.6.30 and, if you're compiling using settings you used before then, you may not get all the various drivers installed. The same possibility may exist for the fbdev module.

Thanks, everyone.    Marking the thread as solved.

In order to help anyone else with the same problem, you should describe your solution when you mark a thread as "solved." 

I have the same problem with a HP 6715b laptop, running Slamd64 Linux 12.2 build. The laptop has ATI Radeon X1200 graphics.    I currently run an older radeon driver. It works, but not flawless. Video playback suffers, and when exiting X the screen blacks out when it should instead display the console.    Tried to solve this by downloading the latest driver from http://support.amd.com/ . But with the new driver i got a hard crash as soon as X loaded.  I had to revert to the old driver to get things working again. To bad the install script for the new driver had done numerous things to my install that made it impossible to even use the older driver, so i had to revert to my backup of the sysdisk to get it working properly. Hm?    I would very much like this problem to be solved. The Radeon driver is not open source, which makes me have to sit and wait until ATI/AMD decides they have to solve the issue. Annoying, since i bought the HP/Compaq laptop with AMD chips inside with the intention to have a nice and reliably working open platform.

I have the same issue, when logging out I get a blank screen. This has occurred after the upgrade in current recently. I am unsure of what the solution is here even though it says SOLVED. The errors in /var/log/Xorg.0.log are  (EE) Failed to load module "i810" (module does not exist, 0) (EE) Failed to load module "fbdev" (module does not exist, 0)  Any ideas?  Thanks

  	Quote:  	  	  		  			  				  					Originally Posted by noidea  					  				  				I am unsure of what the solution is here even though it says SOLVED.  			  		  	  	  The solution (actually more like a workaround) is to...  Edit /etc/kde/kdm/kdmrc  Change this line:   	Code:  	#TerminateServer=true  To:   	Code:  	TerminateServer=true  You may have to reboot for the change to take effect. Now when you log out, it will kill X and kdm will start back up.  I mentioned this in the first post.  The reason I posted this thread was because I wasn't sure if this was worth filing a bug report over. Somebody told me it wasn't, so I marked the thread as solved.

Ok. Maybe we are talking about different things here?  I get a completely blacked out screen. Not even a blinking cursor. Killing X means literally kill screen output until reboot. Doesn't matter if X is run with startx, xdm, kdm, or whatever.

Thanks Piratesmack that fixed it for me

  	Quote:  	  	  		  			  				  					Originally Posted by piratesmack  					  				  				The solution (actually more like a workaround) is to...    Edit /etc/kde/kdm/kdmrc    Change this line:    	Code:  	#TerminateServer=true  To:    	Code:  	TerminateServer=true  You may have to reboot for the change to take effect.  Now when you log out, it will kill X and kdm will start back up.  			  		  	  	  Kudos!  I ran into the same issue on my Acer Aspire One D250 netbook and this fixed it.

Hi guys,  and if one doesn't use kde, where does he set those parameters??    I use wmaker.    bye

  	Quote:  	  	  		  			  				  					Originally Posted by dafrasaga  					  				  				Hi guys,  and if one doesn't use kde, where does he set those parameters??    I use wmaker.    bye  			  		  	  	  If you do not have KDE installed, then you are not using the graphical login manager KDM, and therefore you do not suffer from the KDM issue as described in this thread.    Eric

Hi Alien Bob, I know I'm not under KDE, but I hooked what wroom said..when I kill X, doesn't not matter if you are under xdm kdm gdm ecc, I have a blank screen. However surfing a few, I found this where at "System freezes after logout with GDM, KDM or XDM" could be a solution to my problem. Could be it ?? I'm very very a newbe on linux :-) Cheers Gabriele


Related Links

Slackware and XEN ?
Computer Identified over the Internet?
Compiling a new kernel
kernel 2.6.22 on Slackware not working after installation of Debian 4.0
Problems with a GB Network
comments on s-m-s?
Compiling kernenl modules
Are ATI drivers as easy to install as NVIDIA?
KPPP Connects, No Communication
microsoft lifecam v3000
Nikon D80 problem
login hang a pc speaker as: /class/input/input3 in boot camp and parallels
Package question
SB-Live and synth module
runlevel 4 startx question
discovering libriary links (flac)