From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from duke.felloff.net ([216.126.196.34]) by ur; Thu May 5 19:56:12 EDT 2016 Message-ID: <4f4b26804ba215e9e2491b2e126e3a0d@felloff.net> Date: Fri, 6 May 2016 01:56:04 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org Subject: Re: [9front] installing 9front on Dell Optiplex 790 In-Reply-To: <35132dd23bf81bc7416d8086a9f61774@mars.jitaku.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: mobile extensible NoSQL scripting TOR self-signing high-performance solution thats strange. the igfx driver controls very precisely what output port it will configure. it seems very unlikely to output on the external vga by accident. there are two things. if you have monitor "auto", it will get the edid information of all monitors and pick the one which matches the precise screen resolution. you can also specify a monitor name from vgadb. the monitor itself can then have a lcd=1 attribute, or a display=X attribute where X specifies the port: PortVGA = 0, /* adpa */ PortLCD = 1, /* lvds */ PortDPA = 2, PortDPB = 3, PortDPC = 4, PortDPD = 5, i use "auto" for everything because the resolution of the external vga monitor is different from the internal panel always differs so this is unique for me. aux/vga isnt responsible for setting up the mouse driver. thats done by aux/mouse. unless you have issues with the hardware cursor of course, in which case you configure it to not use the hardware cursor in vgadb. (just leave out the hwgc=igfxhwgc attribute in the ctlr section) everything is setup from /rc/bin/screenrc when you normally boot the system, todo it manually: bind -b '#i' /dev bind -b '#m' /dev aux/vga ... aux/mouse ps2 -- cinap