![]() |
Fatal1ty Z170 Gaming-ITX/ac No display after sleep |
Post Reply ![]() |
Page <12 |
Author | |
Xaltar ![]() Moderator Group ![]() ![]() Joined: 16 May 2015 Location: Europe Status: Offline Points: 27113 |
![]() ![]() ![]() ![]() ![]() |
The integrated graphics on Skylake CPUs is significantly changed over previous generations. Intel have been stepping up the iGPU portion of their CPUs for some time now and I am not surprised there are issues popping up. Skylake has been out for a while now but it has been plagued by issues from the start. That isn't uncommon when intel releases a new socket, it will take a little more time before the platform is mature and relatively problem free. On my own Skylake system I encountered a number of issues all of which were resolved for me by a microcode update (which is provided alongside a BIOS update and comes directly from intel). The fact that a microcode update was necessary to fix the problems I was having means that the original CPU microcode was the fail point. The iGPU, as Parsec noted has received numerous driver updates which can only be due to issues and bugs needing correction. I can't help but feel that Skylake was rushed to market prematurely.
Despite all the problems however, Skylake is a significant step forward over previous generations and all these issues will most certainly be corrected both by intel and motherboard manufacturers soon enough. Unfortunately manufacturers can't really fix much until intel provides a proper fix, the most that can be done without a fix from intel is a workaround or hack in the BIOS that bypasses a function or disables it. Intel does not share the inner workings of their products, they provide standards that all manufacturers must adhere to in order to support their products. If you google search your problem (sleep issues on Skylake) you will see it is not restricted to any one manufacturer. Manufacturers will often use common issues like this as a selling point for their products, by using a hack/workaround in their BIOS it creates the illusion that their product/s are not effected by the issue until you look closer and note that a feature is missing or not functioning correctly. I would imagine issues like yours are being worked on, the problem seems to be that a fix for one issue breaks another, as you noted the issue was improved by changing BIOS versions. It may be of use to post your issues on intel's forums aswell. Also worth noting is that a motherboard is comprised of more than just the chipset and socket, there are numerous other componets/controllers that provide functionality. Many of these are 3rd party and have firmware of their own which needs to be provided by the respective 3rd parties. So a signal converter that provides output to the display connectors may play nice with Haswell but require an update to work properly with Skylake. In a case like this either the manufacturer of the converter can provide an update or intel can patch their microcode to make the 2 components play nice together. The relationships between components on a modern motherboard are complex and intricately connected.
Edited by Xaltar - 14 Apr 2016 at 2:56pm |
|
![]() |
|
![]() |
|
dkeone ![]() Newbie ![]() Joined: 10 Apr 2016 Status: Offline Points: 14 |
![]() ![]() ![]() ![]() ![]() |
Interesting read, come to think of it i have been having issues when displaying the AsRock bios and i figured it was an bios issue but now i think it might actually be related to skylake and the 530 gfx.
Usually when i open the bios on my Asrock z170 ITX the bios looks normal, red and similar design as the motherboard has but sometimes (maybe 3 out of 10 times) the bios looks blue, and strange artifacs like lines and weirdly displayed colors that look somewhat like 3d looks if you don't have 3d glasses on you. I will be looking to update my CPU "microcode" on my i5-6500 skylake cpu. |
|
![]() |
|
dkeone ![]() Newbie ![]() Joined: 10 Apr 2016 Status: Offline Points: 14 |
![]() ![]() ![]() ![]() ![]() |
Just wanted to update that all of my issues have been solved when i updated to BIOS 2.10 and the latest intel GFX driver released earlier this month, thanks for your hard work!
Things that work now that didn't before: TV turns on 100% after sleep, even after sleeping for 24 hours. TV gets signal even if the HTPC booted while TV was not on. Running windows 10. |
|
![]() |
|
Xaltar ![]() Moderator Group ![]() ![]() Joined: 16 May 2015 Location: Europe Status: Offline Points: 27113 |
![]() ![]() ![]() ![]() ![]() |
Thanks for the update
![]() |
|
![]() |
|
![]() |
|
nullredvector ![]() Newbie ![]() Joined: 10 Dec 2016 Status: Offline Points: 2 |
![]() ![]() ![]() ![]() ![]() |
Is everything still working?
I'm having the same 2/3 problems you were having. Im using the latest intel drivers (tried, 4542 and beta 4552) and latest BIOS (7.10). I see BIOS 2.30 has "modified S3 behavior" under release notes. I wonder if I should try that version. I'd assume, that 7.10 has those fixes as well, maybe they broke again? I'm using a Samsung KU6300 (UN40KU6300). Basically the only thing that brings the 4k@60hz signal back is hooking up to the HDMI 1.4, reinstalling the drivers and reconnecting to the HDMI 2.0 port.
Edited by nullredvector - 10 Dec 2016 at 1:40am |
|
![]() |
|
hiluke ![]() Newbie ![]() Joined: 01 Mar 2016 Location: Sydney Status: Offline Points: 28 |
![]() ![]() ![]() ![]() ![]() |
I have just upgraded UEFI to 7.10 (from 1.80) and HDMI firmware to 1.48 (from 1.36) to solve some audio issues I had with HDMI2 4K 60Hz.
However now I have noticed a few times in the last few days that the screen fails to wake after leaving the computer for a while. I have my PC set to never sleep, however if I leave it for an extended period of time, turn the TV on and try to move the mouse to wake the screen, I just get no signal. I can still remote desktop to the PC fine, just no output on the screen. I've also noticed a few times when my PC does wake the monitor that my desktop icons have been re-shuffled (like it's had to adapt to a smaller resolution). I have not noticed this with HDMI1 at all. Is there a recommended UEFI version to revert to in order to fix this problem?
|
|
![]() |
Post Reply ![]() |
Page <12 |
Tweet
|
Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |