- About
- Downloads
- Blogs and news
- Community
- Support
- Documentation
- Hardware Specification - PRMs
- 2020-2021 INTEL(R) PROCESSORS BASED ON THE "TIGER LAKE" PLATFORM
- 2020 Intel(r) Processors with Hybrid Technology based on the Lakefield platform
- 2020 Discrete GPU formerly named "DG1"
- 2019 Intel(r) processors based on Ice Lake platform
- 2018-2019 Intel(r) processors based on Whiskey Lake platform
- 2017-2019 Intel(r) processors based on Amber Lake platform
- 2017-2019 Intel(r) processors based on Coffee Lake platform
- 2019-2020 Intel(r) processors based on Comet Lake platform
- 2016 Intel(r) processors based Kaby Lake platform
- 2016 Intel(R) Processors Based on Apollo Lake Platform (Broxton Graphics)
- 2015-2016 Intel Processors based on Skylake Platform
- 2014 Intel Processors based on the Bay Trail Platform
- 2014-2015 Intel Processors based on Cherry Trail / Braswell Platform
- 2014-2015 Intel Processors based on Broadwell Platform
- 2013 Intel Core Processor Family
- 2012 Intel Core Processor Family
- Code Documentation
- Source Code
- Build Guide
- 2011 Intel Core Processor Family
- 2010 Intel Core Processor Family
- Bugs and Debugging
- Intel® G45 Express Chipset
- Intel® 965 Express Chipset Family and Intel® G35 Express Chipset Graphics Controller PRM
- Intel® Integrated Graphics Device - OpRegion Specification
- Archived documentation
intel driver not loading | Ubuntu 14/15/16 on HP ProOne 400 G2
12 posts / 0 new

Starter
01 Staff (not verified)
01 Staff (not verified)
Apr 28, 2016 - 08:14am
Hello
I have the same problem - Hp Proone 400 G2 and flashing red, green, blue screen.
I have tried debian (knoppix) with kernels 4.4 and 4.7.3 and still no success.
With nomodeset kernel parameter I can see desktop but only with resolution 1024x768.
As I can tell, screen starts flashing in a moment when KMS tries to switch resolution.
Is it a problem with i915 driver or something else?
Don't know, I'm afraid - it _could_ be an i915 problem, or it oculd be to do with misdetection of the built in display (this would be my guess, but it's only a guess) - I've seen other cases where HDMI displays aren't detected correctly, sometimes because of the particular cable (!) in use - although obviously with a built in display the cable probably isn't something you can switch,