[SOLVED] no terminal when switching run level to 3
SlackwareThis 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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Never seen this behaviour on my machines, but then I never run "init 3" from a terminal while logged into a graphical session. I always logout first from my graphical desktop. Then I do a Ctrl-Alt-F1 to switch to a console prompt. I login as root on the console and run "init 3" there.
Wali, does the above sequence work for you? Or do you see the same black console after switching with Ctrl-Alt-F1.
Final question, are you using my Plasma 5 packages from the "latest" repository or from the "testing" repository? The "testing" repository adds Wayland support but that is not yet stable. You should be using the "latest" repository.
There are reasons I need to switch to run level 3, one of them being I have a slow old machine, to compile and build packages I have to kill X.
I find the "newbie" label very degrading and misleading ... I am no expert by any means, I have been using slackware since version 11, if you did not understand what I was saying that is your problem. I did not mention login manager or screen.
To all;
I am going to mark this as solved since this problem does NOT occur with pure slackware64 with kde from current installation tree. It only happens with kde5 plasma from alienbob; no offense is meant Mr.Eric, and thank you for all you do.
By the way: does anybody have this issue?
Thank you all.
Wali.
Had you have better explained what is going on other "no terminal when switching to run level 3", which is a none gui run level, therefore it is a terminal.
shows me that one does not know what a terminal is.
Running KDE with all of the bells and whistles is a ram eater, maybe you should run in run level 3 then use startx to get yourself back to your terminal if your system is that slow where you need to compile programs in just your terminal and not a terminal emulator, with your GUI taking up RAM running the rest of your Desktop, or run a lesser RAM HOG Desktop / Window Manager. Like Fluxbox, or WindowMaker, or other less RAM Hungary Window Managers. Slackware comes with
fluxbox
blackbox
wmaker
fvwm2
twm
already installed. twm is the lesser of the all in eating up RAM in order to run. you can even install OpenBox and maybe use xfce4 panel in it, in fluxbox too. So Hopefully you will not have to be reboot or shifting back and forth between run level 3 and 4 in order to get something done.
Never seen this behaviour on my machines, but then I never run "init 3" from a terminal while logged into a graphical session. I always logout first from my graphical desktop. Then I do a Ctrl-Alt-F1 to switch to a console prompt. I login as root on the console and run "init 3" there.
I've seen it in the past with the nouveau driver. Also, with my intel graphics and xf86-video-intel if I ctrl-alt-f1 and then telinit 3 the Xserver process hangs. if you then ctrl-alt-f7 back to it, it's just a blank screen that doesn't respond to any keypresses and you can't even ctrl-alt-f1 back to a working terminal,and you're stuck. If I use modesetting rather than xf86-video-intel there is no problem, so it's an issue specific to the intel driver. If I do a sleep 10; telinit 3 and then ctrl-alt-f7 back to X and wait, X exits cleanly, so it appears that X only exits cleanly if it's the currently active virtual console. It's all very odd.
Oh yes, Intel. I use graphics from my Intel I3 CPU. When I use only LCD monitor connected thru DVI everything is ok. But when I connect additional HDMI cable to TV I have blank screen after wake up my computer from hibernate or sleep state.
Last edited by Olek; 03-12-2018 at 01:11 PM.
Reason: typo
Again I did not mean to make a big deal about the "Newbie" thing, my apology.
Answering Eric: When logging out of X, then Ctrl-Alt-F1 and I login as root the result of "init 3" will work as long as I do NOT do Ctrl-Alt-F7. With Ctrl-Alt-F7 I lose all ttys (blank - no blinking cursor) and my keyboard is ineffective.
I am using Plasma 5 packages from latest, updated last night to:
Quote:
KDE Plasma Version: 5.12.3
KDE Framework Version: 5.44.0
QT Version: 5.9.4
Kernel Version: 4.14.21
I have Radeon graphic card - old one, I use kernel driver: Renderer ATI RV370
I use icewm version 1.4.2 from https://github.com/bbidulock/icewm/ last built package was on Feb 20th, 2018
I get the same behavior in all window managers namely: Plasma, xfce4 and icewm.
Framebuffer!!! I think mine IS missed up, I am sorry I did not explore this to start with, it very well COULD be the problem.
Solved, really solved. Somebody can make a song out of this.
I changed my graphic card to newer one - had to pull it out of my other machine.
I had bought AMD Radeon HD 6950 more than 2 years ago, installed it in the other machine at that time (the one the wife uses) both machines are Dell Precision Workstation 670. Anyway everything works okay. I can do "init 3" from graphical terminal with things working the way they should, I can see all output from shutdown scripts - just discovered a mistake I made in one script.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.