From: Kyle Milz <krwmilz@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] igfx on haswell
Date: Sat, 13 Nov 2021 13:49:05 -0800 [thread overview]
Message-ID: <YZAy0RuIDj9JHQmq@imac.0x30.net> (raw)
In-Reply-To: <EFBCB699619F707EC9FBFA010B2D36EA@wopr.sciops.net>
On Sat, Nov 13, 2021 at 10:42:17AM +0100, qwx@sciops.net wrote:
> Great, thanks! For hdmi/dvi to work, igfx must manage to get
> an edid from the monitor, this doesn't happen with some of
> them, but you might coerce it to work with yet another vgadb
> entry for it, specifying a port with display=. It will be on
> one of the 4 remaining DP ports, 4-7 (3 is eDP). There's no
> way to force hdmi on a specific port though iirc.
i played around with aux/vga -pvV and it manages to get an edid
for the internal display about 1/10 of the time. the other 9/10
times the 8 edid header bytes contain random garbage. i tried
comparing i915 drm code with igfx.c to find out why but no luck.
i have not tried getting the edid from an external display but
suspect something similar is happening.
> If possible, please add the pci did to
> /sys/src/9/pc/vgaigfx.c:152. The hardware cursor should be
> enabled when you invoke aux/vga. If it's visible while
> /dev/vgactl shows `hwgc igfxhwgc', it works.
i tried that, but got the same output as before. forcing it with
% echo hwgc igfxhwgc >/dev/vgactl
causes the cursor to disappear.
> One last thing, could you please also say if:
>
> ; ls '#g'
prints nothing.
next prev parent reply other threads:[~2021-11-13 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 15:03 qwx
2021-11-12 18:37 ` Kyle Milz
2021-11-13 9:42 ` qwx
2021-11-13 21:49 ` Kyle Milz [this message]
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=YZAy0RuIDj9JHQmq@imac.0x30.net \
--to=krwmilz@gmail.com \
--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).