UHD (4K HDMI)

Hi Jim,

HDMI doesn't have Horizontal and Vertical syncs like Analogue signals.  The port must be HDMI 1.4 or above to drive 4k screen as this requires a fast data rate.  It sounds like you are on the edge of the digital cliff so try a different HDMI cable ideally as short a cable as you can.

Hope this helps,

David

Hi Jim,

The eye diagram will be virtually closed and the odd error will mean pixels may be incorrect or the addressing of the pixels will be incorrect - hence the skewed bits of image.

As I said, try a different cable - shorter the better as a test.

David

Hey Jim - does it work at lower resolutions? I'd also try lowering the refresh rate just to see if you can get it working/stable.

And then I agree w David, try getting a high quality HDMI 1.4 or 2.0 cable. 

It "should" work ;)  And nice TV btw

Hi Jim,

Yep, it's a Series III 88inch Land Rover 30 years old this year.

David

Oh nice ... I've been eyeing that Yoga 2.  It'll either be that or the qhd HP Envy 14 - but Lenovo just seems to be getting it right these days.

I mentioned lowering the res just as a test case - if it works at 1080p it might just the cable.  If not then drivers, etc - but I'm guessing you don't need advice on troubleshooting ....  ;)

Cables in my experience have always been funny. I've had cables that work great with some hardware and then not all with others - at the same resolution.  But I've never seen the issue you're describing - it's usually either all of nothing, and once I had long cable causing random "snow".

To the best of my knowledge a 2.0 cable shouldn't be better than 1.4 cable for handling bandwidth.  Any high speed cable "should" work, And I don't think the certification branding means anything.

If another cable doesn't do it I'd be looking to put the blame on the Ultrabook itself - I'm assuming the Intel dev platforms just don't go through the same level of testing as retail machines (I seem to recall seeing some hand soldered leads in my Ivy Bridge ref platform).  But of course I'm only guessing.

Hey Jim,

I've been watching this thread for a couple of weeks because I also have the Seiki 39" 4k and Yoga Pro 2 combination for my development workstationo. My HP desktop seems to drive the monitor without any issues (it has the same Haswell/Intel HD Graphics 4400 combo with regular HDMI) but I get the "No Support" message when I attempt to get 3840x2160/4k resolution using the Yoga's Micro-HDMI.

Please let me know if you've been able to resolve this with the micro-HDMI cable upgrade,

Thanks

@Jim

Sorry for off-topic question.

I just received Lenovo Yoga 2 ultrabook and seems that I have a problem with the Internet browsing.Failed DNS resolution can be blamed for that.

Now I wanted to ask you did you have the same kind of problems with your ultrabook?

Thanks in advance.

@Jim

Please disregard my question because I have solved the issue.

Hi Iliyapolak,

I always try to include the fix in a post as although the fix might be trivial I believe that if someone felt the need to post a question it implies their problem was causing them a big enough of an issue to make them want to post.  If it was causing them an issue then a similar problem might cause other less savvy people even more of a problem.

Aside from that I was curious.  Was it your ISP or the network adaptor settings for the DNS?  If I get DNS issues one of the first things I do is to use a Google DNS - 8.8.8.8 and this usually works so I can then figure out where the problem actually lies.

David  

Hi 

Sorry for late answer.

Yes I did what you mentioned in your post,but really  nothing was helpful.It was strange because my main laptop and Asus tablet were connected to the same network and were able to access Internet without any problem.

I installed wireshark on the Yoga and started to monitor  websites connections attempts.DNS servers IP's were provided by the ISP and unfortunately very quickly I saw those pesky messages talking about the DNS failed query.At this moment I started to suspect McAffee AV and firewall to be a main culprit of behind the failed DNS resolution.I theorized that probably filter driver installed by McAffee firewall  which is probably sitting above 802.11 driver and below TCP/IP driver and is blocking network traffic.The second suspect was winsock and probably some kind of hooks installed by AV.One of very popular target of hooking could be GetHostByName function.I thought about trying to check the image with the windbg for consistency,but decided to try a very simple workaround.My external usb wi-fi card Alpha was connected and everything started to work fine.

I would disable firewall & AV and retry.  Is the McAfee a trial version?

If the McAfee is doing it by design (and I don't know why it should) then defeating it by adding an additional Network Adaptor seems a flaw in the AV/Firewall policy.   

Personally I dislike preinstalled trial versions.

David 

I did  exactly what you advised me and still was not able to browse the websites.I even uninstalled trial version of McAffee and still DNS resolution was not working.So probably it was not AV or firewall.

I suspect that probably pre- installed version of Win 8.1 could be blamed for DNS issues.

My next thought would be to go to the network adaptors page and look at what is there.  If you have Hyper-V Virtual Ethernet adaptors it could be they are not configured correctly or browsing is routed via them.

I presume it is purely DNS so if you browse to 173.194.34.137 you should get to a well known search engine.

Then I would go to the Yoga WiFi adaptor, disable it and then enable it.

Maybe that would help.

David 

I do not have enabled Hyper-V.I monitored network traffic via netmon and registered interfaces are built-in Intel wlan card and Alpha wlan card.

Regarding Yoga built-in card I disabled and enabled it and it was not helpful so far.Now I am considering to reinstall the driver maybe this will solve the issue.

With just the internal WiFi did you try to browse 173.194.34.137?

Do you have any proxy setup on that I/F?

Does ping google.com from command prompt work?

How about ping 173.194.34.137?

What does ipconfig /all give you?

Reinstalling driver might well clear the issue but it sounds like a configuration issue.  Did Lenovo have any comment?

David 

>>>With just the internal WiFi did you try to browse 173.194.34.137?>>>

It was not successful , DNS resolution failed.

>>>Do you have any proxy setup on that I/F?>>>

No I do not have any proxy.Double checked that.

>>>Does ping google.com from command prompt work?

How about ping 173.194.34.137?>>>

No everything is blocked.There is no response from the remote server.I tried this when Mc Affee was uninstalled.

>>>What does ipconfig /all give you?>>>

It gives properly configured network with DHCP assigned client IP address.

I started to run out of ideas.I do not want to dig deep into networking stack internals.My knowledge is scarce and serious troubleshooting of NIDS driver is supported only in checked build Windows.

Now I am using external card with good results.

if you cannot use a browser to go to 173.194.34.137 or ping 173.194.34.137 then it is not DNS error.  It appears all traffic is failing to get through.  This sounds like a firewall, adaptor configuration or driver issue.

It is worth checking your gateway address is correct.

From command prompt try tracert 173.194.34.137 as this may give you a clue as to where it is failing.

David

Also can you successfully ping/browse to anything on your local network?

David 

>>>It is worth checking your gateway address is correct.

From command prompt try tracert 173.194.34.137 as this may give you a clue as to where it is failing>>>

Actually pinging default gateway also fails so this is issue is probably related to networking stack drivers.I suspect *IRP's beign not received by underlying wlan driver, but it is hard to troubleshoot it properly.I am thinking about the generating full kernel dump with NotMyFault tool and trying to find outstanding IRP's

*IRP = I/O Request Packet.

>>>Also can you successfully ping/browse to anything on your local network?>>>

Unfortunately no.

So the DHCP server is giving the internal wlan adaptor the address, subnet and gateway address and you have double checked they are correct.

When you browse do you get an 'identify problem' or 'troubleshooter' button and if so what happened when you clicked it?

David 

>>>So the DHCP server is giving the internal wlan adaptor the address, subnet and gateway address and you have double checked they are correct>>>

Yes of course.

Also PHY (physical layer) is working fine.The problem could be related to the higher level protocols(TCP/IP stack).

>>>When you browse do you get an 'identify problem' or 'troubleshooter' button and if so what happened when you clicked it>>

I clicked automatic troubleshooting button, but without the any help.

I presume you have raised the issue with Lenovo.

Have you tried a completely different WiFi network?

Just trying to think what else could cause the issues you have reported.

David

Unfortunately all other Wi-Fi networks in the range are protected.Today I plan to reinstall the driver and hope that this will solve the problem.

I still did not contact Lenovo.

Unfortunately driver reinstallation did not help.I will force machine into BSOD and try to debug NDIS.