How to close X Server, to avoid errors while updating nVidia driver?
Clash Royale CLAN TAG#URR8PPP
I tried to update my nVidia driver but I got an error when I ran the driver installation.
See the error:
ERROR: You appear to be running an X server; please exit X before
installing. For further details, please see the section INSTALLING
THE NVIDIA DRIVER in the README available on the Linux driver
download page at www.nvidia.com.
Note:
I tried following a guide by typing init 3
but still nothing changed..
How to close the X server?
So I can update the driver
xorg drivers nvidia error-handling
add a comment |
I tried to update my nVidia driver but I got an error when I ran the driver installation.
See the error:
ERROR: You appear to be running an X server; please exit X before
installing. For further details, please see the section INSTALLING
THE NVIDIA DRIVER in the README available on the Linux driver
download page at www.nvidia.com.
Note:
I tried following a guide by typing init 3
but still nothing changed..
How to close the X server?
So I can update the driver
xorg drivers nvidia error-handling
1
did you try myservice
suggestion?
– Kevin
Nov 29 '11 at 16:57
what distro is this?
– Patrick
Nov 30 '11 at 4:18
add a comment |
I tried to update my nVidia driver but I got an error when I ran the driver installation.
See the error:
ERROR: You appear to be running an X server; please exit X before
installing. For further details, please see the section INSTALLING
THE NVIDIA DRIVER in the README available on the Linux driver
download page at www.nvidia.com.
Note:
I tried following a guide by typing init 3
but still nothing changed..
How to close the X server?
So I can update the driver
xorg drivers nvidia error-handling
I tried to update my nVidia driver but I got an error when I ran the driver installation.
See the error:
ERROR: You appear to be running an X server; please exit X before
installing. For further details, please see the section INSTALLING
THE NVIDIA DRIVER in the README available on the Linux driver
download page at www.nvidia.com.
Note:
I tried following a guide by typing init 3
but still nothing changed..
How to close the X server?
So I can update the driver
xorg drivers nvidia error-handling
xorg drivers nvidia error-handling
edited Feb 15 '16 at 14:49
vonbrand
14.2k22644
14.2k22644
asked Nov 29 '11 at 15:56
Rev3rseRev3rse
176235
176235
1
did you try myservice
suggestion?
– Kevin
Nov 29 '11 at 16:57
what distro is this?
– Patrick
Nov 30 '11 at 4:18
add a comment |
1
did you try myservice
suggestion?
– Kevin
Nov 29 '11 at 16:57
what distro is this?
– Patrick
Nov 30 '11 at 4:18
1
1
did you try my
service
suggestion?– Kevin
Nov 29 '11 at 16:57
did you try my
service
suggestion?– Kevin
Nov 29 '11 at 16:57
what distro is this?
– Patrick
Nov 30 '11 at 4:18
what distro is this?
– Patrick
Nov 30 '11 at 4:18
add a comment |
7 Answers
7
active
oldest
votes
I don't think I've ever gotten that installing/updating nvidia, but here:
# To stop:
sudo init 3
# To resume:
sudo init 5
Though I'm not 100% sure that'll work on Ubuntu, IIRC they moved away from init. On Ubuntu, try this (replace gdm with kdm/slim/whatever display manager you use):
# To stop:
sudo service gdm stop
# To start:
sudo service gdm start
I'm pretty sure that stops the whole X session
Less cleanly, you could just kill them:
sudo killall /usr/bin/X
But they might respawn.
I tried your first solution and didn't work, then I tried your second solution it says unrecognised service(I tried all of them) I also tried your last solution and it saysno proccess found
– Rev3rse
Nov 29 '11 at 17:15
2
Under Ubuntu, the basic display manager isn't GDM but LightDM.service lightdm stop
.
– John WH Smith
Nov 3 '14 at 12:54
@JohnWHSmith maybe it is now, but it wasn't 3 years ago when I wrote this.
– Kevin
Nov 3 '14 at 17:22
add a comment |
Depending on your version the way of stopping the X server varies. You have to exit the graphic mode (by typing alt+ctrl+F1
, for example), login, and then type one of the following commands to stop the X server:
sudo service lightdm stop
sudo service gdm stop
sudo service kdm stop //this is the one that worked for mi as I use kdm and Linux mint
Now you can install the drivers and then type
sudo reboot
When you write sudo service
press tab to see the options you have (gdm, kdm,...)
add a comment |
As the error states, you are still running an X server. This error occurs when you try to install the Nvidia .run files while logged in.
Make sure you are logged out.
- Hit CTRL+ALT+F1 and login using your credentials.
- kill your current X server session by typing
sudo service lightdm stop
orsudo stop lightdm
- Enter runlevel 3 (or 5) by typing
sudo init 3
(orsudo init 5
) and install your .run file. - You might be required to reboot when the installation finishes. If not, run
sudo service lightdm start
orsudo start lightdm
to start your X server again.
add a comment |
From my experience I would try this:
Alt+F1
then login,sudo telinit 3
(if that isn't work try/sbin/telinit 3
), and check that it is changed to level 3 withrunlevel
that should output something like5 3
which means that the current run level is3
and before it was5
.
In case that doesn't work, do:
ps ax | grep X
, and in the output you would see thePID
number of the processX
, so you should kill it withsudo kill -9 number
wherenumber
is thePID
number of the process.
1
sudo kill -9 <all pids from ps ax>
worked!
– voy
Oct 24 '17 at 13:14
add a comment |
If you are using Linux Mint, use sudo service mdm stop
add a comment |
Booting to a different runlevel
Runlevels in Linux dictate which services are started and stopped automatically when the system boots or shuts down. The runlevels typically range from 0 to 6, with runlevel 5 typically starting the X window system as part of the services (runlevel 0 is actually a system halt, and 6 is a system reboot). It is good practice to install the NVIDIA Linux Driver while X is not running, and it is a good idea to prevent X from starting on reboot in case there are problems with the installation (otherwise you may find yourself with a broken system that automatically tries to start X, but then hangs during the startup, preventing you from doing the repairs necessary to fix X). Depending on your network setup, runlevels 1, 2 or 3 should be sufficient for installing the Driver. Level 3 typically includes networking services, so if utilities used by the system during installation depend on a remote filesystem, Levels 1 and 2 will be insufficient. If your system typically boots to a console with a command prompt, you should not need to change anything. If your system typically boots to the X window system with a graphical login and desktop, you must both exit X and change your default runlevel.
On most distributions, the default runlevel is stored in the file /etc/inittab, although you may have to consult the guide for your own distribution. The line that indicates the default runlevel appears as
id:n:initdefault:
or similar, where n indicates the number of the runlevel. /etc/inittab must be edited as root. Please read the sections on editing files and root user if you are unfamiliar with this concept. Also, it is recommended that you create a copy of the file prior to editing it, particularly if you are new to Linux text editors, in case you accidentally corrupt the file:
# cp /etc/inittab /etc/inittab.original
The line should be edited such that an appropriate runlevel is the default (1, 2, or 3 on most systems):
id:3:initdefault:
After saving the changes, exit X. After the Driver installation is complete, you may revert the default runlevel to its original state, either by editing the /etc/inittab again or by moving your backup copy back to its original name.
Different distributions provide different ways to exit X. On many systems, the init utility will change the current runlevel. This can be used to change to a runlevel in which X is not running.
init 3
There are other methods by which to exit X. Please consult your distribution.
NVIDIA Accelerated Linux Graphics Driver README and Installation Guide
List all yours processes with:
ps ax
List all your runing services with:
service --status-all | grep +
add a comment |
I'm running kubuntu and had the same problem and none of the answers worked, but it was coming up with a message saying it was running in "low graphics mode". I had to hit ctrl-alt-backspace
to kill the X-server.
I used ssh to connect to the machine and install the Nvidia drivers after that. Probably going to a virtual shell using ctrl-alt-F1
would work.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f25668%2fhow-to-close-x-server-to-avoid-errors-while-updating-nvidia-driver%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
I don't think I've ever gotten that installing/updating nvidia, but here:
# To stop:
sudo init 3
# To resume:
sudo init 5
Though I'm not 100% sure that'll work on Ubuntu, IIRC they moved away from init. On Ubuntu, try this (replace gdm with kdm/slim/whatever display manager you use):
# To stop:
sudo service gdm stop
# To start:
sudo service gdm start
I'm pretty sure that stops the whole X session
Less cleanly, you could just kill them:
sudo killall /usr/bin/X
But they might respawn.
I tried your first solution and didn't work, then I tried your second solution it says unrecognised service(I tried all of them) I also tried your last solution and it saysno proccess found
– Rev3rse
Nov 29 '11 at 17:15
2
Under Ubuntu, the basic display manager isn't GDM but LightDM.service lightdm stop
.
– John WH Smith
Nov 3 '14 at 12:54
@JohnWHSmith maybe it is now, but it wasn't 3 years ago when I wrote this.
– Kevin
Nov 3 '14 at 17:22
add a comment |
I don't think I've ever gotten that installing/updating nvidia, but here:
# To stop:
sudo init 3
# To resume:
sudo init 5
Though I'm not 100% sure that'll work on Ubuntu, IIRC they moved away from init. On Ubuntu, try this (replace gdm with kdm/slim/whatever display manager you use):
# To stop:
sudo service gdm stop
# To start:
sudo service gdm start
I'm pretty sure that stops the whole X session
Less cleanly, you could just kill them:
sudo killall /usr/bin/X
But they might respawn.
I tried your first solution and didn't work, then I tried your second solution it says unrecognised service(I tried all of them) I also tried your last solution and it saysno proccess found
– Rev3rse
Nov 29 '11 at 17:15
2
Under Ubuntu, the basic display manager isn't GDM but LightDM.service lightdm stop
.
– John WH Smith
Nov 3 '14 at 12:54
@JohnWHSmith maybe it is now, but it wasn't 3 years ago when I wrote this.
– Kevin
Nov 3 '14 at 17:22
add a comment |
I don't think I've ever gotten that installing/updating nvidia, but here:
# To stop:
sudo init 3
# To resume:
sudo init 5
Though I'm not 100% sure that'll work on Ubuntu, IIRC they moved away from init. On Ubuntu, try this (replace gdm with kdm/slim/whatever display manager you use):
# To stop:
sudo service gdm stop
# To start:
sudo service gdm start
I'm pretty sure that stops the whole X session
Less cleanly, you could just kill them:
sudo killall /usr/bin/X
But they might respawn.
I don't think I've ever gotten that installing/updating nvidia, but here:
# To stop:
sudo init 3
# To resume:
sudo init 5
Though I'm not 100% sure that'll work on Ubuntu, IIRC they moved away from init. On Ubuntu, try this (replace gdm with kdm/slim/whatever display manager you use):
# To stop:
sudo service gdm stop
# To start:
sudo service gdm start
I'm pretty sure that stops the whole X session
Less cleanly, you could just kill them:
sudo killall /usr/bin/X
But they might respawn.
answered Nov 29 '11 at 16:13
KevinKevin
27.2k106299
27.2k106299
I tried your first solution and didn't work, then I tried your second solution it says unrecognised service(I tried all of them) I also tried your last solution and it saysno proccess found
– Rev3rse
Nov 29 '11 at 17:15
2
Under Ubuntu, the basic display manager isn't GDM but LightDM.service lightdm stop
.
– John WH Smith
Nov 3 '14 at 12:54
@JohnWHSmith maybe it is now, but it wasn't 3 years ago when I wrote this.
– Kevin
Nov 3 '14 at 17:22
add a comment |
I tried your first solution and didn't work, then I tried your second solution it says unrecognised service(I tried all of them) I also tried your last solution and it saysno proccess found
– Rev3rse
Nov 29 '11 at 17:15
2
Under Ubuntu, the basic display manager isn't GDM but LightDM.service lightdm stop
.
– John WH Smith
Nov 3 '14 at 12:54
@JohnWHSmith maybe it is now, but it wasn't 3 years ago when I wrote this.
– Kevin
Nov 3 '14 at 17:22
I tried your first solution and didn't work, then I tried your second solution it says unrecognised service(I tried all of them) I also tried your last solution and it says
no proccess found
– Rev3rse
Nov 29 '11 at 17:15
I tried your first solution and didn't work, then I tried your second solution it says unrecognised service(I tried all of them) I also tried your last solution and it says
no proccess found
– Rev3rse
Nov 29 '11 at 17:15
2
2
Under Ubuntu, the basic display manager isn't GDM but LightDM.
service lightdm stop
.– John WH Smith
Nov 3 '14 at 12:54
Under Ubuntu, the basic display manager isn't GDM but LightDM.
service lightdm stop
.– John WH Smith
Nov 3 '14 at 12:54
@JohnWHSmith maybe it is now, but it wasn't 3 years ago when I wrote this.
– Kevin
Nov 3 '14 at 17:22
@JohnWHSmith maybe it is now, but it wasn't 3 years ago when I wrote this.
– Kevin
Nov 3 '14 at 17:22
add a comment |
Depending on your version the way of stopping the X server varies. You have to exit the graphic mode (by typing alt+ctrl+F1
, for example), login, and then type one of the following commands to stop the X server:
sudo service lightdm stop
sudo service gdm stop
sudo service kdm stop //this is the one that worked for mi as I use kdm and Linux mint
Now you can install the drivers and then type
sudo reboot
When you write sudo service
press tab to see the options you have (gdm, kdm,...)
add a comment |
Depending on your version the way of stopping the X server varies. You have to exit the graphic mode (by typing alt+ctrl+F1
, for example), login, and then type one of the following commands to stop the X server:
sudo service lightdm stop
sudo service gdm stop
sudo service kdm stop //this is the one that worked for mi as I use kdm and Linux mint
Now you can install the drivers and then type
sudo reboot
When you write sudo service
press tab to see the options you have (gdm, kdm,...)
add a comment |
Depending on your version the way of stopping the X server varies. You have to exit the graphic mode (by typing alt+ctrl+F1
, for example), login, and then type one of the following commands to stop the X server:
sudo service lightdm stop
sudo service gdm stop
sudo service kdm stop //this is the one that worked for mi as I use kdm and Linux mint
Now you can install the drivers and then type
sudo reboot
When you write sudo service
press tab to see the options you have (gdm, kdm,...)
Depending on your version the way of stopping the X server varies. You have to exit the graphic mode (by typing alt+ctrl+F1
, for example), login, and then type one of the following commands to stop the X server:
sudo service lightdm stop
sudo service gdm stop
sudo service kdm stop //this is the one that worked for mi as I use kdm and Linux mint
Now you can install the drivers and then type
sudo reboot
When you write sudo service
press tab to see the options you have (gdm, kdm,...)
answered Nov 27 '12 at 14:21
Jav_RockJav_Rock
15113
15113
add a comment |
add a comment |
As the error states, you are still running an X server. This error occurs when you try to install the Nvidia .run files while logged in.
Make sure you are logged out.
- Hit CTRL+ALT+F1 and login using your credentials.
- kill your current X server session by typing
sudo service lightdm stop
orsudo stop lightdm
- Enter runlevel 3 (or 5) by typing
sudo init 3
(orsudo init 5
) and install your .run file. - You might be required to reboot when the installation finishes. If not, run
sudo service lightdm start
orsudo start lightdm
to start your X server again.
add a comment |
As the error states, you are still running an X server. This error occurs when you try to install the Nvidia .run files while logged in.
Make sure you are logged out.
- Hit CTRL+ALT+F1 and login using your credentials.
- kill your current X server session by typing
sudo service lightdm stop
orsudo stop lightdm
- Enter runlevel 3 (or 5) by typing
sudo init 3
(orsudo init 5
) and install your .run file. - You might be required to reboot when the installation finishes. If not, run
sudo service lightdm start
orsudo start lightdm
to start your X server again.
add a comment |
As the error states, you are still running an X server. This error occurs when you try to install the Nvidia .run files while logged in.
Make sure you are logged out.
- Hit CTRL+ALT+F1 and login using your credentials.
- kill your current X server session by typing
sudo service lightdm stop
orsudo stop lightdm
- Enter runlevel 3 (or 5) by typing
sudo init 3
(orsudo init 5
) and install your .run file. - You might be required to reboot when the installation finishes. If not, run
sudo service lightdm start
orsudo start lightdm
to start your X server again.
As the error states, you are still running an X server. This error occurs when you try to install the Nvidia .run files while logged in.
Make sure you are logged out.
- Hit CTRL+ALT+F1 and login using your credentials.
- kill your current X server session by typing
sudo service lightdm stop
orsudo stop lightdm
- Enter runlevel 3 (or 5) by typing
sudo init 3
(orsudo init 5
) and install your .run file. - You might be required to reboot when the installation finishes. If not, run
sudo service lightdm start
orsudo start lightdm
to start your X server again.
edited Sep 18 '18 at 14:52
htinez
34
34
answered Nov 3 '14 at 12:47
Manan SharmaManan Sharma
1314
1314
add a comment |
add a comment |
From my experience I would try this:
Alt+F1
then login,sudo telinit 3
(if that isn't work try/sbin/telinit 3
), and check that it is changed to level 3 withrunlevel
that should output something like5 3
which means that the current run level is3
and before it was5
.
In case that doesn't work, do:
ps ax | grep X
, and in the output you would see thePID
number of the processX
, so you should kill it withsudo kill -9 number
wherenumber
is thePID
number of the process.
1
sudo kill -9 <all pids from ps ax>
worked!
– voy
Oct 24 '17 at 13:14
add a comment |
From my experience I would try this:
Alt+F1
then login,sudo telinit 3
(if that isn't work try/sbin/telinit 3
), and check that it is changed to level 3 withrunlevel
that should output something like5 3
which means that the current run level is3
and before it was5
.
In case that doesn't work, do:
ps ax | grep X
, and in the output you would see thePID
number of the processX
, so you should kill it withsudo kill -9 number
wherenumber
is thePID
number of the process.
1
sudo kill -9 <all pids from ps ax>
worked!
– voy
Oct 24 '17 at 13:14
add a comment |
From my experience I would try this:
Alt+F1
then login,sudo telinit 3
(if that isn't work try/sbin/telinit 3
), and check that it is changed to level 3 withrunlevel
that should output something like5 3
which means that the current run level is3
and before it was5
.
In case that doesn't work, do:
ps ax | grep X
, and in the output you would see thePID
number of the processX
, so you should kill it withsudo kill -9 number
wherenumber
is thePID
number of the process.
From my experience I would try this:
Alt+F1
then login,sudo telinit 3
(if that isn't work try/sbin/telinit 3
), and check that it is changed to level 3 withrunlevel
that should output something like5 3
which means that the current run level is3
and before it was5
.
In case that doesn't work, do:
ps ax | grep X
, and in the output you would see thePID
number of the processX
, so you should kill it withsudo kill -9 number
wherenumber
is thePID
number of the process.
edited Aug 24 '17 at 12:06
Jeff Schaller
40.1k1054126
40.1k1054126
answered Nov 29 '11 at 22:02
Hanan N.Hanan N.
3,67132028
3,67132028
1
sudo kill -9 <all pids from ps ax>
worked!
– voy
Oct 24 '17 at 13:14
add a comment |
1
sudo kill -9 <all pids from ps ax>
worked!
– voy
Oct 24 '17 at 13:14
1
1
sudo kill -9 <all pids from ps ax>
worked!– voy
Oct 24 '17 at 13:14
sudo kill -9 <all pids from ps ax>
worked!– voy
Oct 24 '17 at 13:14
add a comment |
If you are using Linux Mint, use sudo service mdm stop
add a comment |
If you are using Linux Mint, use sudo service mdm stop
add a comment |
If you are using Linux Mint, use sudo service mdm stop
If you are using Linux Mint, use sudo service mdm stop
edited Jun 29 '17 at 0:18
answered Jun 29 '17 at 0:06
crypdickcrypdick
375216
375216
add a comment |
add a comment |
Booting to a different runlevel
Runlevels in Linux dictate which services are started and stopped automatically when the system boots or shuts down. The runlevels typically range from 0 to 6, with runlevel 5 typically starting the X window system as part of the services (runlevel 0 is actually a system halt, and 6 is a system reboot). It is good practice to install the NVIDIA Linux Driver while X is not running, and it is a good idea to prevent X from starting on reboot in case there are problems with the installation (otherwise you may find yourself with a broken system that automatically tries to start X, but then hangs during the startup, preventing you from doing the repairs necessary to fix X). Depending on your network setup, runlevels 1, 2 or 3 should be sufficient for installing the Driver. Level 3 typically includes networking services, so if utilities used by the system during installation depend on a remote filesystem, Levels 1 and 2 will be insufficient. If your system typically boots to a console with a command prompt, you should not need to change anything. If your system typically boots to the X window system with a graphical login and desktop, you must both exit X and change your default runlevel.
On most distributions, the default runlevel is stored in the file /etc/inittab, although you may have to consult the guide for your own distribution. The line that indicates the default runlevel appears as
id:n:initdefault:
or similar, where n indicates the number of the runlevel. /etc/inittab must be edited as root. Please read the sections on editing files and root user if you are unfamiliar with this concept. Also, it is recommended that you create a copy of the file prior to editing it, particularly if you are new to Linux text editors, in case you accidentally corrupt the file:
# cp /etc/inittab /etc/inittab.original
The line should be edited such that an appropriate runlevel is the default (1, 2, or 3 on most systems):
id:3:initdefault:
After saving the changes, exit X. After the Driver installation is complete, you may revert the default runlevel to its original state, either by editing the /etc/inittab again or by moving your backup copy back to its original name.
Different distributions provide different ways to exit X. On many systems, the init utility will change the current runlevel. This can be used to change to a runlevel in which X is not running.
init 3
There are other methods by which to exit X. Please consult your distribution.
NVIDIA Accelerated Linux Graphics Driver README and Installation Guide
List all yours processes with:
ps ax
List all your runing services with:
service --status-all | grep +
add a comment |
Booting to a different runlevel
Runlevels in Linux dictate which services are started and stopped automatically when the system boots or shuts down. The runlevels typically range from 0 to 6, with runlevel 5 typically starting the X window system as part of the services (runlevel 0 is actually a system halt, and 6 is a system reboot). It is good practice to install the NVIDIA Linux Driver while X is not running, and it is a good idea to prevent X from starting on reboot in case there are problems with the installation (otherwise you may find yourself with a broken system that automatically tries to start X, but then hangs during the startup, preventing you from doing the repairs necessary to fix X). Depending on your network setup, runlevels 1, 2 or 3 should be sufficient for installing the Driver. Level 3 typically includes networking services, so if utilities used by the system during installation depend on a remote filesystem, Levels 1 and 2 will be insufficient. If your system typically boots to a console with a command prompt, you should not need to change anything. If your system typically boots to the X window system with a graphical login and desktop, you must both exit X and change your default runlevel.
On most distributions, the default runlevel is stored in the file /etc/inittab, although you may have to consult the guide for your own distribution. The line that indicates the default runlevel appears as
id:n:initdefault:
or similar, where n indicates the number of the runlevel. /etc/inittab must be edited as root. Please read the sections on editing files and root user if you are unfamiliar with this concept. Also, it is recommended that you create a copy of the file prior to editing it, particularly if you are new to Linux text editors, in case you accidentally corrupt the file:
# cp /etc/inittab /etc/inittab.original
The line should be edited such that an appropriate runlevel is the default (1, 2, or 3 on most systems):
id:3:initdefault:
After saving the changes, exit X. After the Driver installation is complete, you may revert the default runlevel to its original state, either by editing the /etc/inittab again or by moving your backup copy back to its original name.
Different distributions provide different ways to exit X. On many systems, the init utility will change the current runlevel. This can be used to change to a runlevel in which X is not running.
init 3
There are other methods by which to exit X. Please consult your distribution.
NVIDIA Accelerated Linux Graphics Driver README and Installation Guide
List all yours processes with:
ps ax
List all your runing services with:
service --status-all | grep +
add a comment |
Booting to a different runlevel
Runlevels in Linux dictate which services are started and stopped automatically when the system boots or shuts down. The runlevels typically range from 0 to 6, with runlevel 5 typically starting the X window system as part of the services (runlevel 0 is actually a system halt, and 6 is a system reboot). It is good practice to install the NVIDIA Linux Driver while X is not running, and it is a good idea to prevent X from starting on reboot in case there are problems with the installation (otherwise you may find yourself with a broken system that automatically tries to start X, but then hangs during the startup, preventing you from doing the repairs necessary to fix X). Depending on your network setup, runlevels 1, 2 or 3 should be sufficient for installing the Driver. Level 3 typically includes networking services, so if utilities used by the system during installation depend on a remote filesystem, Levels 1 and 2 will be insufficient. If your system typically boots to a console with a command prompt, you should not need to change anything. If your system typically boots to the X window system with a graphical login and desktop, you must both exit X and change your default runlevel.
On most distributions, the default runlevel is stored in the file /etc/inittab, although you may have to consult the guide for your own distribution. The line that indicates the default runlevel appears as
id:n:initdefault:
or similar, where n indicates the number of the runlevel. /etc/inittab must be edited as root. Please read the sections on editing files and root user if you are unfamiliar with this concept. Also, it is recommended that you create a copy of the file prior to editing it, particularly if you are new to Linux text editors, in case you accidentally corrupt the file:
# cp /etc/inittab /etc/inittab.original
The line should be edited such that an appropriate runlevel is the default (1, 2, or 3 on most systems):
id:3:initdefault:
After saving the changes, exit X. After the Driver installation is complete, you may revert the default runlevel to its original state, either by editing the /etc/inittab again or by moving your backup copy back to its original name.
Different distributions provide different ways to exit X. On many systems, the init utility will change the current runlevel. This can be used to change to a runlevel in which X is not running.
init 3
There are other methods by which to exit X. Please consult your distribution.
NVIDIA Accelerated Linux Graphics Driver README and Installation Guide
List all yours processes with:
ps ax
List all your runing services with:
service --status-all | grep +
Booting to a different runlevel
Runlevels in Linux dictate which services are started and stopped automatically when the system boots or shuts down. The runlevels typically range from 0 to 6, with runlevel 5 typically starting the X window system as part of the services (runlevel 0 is actually a system halt, and 6 is a system reboot). It is good practice to install the NVIDIA Linux Driver while X is not running, and it is a good idea to prevent X from starting on reboot in case there are problems with the installation (otherwise you may find yourself with a broken system that automatically tries to start X, but then hangs during the startup, preventing you from doing the repairs necessary to fix X). Depending on your network setup, runlevels 1, 2 or 3 should be sufficient for installing the Driver. Level 3 typically includes networking services, so if utilities used by the system during installation depend on a remote filesystem, Levels 1 and 2 will be insufficient. If your system typically boots to a console with a command prompt, you should not need to change anything. If your system typically boots to the X window system with a graphical login and desktop, you must both exit X and change your default runlevel.
On most distributions, the default runlevel is stored in the file /etc/inittab, although you may have to consult the guide for your own distribution. The line that indicates the default runlevel appears as
id:n:initdefault:
or similar, where n indicates the number of the runlevel. /etc/inittab must be edited as root. Please read the sections on editing files and root user if you are unfamiliar with this concept. Also, it is recommended that you create a copy of the file prior to editing it, particularly if you are new to Linux text editors, in case you accidentally corrupt the file:
# cp /etc/inittab /etc/inittab.original
The line should be edited such that an appropriate runlevel is the default (1, 2, or 3 on most systems):
id:3:initdefault:
After saving the changes, exit X. After the Driver installation is complete, you may revert the default runlevel to its original state, either by editing the /etc/inittab again or by moving your backup copy back to its original name.
Different distributions provide different ways to exit X. On many systems, the init utility will change the current runlevel. This can be used to change to a runlevel in which X is not running.
init 3
There are other methods by which to exit X. Please consult your distribution.
NVIDIA Accelerated Linux Graphics Driver README and Installation Guide
List all yours processes with:
ps ax
List all your runing services with:
service --status-all | grep +
edited Feb 15 '16 at 12:24
answered Feb 15 '16 at 12:09
DevWLDevWL
1012
1012
add a comment |
add a comment |
I'm running kubuntu and had the same problem and none of the answers worked, but it was coming up with a message saying it was running in "low graphics mode". I had to hit ctrl-alt-backspace
to kill the X-server.
I used ssh to connect to the machine and install the Nvidia drivers after that. Probably going to a virtual shell using ctrl-alt-F1
would work.
add a comment |
I'm running kubuntu and had the same problem and none of the answers worked, but it was coming up with a message saying it was running in "low graphics mode". I had to hit ctrl-alt-backspace
to kill the X-server.
I used ssh to connect to the machine and install the Nvidia drivers after that. Probably going to a virtual shell using ctrl-alt-F1
would work.
add a comment |
I'm running kubuntu and had the same problem and none of the answers worked, but it was coming up with a message saying it was running in "low graphics mode". I had to hit ctrl-alt-backspace
to kill the X-server.
I used ssh to connect to the machine and install the Nvidia drivers after that. Probably going to a virtual shell using ctrl-alt-F1
would work.
I'm running kubuntu and had the same problem and none of the answers worked, but it was coming up with a message saying it was running in "low graphics mode". I had to hit ctrl-alt-backspace
to kill the X-server.
I used ssh to connect to the machine and install the Nvidia drivers after that. Probably going to a virtual shell using ctrl-alt-F1
would work.
answered Jan 11 at 8:43
localhostlocalhost
1243
1243
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f25668%2fhow-to-close-x-server-to-avoid-errors-while-updating-nvidia-driver%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
did you try my
service
suggestion?– Kevin
Nov 29 '11 at 16:57
what distro is this?
– Patrick
Nov 30 '11 at 4:18