You are not logged in.
Pages: 1
I updated my system yesterday night (I update my system every week once minimum). Today morning when I started my system, I got a blank screen. There is no login prompt (I do not have a desktop manager). I usually login to console and then run startx command to launch openbox based window manager.
Once I select Arch Linux from boot menu, I get a blank screen.
Any help please ?
Last edited by hanstech (2020-06-14 07:54:05)
Offline
Details of your hardware, specifically video card/driver. Pacman log from the update, and journal from the failed boot. You can grab those from the chroot.
Offline
could be related to this: https://bbs.archlinux.org/viewtopic.php?id=256525
So reverting linux and intel-ucode might be a temporary workaround.
But it may actually be due to this: https://bbs.archlinux.org/viewtopic.php?id=256273&p=2
It seems that starting from kernel 5.7.2, initramfs paths have to use backslashes instead of forwardslashes, so if you are using efistub or rEFInd and if you configured it with forward slashes you may encounter problems.
Last edited by nourathar (2020-06-14 11:50:21)
Offline
Hi,
I think it might be due to the issue reported in the link in the reply.
I configured my system 3 years ago and everything was working fine till last week. I know that I configured my boot using systemd-boot (I had an original windows installation in the laptop, and I am using the same boot device). I am not able to find the command efi* in my machine. I chrooted to the non-working installation. Pacman log says that I am updating to kernel 5.7.2-arch1-1. There is no error message in pacman log.
My VGA controller is Intel Skylake GT2
How can I view what boot utility I am using (efistub or whatever).
In my windows boot partition (efi), I have EFI directory and initramfs, intel-code, vmlinuz and loader directory.
Under loader/entries, I have arch.conf containing following entries
title ArchLinux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options root=PARTUUID=SOMEID rw
I tried changing / with \ and completely removing /. In both settings, it did not work out.
Any help please ?
Last edited by hanstech (2020-06-15 17:39:12)
Offline
As far as I know - which is perhaps not very far - the EFI problems reported did not apply to installations using systemd-boot, but I may be wrong there...
Have you looked at the active topics on the Wiki ? There are a few other people reporting blank screens after updating to the new kernel but for other reasons..
Offline
5.7.2 and i915 aren't working well based on recent bug reports.
Please install linux-lts and try to boot into that kernel, if you can. It should in theory solve your immediate issue.
If you unable to proceed to even install lts.. try booting from live USB or so if you have handy... "arch-chroot" into your current installation and then install lts kernel.
Last edited by pk.gmp (2020-06-16 08:41:51)
Offline
I booted using live USB and chrooted to my arch installation and installed linux-its
I also added a new boot entry for lts. Tried to boot to lts, but same issue. I got just blank screen.
Xorg.log. says,
LoadModule: "fbdev"
wanting, couldn't open module fbdev
unload module fbdev
...........
LoadModule "vesa"
couldn't open module vesa
Unload module vesa
modesetting: Driver for Modesetting Kernel Drivers: kms
open /dev/dri/card0: No such file or directory
......
Fatal server error:
no screens found.
Last edited by hanstech (2020-06-16 12:58:11)
Offline
Please post the actual contents of Xorg.log. See the tip box pastebin. Please also post the output of dmesg.
Offline
Offline
[ 10.623] Current Operating System: Linux sham-lap 4.12.8-2-ARCH #1 SMP PREEMPT Fri Aug 18 14:08:02 UTC 2017 x86_64Is that the most recent Xorg.log? Did you check both ~/.local/share/xorg/ and /var/log ?
The two links are to the same address, if the second one was meant to the dmesg output.
Offline
That one is /var/log/Xorg.0.log
~/.local/share/xorg Xorg.0.log is in the location
Last edited by hanstech (2020-06-16 13:31:24)
Offline
[ 13.942] Current Operating System: Linux sham-lap 5.6.15-arch1-1 #1 SMP PREEMPT Wed, 27 May 2020 23:42:26 +0000 x86_64That is not using linux-lts either. I can not tell if you booted linux-lts or are still booting linux as you did not post the output of dmesg.
Offline
I don't think this is an X11 problem and he's likely not attempting to start Xorg on the failing boots:
There is no login prompt (I do not have a desktop manager). I usually login to console and then run startx command to launch openbox based window manager.
Once I select Arch Linux from boot menu, I get a blank screen.
=> Edit the kernel parameters in the boot manager, remove "quiet" and add "nomodeset" and any number of those: https://wiki.archlinux.org/index.php/Ge … bug_output
See whether you get some output.
If not you'll likely have to boot the iso, chroot into the installed system and dump the journal of an older boot "journalctl -b -1" for the last one.
Offline
dmesg entries can be seen here
Also, how do I make sure that I boot to LTS ? I installed LTS kernel and added a new conf under loader/entries directory. What else I should do ?
Thanks
Last edited by hanstech (2020-06-16 14:53:26)
Offline
[ 9.818434] systemd[1]: Set hostname to <archiso>.That's from the intallation iso. Meaningless.
Offline
Offline
[ 9.818434] systemd[1]: Set hostname to <archiso>.Still meaningless.
Offline
Ok,
can you tell me how can I boot into LTS. I already install lts and added entries under entries directory. I am using systemd-boot
Offline
Offline
Ok, this might help you to help me ? I rebooted to get this new dmesg
Offline
No. Still dmesg for the iso boot.
If not you'll likely have to boot the iso, chroot into the installed system and dump the journal of an older boot "journalctl -b -1" for the last one.
Offline
Pages: 1