Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
$DESKTOP_SESSION just shows a plain line after I hit enter.
Yesterday when I did eselect profile show, and it said I have:
default/linux/amd64/17.0/desktop/plasma
Today, when I did that after all the updates, it now says:
default/linux/amd64/17.0/desktop
I did a different equo command, it said I had Sabayon 18.05 KDE.
I wish I remembered which command that last one was.
I am hoping changing run level could work because I need help with that.
If changing run level doesn't do anything, then I will really have to figure this or just try a different OS.
When you do a normal boot and get to the sababon login prompt, do you enter the user name of the user created during the install then hit the Enter key?
Are you then prompted for your password? If so, enter it and then hit the enter key. Then type startx (all lower case Letters) and hit the Enter key.
If that doesn't do it, then you will need to switch to root user with either su or su -i at the prompt, hit the Enter key and enter your root password at the prompt then go to the /etc/inittab file and change the number 3 to 4 or 5. Different systems use 4, some use 5 so you'll just have to try them Not sure what text editor you will have available but you can always use vi, if you know how to use it: vi /etc/inittab
I did su root before I did the startx and when I typed startx, it brought me here.
Nothing was in any of the text boxes initially, I typed some of the stuff I saw in your post.
To open any file with vi you would type: vi (name of file)
Here is what I get when I type vi /etc/inittab at the cmd-line. Vi opens the file and shows me what's in the file.
To edit the file you have to be root to make changes.
Code:
# 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
# 13.37 2011-03-25 PJV
#
# 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
This is just an example to show you what the file looks like.
-::-I looked under supported products to make sure I saw your card.-::-
Here's what I learned from a man here at LQ that ran Debian Testing for many years and was very good with Linux.
Quote:
If a system won't boot to desktop it has to be xorg, the kernel or maybe a proprietary video driver most likely.
It could also be something in the init system (sysvinit, startup and systemd) but in testing it's xorg related.
Run a update, if that doesn't work try Recovery Mode and direct it to boot when it get's around to asking what you want.
Recovery Mode runs a few more corrective tools and may fix it on it's own.
If you can run the DE as root the problems is with your user not the system at large.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.