similar to: [Bug 72952] [NV94] no HDMI output, xrands claims DVI-D-1 disconnected

https://bugs.freedesktop.org/show_bug.cgi?id=72952 J?rg H?hle <Joerg-Cyril.Hoehle at T-Systems.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #91095|0 |1 is obsolete| | --- Comment #3 from J?rg H?hle

https://bugs.freedesktop.org/show_bug.cgi?id=72952 --- Comment #8 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to comment #7) > I'm sure you meant attachment #92185 [details] [review] not the log file, Indeed. Although a different approach was finally merged, that the original bug reporter (and several others with the same issue) confirmed also fixed the problem. >

https://bugs.freedesktop.org/show_bug.cgi?id=72952 --- Comment #4 from J?rg H?hle <Joerg-Cyril.Hoehle at T-Systems.com> --- No HDMI either when booting Ubuntu 13.04 on the same machine from a live DVD. Alas, using the live DVD, I couldn't check the behaviour described in comment #2 past a suspend&resume cycle, because the machine hung shortly after resume. -- You are receiving

https://bugs.freedesktop.org/show_bug.cgi?id=72952 Aaron Plattner <aplattner at nvidia.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|aplattner at nvidia.com |nouveau at lists.freedesktop.o | |rg

https://bugs.freedesktop.org/show_bug.cgi?id=72952 --- Comment #5 from Ilia Mirkin <imirkin at alum.mit.edu> --- I think this issue might be the same one as bug #60680. Can you try the patch at https://bugs.freedesktop.org/attachment.cgi?id=92319 and see if it helps? If it doesn't, can you upload your vbios (/sys/kernel/debug/dri/0/vbios.rom) as well as a dmesg booting with

https://bugs.freedesktop.org/show_bug.cgi?id=72952 --- Comment #6 from Ilia Mirkin <imirkin at alum.mit.edu> --- Erm, sorry, that patch link was wrong. Can you give drm-next a shot? (Or try 3.14-rc1 when that comes out?) -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=72952 Martin Peres <martin.peres at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED --- Comment #9 from Martin Peres

https://bugs.freedesktop.org/show_bug.cgi?id=84706 Bug ID: 84706 Summary: [NV94] HDMI Connected, but TV reports "no signal" Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

The important thing for display detection/setting proper modes/etc is the kernel -- what kernel version are you using? Separately, there has been a fix that affected VBIOSes found in NV96 cards, and it would not be a stretch to believe that a similar VBIOS script could be found in a NV92 card. However the NV96 error condition was different (everything detected fine, but no actual image displayed,

Dear R Community, I would like to announce the package "surveillance", which provides methods for the surveillance of count data time series originating from the routine collection of public health data. The package addresses epidemiologists and statisticians working with routine surveillance, but it also offers an infrastructure for developers of new detection algorithms. Implemented

Dear R Community, I would like to announce the package "surveillance", which provides methods for the surveillance of count data time series originating from the routine collection of public health data. The package addresses epidemiologists and statisticians working with routine surveillance, but it also offers an infrastructure for developers of new detection algorithms. Implemented

https://bugs.freedesktop.org/show_bug.cgi?id=90145 Bug ID: 90145 Summary: [NV94] Corruption on very long (vertical) pages in Firefox Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=43668 Bug #: 43668 Summary: Secondary monitor always in standby on dual head NV94 Classification: Unclassified Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium

Hi List, I'm stuck how to get a dual head monitor solution to work with Nouveau, running openSUSE 13.1 on my hp8710w mobile workstation equipped with a Nvidia graphical card. Beyond the built-in WUXGA display, an external WQHD monitor is connected to the HDMI port on the graphical card and/or to the dual link DVI-D on a hp docking station. To compare with SLED11/Nvidia driver running in

https://bugs.freedesktop.org/show_bug.cgi?id=85160 Bug ID: 85160 Summary: [NV94] INVALID_STATE error, X fails to start on GeForce 9600 GT with dual monitors, kernels 3.18.0-0.rc0.git8.2.fc22.1 onwards Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All)

https://bugs.freedesktop.org/show_bug.cgi?id=84880 Bug ID: 84880 Summary: [NV94] X freeze on nouveau list_del corruption / unable to handle kernel paging request Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical

Hi I have an issue with a Nvidia GeForce 710 graphic card since several weeks, probably related to a bug in Nouveau. Here is my setup : A Computer based on X58 chipset running Proxmox VE 4.x. The graphic card is used by a qemu-kvm virtual machine running Debian 9 testing thanks to PCI passthrough. The issue : the graphic card has 1 VGA, 1 DVI, 1 HDMI outputs. If a DVI or HDMI monitor is plugged

The driver stores lut values from the fbdev interface, and is able to give them back, but does not appear to do anything with these lut values. The generic fb helpers have replaced this function, and may even have made the driver work for the C8 mode from the fbdev interface. But that is untested. Since the fb helper .gamma_set and .gamma_get are no longer used, just kill the mysterious dead

Currently we set intel_connector->mst_port to NULL to signify that the MST port has been removed from the system so that we can prevent further action on the port such as connector probes, mode probing, etc. However, we're going to need access to intel_connector->mst_port in order to fixup ->best_encoder() so that it can always return the correct encoder for an MST port to prevent

Currently we set intel_connector->mst_port to NULL to signify that the MST port has been removed from the system so that we can prevent further action on the port such as connector probes, mode probing, etc. However, we're going to need access to intel_connector->mst_port in order to fixup ->best_encoder() so that it can always return the correct encoder for an MST port to prevent