You are not logged in.
I have a Dell Precision 5510 and a Dell 4K monitor. I'm using the USB-c port to drive the monitor. The resolution on the laptop is 1920x1080 and 3840x2160 on the External monitor. The distro is AntergOS.
Anyway, on to the bug: Given the set up above, the displays work fine. I can move a window to the external monitor and it will display normally. However, if the cursor moves onto the external monitor, the monitor is shut off. If I move it back to the laptop screen, the monitor turns back on. When I say "shuts off", I actually mean that the signal is turned off and the monitor goes into standby mode.
$ uname -a
Linux mark-dell 4.5.1-1-ARCH #1 SMP PREEMPT Thu Apr 14 19:19:32 CEST 2016 x86_64 GNU/Linux
dmesg logs: http://pastebin.com/UEiNfxN3
Xorg logs: http://pastebin.com/i6dYdCxw
lightdm logs: http://pastebin.com/NvMyARYA
I don't see anything worth noting in the logs (other than the intel driver WARN). I'm unsure how to triage this bug. Any help is appreciate it.
Last edited by Semaphor (2016-04-26 15:19:23)
Offline
Well, I'm running straight up Arch and have a similar issue only backward. My primary monitor is the laptop screen (3840x2160) and my external (1920x1080). When I boot into Gnome the laptop screen goes blank until I move onto it. After a few minutes if I move the mouse to it it blanks out. Also, suspend fails now. I had to roll back my install to 4/11/2016 to get any use out of my system.
Dell Inspiron 7559
i7-6700HQ
16GB Ram
Intel 530/Nvidia GTX 960M 4GB
Offline
I had to roll back my install to 4/11/2016 to get any use out of my system.
Did you isolate which driver/module was causing the issue? My laptop does have a secondary Nvidia card, but it's not used since I don't run games.
Offline
Having similar issue on my Dell XPS 9550 (late 2015). It started with 4.5 kernel.
I'm using only i915, I've blacklisted nouveau and I'm using acpi_call to turn off the Nvidia card.
When the system boots up with connected external display (FHD Asus monitor using HDMI port) GDM doesn't even show up on internal display (it stays black).
If I log in to gnome shell the internal display turns on but it constantly flickers (or turns black) if I move mouse cursor on it.
The only thing that fixes this issue for me is downgrading to 4.4.5 kernel. I thought that the issue was in i915 module options (4.5 uses some different default values), so I changed the different values to use the same ones as 4.4 kernel uses, but this didn't help, so I guess that this is not the culprit.
The interesting thing is that I get the same issues when booting live Ubuntu 16.04 and Ubuntu uses 4.4 kernel.
I'm without ideas
Offline
Well, I'm running straight up Arch and have a similar issue only backward. My primary monitor is the laptop screen (3840x2160) and my external (1920x1080). When I boot into Gnome the laptop screen goes blank until I move onto it. After a few minutes if I move the mouse to it it blanks out. Also, suspend fails now. I had to roll back my install to 4/11/2016 to get any use out of my system.
Dell Inspiron 7559
i7-6700HQ
16GB Ram
Intel 530/Nvidia GTX 960M 4GB
I updated to 4/14/2016 (in steps day by day from my last good day, 4/11/2016) and these are the packages that changed...
4/12/16 (Internal Display and suspend still WORK)
baobab-3.20.1-1 farstream-0.2.8-1 fontconfig-2.11.95-1 gnome-desktop-1:3.20.1-1 gvfs-1.28.1-1
gvfs-afc-1.28.1-1 gvfs-goa-1.28.1-1 gvfs-google-1.28.1-1 gvfs-gphoto2-1.28.1-1 gvfs-mtp-1.28.1-1
gvfs-nfs-1.28.1-1 gvfs-smb-1.28.1-1 lib32-libglvnd-0.1.0.20160329-3 lib32-mpg123-1.23.3-1
lib32-sqlite-3.12.1-1 libdmapsharing-2.9.34-1 libreoffice-fresh-5.1.2-1 python-urllib3-1.15.1-1
sqlite-3.12.1-1 xf86-video-intel-1:2.99.917+622+gde44aaa-1
4/13/16 (Internal Display and suspend still WORK)
at-spi2-atk-2.20.1-1 at-spi2-core-2.20.1-1 cheese-3.20.1-1 dhcpcd-6.10.2-1 eog-3.20.1-1 epiphany-3.20.1-1
evolution-3.20.1-1 evolution-data-server-3.20.1-1 file-roller-3.20.1-1 firefox-45.0.2-1
geocode-glib-3.20.1-1 gnome-devel-docs-3.20.1-1 gnome-disk-utility-3.20.1-1 gnome-klotski-3.20.1-1
gnome-logs-3.20.1-1 gnome-maps-3.20.1-1 gnome-nibbles-3.20.1-1 gnome-online-accounts-3.20.1-1
gnome-robots-3.20.1-1 gnome-session-3.20.1-1 gnome-shell-3.20.0-3 gnome-system-monitor-3.20.1-1
gnome-terminal-3.20.1-1 gnome-user-docs-3.20.1-1 gspell-1.0.1-1 gthumb-3.4.3-1
gtk-update-icon-cache-3.20.3-1 gtk3-3.20.3-1 lib32-glib2-2.48.0-1 libgames-support-1.0.1-1
libinput-1.2.3-1 libxml2-2.9.3+14+gd5bd2a9-1 pango-1.40.1-1 python-atspi-2.20.1-1 rygel-0.30.1-1
vinagre-3.20.1-1 vino-3.20.1-1 vte-common-0.44.1-1 vte3-0.44.1-1 yelp-3.20.1-1 yelp-xsl-3.20.1-1
4/14/16 (Internal Display and suspend STOP WORKING)
android-tools-6.0.1_r30-1 gnome-control-center-3.20.1-1 gnome-settings-daemon-3.20.1-1 gnome-shell-3.20.1-1
lib32-fontconfig-2.11.95-1 lib32-harfbuzz-1.2.6-1 lib32-libglvnd-0.1.0.20160411-1
lib32-nvidia-utils-364.16-1 libgit2-1:0.24.1-1 libglvnd-0.1.0.20160411-1 linux-4.5-1 linux-headers-4.5-1
mutter-3.20.1-1 nvidia-364.16-2 nvidia-utils-364.16-2 ocl-icd-2.2.9-1 totem-3.20.1-1
Having similar issue on my Dell XPS 9550 (late 2015). It started with 4.5 kernel.
I'm using only i915, I've blacklisted nouveau and I'm using acpi_call to turn off the Nvidia card.
When the system boots up with connected external display (FHD Asus monitor using HDMI port) GDM doesn't even show up on internal display (it stays black).
If I log in to gnome shell the internal display turns on but it constantly flickers (or turns black) if I move mouse cursor on it.
The only thing that fixes this issue for me is downgrading to 4.4.5 kernel. I thought that the issue was in i915 module options (4.5 uses some different default values), so I changed the different values to use the same ones as 4.4 kernel uses, but this didn't help, so I guess that this is not the culprit.
The interesting thing is that I get the same issues when booting live Ubuntu 16.04 and Ubuntu uses 4.4 kernel.
I'm without ideas
It does seem to be the linux kernel causing the issue though.... And still nothing in any log files to help...
Offline
It does seem to be the linux kernel causing the issue though.... And still nothing in any log files to help...
I wouldn't bet that the kernel is the only issue here. That's why I mentioned that I'm having these issues on Ubuntu 16.04 as well and it uses kernel 4.4. I don't have these issues on Arch with kernel version 4.4. This is why I think the configuration of some kind is the reason for this (maybe kernel 4.5 and up use some different default configuration values and Ubuntu 16.04 uses the same configuration just on kernel 4.4)
Offline
workdowg wrote:It does seem to be the linux kernel causing the issue though.... And still nothing in any log files to help...
I wouldn't bet that the kernel is the only issue here. That's why I mentioned that I'm having these issues on Ubuntu 16.04 as well and it uses kernel 4.4. I don't have these issues on Arch with kernel version 4.4. This is why I think the configuration of some kind is the reason for this (maybe kernel 4.5 and up use some different default configuration values and Ubuntu 16.04 uses the same configuration just on kernel 4.4)
Yeah, I didn't mean to ssay it was.... But one of the updated files (and an existing one?) has to be the culprit. I'm going to try more later.
There is a new Intel driver that hit extra today and when I tried to update my whole system to today, I still got the issues. I'll have to try ignoring the Linux and Nvidia (only using for Bumblebee anyway) updates and see what that brings...
Offline
So, by upgrading everything but the following... I have a functional system.
(Without ignoring the linux-headers, Virtualbox gets borked)
pacman -Syyuu --ignore nvidia,linux,nvidia-utils,linux-headers
I'll try the live 'Buntu (as Caspian did) also for some confirmation...
Edit: 'Buntu won't even boot for me...
Last edited by workdowg (2016-05-02 13:07:07)
Offline
So, by upgrading everything but the following... I have a functional system.
(Without ignoring the linux-headers, Virtualbox gets borked)pacman -Syyuu --ignore nvidia,linux,nvidia-utils,linux-headers
I'll try the live 'Buntu (as Caspian did) also for some confirmation...
Edit: 'Buntu won't even boot for me...
I currently don't even use the linux package for kernel. I switched to linux-lts (it's on 4.4.8 currently). This way I don't have to ignore the packages from upgrading.
Offline
kernel 4.5.2-1 (it got flagged out of date directly after moving into core...) did not work either for me... Still have to go back to 4.4.5-1 to get it working... linux-lts fails also.
I'm ok for now but without being able to update Nvidia because of Linux, I am unable to use Bumblebee... May have try the the nouveau driver for that.
Last edited by workdowg (2016-05-08 16:38:24)
Offline