#10354 NORM F14: Xorg corruption when not started on tty1

[Zarro Boogs per Child]

#10354: Xorg corruption when not started on tty1
-------------------------------------+--------------------------------------
           Reporter:  jon.nettleton  |       Owner:  dsd          
               Type:  defect         |      Status:  new          
           Priority:  normal         |   Milestone:  F14          
          Component:  not assigned   |     Version:  not specified
         Resolution:                 |    Keywords:               
        Next_action:  never set      |    Verified:  0            
Deployment_affected:                 |   Blockedby:               
           Blocking:                 |  
-------------------------------------+--------------------------------------

Comment(by dsd):

 X has code to look for unused consoles to start on. First of all it checks
 the current vt, and if not, it checks vt1, vt2, vt3, ...

 X is now started very early - before the gettys, so the vts are generally
 free.

 There is 1 bit that I don't understand still - we boot up on vt1 in
 verbose mode, so why does X get started on tty2? Well, perhaps systemd has
 done something to occupy vt1.

 When we boot with pretty boot, vt2 is active but used by bootanim, so its
 normal for X to then move onto vt3.

 One solution would be to make bootanim more like plymouth (runs on tty1,
 somehow swallows console messages) but I suspect that might be a bit
 heavy-weight.

 The solution I'll try first is to modify olpc-dm to pass a vt number to
 the X server (you can pass e.g. vt01 as a parameter).

-- 
Ticket URL: <http://dev.laptop.org/ticket/10354#comment:8>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system