Black screen

Alfatrion

Member

Reaction score: 4
Messages: 28

I have a sddm with kde5 setup. Since yeasterday I get a blank screen after I login.

I have a intel graphics card. It all worked until a couple days ago. Now I sometimes am able to start kde5 and then can work, but I am starting at a blank screen more often then not.

I am running out of ideas on what to do.
 
OP
A

Alfatrion

Member

Reaction score: 4
Messages: 28

The command shell looks fine. I can als start X fine. I am only having problems with KDE.
 

George

Aspiring Daemon

Reaction score: 212
Messages: 520

I would try to look at dmesg for hints, and also the xorg log files (/var/log/Xorg.0.log or Xorg.0.log.old.

Are your packages up to date?

Black screen could mean that KDE crashed. Look for a .core file in your Home directory.
 
OP
A

Alfatrion

Member

Reaction score: 4
Messages: 28

The lock screen works just fine. I walked away from the black screen. When I returned there was a perfectly working black screen. After unlocking it, then the black screen came back.

I found no core files.

All packages are up to date.

Dmesg gives
Code:
info: [drm] Initialized drm 1.1.0 20060810
drmn0: =======================================================
drmn0: This code is obsolete abandonware. Install the graphics/drm-legacy-kmod pkg
drmn0: =======================================================
drmn0: Deprecated code (to be removed in FreeBSD 13): drm2 drivers
drmn0: =======================================================
drmn0: This code is obsolete abandonware. Install the graphics/drm-legacy-kmod pkg
drmn0: =======================================================
drmn0: Deprecated code (to be removed in FreeBSD 13): drm2 drivers
drmn0: <Intel Haswell (GT2 desktop)> on vgapci0
info: [drm] Memory usable by graphics device = 2048M
info: [drm] MTRR allocation failed.  Graphics performance may suffer.
intel_iicbb0 on drmn0
iicbus0: <Philips I2C bus>error: [drm:pid2532:i915_write32] *ERROR* Unknown unclaimed register before writing to c5100
on iicbb_nostop0 addr 0xff
iic0: <I2C generic I/O> on iicbus0
iicbus1: <Philips I2C bus> on intel_gmbus0
iic1: <I2C generic I/O> on iicbus1
intel_iicbb1 on drmn0
iicbus2: <Philips I2C bus> on iicbb_nostop1 addr 0xff
iic2: <I2C generic I/O> on iicbus2
iicbus3: <Philips I2C bus> on intel_gmbus1
iic3: <I2C generic I/O> on iicbus3
intel_iicbb2 on drmn0
iicbus4: <Philips I2C bus> on iicbb_nostop2 addr 0xff
iic4: <I2C generic I/O> on iicbus4
iicbus5: <Philips I2C bus> on intel_gmbus2
iic5: <I2C generic I/O> on iicbus5
intel_iicbb3 on drmn0
iicbus6: <Philips I2C bus> on iicbb_nostop3 addr 0xff
iic6: <I2C generic I/O> on iicbus6
iicbus7: <Philips I2C bus> on intel_gmbus3
iic7: <I2C generic I/O> on iicbus7
intel_iicbb4 on drmn0
iicbus8: <Philips I2C bus> on iicbb_nostop4 addr 0xff
iic8: <I2C generic I/O> on iicbus8
iicbus9: <Philips I2C bus> on intel_gmbus4
iic9: <I2C generic I/O> on iicbus9
intel_iicbb5 on drmn0
iicbus10: <Philips I2C bus> on iicbb_nostop5 addr 0xff
iic10: <I2C generic I/O> on iicbus10
iicbus11: <Philips I2C bus> on intel_gmbus5
iic11: <I2C generic I/O> on iicbus11
info: [drm] MSI enabled 1 message(s)
info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
info: [drm] Driver supports precise vblank timestamp query.
drm_iic_dp_aux0 on drmn0
drm_iic_dp_aux1 on drmn0
drmn0: taking over the fictitious range 0xe0000000-0xf0000000
info: [drm] Connector VGA-1: get mode from tunables:
info: [drm]   - kern.vt.fb.modes.VGA-1
info: [drm]   - kern.vt.fb.default_mode
info: [drm] Connector HDMI-A-1: get mode from tunables:
info: [drm]   - kern.vt.fb.modes.HDMI-A-1
info: [drm]   - kern.vt.fb.default_mode
info: [drm] Connector DP-1: get mode from tunables:
info: [drm]   - kern.vt.fb.modes.DP-1
info: [drm]   - kern.vt.fb.default_mode
info: [drm] Connector HDMI-A-2: get mode from tunables:
info: [drm]   - kern.vt.fb.modes.HDMI-A-2
info: [drm]   - kern.vt.fb.default_mode
info: [drm] Connector DP-2: get mode from tunables:
info: [drm]   - kern.vt.fb.modes.DP-2
info: [drm]   - kern.vt.fb.default_mode
info: [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00
drmn0: warning: VGA-1: EDID block 0 invalid.
info: [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
fbd0 on drmn0
VT: Replacing driver "efifb" with new "fb".
drmn0: More than 8 outputs detected
info: [drm] Initialized i915 1.6.0 20080730 for drmn0 on minor 0
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
info: [drm] capturing error event; look for more information in sysctl hw.dri.0.info.i915_error_state
error: [drm:pid2599:i915_write32] *ERROR* Unknown unclaimed register before writing to 20a8
error: [drm:pid0:i915_write64] *ERROR* Unknown unclaimed register before writing to 100000
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
error: [drm:pid12:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung

I have always seen the hung messages.
 
OP
A

Alfatrion

Member

Reaction score: 4
Messages: 28

/var/log/Xorg.0.log contains

Code:
[   174.714]
X.Org X Server 1.20.8
X Protocol Version 11, Revision 0

(...)

[   180.354] (II) event5  - Logitech USB Receiver, class 0/0, rev 2.00/12.03, addr 4: is tagged by udev as: Mouse
[   180.355] (II) event5  - Logitech USB Receiver, class 0/0, rev 2.00/12.03, addr 4: device is a pointer
[   228.150] (II) intel(0): EDID vendor "GSM", prod id 22271
[   228.150] (II) intel(0): Using EDID range info for horizontal sync
[   228.150] (II) intel(0): Using EDID range info for vertical refresh
[   228.150] (II) intel(0): Printing DDC gathered Modelines:
[   228.150] (II) intel(0): Modeline "1920x1080"x0.0  138.50  1920 1968 2000 2080  1080 1082 1087 1111 +hsync -vsync (66.6 kHz eP)
[   228.150] (II) intel(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[   228.150] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[   228.150] (II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[   228.150] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[   228.150] (II) intel(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[   228.150] (II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[   228.150] (II) intel(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[   228.150] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   228.150] (II) intel(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[   228.150] (II) intel(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[   228.150] (II) intel(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[   228.150] (II) intel(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[   228.150] (II) intel(0): Modeline "1280x720"x75.0   95.65  1280 1352 1488 1696  720 721 724 752 -hsync +vsync (56.4 kHz e)
[   228.150] (II) intel(0): Modeline "1280x960"x75.0  129.86  1280 1368 1504 1728  960 961 964 1002 -hsync +vsync (75.1 kHz e)
[   232.343] (II) intel(0): EDID vendor "GSM", prod id 22271
[   232.344] (II) intel(0): Using hsync ranges from config file
[   232.344] (II) intel(0): Using vrefresh ranges from config file
[   232.344] (II) intel(0): Printing DDC gathered Modelines:
[   232.344] (II) intel(0): Modeline "1920x1080"x0.0  138.50  1920 1968 2000 2080  1080 1082 1087 1111 +hsync -vsync (66.6 kHz eP)
[   232.344] (II) intel(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[   232.344] (II) intel(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[   232.344] (II) intel(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[   232.344] (II) intel(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[   232.344] (II) intel(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[   232.344] (II) intel(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[   232.344] (II) intel(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[   232.344] (II) intel(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[   232.344] (II) intel(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[   232.344] (II) intel(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[   232.344] (II) intel(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[   232.344] (II) intel(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[   232.344] (II) intel(0): Modeline "1280x720"x75.0   95.65  1280 1352 1488 1696  720 721 724 752 -hsync +vsync (56.4 kHz e)
[   232.344] (II) intel(0): Modeline "1280x960"x75.0  129.86  1280 1368 1504 1728  960 961 964 1002 -hsync +vsync (75.1 kHz e)
[   304.544] (EE) intel(0): Detected a hung GPU, disabling acceleration.[   304.544] (EE) intel(0): When reporting this, please include i915_error_state from debugfs and the full dmesg
 

George

Aspiring Daemon

Reaction score: 212
Messages: 520

304.544] (EE) intel(0): Detected a hung GPU, disabling acceleration.
KDE without hardware acceleration is certainly not ideal.

drmn0: <Intel Haswell (GT2 desktop)> on vgapci0
Look at FreeBSD Graphics:
"For haswell based systems, if the drm-kmod port does not work, it is suggested to install the drm-legacy-kmod."
 
OP
A

Alfatrion

Member

Reaction score: 4
Messages: 28

Before, I was running using the vesa driver. At this point, I am happy to go back to that.

I have DRM-legacy-kmod installed. This port gives the same warning as DRM-kmod to install DRM-legacy-kmod.
 
OP
A

Alfatrion

Member

Reaction score: 4
Messages: 28

Today, I created a new user. I copied .xinitrc, chown it and adjusted the group's. I got KDE one but not wit a second new user.
 
OP
A

Alfatrion

Member

Reaction score: 4
Messages: 28

I have installed Xfce and that works, so this would appear to be a KDE issue.
 

the3ajm

Member

Reaction score: 20
Messages: 85

That happened to me, I had to boot into single user mode to make sure plasma5-plasma-desktop/workspace is reinstalled. Another variant is when you're stuck in a loop with sddm screen, this doesn't seem to be related to a KDE setting (renaming my local settings, reinstalling packages, checking the logs) because after when I remove a old and add a new user to try if it works my main login started working since my profile icon was there.

The intel drivers helped me to get the full resolution of my laptop so I don't think it's related to loading the desktop portion of KDE.
 
OP
A

Alfatrion

Member

Reaction score: 4
Messages: 28

My SSD went bad a coupe of weeks ago. I have installed FreeBSD on a new SSD. Currently I am able to run KDE again.
 
Top