Timeline for xorg - black screen after installing xorg-x11-drv-nvidia
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 26, 2017 at 20:30 | comment | added | Lizardx | And yes, there are multiple possible syntaxes required to successfully block nouveau or modesetting across time and across distros. Also, I don't even see what distro this is in the first place, which makes support impossible even if time were not a factor. | |
| Sep 26, 2017 at 20:28 | comment | added | Lizardx | As noted, the time cost to support each case, is too high, I suggest filing a bug report with the packager, noting that the package is radically incomplete, and does not lead to success, and that bug is repeatable and predictable for every single user who does not know each and every real step required. My only reason to reply to your specific issue was to point out the absurdity of the linux community refusing to correct an issue that has been corrected by 3rd party tools in a scaleable and scripted way. 1 person can help 1 other person in about the same time it takes to help 10,000. | |
| Sep 26, 2017 at 20:19 | comment | added | k0st1x | i've just tried "nvidia-xconfig" xorg.conf and rebooted - it even worse than before - loaded into the blank screen, ctrl+alt+f2, login/password and "startx" - blank screen again xorg.1.log. the strange thing is the "nvidia-settings" shows two devices: "PRIME Display" and "X screen 0" but i have only 1 screen - is that normal? "and you need to blacklist modesetting" - but previously i've described as "nomodeset" was added into the grub-file - should I do it another way? may be you can give me more suggestions that i could try? | |
| Sep 25, 2017 at 21:26 | comment | added | Lizardx | mdpc, no reboot is required if done correctly I have NEVER seen that, that sounds like some mistaken idea from windows land. Now, you might be missing a key step, which of course, would be and are scripted in better solutions. k0st1x, perfect example of why the packaged drivers have huge bugs, those two are the primary 2, you need xorg.conf, and you need to blacklist modesetting. Since this has never changed in the 10 years I have supported this stuff, it's inexcusable for pre installer and post installer of package to not do these for you. | |
| Sep 25, 2017 at 21:04 | comment | added | k0st1x | there was no xorg.conf on system with xorg-x11-drv-nvidia package installed. (also i've tried the "fedora-nvidia" negativo17 repository but with the same result, but with the exist 10-nvidia.conf file). i've appended "nomodeset" value to the GRUB_CMDLINE_LINUX key in the /etc/default/grub file update grub menu via the "grub2-mkconfig -o /boot/grub2/grub.cf" command (i've double checked the /boot/grub2/grub.cr - it realy contains a new "nomodeset" key on the "linuxefi" line) and again - here the logs I really appreciate any help! | |
| Sep 19, 2017 at 1:06 | history | edited | Lizardx | CC BY-SA 3.0 | added 135 characters in body |
| Sep 19, 2017 at 1:03 | comment | added | Lizardx | The run installer is slightly more robust than the normal debian type packaged nvidia, in that at least it checks some things, and has decent debuggers included with the installer, not just decent, actually excellent ones. | |
| Sep 19, 2017 at 1:00 | comment | added | mdpc | Hmm...The current NVIDIA driver load package (from the NVIDIA site) posts a question as to whether the xorg.conf file should be modified during its installation. The only problem that I have had is that you need to reinstall the NVIDIA driver AFTER each kernel update and reboot (to build the kernel modules) otherwise black screen. | |
| Sep 18, 2017 at 21:25 | history | edited | Lizardx | CC BY-SA 3.0 | added 520 characters in body |
| Sep 18, 2017 at 20:54 | history | answered | Lizardx | CC BY-SA 3.0 |