From: Paul Gardiner <lists@glidos.net>
To: Jani Nikula <jani.nikula@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] Does the intel driver support faking a connected monitor?
Date: Sat, 21 Nov 2020 10:52:02 +0000 [thread overview]
Message-ID: <d89b2287-51dc-87a5-4e38-022b0b8da648@glidos.net> (raw)
In-Reply-To: <87sg98ox2i.fsf@intel.com>
On 17/11/2020 14:52, Jani Nikula wrote:
> On Thu, 29 Oct 2020, Paul Gardiner <lists@glidos.net> wrote:
>> I use an open source DVR called MythTV. I've just swapped from using
>> nvidia graphics to intel graphics. Generally it's working great, but
>> I've run into one thing I used to do with the old system that I cannot
>> find out how to achieve with the new.
>>
>> MythTV doesn't currently entirely handle starting without a TV
>> connected. With nvidia graphics I could specify, within the X config,
>> the "ConnectMonitor" and "CustomEDID" options to fool MythTV into
>> thinking there was a TV. With intel graphics I can load EDID, but so far
>> I haven't discovered an equivalent of the "ConnectedMonitor" option.
>
> Sorry for the delay, I seem to have missed this.
>
> Please try a kernel command-line parameter to force enable the
> connector.
>
> video=TV-1:e
>
> Assuming the connector name is "TV-1"; replace with whatever you have.
Thanks for the reply. I gave that a try, in my case "video=HDMI1:e", but
saw no difference. That's KMS, right? Is there anything I might have
failed to install or enable that KMS relies on? Are there any logs I
should monitor?
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-11-21 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 12:32 [Intel-gfx] Does the intel driver support faking a connected monitor? Paul Gardiner
2020-11-17 14:52 ` Jani Nikula
2020-11-21 10:52 ` Paul Gardiner [this message]
2020-11-23 16:19 ` Jani Nikula
2020-11-24 15:03 ` Paul Gardiner
2020-12-04 11:22 ` Paul Gardiner
2020-12-09 10:19 ` Jani Nikula
2020-12-20 10:31 ` Paul Gardiner
2020-12-21 14:04 ` Jani Nikula
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=d89b2287-51dc-87a5-4e38-022b0b8da648@glidos.net \
--to=lists@glidos.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.