you still get a display so there is some threads of hope. That is extremely bizarre though.
I suggest doing a full power cycle. power off the pc unplug the power cable and hold the power button for about 10-20 seconds to discharge everything. then give the system a bit to cool down and maybe double check that there isn’t any dust or something wrong with the gpu fan or something.
Phew. Just launched Kubuntu, no artifacts or any other nasty stuff. Survived furmark without issues.
So things are a lot better than I was afraid of. It didn’t kill my GPU, it just totally messed my Windows installation to the point it now just BSODs with different reasons every time, but first couple ones were about video driver (now it complains about memory and everything else, just totally mad thing).
And my NTFS partitions can’t be mounted by /etc/fstab, for some reason they are in RO and Steam complaints about them not being executable.
windows and linux manage time differently. when you install linux it will update your bios time to be based on GMT and then it modifies the value it displays to you based on your time zone. windows just sets the bios time to your local time.
1 Like
Heard something about it and forgot, thank you. Ok, now to main deal. Looks like my Windows is dead for now and I am pushed to set up Kubuntu.
To add to this:
https://help.ubuntu.com/community/UbuntuTime#Multiple_Boot_Systems_Time_Conflicts
A solution is listed in that link.
1 Like
alright so if you haven’t already, please use an updated mesa ppa, with amd gpus it makes a big difference.
here’s the instructions from the one the valve recommends
sudo add-apt-repository ppa:paulo-miguel-dias/pkppa
sudo apt dist-upgrade
sudo apt install mesa-vulkan-drivers mesa-vulkan-drivers:i386
additionally install “mesa-utils” and give use the output of
glxinfo | grep OpenGL
Its likely your windows install didnt shut down completely.
Yes, got error message after manual remount. Well, it BSODed. Screw it, I need one thing a time, so would continue vga drivers fun in Kubuntu.
OpenGL vendor string: X.Org
OpenGL renderer string: AMD Radeon ™ R9 380 Series (TONGA, DRM 3.27.0, 4.19.1-041901-generic, LLVM 7.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.4 - padoka PPA
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.4 - padoka PPA
OpenGL shading language version string: 4.40
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.4 - padoka PPA
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:
No second monitor.
ok well now at least when we fix your monitor you’ll be able to game too 
I was thinking about what else it might be. I’m thinking that linux may be interpreting the edid data wrong from your other monitor and using invalid parameters for the display. thats one way you can wind up with the os thinking it’s got two working displays while one is obviously not. on the display settings screen check what refresh rate options you have under advanced and try manually setting it to something you know should work.
Already tried through gui, xrandr and gui for xrandr (arandr). System tells it’s running it on [email protected], it could handle up to 78 Hz before image became blurry when I tested it before, so this settings are in spec and must always work. 60Hz does not help.
just humor me and try setting it down to 60.
Tried again while you were typing, no luck.
I noticed this repeating in journalctl when I change display settings. Maybe it can help, but not so sure.
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: Output 68 : connected = false , enabled = false
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: XRandROutput 152 update
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: m_connected: 0
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: m_crtc XRandRCrtc(0x556e46ef7f60)
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: CRTC: 146
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: MODE: 72
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: Connection: 0
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: Primary: true
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: Output 152 : connected = true , enabled = true
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: XRandROutput 68 update
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: m_connected: 1
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: m_crtc QObject(0x0)
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: CRTC: 0
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: MODE: 0
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: Connection: 1
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: Primary: false
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: Output 68 : connected = false , enabled = false
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: XRandROutput 152 update
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: m_connected: 0
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: m_crtc XRandRCrtc(0x556e46ef7f60)
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: CRTC: 146
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: MODE: 72
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: Connection: 0
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: Primary: true
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: Output 152 : connected = true , enabled = true
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: XRandROutput 152 update
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: m_connected: 0
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: m_crtc XRandRCrtc(0x556e46ef7f60)
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: CRTC: 146
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: MODE: 72
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: Connection: 0
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: Primary: true
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: Output 152 : connected = true , enabled = true
ноя 09 23:54:57 MHPCku org.kde.KScreen[1311]: kscreen.xrandr: Emitting configChanged()
I went back over your previous images and noticed something important. You said you had it hooked up to an adapter on a DVI-I port. well linux is currently using that DVI-I port as DVI-D instead of DVI-A.
I don’t know for sure how to correct that but I’m fairly certain that trying to send a digital signal over vga ain’t gonna work 
That makes sense. Thank you, would dig into it.
I am pretty sure it was DVI-I in ubuntu some time ago, and it didn’t work then.
unplug your non working monitor (from the gpu side) and see if the journalctl spam stops.
It start when I touch monitors. Tried unplugging VGA cable, journalctl exploded in this stuff (it did not fit into standard konsole buffer, lol) in a second, than stopped. Just gave up and grabbed my mate’s monitor, plugged it in via DP, my LG via HDMI, they work fine as expected. This monitor does not work with VGA either, as expected.
So probably I need to make Linux send analog signal through that port. Probably it can, but I am not sure and could not find how to do it yet.