Why does startx give a black screen, with no errors?












6














I recently wanted to solve a problem with using a second monitor from my laptop that is running debian (jessie) but because I lack knowledge things didn't go as planned. Now I am getting booted into tty1, without any kind of graphical environment starting.



I got a Dell XPS17 laptop, using an Intel HD 2nd gen chipset and a Nvidia gt555m graphic card.



What I initially did was install some drivers (some nvidia drivers iirc) and then creating an xorg.conf.



When I now execute startx only a black screen appears, but no errors are printed in the /var/log/Xorg.0.log.



My goal is to make the default laptop display run again, using the Intel hd graphic card and an additional monitor using the Nvidia card (but I would be happy as well if only the laptop display would work again).



What do? I'm not that familiar with Linux/unix and I would appreciate any stp-by-step solution available.










share|improve this question
























  • How did you create the xorg.conf file? The recommended way is to use Xorg -configure (see: the Debian documentation on Xorg).
    – Benjamin B.
    Jul 31 '15 at 17:26










  • First step is to check if a window manager is running.
    – dirkt
    May 4 '17 at 6:34
















6














I recently wanted to solve a problem with using a second monitor from my laptop that is running debian (jessie) but because I lack knowledge things didn't go as planned. Now I am getting booted into tty1, without any kind of graphical environment starting.



I got a Dell XPS17 laptop, using an Intel HD 2nd gen chipset and a Nvidia gt555m graphic card.



What I initially did was install some drivers (some nvidia drivers iirc) and then creating an xorg.conf.



When I now execute startx only a black screen appears, but no errors are printed in the /var/log/Xorg.0.log.



My goal is to make the default laptop display run again, using the Intel hd graphic card and an additional monitor using the Nvidia card (but I would be happy as well if only the laptop display would work again).



What do? I'm not that familiar with Linux/unix and I would appreciate any stp-by-step solution available.










share|improve this question
























  • How did you create the xorg.conf file? The recommended way is to use Xorg -configure (see: the Debian documentation on Xorg).
    – Benjamin B.
    Jul 31 '15 at 17:26










  • First step is to check if a window manager is running.
    – dirkt
    May 4 '17 at 6:34














6












6








6


1





I recently wanted to solve a problem with using a second monitor from my laptop that is running debian (jessie) but because I lack knowledge things didn't go as planned. Now I am getting booted into tty1, without any kind of graphical environment starting.



I got a Dell XPS17 laptop, using an Intel HD 2nd gen chipset and a Nvidia gt555m graphic card.



What I initially did was install some drivers (some nvidia drivers iirc) and then creating an xorg.conf.



When I now execute startx only a black screen appears, but no errors are printed in the /var/log/Xorg.0.log.



My goal is to make the default laptop display run again, using the Intel hd graphic card and an additional monitor using the Nvidia card (but I would be happy as well if only the laptop display would work again).



What do? I'm not that familiar with Linux/unix and I would appreciate any stp-by-step solution available.










share|improve this question















I recently wanted to solve a problem with using a second monitor from my laptop that is running debian (jessie) but because I lack knowledge things didn't go as planned. Now I am getting booted into tty1, without any kind of graphical environment starting.



I got a Dell XPS17 laptop, using an Intel HD 2nd gen chipset and a Nvidia gt555m graphic card.



What I initially did was install some drivers (some nvidia drivers iirc) and then creating an xorg.conf.



When I now execute startx only a black screen appears, but no errors are printed in the /var/log/Xorg.0.log.



My goal is to make the default laptop display run again, using the Intel hd graphic card and an additional monitor using the Nvidia card (but I would be happy as well if only the laptop display would work again).



What do? I'm not that familiar with Linux/unix and I would appreciate any stp-by-step solution available.







linux debian xorg nvidia intel-graphics






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 21 '16 at 0:44









Anko

2,69912141




2,69912141










asked Aug 25 '14 at 12:32









Ogofo

31112




31112












  • How did you create the xorg.conf file? The recommended way is to use Xorg -configure (see: the Debian documentation on Xorg).
    – Benjamin B.
    Jul 31 '15 at 17:26










  • First step is to check if a window manager is running.
    – dirkt
    May 4 '17 at 6:34


















  • How did you create the xorg.conf file? The recommended way is to use Xorg -configure (see: the Debian documentation on Xorg).
    – Benjamin B.
    Jul 31 '15 at 17:26










  • First step is to check if a window manager is running.
    – dirkt
    May 4 '17 at 6:34
















How did you create the xorg.conf file? The recommended way is to use Xorg -configure (see: the Debian documentation on Xorg).
– Benjamin B.
Jul 31 '15 at 17:26




How did you create the xorg.conf file? The recommended way is to use Xorg -configure (see: the Debian documentation on Xorg).
– Benjamin B.
Jul 31 '15 at 17:26












First step is to check if a window manager is running.
– dirkt
May 4 '17 at 6:34




First step is to check if a window manager is running.
– dirkt
May 4 '17 at 6:34










1 Answer
1






active

oldest

votes


















0














Have you tried right or left-clicking on the black screen? Some WindowManagers doesn't leave much evidence that they're running... You may even have started a WM that doesn't use the mouse but keyboard-commands (like ratpoison). Try running ps to see what WM you're running.



Try starting X with xinit - this usually gives you a terminal-window (xterm) on a "dotted" desktop, but may start a WM too. You can also specify a WM - eg. xinit /usr/bin/icewm (depending on which WMs you've got installed and where they're located).



Try looking in /etc/X11/ for the file which selects what WM you're using -- or use the alternatives command to select the WM you want among those available.






share|improve this answer

















  • 1




    startx and xinit are pretty much equivalent, as former uses the latter, so I doubt it will fix anything. Your comment about searching /etc/X11 for some file is confusing. I guess you mean xinitrc? It's not the first place xinit starts looking, but rather ~/.xinitrc, so I would check that first (if it exists).
    – Benjamin B.
    Jul 31 '15 at 17:32











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f152065%2fwhy-does-startx-give-a-black-screen-with-no-errors%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Have you tried right or left-clicking on the black screen? Some WindowManagers doesn't leave much evidence that they're running... You may even have started a WM that doesn't use the mouse but keyboard-commands (like ratpoison). Try running ps to see what WM you're running.



Try starting X with xinit - this usually gives you a terminal-window (xterm) on a "dotted" desktop, but may start a WM too. You can also specify a WM - eg. xinit /usr/bin/icewm (depending on which WMs you've got installed and where they're located).



Try looking in /etc/X11/ for the file which selects what WM you're using -- or use the alternatives command to select the WM you want among those available.






share|improve this answer

















  • 1




    startx and xinit are pretty much equivalent, as former uses the latter, so I doubt it will fix anything. Your comment about searching /etc/X11 for some file is confusing. I guess you mean xinitrc? It's not the first place xinit starts looking, but rather ~/.xinitrc, so I would check that first (if it exists).
    – Benjamin B.
    Jul 31 '15 at 17:32
















0














Have you tried right or left-clicking on the black screen? Some WindowManagers doesn't leave much evidence that they're running... You may even have started a WM that doesn't use the mouse but keyboard-commands (like ratpoison). Try running ps to see what WM you're running.



Try starting X with xinit - this usually gives you a terminal-window (xterm) on a "dotted" desktop, but may start a WM too. You can also specify a WM - eg. xinit /usr/bin/icewm (depending on which WMs you've got installed and where they're located).



Try looking in /etc/X11/ for the file which selects what WM you're using -- or use the alternatives command to select the WM you want among those available.






share|improve this answer

















  • 1




    startx and xinit are pretty much equivalent, as former uses the latter, so I doubt it will fix anything. Your comment about searching /etc/X11 for some file is confusing. I guess you mean xinitrc? It's not the first place xinit starts looking, but rather ~/.xinitrc, so I would check that first (if it exists).
    – Benjamin B.
    Jul 31 '15 at 17:32














0












0








0






Have you tried right or left-clicking on the black screen? Some WindowManagers doesn't leave much evidence that they're running... You may even have started a WM that doesn't use the mouse but keyboard-commands (like ratpoison). Try running ps to see what WM you're running.



Try starting X with xinit - this usually gives you a terminal-window (xterm) on a "dotted" desktop, but may start a WM too. You can also specify a WM - eg. xinit /usr/bin/icewm (depending on which WMs you've got installed and where they're located).



Try looking in /etc/X11/ for the file which selects what WM you're using -- or use the alternatives command to select the WM you want among those available.






share|improve this answer












Have you tried right or left-clicking on the black screen? Some WindowManagers doesn't leave much evidence that they're running... You may even have started a WM that doesn't use the mouse but keyboard-commands (like ratpoison). Try running ps to see what WM you're running.



Try starting X with xinit - this usually gives you a terminal-window (xterm) on a "dotted" desktop, but may start a WM too. You can also specify a WM - eg. xinit /usr/bin/icewm (depending on which WMs you've got installed and where they're located).



Try looking in /etc/X11/ for the file which selects what WM you're using -- or use the alternatives command to select the WM you want among those available.







share|improve this answer












share|improve this answer



share|improve this answer










answered Aug 25 '14 at 14:22









Baard Kopperud

4,42842744




4,42842744








  • 1




    startx and xinit are pretty much equivalent, as former uses the latter, so I doubt it will fix anything. Your comment about searching /etc/X11 for some file is confusing. I guess you mean xinitrc? It's not the first place xinit starts looking, but rather ~/.xinitrc, so I would check that first (if it exists).
    – Benjamin B.
    Jul 31 '15 at 17:32














  • 1




    startx and xinit are pretty much equivalent, as former uses the latter, so I doubt it will fix anything. Your comment about searching /etc/X11 for some file is confusing. I guess you mean xinitrc? It's not the first place xinit starts looking, but rather ~/.xinitrc, so I would check that first (if it exists).
    – Benjamin B.
    Jul 31 '15 at 17:32








1




1




startx and xinit are pretty much equivalent, as former uses the latter, so I doubt it will fix anything. Your comment about searching /etc/X11 for some file is confusing. I guess you mean xinitrc? It's not the first place xinit starts looking, but rather ~/.xinitrc, so I would check that first (if it exists).
– Benjamin B.
Jul 31 '15 at 17:32




startx and xinit are pretty much equivalent, as former uses the latter, so I doubt it will fix anything. Your comment about searching /etc/X11 for some file is confusing. I guess you mean xinitrc? It's not the first place xinit starts looking, but rather ~/.xinitrc, so I would check that first (if it exists).
– Benjamin B.
Jul 31 '15 at 17:32


















draft saved

draft discarded




















































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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f152065%2fwhy-does-startx-give-a-black-screen-with-no-errors%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Morgemoulin

Scott Moir

Souastre