Black screen.

SnillyWead

Hi,
I tried Solus Budgie 4.3 the live version and later installed it on my computer and with both I experienced random black screens. Even after reboot and all the latest updates. I later installed Pop OS 21.04 and no black screens. HP All in one with Intel i5-7200U (4) @ 3.100GHz and Intel HD Graphics 620.

dalto

SnillyWead I experienced random black screens.

Can you explain what you mean by "random black screens"?

[deleted]

i am not sure if this affects, but could it be related to uefi/legacy booting mechanisms? 🤔

additionally,there is a uefi guide in the help center

SnillyWead

[deleted] uefi with secure boot disabled. I will try the Gnome version next to see if the same problem.

MarkoB

I have uefi also , but kde, no issues so far

SnillyWead

Just tried Gnome and same problem. No downloading Mate.

SnillyWead

dalto When moving mouse and sometimes doing nothing. Tried Mate and KDE. Same problem. I just don't get it. With Pop no black screen. Tried different USB. Makes no difference.

dalto

SnillyWead

Can you share the output of inxi -CGa

SnillyWead

dalto CPU:
Info: Dual Core model: Intel Core i5-7200U bits: 64 type: MT MCP
arch: Amber/Kaby Lake note: check family: 6 model-id: 8E (142) stepping: 9
microcode: EA L2 cache: 3 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 21599
Speed: 3004 MHz min/max: 400/3100 MHz Core speeds (MHz): 1: 3004 2: 3082
3: 1530 4: 2235
Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
Type: l1tf mitigation: PTE Inversion
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel HD Graphics 620 vendor: Hewlett-Packard driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5916 class ID: 0300
Device-2: Cheng Uei Precision Industry (Foxlink) HP Integrated Webcam type: USB
driver: uvcvideo bus ID: 1-3:4 chip ID: 05c8:0230 class ID: 0e02
serial: 200901010001
Display: x11 server: X.Org 1.20.11 compositor: gnome-shell v: 3.38.4 driver:
loaded: modesetting unloaded: fbdev,vesa display ID: :1 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 93 size: 527x297mm (20.7x11.7")
diag: 605mm (23.8")
OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 21.0.1
direct render: Yes

dalto

SnillyWead

You are currently using the modesetting driver which is, generally speaking, more compatible. You could try switching to the intel driver and see if that is better or worse.

Alternatively, if you still have popOS installed, you could see which driver it is using.

This is the relevant line:

Display: x11 server: X.Org 1.20.11 compositor: gnome-shell v: 3.38.4 driver: loaded: modesetting unloaded: fbdev,vesa display ID: :1 screens: 1

The current driver is listed immediately after loaded:

SnillyWead

dalto This output is from Pop OS. How do I enable the Intel driver?

dalto

SnillyWead This output is from Pop OS.

If the original output was from popOS, can you share the inxi -Ga from Solus first? It may be different.

SnillyWead

dalto Output is the same except on Solus display ID is 0 instead of 1 on Pop. But I'm not the only one who has black screens. Solus section on reddit more users with same problem. With all versions of Solus. I have tried many distro's and those never had black screen, so must be Solus. Or kernel maybe?

[deleted]

SnillyWead hi did you fix your issue?

SnillyWead

[deleted] No. I still don't know what causes it. Egee on youtube did a live stream with 4.3 KDE and after install and reboot, immediately black screen. And he's not the only one with black screen. Several other users on reddit same problem. So must be Solus or maybe kernel? Bummer because I wanted to try Budgie for at least a month. Maybe if it gets fixed I will try Solus again, but for now I went back to Pop OS.

[deleted]

yes,hopefully it will get fixed 🙂