Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
|
01-07-2010, 08:49 AM
|
#1
|
|
Member
Registered: Feb 2009
Distribution: Slackware, Arch
Posts: 513
Rep: 
|
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
Last edited by piratesmack; 01-07-2010 at 03:05 PM.
|
|
|
|
01-07-2010, 11:38 AM
|
#2
|
|
Senior Member
Registered: Mar 2006
Distribution: SLACKWARE 4TW! =D
Posts: 1,515
Rep:
|
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.
|
|
|
|
01-07-2010, 01:47 PM
|
#3
|
|
Member
Registered: Aug 2003
Location: Terneuzen Netherlands
Distribution: Slack current
Posts: 129
Rep:
|
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.
|
|
|
|
01-07-2010, 02:12 PM
|
#4
|
|
Senior Member
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 3,932
|
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.
|
|
|
|
01-07-2010, 03:05 PM
|
#5
|
|
Member
Registered: Feb 2009
Distribution: Slackware, Arch
Posts: 513
Original Poster
Rep: 
|
Thanks, everyone.
Marking the thread as solved.
|
|
|
|
01-09-2010, 03:00 PM
|
#6
|
|
Senior Member
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 3,932
|
In order to help anyone else with the same problem, you should describe your solution when you mark a thread as "solved." 
|
|
|
|
01-10-2010, 05:06 AM
|
#7
|
|
Member
Registered: Dec 2009
Location: Sweden
Posts: 50
Rep:
|
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.
|
|
|
|
01-12-2010, 05:43 AM
|
#8
|
|
LQ Newbie
Registered: Jan 2006
Posts: 24
Rep:
|
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
|
|
|
|
01-12-2010, 12:50 PM
|
#9
|
|
Member
Registered: Feb 2009
Distribution: Slackware, Arch
Posts: 513
Original Poster
Rep: 
|
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.
Last edited by piratesmack; 01-12-2010 at 12:52 PM.
|
|
|
|
01-13-2010, 03:57 AM
|
#10
|
|
Member
Registered: Dec 2009
Location: Sweden
Posts: 50
Rep:
|
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.
|
|
|
|
01-13-2010, 07:57 AM
|
#11
|
|
LQ Newbie
Registered: Jan 2006
Posts: 24
Rep:
|
Thanks Piratesmack that fixed it for me
|
|
|
|
01-14-2010, 06:09 PM
|
#12
|
|
Member
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 396
Rep:
|
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.
|
|
|
|
06-21-2010, 09:20 AM
|
#13
|
|
LQ Newbie
Registered: Jun 2010
Location: Italy
Distribution: Slackware 13.1 32/64 bit
Posts: 6
Rep:
|
Hi guys,
and if one doesn't use kde, where does he set those parameters??
I use wmaker.
bye 
|
|
|
|
06-21-2010, 10:05 AM
|
#14
|
|
Slackware Contributor
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 4,684
Rep: 
|
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
|
|
|
|
06-21-2010, 10:44 AM
|
#15
|
|
LQ Newbie
Registered: Jun 2010
Location: Italy
Distribution: Slackware 13.1 32/64 bit
Posts: 6
Rep:
|
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
Last edited by dafrasaga; 06-21-2010 at 10:46 AM.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 10:39 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|