My current theory is that something in the firmware is switching the 'internal' output over to the external monitor during boot, which the OS is then expected to explicitly switch back. With that configuration, when booting with the HDMI connected, the TrueCrypt prompt would display on the external monitor and then Windows (presumably via an ASUS supplied driver) would do something to reactivate the internal monitor while completing the boot process. I previously had TrueCrypt + Windows on this machine. The external monitor then remains blank until later in the boot process (presumably whenever X starts up the dual monitor support). It all works fine if the HDMI monitor is left unplugged until after the disk decryption prompt has been displayed. 'Identify outputs' displays the eDP1 label on the internal monitor and the HDMI label on the external monitor Internal LCD screen is reactivated during the boot process (either before or after disk decryption).Ĭontent configured for display on eDP1 is visible on the internal monitor The eDP1 label appears to be in roughly the right position for a 1600x900 display anchored to the top left of the 1920x1080 external HDMI display

'Identify outputs' in KDE dual monitor settings displays both the eDP1 and HDMI labels on the HDMI monitor. Internal LCD screen (eDP1) remains deactivated even though xrandr considers two monitors to be available (eDP1 and HDMI)Ĭontent configured for display on eDP1 is not visible at all

BIOS splash screen and disk decryption prompt are displayed on external monitor Connect external monitor to HDMI port with the Zenbook powered offģ. Version-Release number of selected component (if applicable):ġ. If an external HDMI monitor is connected while booting the ASUS Zenbook UX31E, the internal LCD monitor is not enabled, preventing use in dual screen mode until the device is rebooted without the HDMI monitor connected.

Asus zenbook ux31e drivers