Bug 87543 - [NV96] MXM "unmatched output device 0x0103010201010100" when connecting to hdmi
Summary: [NV96] MXM "unmatched output device 0x0103010201010100" when connecting to hdmi
Status: NEW
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-20 23:59 UTC by Somelauw
Modified: 2014-12-21 00:23 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg, acpidump, vbios (197.30 KB, application/x-gzip)
2014-12-20 23:59 UTC, Somelauw
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Somelauw 2014-12-20 23:59:11 UTC
Created attachment 111096 [details]
dmesg, acpidump, vbios

I'm trying to get an external screen (a television) to work using a HDMI cable.
Unfortunately the HDMI screen doesn't show up in the output of xrandr.
This all works under windows, so the cable isn't broken or anything.

In my dmesg, I found the following problem:
nouveau  [     MXM][0000:01:00.0] unmatched output device 0x0103010201010100

My OS is LMDE.
I'm using the following kernel: 3.17-7.dmz.1-liquorix-amd64

Here is some info about my graphical card:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96GLM [Quadro FX 770M] [10de:065c] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: Hewlett-Packard Company Device [103c:30e7]
	Flags: bus master, fast devsel, latency 0, IRQ 35
	Memory at 92000000 (32-bit, non-prefetchable) [size=16M]
	Memory at 80000000 (64-bit, prefetchable) [size=256M]
	Memory at 90000000 (64-bit, non-prefetchable) [size=32M]
	I/O ports at 7000 [size=128]
	Expansion ROM at <ignored> [disabled]
	Capabilities: <access denied>
	Kernel driver in use: nouveau

Chipset: G96 (NV96)
Family : NV50


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.