How do I disable X at boot time so that the system boots in text mode?


Is it possible to disable X at boot time? I'm setting up a server so it would be nice if it wouldn't load the graphical interface every time I boot. I am a new Ubuntu Linux version 12.04 LTS user. How do I stop or start iptables based firewall service on Ubuntu Linux using bash command line options? I spent a lot of time trying to figure out how to disable plymouth and get a clean text boot on Ubuntu 12.04. Hence thought of documenting it in case I forget how I. Atftp is Multi-threaded TFTP server implementing all options (option extension and multicast) as specified in RFC1350, RFC2090, RFC2347, RFC2348 and RFC2349.

Originally Posted by f69m. Current Status: Ubuntu Touch is booting and can be accessed via adb, but the screen stays black. Enable Verbose Boot Logging for Drivers and Such. Open up msconfig.exe through the Start Menu search or run box, and then head over to the Boot tab.

How do I disable X at boot time so that the system boots in text mode? I noticed...

0 0
0 0

This simple tutorial will show you how to boot your Ubuntu system directly into command line (text mode or console). If you just want a console for temporary use, press Ctrl+Alt+F1 on keyboard will switch your desktop to tty1.

Update: Thanks to August Karlstrom, before getting started, make a backup by running the command below:

sudo cp -n /etc/default/grub /etc/default/grub.orig

If for some reason you want to revert to original settings, just run command below in terminal:

sudo mv /etc/default/grub.orig /etc/default/grub && sudo update-grub

To get started, press Ctrl+Alt+T to open terminal. When it opens, follow the below steps:

1. Copy and paste below command into terminal and hit enter:

sudo gedit /etc/default/grub

This opens Grub boot loader config file with text editor.

2. Do below changes:

Comment the line GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”, by adding # at the beginning, which will disable the Ubuntu purple screen....
0 0

If Secure Boot does not recognize a video card that you install, you may experience problems starting the computer, or there might be no video output at all. First remove the new video card and restore the computer to its original configuration so that the computer display works. Then disable Secure Boot and enable Legacy Boot. Once Legacy Boot is enabled, you can install the new video card.

Step 1: Restore the computer to its original configuration

If your computer came with on-board video only and you installed a new video card, remove the video card.

If your computer came with a video card installed and you replaced the original card with a new card, remove the new card. Then replace the original card in the computer.

Step 2: Disable Secure Boot and enable Legacy Boot

Follow these steps to disable Secure Boot and enable Legacy Boot:

Turn off the computer.

Turn on the computer and immediately press F10 repeatedly, about...

0 0

I think this post has a much better solution for modern Ubuntu (10.X):

... booting with the text kernel parameter will also prevent display managers managed by Upstart (e.g. gdm, kdm and lxdm) from being started at boot time.

If you are using Grub2, then in /etc/default/grub replace:



GRUB_CMDLINE_LINUX_DEFAULT="quiet splash text"

then run:

sudo update-grub

Remove splash to disable the splash screen and/or quiet to make the boot process verbose. If you wish to create a separate boot option for the text and GUI mode then check out this.

Then, if you want to go graphical after booting up, I guess you can use startx or start...

0 0

Many Linux distros usually start a lot of daemons when booting, resulting in a long wait before you can get to work after powering on your machine. Some of those daemons are rarely used (or even not al all) by the majority of users. This tutorial describes how to disable unused or rarely used daemons in a proper way, resulting in faster boot sequences and less CPU load.

Note: Although this tutorial aims to be system-friendly and not dangerous, please do not disable any service if you don’t know what you are doing. Especially on server systems, (accidently) disabling an important service can have serious consequences. This tutorial is provided as-is, without any warranty and so on. Just be careful, ok? =)

Another note: This tutorial uses the words “service” and “daemon”. These words have an almost identical meaning, although service focuses a bit more on what a process does, or, in other words, which service a process provides. The word daemon refers to the “physical”...

0 0

I noticed this thread revolves around assuming you are using LightDM as the Display Manager. Though this may be the usual DM/welcomer, that isn't part of the original question. (And he did not specify..)

In my case:

I use KDE/KDM on my server. Instead, I simply disable the upstart/service from starting under runlevel 2:

/etc/init/kdm.conf: (kdm: 4:4.8.5-0ubuntu0.3 , Upstart Version: 1.5-0ubuntu7.2)


start on ((filesystem


and runlevel [!06]


and runlevel [!026]

Assuming your default runlevel is 2 on fresh reboot, you will have a console and not KDM. Then you can run DM/DE manually when needed = Use 'startx' /etc. To return machine to console and exit X server completely after this, just use 'log out'.

Other dm .confs scripts are similar. (I setup my server like this.. to be able to work using a GUI occasionally - but, not pull resources when not using/needed or simply rebooting.)



0 0

Apple has enabled a new default security oriented featured called System Integrity Protection, often called rootless, in OS X 10.11 onward. The rootless feature is aimed at preventing Mac OS X compromise by malicious code, whether intentionally or accidentally, and essentially what SIP does is lock down specific system level locations in the file system while simultaneously preventing certain processes from attaching to system-level processes.

While the System Integrity Protection security feature is effective and the vast majority of Mac users should leave rootless enabled, some advanced Mac users may find rootless to be overly protective. Thus, if you’re in the group of advanced Mac users who do not want SIP rootless enabled on their OS X installation, we’ll show you how to turn this security feature off.

For those wondering, System Integrity Protection locks down the following system level directories in OS X:

/usr (with...

0 0

I realize this is an old question, but it's also pretty general without any details about the specific hardware involved. That said, you can't file a bug or go about fixing things until you figure out some more details.

I thought I'd take a stab at this since I faced the issue and recovered from it pretty recently. I'll probably run through here again later and throw in some more info and simplify the steps, but the answer list is already pretty big, so I'll go easy on the screenshots.

Recovery mode is your friend, but you don't always need a single-user root session to solve things. In fact, you might just be able to do a normal console login by selecting "resume" without considering any of the other options on the recovery menu. The nice thing about a normal console session over the single-user root mode is that you can get multiple terminals running at once--Switch between them or open up new ones with Alt+F1, Alt+F2, etc. There's a good chance that it's a video...

0 0

I've found ways to disable gdm or lightdm or whatever 11.10 uses, but I can't find a way to get a true text-mode boot. I want to see all the kernel messages fly by as it boots, not a stupid purple screen.

I got the desktop manager turned off finally, but now I get a purple screen for a while, then it switches to TTY1. After that happens, I get about half a screen of kernel messages (the end of the boot sequence; stuff about running init scripts etc.) and the login prompt. I did this by changing GRUB_CMDLINE_LINUX_DEFAULT and GRUB_CMDLINE_LINUX to text in /etc/defaults/grub.

Really my main question is, what is putting that dumb purple screen up at boot, and how do I disable...

0 0

Booting into safe mode in Mac OS X is a troubleshooting trick that can help to diagnose many common system problems, and even some more obscure issues with OS X. While safe mode is considered an advanced troubleshooting technique, it’s easy to use and easy to exit out of, meaning just about any experience level should be able to try it out.

Let’s learn a bit more and see how to boot into safe mode, what safe mode does, and how to exit and return the Mac to it’s normal boot state. And yes, this works in all versions of OS X, from Yosemite to Mavericks, Mountain Lion, Snow Leopard, you name it, you can boot into safe mode with it.

How to Boot a Mac Into Safe Mode with the Shift Key

To boot into safe mode on any Mac, all you need to do is start holding down the shift key during system start after you hear the initial boot chime. You must hold the Shift key immediately after hearing the bootup sound effect otherwise Safe Mode will not...

0 0

If your Mac is experiencing problems running, one step for determining the problem is to boot the system into Safe Mode, which is a limited environment that only loads Apple-provided software for basic functionality. To get into Safe Mode you simply restart your Mac with the Shift key held; however, in some cases this will not work and the computer may simply boot normally or experience a problem and hang without booting at all.

The inability to boot into Safe Mode may happen because the system is configured with encryption or other security settings that prevent booting to such modes, because of nuances with how wireless keyboards pass boot arguments to the system, or because of errors in the file system.

Security settings
Some security settings in OS X may contribute to the inability to boot to Safe Mode. If you have Apple's FileVault disk encryption technology enabled, or if you have a firmware password set on your system, then the computer will not boot to...

0 0

We build a server according to our plan and requirements, but what are the intended functions while building a server to make it function quickly and efficiently. We all know that while installing a Linux OS, some unwanted Packages and Application gets installed automatically without the knowledge of a User.

Remove Unwanted Services From Linux

When building a server we need to ask ourselves what we actually need from the box. Do I need a Web Server or a FTP Server, a NFS Server or a DNS Server, a Database Server or something else.

Here in this article, we will be discussing some of these unwanted applications and services which you might not needed but they are installed by default during OS installation and unknowingly start eating your system resources.

Lets first know what kind of services are running on the system using the following commands.

[avishek@tecmint]# ps ax Sample Output PID TTY STAT TIME COMMAND 2 ? S 0:00 [kthreadd] 3 ? S...
0 0

If your El Capitan update won’t reboot and you want to skip to the fix, click here. Otherwise feel free to read the saga below!

Update 3/23/2016 – It happened again when I updated to 10.11.4! Even fewer clues this time, additional details and an updated script to remove non-default kext files at the very bottom.

After Update, El Capitan Won’t Reboot

After upgrading to OS X El Capitan (10.11) when it was released, I had been generally pleased with the new version but there were a few quirks – like random beach ball pauses – that made me think the 10.11.1 update would address some of them. Thus when I was notified that it was available, I dutifully upgraded… and then my MacBook Pro Retina wouldn’t reboot. I reset the SMC (Shft+Ctrl+Opt+Pwr while off, then Pwr), I reset the PRAM (Cmd+Opt+P+R+Pwr while booting, then hold until the chime sounds again), I tried to boot into Safe Mode (Shft+Pwr). Nothing.

I was unable to boot into Single User Mode...

0 0

When you boot a Mac system you have the option to supply keyboard commands at startup to boot the system to alternate environments. For instance, a common option is to hold the Shift key to boot to Safe Mode, but you can also hold Command-V for verbose mode (a text output of items as they load), or Command-S for Single User mode, which drops you to the command line as the "root" user so you can perform troubleshooting tasks.

In addition to keyboard commands at startup, you can use the "nvram" terminal command to set a number of different boot options, which might be useful when troubleshooting your Mac. Apple's machines have a number of hidden boot options that you can use, though do keep in mind that most of these are for troubleshooting purposes and will only be useful to programmers.

sudo nvram boot-args="-v"
This command will set the system to always boot to Verbose mode, so you do not have to hold Command-V at startup.
sudo nvram boot-args="-x"
0 0