# 10-09-2016 Update went bust \>\>\> black screen

**URL:** https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103
**Category:** Rolling 2016.01
**Created:** [October 10, 2016, 10:27am UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103 "2016-10-10T10:27:36Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![chatan](https://support.blue-systems.com/letter_avatar/chatan/32/5_5575768a8748004e209b776fc1b2916d.png) [@chatan](https://support.blue-systems.com/u/chatan)
#### Post date: [October 10, 2016, 10:27am UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/1 "2016-10-10T10:27:36Z")

</div>

I saw my taskbar notification that there was an update available, so I went ahead and did it (sudo pacman -Syyu). After the update my graphics went screwy and on reboot I ended up with a black screen (no cursor, no mouse) before the KDE login. I was able to Ctrl-Alt-F2 and got a terminal. I tried some of the stuff at [https://forum.manjaro.org/t/stable-update-2016-10-09-kernels-manjaro-tools-deepin-nm-libreoffice-steam/10663/57](https://forum.manjaro.org/t/stable-update-2016-10-09-kernels-manjaro-tools-deepin-nm-libreoffice-steam/10663/57), where black screens seemed to be an issue…  
but no luck.  
Checked my log (journalctl -xb) and there was sddm-greeter dump errors that google didn’t seem to lead me to solutions so I just restored my clonezilla backup and I’m back to my pre-update working state. …and standing by for now.  
I guessing my problem might be related to my NVIDIA 304.xxx driver.  
Cheers

---

<div class="post-metadata">

### Author: ![AJSlye](https://support.blue-systems.com/user_avatar/support.blue-systems.com/ajslye/32/263_2.png) [@AJSlye](https://support.blue-systems.com/u/AJSlye)
#### Post date: [October 10, 2016, 3:14pm UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/2 "2016-10-10T15:14:44Z")

</div>

I apologize, I had no electricity (besides a generator), or internet access for 3 days due to hurricane Matthew so I didn’t get a chance to post the update announcement. There is an issue with the systemd update that causes an issue where the x-session might get lost. Did you follow the two links from the bug report to see if maybe there was an answer to your issue there: [https://bugs.archlinux.org/task/51275](https://bugs.archlinux.org/task/51275)

Note: there are also some issues with the 4.8.0 kernel series, please do not use this kernel until these are resolved.

---

<div class="post-metadata">

### Author: ![chatan](https://support.blue-systems.com/letter_avatar/chatan/32/5_5575768a8748004e209b776fc1b2916d.png) [@chatan](https://support.blue-systems.com/u/chatan)
#### Post date: [October 10, 2016, 9:11pm UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/3 "2016-10-10T21:11:15Z")

</div>

Thanks and no worries. I didn’t get as far as those links; a little over my head anyways.  
Cheers

---

<div class="post-metadata">

### Author: ![chandra](https://support.blue-systems.com/letter_avatar/chandra/32/5_5575768a8748004e209b776fc1b2916d.png) [@chandra](https://support.blue-systems.com/u/chandra)
#### Post date: [October 10, 2016, 11:00pm UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/4 "2016-10-10T23:00:51Z")

</div>

Perhaps [this update announcement](https://forum.manjaro.org/t/stable-update-2016-10-09-kernels-manjaro-tools-deepin-nm-libreoffice-steam/10663) and this [update recommendation](https://manjaro.org/2016/10/10/update-recommendation-for-systemd-users/) will help.

I too lost the screen on updating, but on rebooting, was able to resume the update. I saw the above links only thereafter.

---

<div class="post-metadata">

### Author: ![AJSlye](https://support.blue-systems.com/user_avatar/support.blue-systems.com/ajslye/32/263_2.png) [@AJSlye](https://support.blue-systems.com/u/AJSlye)
#### Post date: [October 10, 2016, 11:03pm UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/5 "2016-10-10T23:03:59Z")

</div>

> [@chandra](#):
>
> Perhaps [this update announcement](https://forum.manjaro.org/t/stable-update-2016-10-09-kernels-manjaro-tools-deepin-nm-libreoffice-steam/10663) and this [update recommendation](https://manjaro.org/2016/10/10/update-recommendation-for-systemd-users/) will help.
> 
> I too lost the screen on updating, but on rebooting, was able to resume the update. I saw the above links only thereafter.

He already covered that Manjaro forum thread in his original post.

---

<div class="post-metadata">

### Author: ![chatan](https://support.blue-systems.com/letter_avatar/chatan/32/5_5575768a8748004e209b776fc1b2916d.png) [@chatan](https://support.blue-systems.com/u/chatan)
#### Post date: [October 11, 2016, 12:03am UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/6 "2016-10-11T00:03:17Z")

</div>

> [@AJSlye](#):
>
> > [@chandra](#):
> >
> > Perhaps [this update announcement](https://forum.manjaro.org/t/stable-update-2016-10-09-kernels-manjaro-tools-deepin-nm-libreoffice-steam/10663) and this [update recommendation](https://manjaro.org/2016/10/10/update-recommendation-for-systemd-users/) will help.
> > 
> > I too lost the screen on updating, but on rebooting, was able to resume the update. I saw the above links only thereafter.
> 
> He already covered that Manjaro forum thread in his original post.

I actually didn’t get to the [update recommendation](https://manjaro.org/2016/10/10/update-recommendation-for-systemd-users/), but I’m out of country for a few days anyways.  
Should I try that when I get back?  
Cheers

---

<div class="post-metadata">

### Author: ![AJSlye](https://support.blue-systems.com/user_avatar/support.blue-systems.com/ajslye/32/263_2.png) [@AJSlye](https://support.blue-systems.com/u/AJSlye)
#### Post date: [October 11, 2016, 12:56am UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/7 "2016-10-11T00:56:43Z")

</div>

It says basically the same thing as the top of the Manjaro’s update announcement forum post.  
The only difference is it has you update the systemd packages first by themselves.

---

<div class="post-metadata">

### Author: ![chatan](https://support.blue-systems.com/letter_avatar/chatan/32/5_5575768a8748004e209b776fc1b2916d.png) [@chatan](https://support.blue-systems.com/u/chatan)
#### Post date: [October 13, 2016, 10:08pm UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/8 "2016-10-13T22:08:05Z")

</div>

Well, I followed the [update recommendation](https://manjaro.org/2016/10/10/update-recommendation-for-systemd-users/):  
Pre-update, pacman -Q systemd showed I had systemd 231-1, so I did sudo pacman -Sy libsystemd systemd systemd-sysvcompat , after which pacman -Q systemd gave systemd 231-4, then I did sudo pacman -Syyu, answered yes to removing qtchooser. Rebooted.  
Same problem as my original post: black screen (no cursor, no mouse) and doesn’t get to the KDE login. Ctrl-Alt-F2 gets the terminal and my log (journalctl -xb) and there still is sddm-greeter crashed and dumped core errors.

I’m still using the LTS kernel (4.4.21)  
Any ideas?

---

<div class="post-metadata">

### Author: ![AJSlye](https://support.blue-systems.com/user_avatar/support.blue-systems.com/ajslye/32/263_2.png) [@AJSlye](https://support.blue-systems.com/u/AJSlye)
#### Post date: [October 13, 2016, 11:15pm UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/9 "2016-10-13T23:15:58Z")

</div>

Could you post the errors?

---

<div class="post-metadata">

### Author: ![chatan](https://support.blue-systems.com/letter_avatar/chatan/32/5_5575768a8748004e209b776fc1b2916d.png) [@chatan](https://support.blue-systems.com/u/chatan)
#### Post date: [October 14, 2016, 10:03am UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/10 "2016-10-14T10:03:04Z")

</div>

Hopefully there is nothing sensitive here 🙂

[http://pastebin.com/DBDLFsA1](http://pastebin.com/DBDLFsA1)

I see lots of “unable” “failed” and “cannot”

Some googling led me to try “systemctl restart sddm”; but that still yields black screen. Tried various other things, but no luck.  
Cheers

---

<div class="post-metadata">

### Author: ![AJSlye](https://support.blue-systems.com/user_avatar/support.blue-systems.com/ajslye/32/263_2.png) [@AJSlye](https://support.blue-systems.com/u/AJSlye)
#### Post date: [October 14, 2016, 1:32pm UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/11 "2016-10-14T13:32:11Z")

</div>

Hmm, what drivers are you using for your gpu again?  
This seems to be a bit concerning:

> [@](#):
>
> Oct 14 18:02:06 Tiger-Rolling sddm-greeter[655]: Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior 2, swapInterval 1, profile 0)

You could also try editing the /etc/sddm.conf to use a different theme.

---

<div class="post-metadata">

### Author: ![chatan](https://support.blue-systems.com/letter_avatar/chatan/32/5_5575768a8748004e209b776fc1b2916d.png) [@chatan](https://support.blue-systems.com/u/chatan)
#### Post date: [October 14, 2016, 2:58pm UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/12 "2016-10-14T14:58:05Z")

</div>

Graphic info:

`+------------------------------------------------------+                      
| NVIDIA-SMI 4.304... Driver Version: 304.132 |                      
|-------------------------------+----------------------+----------------------+
| GPU Name | Bus-Id Disp. | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce 6100 nForce 405 | 0000:00:0D.0 N/A | N/A |
| N/A N/A N/A N/A / N/A | 0% 0MB / 62MB | N/A N/A |
+-------------------------------+----------------------+----------------------+
                                                                         `

Theme: I changed netrunner to both breeze and then maui; both still black screen.  
Thanks!  
Good night from Japan

---

<div class="post-metadata">

### Author: ![AJSlye](https://support.blue-systems.com/user_avatar/support.blue-systems.com/ajslye/32/263_2.png) [@AJSlye](https://support.blue-systems.com/u/AJSlye)
#### Post date: [October 14, 2016, 3:03pm UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/13 "2016-10-14T15:03:13Z")

</div>

Try adding sddm to the video group.

Reference: [https://forums.gentoo.org/viewtopic-p-7849988.html](https://forums.gentoo.org/viewtopic-p-7849988.html)  
This person had the exact same error.

---

<div class="post-metadata">

### Author: ![chatan](https://support.blue-systems.com/letter_avatar/chatan/32/5_5575768a8748004e209b776fc1b2916d.png) [@chatan](https://support.blue-systems.com/u/chatan)
#### Post date: [October 14, 2016, 11:49pm UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/14 "2016-10-14T23:49:28Z")

</div>

No luck: Here is what I’ve tried from that thread and others I found:

[color=#000000][size=small][font=Arial]Usermod -a -G video sddm[/font][/size][/color]

[color=#000000][size=small][font=Arial]I already had the /var/lib/sddm folder.[/font][/size][/color]

[color=#000000][size=small][font=Arial]remove _both_ /var/lib/sddm/.cache and ~/.cache and see if it improves things.[/font][/size][/color]

[color=#000000][size=small][font=Arial]sddm-greeter --theme /usr/share/sddm/themes/breeze/ --test-mode[/font][/size][/color]  
[color=#000000][size=small][font=Arial]Tried all five themes in that folder and all gave:[/font][/size][/color][color=#000000][size=small][font=Arial] QXcbConnection: Could not connect to display[/font][/size][/color]

[color=#000000][size=small][font=Arial]I changed the permissions for all the themes in /usr/share/sddm/themes/ to 777[/font][/size][/color]

[color=#000000][size=small][font=Arial]Nvidia-xconfig:[/font][/size][/color][color=#000000][size=small][font=Arial] created /etc/X11/xorg.conf file.[/font][/size][/color]

Never had this kind of problem before. I notice in googling, this has happened to others mainly in 2015, with intel graphics and other distros and themes. And some solution for some but not others. I’m guessing I could downgrade some package, but not sure which one yet.  
Cheers

---

<div class="post-metadata">

### Author: ![AJSlye](https://support.blue-systems.com/user_avatar/support.blue-systems.com/ajslye/32/263_2.png) [@AJSlye](https://support.blue-systems.com/u/AJSlye)
#### Post date: [October 15, 2016, 12:21am UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/15 "2016-10-15T00:21:21Z")

</div>

This really sounds like a GPU driver issue.  
Have you tried switching to the nouveau drivers or reconfiguring your /etc/X11/mhwd.d/nvidia.conf file (try different options out)?

---

<div class="post-metadata">

### Author: ![chatan](https://support.blue-systems.com/letter_avatar/chatan/32/5_5575768a8748004e209b776fc1b2916d.png) [@chatan](https://support.blue-systems.com/u/chatan)
#### Post date: [October 15, 2016, 4:38am UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/16 "2016-10-15T04:38:19Z")

</div>

Nouveau drivers have never worked on this nvidia card. I looked at /etc/X11/mhwd.d/nvidia.conf but don’t see anything obvious to try differently.

This post and the others around it seems to point to nvidia-304xx driver regression: [https://forum.manjaro.org/t/testing-update-2016-10-02-kernels-manjaro-tools-deepin-nm-libreoffice-steam/10310/17](https://forum.manjaro.org/t/testing-update-2016-10-02-kernels-manjaro-tools-deepin-nm-libreoffice-steam/10310/17)

For now I’m going to restore my clonezilla clone and give this upgrade a rest for now. Maybe for my next step, it should be possible to “hold” the nvidia driver and get the other upgrades?

Cheers

---

<div class="post-metadata">

### Author: ![chatan](https://support.blue-systems.com/letter_avatar/chatan/32/5_5575768a8748004e209b776fc1b2916d.png) [@chatan](https://support.blue-systems.com/u/chatan)
#### Post date: [October 18, 2016, 1:56pm UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/17 "2016-10-18T13:56:21Z")

</div>

After I restored my system again to pre-update state, I held the nvidia driver (at version 304.131) by editing /etc/pacman.conf with this line:

```auto
IgnorePkg = lib32-nvidia-304xx linux44-nvidia-304xx mhwd-nvidia-304xx nvidia-304xx-utils
```

…then did the updates per the manjaro update thread. All seems well. I just have to keep an eye out if the nvidia-304xx get fixed. For reference, Other posts at nvidia forum: [https://devtalk.nvidia.com/default/topic/972001/linux/serious-regression-in-legacy-304xx-304-132-drivers/](https://devtalk.nvidia.com/default/topic/972001/linux/serious-regression-in-legacy-304xx-304-132-drivers/)  
[https://devtalk.nvidia.com/default/topic/968892/linux/geforce-7300le-with-304-132-glxinfo-fails-now-with-quot-x-error-of-failed-request-badvalue-quot-/](https://devtalk.nvidia.com/default/topic/968892/linux/geforce-7300le-with-304-132-glxinfo-fails-now-with-quot-x-error-of-failed-request-badvalue-quot-/)

Boy am I glad I started making clones with clonezillla!  
Cheers.

---

<div class="post-metadata">

### Author: ![chatan](https://support.blue-systems.com/letter_avatar/chatan/32/5_5575768a8748004e209b776fc1b2916d.png) [@chatan](https://support.blue-systems.com/u/chatan)
#### Post date: [October 26, 2016, 7:52am UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/18 "2016-10-26T07:52:16Z")

</div>

Since I held back the nvidia updates, I was hoping the [[Update] 2016-10-23](http://forums.netrunner.com/showthread.php?tid=23954) would go smoothly, but after the updates, system freezes: I do Ctrl-Alt f2 and check my journal and I see a “failed to load module nvidia”  
Back to drawing board… :s in mean clonezilla restore.

---

<div class="post-metadata">

### Author: ![AJSlye](https://support.blue-systems.com/user_avatar/support.blue-systems.com/ajslye/32/263_2.png) [@AJSlye](https://support.blue-systems.com/u/AJSlye)
#### Post date: [October 26, 2016, 11:46am UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/19 "2016-10-26T11:46:11Z")

</div>

@ chantan,  
You should have held back the kernel from updating as well as the nvidia driver modules. Unfortunately, sometimes the drivers need to be updated along with the kernel even for point releases.

---

<div class="post-metadata">

### Author: ![chatan](https://support.blue-systems.com/letter_avatar/chatan/32/5_5575768a8748004e209b776fc1b2916d.png) [@chatan](https://support.blue-systems.com/u/chatan)
#### Post date: [October 26, 2016, 12:35pm UTC](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103/20 "2016-10-26T12:35:01Z")

</div>

ahhhh, OK that makes sense. Could you confirm that I just need to add “linux” to the IgnorePkg line? Thats what I found here: [https://www.digitalocean.com/community/tutorials/pacman-syu-kernel-update-solved-how-to-ignore-arch-kernel-upgrades](https://www.digitalocean.com/community/tutorials/pacman-syu-kernel-update-solved-how-to-ignore-arch-kernel-upgrades)

Cheers!

[Next page](https://support.blue-systems.com/t/10-09-2016-update-went-bust-black-screen/4103.md?page=2)
