Bug 111931

Computer: Dell Latitude E6430 (singel graphics card model)
Dist: ArchLinux
Setup: Two external monitors attached via VGA and HDMI.

Problem:
tl;dr-version
Previous to 4.4.1-1 I could get my console to show on my external monitors. Now I can't.

Long-version:
Lets begin by starting the computer and go from there. Note that I boot into a TTY and use 'startx' from there to get my graphical environment up as I sometimes don't use X to conserve battery.

Pre-upgrade; When I booted the computer I would get my login in my laptops screen and my external monitor attaced to the VGA port. I would login and (usually) type 'startx'. This, ofc, read my .xinitrc. To this I had added the line "xrandr --output VIRTUAL1 --off --output DP3 --off --output DP2 --off --output DP1 --off --output HDMI3 --off --output HDMI2 --off --output HDMI1 --mode 1920x1080 --pos 1080x480 --rotate normal --output LVDS1 --off --output VGA1 --mode 1920x1080 --pos 0x0 --rotate left" which sets the output to my external monitors. My computer only supports 2 monitors to be active at the same time, so the laptops screen is not used.
Anyhow. After the graphical environment had started I could go to a TTY with Alt+F# or just kill X. The TTY would now display on my external monitors and the laptop would still be blank. Just like I want it to.

Post-upgrade: When I boot the computer I get my login on the laptop-screen ONLY. No output to VGA or HDMI. I login with the same steps as before. xrandr fails to setup the screens correctly on startx.  The external monitors are activated and the laptop screen goes blank, but the external monitors show the same image. No rotation or extending is done. I can re-issue the xrandr line seen above and the settings take affect.
When I now either kill X or switch to a TTY, I get nothing. Laptop monitor is blank. VGA is blank. And HDMI is blank. Meaning: Once I've started X and set up my monitors I can't use a TTY unless I tell xrandr to set my laptop-monitor as active.

I installed 4.1.17-1 (linux-lts) to double check if it really was the kernel. Sure enough, it works as before there.

Is there any other information that I can provide to help in this issue?
This is my first bug-report regarding the kernel, and I'm unsure if I filed this in the correct category. Sorry if I did.