public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: markh@compro.net
Cc: linux-kernel@vger.kernel.org, Mark Hounschell <dmarkh@cfl.rr.com>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: Intel graphics drm issue?
Date: Fri, 12 Oct 2012 23:14:59 +0200	[thread overview]
Message-ID: <20121012231459.166e29fd@neptune.home> (raw)
In-Reply-To: <507812E8.3060607@compro.net>

Hi Mark,

[CCing intel-gfx]

On Fri, 12 October 2012 Mark Hounschell <markh@compro.net> wrote:
> Not sure this is the correct place to ask about a possible drm issue. I 
> have an intel based PC with an HDMI port that I'm trying to connect to 
> an LG TV. I have successfully used this HDMI port connected to an Optima 
> projector. Using that projector, everything from the BIOS post, BIOS 
> configuration, and all the way up to a graphical login worked just fine. 
> The same HDMI port and cable connected to this TV gives me the below 
> messages during boot. I also get no BIOS post or BIOS configuration 
> output while in the BIOS. I have a monitor connected to the DVI port so 
> I can see what I should see on the TV there, just as when I was 
> connected to the Optima projector. That alone makes me pretty sure it's 
> not a kernel issue but here are the messages anyway. Maybe they will 
> give someone a hint as to what the problem may be, in the case they 
> might be willing to give me any pointers.
> 
> TV - LG 42lb9df
> PC - intel DH77DF motherboard

> [    0.000000] Linux version 3.4.10-lcrs (root@geexbox) (gcc version 4.7.1 20120723 [gcc-4_7-branch revision 189773] (SUSE Linux) ) #1 SMP PREEMPT Wed Oct 10 16:16:16 EDT 2012
> ...
> [    1.897955] [drm] MTRR allocation failed.  Graphics performance may suffer.
> [    1.898045] i915 0000:00:02.0: irq 43 for MSI/MSI-X
> [    1.898050] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
> [    1.898051] [drm] Driver supports precise vblank timestamp query.
> [    1.898084] [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed
> [    1.898737] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
> [    1.995523] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
> [    2.299535] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128
> [    2.299865] Raw EDID:
> [    2.299957]          ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    2.300188]          ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    2.300418]          ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    2.300648]          ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    2.300879]          ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    2.301109]          ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    2.301339]          ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> [    2.301569]          ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

This looks like your LG TV either does not provide EDID information via HDMI
connector, or otherwise behaves in a special way which makes reading EDID
fail.

Did you try the TV on some other computer to check if EDID can be read there
(e.g. with nvidia/amd GPU and matching open/closed driver)?

Also make sure the TV is on (neither off nor on stand-by) as some TVs
disable too much of connector interface in those states.

> [    2.434378] i915 0000:00:02.0: HDMI-A-3: EDID block 0 invalid.
> [    2.477539] checking generic (e0000000 3ff0000) vs hw (e0000000 10000000)
> [    2.477541] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
> [    2.477549] Console: switching to colour dummy device 80x25
> [    2.477831] fbcon: inteldrmfb (fb0) is primary device
> [    2.637915] Console: switching to colour frame buffer device 128x48
> [    2.679625] fb0: inteldrmfb frame buffer device
> [    2.679626] drm: registered panic notifier
> [    2.691536] acpi device:4b: registered as cooling_device9
> [    2.691660] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input4
> [    2.691698] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
> [    2.691709] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

> geexbox:/home/mplayer # lspci
> 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
> ...
> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
> ...

Note, usually `lspci -nn` is more informative as it also provides vendor/device
IDs in addition to nice names.

Bruno

  reply	other threads:[~2012-10-12 21:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 12:54 Intel graphics drm issue? Mark Hounschell
2012-10-12 21:14 ` Bruno Prémont [this message]
2012-10-13 18:57   ` Mark Hounschell
2012-10-13 19:17     ` Mark Hounschell
2012-10-14  8:41       ` Bruno Prémont
2012-10-14 10:34         ` Mark Hounschell
2012-10-14 10:52         ` Mark Hounschell
2012-10-14 11:03           ` Bruno Prémont
2012-10-14 16:54             ` Mark Hounschell
2012-10-14 17:22               ` Bruno Prémont
2012-10-14 18:03                 ` Mark Hounschell
2012-10-14 18:19                   ` Bruno Prémont
2012-10-14 18:57                     ` Mark Hounschell
2012-10-14 20:40                       ` Bruno Prémont
2012-10-15  9:58                         ` Mark Hounschell
2012-10-14  8:58       ` [Intel-gfx] " Daniel Vetter
2012-10-14 10:20         ` Mark Hounschell
2012-10-14 11:26           ` Daniel Vetter
2012-10-14 11:39             ` Mark Hounschell
2012-10-14 14:19             ` Mark Hounschell
2012-10-14 14:40               ` Daniel Vetter
2012-10-14 15:41                 ` Mark Hounschell
2012-10-14 15:53                   ` Daniel Vetter
2012-10-14 15:55                     ` Bruno Prémont
2012-10-14 16:09                       ` Mark Hounschell
2012-10-14 16:13                         ` Mark Hounschell

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=20121012231459.166e29fd@neptune.home \
    --to=bonbons@linux-vserver.org \
    --cc=dmarkh@cfl.rr.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@compro.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