From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] installing 9front on Dell Optiplex 790
Date: Fri, 6 May 2016 01:56:04 +0200 [thread overview]
Message-ID: <4f4b26804ba215e9e2491b2e126e3a0d@felloff.net> (raw)
In-Reply-To: <35132dd23bf81bc7416d8086a9f61774@mars.jitaku.localdomain>
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
next prev parent reply other threads:[~2016-05-05 23:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 21:49 James
2016-04-30 21:57 ` [9front] " Nicolas Owens
2016-04-30 22:15 ` James
2016-04-30 22:47 ` cinap_lenrek
2016-04-30 22:39 ` cinap_lenrek
2016-05-01 0:43 ` James
2016-05-01 4:05 ` cinap_lenrek
2016-05-01 4:41 ` Matthew Veety
2016-05-01 4:51 ` sl
2016-05-01 7:19 ` Matthew Veety
2016-05-01 20:02 ` sl
2016-05-05 7:47 ` kokamoto
2016-05-05 10:53 ` kokamoto
2016-05-05 23:33 ` kokamoto
2016-05-05 23:56 ` cinap_lenrek [this message]
2016-05-06 0:33 ` kokamoto
2016-05-06 1:06 ` kokamoto
2016-05-06 5:29 ` kokamoto
2016-05-06 5:33 ` cinap_lenrek
2016-05-06 5:34 ` kokamoto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f4b26804ba215e9e2491b2e126e3a0d@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).