From: Jani Nikula <jani.nikula@linux.intel.com>
To: Paul Gardiner <lists@glidos.net>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] Does the intel driver support faking a connected monitor?
Date: Wed, 09 Dec 2020 12:19:26 +0200 [thread overview]
Message-ID: <87ft4f9t8x.fsf@intel.com> (raw)
In-Reply-To: <81a0f2f9-8669-8409-1ca5-8111bedef6b1@glidos.net>
On Fri, 04 Dec 2020, Paul Gardiner <lists@glidos.net> wrote:
> On 24/11/2020 15:03, Paul Gardiner wrote:
>> On 23/11/2020 16:19, Jani Nikula wrote:
>>> On Sat, 21 Nov 2020, Paul Gardiner <lists@glidos.net> wrote:
>>>> 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?
>>>
>>> I think it should probably be HDMI-1 with the hyphen; is that a typo
>>> above or in the command line you used?
>>
>> Thanks for the continued help. I tried "video=HDMI1:e" because my Xorg
>> log listed outputs HDMI1, HDMI2, DP1 and VIRTUAL1. I've now tried
>> "video=HDMI-1:e", but still no luck.
>
> Not wishing to hassle you, but before I give up, any further thoughts on
> this? I have a solution at least, which is to use a EDID emulator, so
> it's no great inconvenience how it is.
This should work. ISTR it's been used before by MythTV users. (I don't
know what you refer to with EDID emulator.)
Please file a bug over at [1]. Add drm.debug=14 module parameter, and
attach full dmesg from boot to reproducing the problem in the bug.
BR,
Jani.
[1] https://gitlab.freedesktop.org/drm/intel/-/issues/new
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-12-09 10:19 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
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 [this message]
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=87ft4f9t8x.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lists@glidos.net \
/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