You are not logged in.
I have been using Arch for 4 months now, constantly doing updates, but I have never experienced this before. I updated my system and now the only thing I see is a black screen on boot. I can use Alt+Ctrl+F2 and tried installing and using linux-lts but it made no difference; the black screen is still there even when booting up from the lts kernel.
Last edited by insciwetrust (2020-02-15 10:02:25)
No gods, no masters!
Offline
Do you auto boot to X or to tty? Can you boot to tty? Looks like you can. What graphics hardware do you have? What Display manager, desktop environment or window manager is doing this? Does journalctl tell you anything?
If you don't add some info, members won't answer you.
Offline
Do you auto boot to X or to tty? Can you boot to tty? Looks like you can. What graphics hardware do you have? What Display manager, desktop environment or window manager is doing this? Does journalctl tell you anything?
If you don't add some info, members won't answer you.
To X, but I can boot to tty. I am using an AMD graphics card. My system runs XFCE with Light Display Manager.
I don't know how I can submit my journalctl output, as I am on mobile. So here is a photo of the output of
journalctl -b -1
I also tried adding "nomodeset" to the kernel parameters, it only directed me to tty, I still can't access my system. I tried running startx but it said
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error"
.
Last edited by insciwetrust (2020-02-14 21:59:15)
No gods, no masters!
Offline
[
I don't know how I can submit my journalctl output, as I am on mobile. So here is a photo of the output ofjournalctl -b -1
See the tip box from pastebin
Offline
insciwetrust wrote:[
I don't know how I can submit my journalctl output, as I am on mobile. So here is a photo of the output ofjournalctl -b -1
See the tip box from pastebin
It is banned in my country.
No gods, no masters!
Offline
Perhaps you could try actually reading the page?
Note: pastebin.com is blocked for some people and has a history of annoying issues (javascript, adverts, poor formatting, etc). Do not use it.
Offline
command |& curl -F 'f:1=<-' ix.io
curl -F 'f:1=<-' ix.io < file
These work too
https://0x0.st
http://sprunge.us
Edit: Also look at your ~/.local/share/xorg/Xorg.0.log for clues.
Last edited by teckk (2020-02-14 23:01:24)
Offline
I auto-login on GNOME+Wayland and after today's updates my first 2 reboots resulted in gnome-shell core-dumping (i.e. ended up a black screen). Seems to be working fine since the 3rd reboot however and I can't recreate it.
Offline
command |& curl -F 'f:1=<-' ix.io curl -F 'f:1=<-' ix.io < file
These work too
https://0x0.st
http://sprunge.usEdit: Also look at your ~/.local/share/xorg/Xorg.0.log for clues.
Hastebin seemed to work fine. Here is my xorg.log: https://hastebin.com/jubijimafe
And here is my latest journalctl output on boot: https://hastebin.com/laqowamise
Thank you for your kind instructions.
No gods, no masters!
Offline
Offline
Seems like mesa was indeed the problem, downgrading worked for me as well. Thank you!
No gods, no masters!
Offline
My gnome-shell abort problem described above, which I thought was the same issue, is still occurring and not due to mesa. It is due to a bug from the recent upgrade of libnput 1.15.0-1 -> 1.15.1-1. I have annotated the upstream bug.
Offline