Black screen after GRUB and before log-in screen [SOLVED]

So I am using a 2018 Dell XPS 13 (9730) with the latest unstable build of Manjaro.

However for some reason after GRUB when you see in the top left corner: ‘Version: 239’ etc etc my screen goes black and a hard-reset is required to restart my laptop and go into the login screen. This sometimes may require 2 or 3 times.

This problem still persists after I updated my BIOS from 1.3.3 to 1.4.0 succesfully through fwupd in the terminal.

Here is my inxi -Fx output:

System:
  Host: Dell-XPS-13-9370 Kernel: 4.18.4-1-MANJARO x86_64 bits: 64 
  compiler: gcc v: 8.2.0 Desktop: Xfce 4.13.2 Distro: Manjaro Linux 
Machine:
  Type: Laptop System: Dell product: XPS 13 9370 v: N/A 
  serial: <root required> 
  Mobo: Dell model: 0F6P3V v: A00 serial: <root required> UEFI: Dell 
  v: 1.4.0 date: 05/25/2018 
Battery:
  ID-1: BAT0 charge: 29.3 Wh condition: 49.4/52.0 Wh (95%) 
  model: SMP DELL G8VCF6C status: Charging 
CPU:
  Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP 
  arch: Kaby Lake rev: A L2 cache: 8192 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31880 
  Speed: 900 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 900 2: 900 
  3: 901 4: 900 5: 900 6: 900 7: 900 8: 900 
Graphics:
  Device-1: Intel UHD Graphics 620 driver: i915 v: kernel bus ID: 00:02.0 
  Display: x11 server: X.Org 1.20.1 driver: intel unloaded: modesetting 
  tty: N/A 
  OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) 
  v: 4.5 Mesa 18.1.6 direct render: Yes 
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel v: kernel 
  bus ID: 00:1f.3 
  Sound Server: ALSA v: k4.18.4-1-MANJARO 
Network:
  Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter 
  driver: ath10k_pci v: kernel bus ID: 02:00 
  IF: wlp2s0 state: up mac: 9c:b6:d0:8f:f5:d9 
Drives:
  Local Storage: total: 476.94 GiB used: 21.51 GiB (4.5%) 
  ID-1: /dev/nvme0n1 vendor: Toshiba model: KXG50ZNV512G NVMe 512GB 
  size: 476.94 GiB 
Partition:
  ID-1: / size: 451.50 GiB used: 21.49 GiB (4.8%) fs: ext4 
  dev: /dev/nvme0n1p2 
  ID-2: swap-1 size: 16.93 GiB used: 0 KiB (0.0%) fs: swap 
  dev: /dev/nvme0n1p3 
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 210 Uptime: 8m Memory: 15.39 GiB used: 1.25 GiB (8.1%) 
  Init: systemd Compilers: gcc: 8.2.0 Shell: bash v: 4.4.23 inxi: 3.0.21

Let me know if you need more info. Much obliged!

(And yes I am well aware of other topics with black screens and all but most are after hibernate. Mine is during a clean start-up of the system or after a simple reboot. And sometimes it goes straight into the log-in screen and sometimes it doesn’t. And this is a serious issue for me as hard-resetting my laptop isn’t going to expand it’s lifetime overall.)

Why are you posting in the Newbies section? Mistake or…
I guess the one that convinced you to go to Unstable was playing some game with you… :rofl:

Good point there @AgentS

I think I need to play my cards differently.

To be clearly honest, I simply assumed the unstable build was more fitted for newer or modern laptops.

EDIT: Where should I post this question then? If I may friendly ask? :grinning:

EDIT2: I had this same problem before when I did install a stable build of Manjaro.

The meaning of “unstable”:
It may or may not blend.

Yes yes, I learned my lesson and put on my “donkey hat” or whatever it is called :rofl:

So I am running the stable build now (17.1.12) and the problem continues but only after installing Linux kernel 4.18. So gone back to 4.14 and it runs fine, only I am getting ACPI errors? (It’s going by really fast to properly read.

Here is my new inxi -Fx output:

System:
  Host: Dell-XPS-13-9730 Kernel: 4.14.65-1-MANJARO x86_64 bits: 64 
  compiler: gcc v: 8.2.0 Desktop: N/A Distro: Manjaro Linux 
Machine:
  Type: Laptop System: Dell product: XPS 13 9370 v: N/A 
  serial: <root required> 
  Mobo: Dell model: 0F6P3V v: A00 serial: <root required> UEFI: Dell 
  v: 1.4.0 date: 05/25/2018 
Battery:
  ID-1: BAT0 charge: 39.8 Wh condition: 49.4/52.0 Wh (95%) 
  model: SMP DELL G8VCF6C status: Discharging 
CPU:
  Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP 
  arch: Kaby Lake rev: A L2 cache: 8192 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31880 
  Speed: 900 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 900 2: 900 
  3: 900 4: 900 5: 900 6: 900 7: 900 8: 900 
Graphics:
  Card-1: Intel UHD Graphics 620 driver: i915 v: kernel bus ID: 00:02.0 
  Display: x11 server: N/A driver: intel unloaded: modesetting 
  resolution: <xdpyinfo missing> 
  OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) 
  v: 4.5 Mesa 18.1.6 direct render: Yes 
Audio:
  Card-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel v: kernel 
  bus ID: 00:1f.3 
  Sound Server: ALSA v: k4.14.65-1-MANJARO 
Network:
  Card-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter 
  driver: ath10k_pci v: kernel bus ID: 02:00 
  IF: wlp2s0 state: up mac: 9c:b6:d0:8f:f5:d9 
Drives:
  Local Storage: total: 476.94 GiB used: 8.96 GiB (1.9%) 
  ID-1: /dev/nvme0n1 vendor: Toshiba model: KXG50ZNV512G NVMe 512GB 
  size: 476.94 GiB 
Partition:
  ID-1: / size: 451.49 GiB used: 8.96 GiB (2.0%) fs: ext4 
  dev: /dev/nvme0n1p2 
  ID-2: swap-1 size: 16.93 GiB used: 0 KiB (0.0%) fs: swap 
  dev: /dev/nvme0n1p3 
Sensors:
  System Temperatures: cpu: 39.5 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 193 Uptime: 1m Memory: 15.39 GiB used: 1.01 GiB (6.5%) 
  Init: systemd Compilers: gcc: 8.2.0 Shell: bash v: 4.4.23 inxi: 3.0.20

And to whom it may concern, I only use this website when I am stuck, so if this needs to be somewhere else on the forum, by all means, move it to the proper category :grinning:

If there are no problems with 414 stick with it. This is an very stable kernel. I would not worry too much about the ACPI thing. I have some of this stuff too with surface pro and 414. At this time i am running the 417 which gives me no errors at all. At least not at boot time.
You can check for boot error messages with

journalctl -b0 -p3

for the current boot, but ACPI errors are not so much to concern, normally.
For your failing kernel, you can see errors watching a previous boot with

journalctl -b -1 -p3

meaning “-b -1” is for the previous boot. -2 is for the one previous to previous and so on…
p3” is for seriousness being less for more serious and so on…

Study this for more

@calvous & @AgentS Thanks a bunch! Really appreciate your help! Sorry for the late response!

Much obliged!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by