Windows 7 installation help for Intel Skylake and Kaby Lake laptops

So far i have not seen any serious cracker who would be interested to mod a driver for Windows 7. Obviously they use Windows 10 or other, so why would they mod? It is also possible a few did for him/herself they just not publishing for public...

So by now only for Kaby Lake exist modded driver. It is easy to mod, the latest by me is the 21.20.16.4821.

 

The following is information from the 1st page of an article at Phoronix, https://www.phoronix.com/scan.php?page=article&item=coffee-uhd-graphics&num=1 a site specializing in Linux with an emphasis on hardware including graphics. It appears that linux users faced similar issues relating to Coffee Lake and graphics as do users of Win 7 & 8. The author outlines methods used to overcome limitations of the Intel Linux drivers. Hopefully this can help someone apply a similar fix for Windows. I am not a Linux technical person; I just ran across this looking for info and thought I would share it. I was disappointed to see this thread start to stagnate.

Intel UHD Graphics 630 "Coffee Lake" On Linux

Written by Michael Larabel in Graphics Cards on 5 October 2017. Page 1 of 4. 22 Comments

This morning I delivered the initial Linux processor benchmarks of the Core i7 8700K and Core i5 8400 for the just-launched "Coffee Lake" desktop processors. With these Intel "Gen 8" processors, the integrated "HD Graphics" from Kabylake have been rebranded to "UHD Graphics". While there wasn't any real changes architecturally to the graphics hardware, right now the Linux support isn't quite out-of-the-box.

When first powering on the i5-8400 and i7-8700K configurations, I was surprised to see the Intel DRM driver not working... This was connected to a 4K display and the mode-setting to it didn't happen with being stuck on the efifb driver. Of course, LLVMpipe was at play to lead to a sluggish experience...

At first I didn't realize what was going on since the Coffee Lake PCI IDs are present in all of the components of the Intel Linux graphics driver stack, I was using Ubuntu 17.10 with its stock Linux 4.13 that is quite new, and these Coffee Lake graphics that are essentially rebranded Gen 9 GT2 graphics hardware from Kabylake were not working. When grep'ing dmesg for i915 (Intel's DRM driver name), there were just some audio references and a line about alpha support. Initially off the top of my head I figured it was some new tunable having something to do with alpha compositing or the like given all the new display work happening within the Intel space.

Well, after then searching the contents of dmesg after finding the time today, I realize the i915.alpha_support option is actually for alpha/preliminary hardware support... Previously this was the "i915.preliminary_hw_support=1" switch for enabling early hardware support, but seems to have quietly been renamed to just "alpha". And if you are grep'ing dmesg looking for the i915 hints of what's going wrong, the actual line mentioning it's to do with alpha hardware support doesn't have any references. So just a silly little thing to be aware of if you plan on being an early Coffee Lake customer.

When booting the Ubuntu 17.10 stock kernel with i915.alpha_support=1, 4K was working, OpenGL acceleration present, and Vulkan also working... I have yet to run into any Coffeelake graphics issues with the Core i5 8400 or Core i7 8700K yet. So I'm quite surprised Intel developers are still hiding this Coffeelake support behind the "alpha_support" flag consider these CPUs are now shipping, the Linux 4.13 stable still has it marked as stable, Linux 4.14 Git still requires the alpha flag for Coffee Lake, and even the current DRM-Next code still requires this be set. It's quite surprising especially with Coffeelake still being the Gen 9 / Kabylake-era graphics that have been well supported on Linux for effectively many months. I haven't seen any public references why it's this way or any responses from the upstream Intel Linux developers, but presumably just an oversight on their part.

I have spent most of my UHD Graphics 630 testing so far with the Core i7 8700K and paired with the Ubuntu 17.10 base I have tested its stock kernel as well as the vanilla/upstream Linux 4.13.0, Linux 4.14 Git, and DRM-Next kernels. Additionally, both with the Mesa 17.2 stable Vulkan/OpenGL driver stack as shipped by Ubuntu 17.10 and as well with Mesa 17.3-dev Git via the Padoka PPA as of earlier today.

Included in this article are a few different reference benchmarks of the Core i7 8700K graphics compared to other Intel integrated graphics hardware and other Linux graphics tests. Further Coffee Lake tests are being worked on for publishing in the coming days and weeks.

-turbo111

 

Hi,
I'm having this exact same problem after downgrading my Asus UX330UA laptop from Win 10 x64 to Win 7 x64. The touchpad does not work no matter how many drivers I've tried. It appears that the touchpad uses the I2C protocol rather than the Legacy PS/2 protocol. I was even able to get the touchpad (ACPI/ELAN1300) showing up under "Device Unknown" only after installing the Intel Serial IO Driver.

Any guidance is much appreciated. I have tried many forums only to find out that the Asus touchpad does not work in Win 7 x64 for Kaby Lake processors.

 

julian,

Have you tried the following:

1. Make sure the Asus Touchpad is enabled in UEFI? The same goes for the Serial port.

2. Reverse your USB Legacy UEFI setting ( on>off or off>on)?

3. Turn on or off UEFI?

I'm sure you have adjusted some of the above but it is worth double checking the settings and trying different configurations.

Since you have tried all or many drivers on the Asus product page, have you tried the ones listed at the MS Windows Update Catalog (WUC) for the device?
Assuming that ELAN1300 is the Hardware ID for it, WUC has 33 drivers for it:

http://www.catalog.update.microsoft.com/Search.aspx?q=elan1300

Most of the drivers are for Win10 but don't assume that they will not work for Win7. MS is purposely making things difficult for Win7 users and have convinced most hardware makers to do the same. It is interesting that there are a few drivers listed for XP, but none for Vista or Win7!

I would suggest sorting the drivers by Date at the WUC (click on the "Last Updated" column to sort) and try the oldest ones (Including XP drivers) first. If the driver does not work, maybe try toggling UEFI and/or USB Legacy UEFI on or off before going to the next driver. Keep a list of changes if you do toggle the settings.

Not sure what else you can try. Good luck.

turbo111

 

Reading the thread so far, It seems no one has got good working windows 7 drivers for 8th gen intel cpu graphics drivers?

I decided to give it a go for my UHD 620. I got drivers to install on 15.45.23.4860 by inf hacks. The display works, but trying to play video files on either windows media player or MPC-HC crashes both players (MPC-HC crashes with a memory access violation). Trying to run WEI doesn't work either. It gets stuck on windows media section. As far as I can tell, non video activities are okish.

I then tried inf hacks on later native drivers. They would install, but once rebooted, device manager would show the device as not active, some error.

Has anyone been more successful in getting it working a bit better? I would like to at least get video playback, but it seems my skills fall a bit short.

 

After installing the Intel Serial IO Drivers available for Lenovo, I was able to get my Asus Synaptics touchpad driver recognized, but then ran into an another trouble. The device recognizes as Synaptics I2C Miniport (Device Type: Human Interface Device; Device Location: on Intel(R) Serial IO I2C Host Controller - 9D61), but the device gives an error as "This device cannot find enough free resources that it can use. (Code 12)". If I tried disabling the Intel Serial IO I2C Host Controller - 9D61 device which was separately available under System Devices, then the Synaptics I2C Miniport won't show up at all. Any thoughts on how to fix this?

 

The Serial IO I2C Host Controller might be needed to get the touchpad working since it was key to getting the touchpad recognized, so that would be the last thing I would disable. It sounds like your bios might not be set to let Win7 manage hardware resources. In my experience, IRQ, DMA and memory conflicts seem pretty rare ever since the release of Vista or 7.

If you get the resource conflict fixed, you might have a working touchpad pretty quickly. Just guessing.

 

Oculus Drops Support for Windows 7 & 8.1
“Oculus said it decided to drop Windows 7 and 8.1 support because Microsoft doesn’t support those operating systems anymore.”

 

What is that Oculus?

But I do not understand, if Coffe Lake driver exist or under construction for Linux, why no driver for Windows 7? It is much more popular OS and more wanted than Linux.
Anyway, im happy with my current rig, but once the new Nvidia GPUs are out in laptops, i will want to change the machine.

 

It's a political/commercial decision by Microsoft. Seems Intel/AMD/others are towing the MS line. Sad I know.