You are not logged in.
Pages: 1
Topic closed
Kernel: linux-lts.
I had recently performed full system upgrade and to do so I issued command
sudo pacman -Syu
and after successful installation of update, I rebooted my machine and after reboot I am only seeing black screen and also I am not able to access terminal (if display manager had broken). How to fix?
Laptop name : Asus zenbook UX305UA (dual booted with windows 10).
Configuration: i5, 8GB RAM, 256GB SSD, Intel graphic card.
Update: I tried to boot live arch Linux (2017.08.01) black screen after boot
Last edited by vaibhavsingh97 (2017-08-05 11:31:57)
Offline
after reboot I am only seeing black screen
Unusual for that to be needed after an LTS update though
Jin, Jîyan, Azadî
Offline
Can you switch tty with alt+ctrl+(F1,F2,F3..)?
Offline
Can you switch tty with alt+ctrl+(F1,F2,F3..)?
No, I am not able to
Offline
vaibhavsingh97 wrote:after reboot I am only seeing black screen
Unusual for that to be needed after an LTS update though
I tried but problem remains the same
Offline
When exactly does the screen go black?
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
after reboot I am only seeing black screen
- At what stage in particular?
Do you get the boot menu? Boot messages (disable "quiet" booting)? A Desktop manager?
- Can you boot into the multi-user.target, see https://wiki.archlinux.org/index.php/Sy … _boot_into ?
- Can you ping the machine? Ssh into it?
Offline
after reboot I am only seeing black screen
- At what stage in particular?
Do you get the boot menu? Boot messages (disable "quiet" booting)? A Desktop manager?
- Can you boot into the multi-user.target, see https://wiki.archlinux.org/index.php/Sy … _boot_into ?
- Can you ping the machine? Ssh into it?
Getting grub menu and after selecting the arch getting message
loading linux-lts
after that black screen and when I press the power button, my machine simply shutdown
Last edited by vaibhavsingh97 (2017-08-05 11:13:57)
Offline
vaibhavsingh97 wrote:after reboot I am only seeing black screen
Unusual for that to be needed after an LTS update though
I installed fresh and still the problem is same so i added
i915.modeset=0
then I am able to boot....how to permanently fix?
Offline
Without modesetting, you cannot run X11 or wayland, but I guess the problem is in starting the displayserver or display manager or desktop session anyway, so start by looking into the journal of the previous boot(s) to figure what actually failed.
Offline
Without modesetting, you cannot run X11 or wayland, but I guess the problem is in starting the displayserver or display manager or desktop session anyway, so start by looking into the journal of the previous boot(s) to figure what actually failed.
I found an issue which I think it's similar to me. https://bugs.archlinux.org/task/54471
Laptop configuration mentioned in a bug is also same.
Offline
Did you see the suggestion to disable CSM?
Offline
Did you see the suggestion to disable CSM?
CSM is already disabled in BIOS. I tried to boot antergos, manjaro but problem is smae black screen so i installed ubuntu temporary.
As soon i will get solution, will sift to arch <3
Offline
Then you're probably not facing the same bug.
Quoting mysefl:
Can you ping the machine? Ssh into it?
Offline
Then you're probably not facing the same bug.
Quoting mysefl:Can you ping the machine? Ssh into it?
I am not able to access terminal. I have to connect and enter credentials in order to access internet so ssh is not possible
Last edited by vaibhavsingh97 (2017-08-06 21:15:51)
Offline
Internet?? You'd just use another system in the same subnet.
Anyway: since you can boot w/o modeset and the other bug is recorded in the journal, lookup the journal from a previous ("failing") boot.
Offline
Internet?? You'd just use another system in the same subnet.
Anyway: since you can boot w/o modeset and the other bug is recorded in the journal, lookup the journal from a previous ("failing") boot.
I had gone with unbuntu for now, will wait for bug fix and will switch to Arch. As I redownloaded arch, antergos and manjaro but none of them boot, getting black screen after booting.
Last edited by vaibhavsingh97 (2017-08-07 13:26:11)
Offline
Bugs don't get magically fixed.
If this is a kernel regression, prepare to be hit by it as soon as ubuntu catches up...
Offline
Bugs don't get magically fixed.
If this is a kernel regression, prepare to be hit by it as soon as ubuntu catches up...
I am using arch since 3 years but first time my system is broken like this and i have to wait for next release to test
Offline
Without knowing the kernel version that last worked. The kernel version that the issue first occurred with.
The journal for the boot with blank screen if any is recorded I am not sure what additional help can be provided.
Offline
I've the same issue too... Ctrl + alt + f1/f2/f3 don't work... Pressing power button instantly turns off PC... It gives few boot logs with all [OK] on the side and suddenly goes blank after like 2sec... These issues started arising after I updated my windows(I'm triple booting my system with windows, ubuntu and arch) and grub disappeared... I used ubuntu live usb to get back grub but this happened after that... When secure boot was enabled it gave "bad shim signature. you need to load kernel first"... Disabling secure boot gave the blank screen problem..
Offline
Please don't necro-bump, there's no chance you're hitting this very same problem after 5 years.
See the 3rd link below, open a new thread and post a system jorunal from a failing boot.
If you've an nvidia system, chances are you might have to add "ibt=off" to the kernel parameters.
Offline
If you are able to get in a terminal shell with ctrl + alt + F2 or ctrl + alt + F6
mkinitcpio -P
and then reboot with
reboot
I sometimes have that issue when I upgrade my nvidia drivers.
Offline
If you are able to get in a terminal shell with ctrl + alt + F2 or ctrl + alt + F6
Ctrl + alt + f1/f2/f3 don't work...
…
Offline
Please don't necro-bump, there's no chance you're hitting this very same problem after 5 years.
See the 3rd link below, open a new thread and post a system jorunal from a failing boot.
Closing this old thread.
Offline
Pages: 1
Topic closed