similar to: [Bug 91333] New: Connecting second of two monitors to a Lenovo W520 causes displays to go crazy

https://bugs.freedesktop.org/show_bug.cgi?id=56615 Priority: medium Bug ID: 56615 Assignee: nouveau at lists.freedesktop.org Summary: Unable to start X on ThinkPad T420s laptop QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: mark.cave-ayland at

Hi there, I'm currently experiencing a minor problem using the bridge module under kernel 2.4.27 part of the Devil Linux distribution (http://www.devil-linux.org). The problem I am having is that when the bridge is unloaded during a reboot I receive the following errors in /var/log/messages: Nov 14 13:22:13 src@Devil kernel: unregister_netdevice: waiting for br0 to become free. Usage count =

Hi again, I got a new dmesg log with the debug parameters, but I guess I could not isolate VESA. I blacklisted it at /etc/modprobe.d/blacklist.conf but comparing those logs I see no difference... Is it possible to isolate VESA somehow without removing it? The new logs are here, I'm posting full content because I'm not sure what information is more relevant...

Have just upgraded from 3.0.14a to 3.0.25b. On starting winbindd it puts the following in /var/log/messages: initialize_winbindd_cache: clearing cache and re-creating with version number 1 All the winbind UID/GID mappings are lost and it starts again from scratch. Hence all file ownership / ACLs on this samba server become invalid. Anyone else seen this? Why does it see fit to destroy this

https://bugs.freedesktop.org/show_bug.cgi?id=77529 Priority: medium Bug ID: 77529 Assignee: nouveau at lists.freedesktop.org Summary: NVS 510 DP-3 output doesn't work QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: tex at sergio.spb.ru

https://bugs.freedesktop.org/show_bug.cgi?id=67628 Priority: medium Bug ID: 67628 Assignee: nouveau at lists.freedesktop.org Summary: [BISECTED] Monitor on Display port shows distortions QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified OS: Linux (All) Reporter:

Misha Brukman wrote: >On Thu, Aug 19, 2004 at 10:35:02AM +1200, Peter Ashford wrote: > > >>Does that mean the front end must decide between emiting bytecode for >>interpretting/JITing and LLVM assembly for native compilation? You >>can't emit the one kind of output for either end target (interpretted >>bytecode or native compilation)? >>

https://bugs.freedesktop.org/show_bug.cgi?id=76483 Priority: medium Bug ID: 76483 Assignee: nouveau at lists.freedesktop.org Summary: [NV50, bisected, RFC patch] xset dpms force {on,off} does not work over DP QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified OS:

I have a AIS Receiver which requires a ftdi chip driver(which I have) but I am stumped as to how I may get wine to load and see it. I need to run ShipPlotter software which seems to sit very nicely in the Wine environment but cannot make contact with the receiver as there is no driver. Any help would be appreciated.

Reid Spencer wrote: >Yes, that's right! > >In fact, shortly the process of doing that will get easier with the >llvmc (compiler driver) tool that I'm working on. You write your >compiler to generate either bytecode or LLVM assembly and a > > Does that mean the front end must decide between emiting bytecode for interpretting/JITing and LLVM assembly for native

https://bugs.freedesktop.org/show_bug.cgi?id=77674 Priority: medium Bug ID: 77674 Assignee: nouveau at lists.freedesktop.org Summary: "failed to read DPCD" on wake up with external monitor QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter:

Hi There, I've just started reading about LLVM and I just wanted to make sure that it can do what I was hoping it could do. Am I correct in assuming that I could use LLVM as a backend for a compiler, emiting LLVM byte codes which could either be natively compiled (Sparc and x86) or byte code interpretted / JITed??

Feature Requests item #25792, was opened at 2009-05-05 17:29 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=414&aid=25792&group_id=85 Category: None Group: None Status: Open Resolution: None Priority: 3 Submitted By: Daniel Berger (djberg96) Assigned to: Nobody (None) Summary: Create a pure Ruby win32-ole library Initial Comment: The current Win32OLE

This fixes a deadlock inversion when vblank is enabled/disabled by drm. &dev->vblank_time_lock is always taken when the vblank state is toggled, which caused a deadlock when &event->lock was also taken during event_get/put. Solve the race by requiring that lock to change enable/disable state, and always keeping vblank on the event list. Core drm ignores unwanted vblanks, so extra

https://bugs.freedesktop.org/show_bug.cgi?id=90453 Bug ID: 90453 Summary: Desktop periodically freezes when using Nouveau & getting "nouveau E[PDISP]" errors in dmesg Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity:

On 9 February 2014 02:57, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Sat, Feb 8, 2014 at 10:38 AM, Daniel J Blueman <daniel at quora.org> wrote: >> Interestingly, there was graphical failure booting 3.6.11, even >> nvidia-current fails to initialise, but these two issues could be due >> to running the Xorg stack in Ubuntu 14.04 pre-release. Using >>

In https://nouveau.freedesktop.org/KernelModuleParameters.html, there is: Here is a list of engines: DEVICE DMAOBJ PBSP PCE0 PCE1 PCE2 PCRYPT PDISP PFIFO PGRAPH PMPEG PPM PPPP PVP SW Also, in debug: CLIENT I have tried to find a description of those. https://envytools.readthedocs.io/en/latest/ help a bit, but I don't find a

On Tue, 2013-03-19 at 11:13 -0400, Peter Hurley wrote: > On vanilla 3.9.0-rc3, I get this 100% repeatable oops after login when > the user X session is coming up: Perhaps I wasn't clear that this happens on every boot and is a regression from 3.8 I'd be happy to help resolve this but time is of the essence; it would be a shame to have to revert all of this for 3.9 Regards, Peter

https://bugs.freedesktop.org/show_bug.cgi?id=73924 Priority: medium Bug ID: 73924 Assignee: nouveau at lists.freedesktop.org Summary: E[ PDISP][0000:01:00.0] chid 0 mthd 0x0080 data 0x00000000 0x00055080 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All

We assume that each board has 4 heads for GF119+. However this is not necessarily true - in the case of a GP108 board, the register indicated that there were only 2. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101601 Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- I'm not extremely happy about the fact that we have to duplicate the head count in both the