Bug 87543

Summary: [NV96] MXM "unmatched output device 0x0103010201010100" when connecting to hdmi
Product: xorg Reporter: Somelauw
Component: Driver/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED MOVED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg, acpidump, vbios none

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
Comment 1 Martin Peres 2019-12-04 08:53:14 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/158.

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.