9front - general discussion about 9front
 help / color / mirror / Atom feed
From: kokamoto@hera.eonet.ne.jp
To: 9front@hera.eonet.ne.jp
Subject: strange behaviour of igfx and vesa
Date: Fri, 17 Jun 2016 15:48:16 +0900	[thread overview]
Message-ID: <9964dda00ad1dae2d73742d1c7878f2b@mars.jitaku.localdomain> (raw)

I'm trying to use 8086/29a2 chip on a desktop terminal.
pci -v says:
0.2.0:	vid  03.00.00 8086/29a2  10 0:fde00000 1048576 2:d000000c 268435456 4:0000ff01 16
	Intel Corporation 82G965 Integrated Graphics Controller

I added that 8086/29a2  entry to /sys/src/9/pc/vgaigfx.c and /sys/src/cmd/aux/vga/igfx.c
and /lib/vgadb.

When I set the /cfg/pxe/xxx file like monitor=s3321wA,
I got blank screen.  I've tried display=0,1,2,3,4,5, and got
the same result.

However, I changed the the file content to:
monitor=vesa, and vgasize=1024x768x8,
and bootup the terminal as usual.

After that, I dispatched the command:
term% aux/vga -m igfx -l 1680x1050x32

Then I got the normal 1680x1050x32 screen on my LCD panel!
Of course, hardware cusor is also working fine.

What's going on here?

Kenji

PS. I'm writing this mail from that terminal.



             reply	other threads:[~2016-06-17  6:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-17  6:48 kokamoto [this message]
2016-06-17 12:46 ` [9front] " cinap_lenrek
2016-06-17 23:40   ` kokamoto
2016-06-18  1:29   ` kokamoto
2016-06-18  7:45   ` kokamoto
2016-06-18 23:38   ` kokamoto
2016-06-19  5:58   ` kokamoto
2016-06-20  2:48   ` kokamoto
2016-06-20  4:14     ` kokamoto
2016-06-22  0:25   ` kokamoto
2016-06-22  7:26     ` cinap_lenrek
2016-06-23  6:43       ` kokamoto
2016-06-23 10:55         ` cinap_lenrek
2016-06-23 11:24           ` kokamoto
2016-06-25  1:50             ` kokamoto
2016-06-30  2:06               ` 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=9964dda00ad1dae2d73742d1c7878f2b@mars.jitaku.localdomain \
    --to=kokamoto@hera.eonet.ne.jp \
    --cc=9front@hera.eonet.ne.jp \
    /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).