LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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


Reply
  Search this Thread
Old 12-01-2016, 08:18 PM   #1
Chronic13
LQ Newbie
 
Registered: Nov 2016
Location: Tokyo
Distribution: Fedora
Posts: 18

Rep: Reputation: Disabled
Unhappy Unexpectedly Booting Into Console


I was studying the Advanced Bash-Scripting Guide from the Linux Documentation Project at work yesterday in my free time. I was excited to get home so I could try out some of the exercises.

I've been using nano as a text editor up until yesterday, when I decided to try out vim. Admittedly I didn't do enough research into vim before launching it thinking it's only a text-editor - How complicated can it be.

Certainly not complicated if you do a little reading before hand, but the command mode, insert mode, etc wasn't naturally intuitive and I found myself not understanding how to exit even just the vim menu. I started inputting random keystrokes to try and exit, and then did some reading up on vim.

In the end, I was able to create my scriptfile and run it - and it ran exactly as expected.

Afterwards I wanted to try and debug a problem that I am having with the Alsa Sound Drivers. The problem is that sound works for certain media (Youtube & some others), but it won't work on other media, namely videos from CNN & other sites.

I decided to reinstall Alsa, so I removed the package, and reinstalled it. Immediately following this I rebooted my system, and now my GUI isn't loading. After entering the encryption key for my drive, the system boots directly to the console.

Is there any hope of debugging this problem or should I reinstall Fedora?

Is it possible I could have messed something up when I was trying to exit vim?

It couldn't possibly have to do with Alsa, could it?

Thank you for any and all input!
 
Old 12-01-2016, 08:49 PM   #2
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, Debian 12 & Devuan
Posts: 9,514
Blog Entries: 15

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Alsa is associated with the sound on your system but it's also a part of the Linux Kernel so the boot configuration may have become misconfigured or corrupt when you removed alsa.

When a gui doesn't run properly it's usually because the run level has changed, the boot file got messed like mentioned above or the kernel configuration file became corrupted. If that's the case I'm not good with that. Sorry.

It sounds like your in single user mode.
If your not able to change the run level in Fedora or repair the boot than yeah you'll have to do a fresh install of Fedora. (Replace the N with the run-level number.)
http://www.tldp.org/LDP/sag/html/run-levels-intro.html

Look at your Fedora boot partition is it flagged with a star like mine?

Code:
/dev/sda1          2048   4196351   4194304     2G 82 Linux swap
/dev/sda2  *    4196352 976773167 972576816 463.8G 83 Linux
Quote:
In the end, I was able to create my scriptfile and run it - and it ran exactly as expected.
What was that script for?

Last edited by Ztcoracat; 12-01-2016 at 09:28 PM.
 
Old 12-01-2016, 08:54 PM   #3
AwesomeMachine
LQ Guru
 
Registered: Jan 2005
Location: USA and Italy
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524

Rep: Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015Reputation: 1015
When you unistalled ALSA some other packages might have been removed along with it. Check
Code:
Xorg.0.log
and see what is says at the end of the file. You can also try:
Code:
$ startx &
from the command line.
 
Old 12-01-2016, 09:45 PM   #4
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, Debian 12 & Devuan
Posts: 9,514
Blog Entries: 15

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Switching to a Graphical Login

https://docs.fedoraproject.org/en-US...gui-login.html

Last edited by Ztcoracat; 12-01-2016 at 09:47 PM.
 
Old 12-01-2016, 09:50 PM   #5
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, Debian 12 & Devuan
Posts: 9,514
Blog Entries: 15

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Quote:
When you unistalled ALSA some other packages might have been removed along with it.
I think you can pretty much bank on that.
 
Old 12-02-2016, 12:33 AM   #6
c0wb0y
Member
 
Registered: Jan 2012
Location: Inside the oven
Distribution: Windows
Posts: 421

Rep: Reputation: 74
So you're using Fedora. Did you bother checking what's the default runlevel? systemctl is your friend there. Did you check if X video or input driver got accidentally hosed by your previous action? Did you check the process list if any display manager or X is listed there? How about the log file, did you have a look at it?

You can do a lot of things to figure this out.
 
Old 12-02-2016, 12:46 AM   #7
Chronic13
LQ Newbie
 
Registered: Nov 2016
Location: Tokyo
Distribution: Fedora
Posts: 18

Original Poster
Rep: Reputation: Disabled
Thank you for your suggestions & input!

I need to do some reading up on:
  • Default run levels - Update (I am now well-read on runlevels)
  • How to verify the integrity of X Video & input drivers
  • How to check the process list & log files from the console

Now I know what to research, though can you point me in the right direction to learn about checking the drivers?

Quote:
What was that script for?
It was the simplest of scripts - I was doing the below exercise.
Quote:
Write a script that upon invocation shows the time and date, lists all logged-in users, and gives the system uptime. The script then saves this information to a logfile.

Last edited by Chronic13; 12-02-2016 at 01:21 AM.
 
Old 12-02-2016, 01:33 AM   #8
c0wb0y
Member
 
Registered: Jan 2012
Location: Inside the oven
Distribution: Windows
Posts: 421

Rep: Reputation: 74
Start reading more about your package manager. I think it is called dnf. You don't verify the integrity of X video or input drivers. You ask the package manager if it installed or not. For your additional reading, check ps manpage.

Quote:
Write a script that upon invocation shows the time and date, lists all logged-in users, and gives the system uptime. The script then saves this information to a logfile.
Sounds like a homework to me. What have you done so far?
 
Old 12-02-2016, 01:45 AM   #9
Chronic13
LQ Newbie
 
Registered: Nov 2016
Location: Tokyo
Distribution: Fedora
Posts: 18

Original Poster
Rep: Reputation: Disabled
Thanks & I certainly will.

Quote:
Sounds like a homework to me. What have you done so far?
- I'm a business professional and programming enthusiast/hobbyist
- I am teaching myself Bash-Scripting for fun via the Linux Documentation Project's Guides
- I wrote the script already and it worked!

After verifying the script worked by checking the created logfile - I began to debug my sound issues and upon reboot, voila! - my feeling of accomplishment disappeared, though I see it as a learning opportunity. I now know the system is likely unable to boot into runlevel 5 due to something that went wrong when I removed Alsa packages, so it's probably defaulting to runlevel 3.

I suppose I could try
Code:
Telinit 5
- though I'm not expecting the problem to be resolved so easily lol.

Last edited by Chronic13; 12-02-2016 at 01:54 AM.
 
Old 12-02-2016, 02:18 AM   #10
c0wb0y
Member
 
Registered: Jan 2012
Location: Inside the oven
Distribution: Windows
Posts: 421

Rep: Reputation: 74
Since the inception of systemd, traditional "runlevels" shifted away from so-called runlevels 2-3-4-5. In systemd it is now called 'targets' which is akin to traditional ones in some sense. And the most commonly-used 'targets' are multi-user and graphical.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Ubuntu 10.10 booting into console Seniorshot Linux - Newbie 34 03-13-2011 06:05 PM
Machine shutdown unexpectedly unexpectedly pinga123 Linux - Newbie 1 02-25-2011 03:48 PM
Booting into console... where is the KDE? sherrife Linux - Newbie 4 12-03-2007 06:03 AM
Booting to console? sdouble Linux - Newbie 3 09-19-2004 12:36 PM
booting suse into console instead of x? Moses420ca Linux - Newbie 4 08-27-2003 03:26 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 04:51 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration