9front - general discussion about 9front
 help / color / mirror / Atom feed
From: qwx@sciops.net
To: 9front@9front.org
Subject: [9front] igfx on haswell
Date: Wed, 10 Nov 2021 16:03:05 +0100	[thread overview]
Message-ID: <7E90DAD1DDA3E727F15D70ACD67F1717@wopr.sciops.net> (raw)

Hello,

I recently acquired an x240 and upgraded it with some
x250 parts, and I noticed that igfx now magically works
on it.  Previous reports suggested that the only
haswell machines on which igfx worked were the two I
had worked with in the past.  Everything was configured
correctly according to both the spec and the values of
the card's registers, but screens remained blank, and
short of blind guessing games and trial and error, I
couldn't do much debugging without the hardware at hand.
Since broadwell is not very different from haswell, it's
possible that it works there as well without modification.

It would be great if anyone with haswell (*40 thinkpads)
or broadwell (*50 thinkpads) could try to test if it
works for them as well.  eDP (internal display), DP
and HDMI/DVI could/should work, as they do for me.  Note
that haswell VGA is still unimplemented.

The steps necessary are adding the PCI did (use pci(8))
to /lib/vgadb under the igfx ctrl entry, and
/sys/src/cmd/aux/vga/igfx.c:/^devtype if it's not
there already, and either booting with monitor=auto in
plan9.ini, or calling vga(8) eg.:

	; aux/vga -m auto -l $vgasize

If things worked correctly, you will see a picture,
otherwise the screen will remain blank.

Setups that require more than just automatic
configuration would be more painful.  You could either
refer to [1] or ask here, but please don't waste too
much time :)

Thanks!

Cheers,
qwx

[1] http://nopenopenope.net/posts/igfx

             reply	other threads:[~2021-11-10 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 15:03 qwx [this message]
2021-11-12 18:37 ` Kyle Milz
2021-11-13  9:42   ` qwx
2021-11-13 21:49     ` Kyle Milz
2021-11-13 22:29       ` qwx
2021-11-15  3:05         ` Kyle Milz
2021-11-15  9:25           ` qwx

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=7E90DAD1DDA3E727F15D70ACD67F1717@wopr.sciops.net \
    --to=qwx@sciops.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).