Bug 94095 - Sandybridge-M 8086:0106 can't output to HDMI "invalid format" displayed on display
Summary: Sandybridge-M 8086:0106 can't output to HDMI "invalid format" displayed on d...
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-11 17:25 UTC by Calico Bass
Modified: 2017-06-02 12:20 UTC (History)
1 user (show)

See Also:
i915 platform: SNB
i915 features: display/HDMI


Attachments
intel_reg dump (16.76 KB, text/plain)
2016-02-11 17:35 UTC, Calico Bass
no flags Details
xrandr --verbose (8.38 KB, text/plain)
2016-02-11 17:41 UTC, Calico Bass
no flags Details

Description Calico Bass 2016-02-11 17:25:47 UTC
Sandybridge-M 8086:0106 can't output to HDMI  "invalid format" displayed on display


Intel(R)Sandybridge Mobile PCI Accelerated SVGA BIOS
Build Number: 2111 ASID:2111.I13K53.011$ PC 14.34  02/23/2011  17:45:47

Intel(R) Pentium(R) CPU B940 @ 2.00GHz


(II) intel(0): SNA compiled from 2.99.917-519-g8229390
(II) intel(0): SNA initialized with Sandybridge (gen6, gt1) backend


xorg-util-macros-1.19.0-1-any.pkg.tar.xz
xorg-xinit-1.3.4-3-x86_64.pkg.tar.xz
xorg-xrdb-1.1.0-2-x86_64.pkg.tar.xz
xf86-input-evdev-2.10.1-1-x86_64.pkg.tar.xz
xf86-video-intel-1:2.99.917+519+g8229390-0.1-x86_64.pkg.tar.xz
lib32-mesa-11.1.1-1-x86_64.pkg.tar.xz
mesa-11.1.1-1-x86_64.pkg.tar.xz

Tried all kinds of xrandr settings and have given up, well not completely given up because I am logging this bug, right?

The display is fine and works via HDMI with a PS3 at 1080i, a DVD at 480 and another laptop with ivybridge.
Comment 1 Calico Bass 2016-02-11 17:35:13 UTC
Created attachment 121684 [details]
intel_reg dump

This is an intel_reg dump, it represents a dump of the registers on the intel.
Comment 2 Calico Bass 2016-02-11 17:41:54 UTC
Created attachment 121685 [details]
xrandr --verbose

This is the output from xrandr --verbose that was redirected to a text file and then attached here for, posterity at least, and as a useful bit of information, at best, to help resolve this utterly pernicious issue.
Comment 3 Calico Bass 2016-02-11 17:59:23 UTC
I have tried kernels 4.1, 4.4 and 4.5-rc3 in case you were wondering. I actually hope you weren't wondering and already have a hunch on what problem I am encountering. But perhaps I am getting my expectations high too soon.
Comment 4 Chris Wilson 2016-02-11 21:25:08 UTC
Rough guess would be that this is an aviframe issue.
Comment 5 Calico Bass 2016-02-17 22:04:22 UTC
Where to look for "aviframe" code? Where would this kind of issue occur? Is there much chance that this will get fixed?

I have searched for aviframe but come up pretty empty. I also gitcloned the driver and grep'd blindly. Still not much fruit. Thanks for any tips and/or guidance.
Comment 6 Calico Bass 2016-08-02 19:38:45 UTC
I tried this with newer software. Different kernel and stuff like that. You know those things you get when you install the new things that are released. Well I'm excited to report that the "invalid format" messages are no longer seen. But now nothing at all occurs. I am keeping my HDMI cable (and my VGA cable of course) because it's a nicely made cable. Who knows maybe one day when more new things are installed my HDMI cable can be put into action. I'll try to report back before the winter solstice.
Comment 7 Ville Syrjala 2016-08-05 07:02:46 UTC
(In reply to Calico Bass from comment #0)
> Sandybridge-M 8086:0106 can't output to HDMI  "invalid format" displayed on
> display
>...
> The display is fine and works via HDMI with a PS3 at 1080i, a DVD at 480 and
> another laptop with ivybridge.

Well, that makes this quite difficult. In general SNB and IVB are _very_ closely related in terms of display output hardware.

Can you grab the dmesg, with drm.debug=0xe passed to the kernel command line, from _both_ machines after booting up with this display connected? Also reg dump from both machines would be good, when the display is connected and active.

Also 'intel_reg read --count 10 0xE4F00' from both machines might be interesting, although I'm not actually sure these buffer translation values do anything in HDMI mode.
Comment 8 Ricardo 2017-02-21 16:52:42 UTC
Hi Calico please provide information requested in pervious comment, and if the issue is not there anymore with latest kernel also please update, if no response is received in 30 days the bug will be closed since has been several months with no activity
Comment 9 Ricardo 2017-05-30 17:38:09 UTC
based on the lack of activity and a response from the submitter to update results with latest configuration the bug will be closed


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.