Comment # 7 on bug 1206316 from Felix Miata

(In reply to Takashi Iwai from comment #6)
> The manual tweak like yours might have some side effect, so likely a WONTFIX
> issue.

If bug 1188954 would go away I wouldn't need the tweak. 

Why when they do start X is it happening on /dev/dri/card1 instead of
/dev/dri/card0? I don't have to do this only on RKL, but also both my KBLs at
least. I've lost track, but I think this is the general rule here no matter the
GPUor chipset. e.g., KBL ab250:
# systemd-analyze
Startup finished in 14.862s (firmware) + 2.698s (loader) + 2.024s (kernel) +
2.606s (initrd) + 1min 30.834s (userspace) = 1min 53.027s
graphical.target reached after 1min 30.802s in userspace.
# systemd-analyze critical-chain
...
graphical.target @1min 30.802s
������������������display-manager.service @1min 30.703s +98ms
  ������������������systemd-logind.service @1.696s +54ms
    ������������������basic.target @1.677s
      ������������������sockets.target @1.676s
        ������������������telnet.socket @1.675s
          ������������������sysinit.target @1.635s
            ������������������systemd-timesyncd.service @1.595s +38ms
              ������������������systemd-tmpfiles-setup.service @1.573s +18ms
                ������������������local-fs.target @1.571s
                  ������������������run-user-0.mount @43.172s
                    ������������������local-fs-pre.target @606ms
                      ������������������systemd-tmpfiles-setup-dev.service @561ms +43ms
                        ������������������kmod-static-nodes.service @497ms +38ms
                          ������������������systemd-journald.socket
                            ������������������system.slice
                              ������������������-.slice
#
Little different from comment #1 KBL host gb250.