- 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
e7440 Latitude / Dell Dock + Dual Monitors + Ubuntu 14.04 [FIXED]
19 posts / 0 new

Starter
01 Staff (not verified)
01 Staff (not verified)
Jul 10, 2014 - 12:16pm
Mouse "freeze" also happens on the standard 14.04 but I can get away with it by switching to another app using ALT-Tab, ie. it makes the mouse pointer re-appear and the mouse works again. With the modified 3.15 kernel this does not work and you either use ALT-keys for the rest of the session or you reboot :-(
Sticky keys are indeed an issue but I had it with std 14.04 and if I recall I also had it with the pre-installed 12.04. so it cannot be blamed on the new kernel.
BTW where did you get your E7440 ? I got mine in Asia and it may have some different components which could explain the different behavious with a same ubuntu kernel ?
I'm having the same trouble, only I'm running CentOS 7. It seems like I have analogous tools to compile this kernel to an RPM instead of a DEB, but... well, I'm a noob to kernel modification in general. Is it wise to use this as a CentOS kernel? Does it matter? Would it work?
Hello, I have the same freezing of the touchpad issue. I can't get around it (yet) with less than a suspend and reactivation. My usb mouse works fine always.
This is a very annoying bug. Has anyone found a solution?
Cheers
Hello,
This solution worked fine for me but with last version of xserver-xorg-video-intel: http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/pool/main/x/xserver-xorg...
Thanks!
Hi,
@z06kris did you get a resolution to booting up with lid closed?
@vicntt -- No, not yet. To be honest, haven't really had the time for it, but I'll definitely post any/all fixes on this thread when I do.
Here isHere is a version including WIFI support
http://preview.tinyurl.com/oyz2uay
Same words of caution as usual..
Hi everyone,
Finally got around to looking into the blank screen on boot/login more in-depth (i.e., CRTC error dialog, etc). While I could be absolutely wrong here, I suspect this behavior is related to this patch (https://bugzilla.kernel.org/attachment.cgi?id=25007).
Before getting too far down that road though, I decided to try a more simple test first. For those of you encountering the same issue (blank screens on boot), can you confirm whether this "band-aids" the problem on your end? This isn't supposed to be considered a "fix", rather just to help diagnose/isolate the problem.
1. Edit /etc/UPower/UPower.conf
2. Modify (or add to) last line:
IgnoreLid=false
to
IgnoreLid=true
3. Save, exit, and reboot.
After rebooting (with the lid closed), my external monitors will quickly flash the login screen, and go blank (as they did before). However now they're only blank for ~1-2 seconds, and come back (staying on) as they're supposed to.
Please let me know if any of you got the same result I did.
Thanks!
Hi there,
I ran into this issue too :
Having a laptop and a docking station and wanting to use 2 external monitors while docked (but not the laptop screen).
The previous post showing the IngoreLid=true of the Upower.conf file helped me with the startup CRTC error :)
By the way, the login screen is not showing on the external monitors but on the "first" screen, the laptop one...
Can we just disable the laptop screen if only we are docked ? (as I want to be able to connect without the docking station !)
Thanks for the tips :)