Answers to: Revive Dead Consoles after Suspendhttp://linuxexchange.org/questions/135/revive-dead-consoles-after-suspend<p>Hello everyone. I'm using Slackware13.0 &amp; I've encountered a rather perplexing situation. I was wondering if there where any fellow slackers or wizened gnu 'rus out there who could lend a hand.</p> <p>While using the kde4 desktop environment, after using the suspend to ram feature, I cannot revive the other consoles? tty0-7, or the consoles you get when you ctrl+alt+fn". The only one I can revive is the one I last used; xwindows, or tty7.</p> <p>If anyone could help point me in the right direction towards a resolution, I'd be most grateful! </p>enMon, 13 Sep 2010 09:04:33 -0400Answer by udothttp://linuxexchange.org/questions/135/revive-dead-consoles-after-suspend/1345<p>Have been googling an LVM question on Slackware and came across this great slackware tips and tricks with explicit instructions on tweaking a couple may apply: <a href="http://www.fprimex.com/linux/slackware/tips.html" rel="nofollow">link text</a></p> <p>What run level are you using? I don't use KDE although its installed but sometimes Xserver blinks out and I alt ctrl till I get another terminal then shutdown as root. Are you using a laptop or desktop? Wireless keyboard or PS2? Caps lock blinking - batteries for the keyboard? $ps aux shows tty7 as root. For me first line is tty3 and tty1 the one i am using. Do you have 3 or 4'initdefault'... Goto the above link it will walk you through your startup 'display manager' settings, edit /etc/rc.d/rc.4 and change the order of preferred display managers, so kdm is first. Let us know if it works ;) Problem solve in this post: <a href="http://www.linuxquestions.org/questions/linux-desktop-74/down-arrow-and-end-keys-dont-work-in-kde-or-xfce-771214/" rel="nofollow">link text</a></p>udotMon, 13 Sep 2010 09:04:33 -0400http://linuxexchange.org/questions/135/revive-dead-consoles-after-suspend/1345Answer by memnoch_proxyhttp://linuxexchange.org/questions/135/revive-dead-consoles-after-suspend/485<p>I would attempt to boot without framebuffer console graphics mode. The kernel switch to turn that off should be "nofb". I don't know if Slack uses a graphical boot mode (like the rhgb option), but if it does, I would turn that off as well.</p> <p><a href="http://www.nvnews.net/vbulletin/showthread.php?t=49005" rel="nofollow">http://www.nvnews.net/vbulletin/showthread.php?t=49005</a></p>memnoch_proxyTue, 11 May 2010 20:22:44 -0400http://linuxexchange.org/questions/135/revive-dead-consoles-after-suspend/485Answer by Jubhttp://linuxexchange.org/questions/135/revive-dead-consoles-after-suspend/239<p>I've never heard of a problem like that. Those other consoles could be in use... possibly..? Try:</p> <pre><code>cat /etc/passwd | cut -d":" -f1 </code></pre> <p>and then run:</p> <pre><code>top </code></pre> <p>The first should list all your users and the second all processes... See if any are actually logged into and using another console</p>JubTue, 04 May 2010 03:40:17 -0400http://linuxexchange.org/questions/135/revive-dead-consoles-after-suspend/239