similar to: Linux 3.7 Nouveau msi module parameter

https://bugs.freedesktop.org/show_bug.cgi?id=104672 Bug ID: 104672 Summary: [NVAC] Compiz segfaults on login on Ubuntu 17.10 with Unity 7 (kernel DRM bug?) Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=54786 Bug #: 54786 Summary: random crashes of X with failed to idle channel 0xcccc0000 Classification: Unclassified Product: xorg Version: 7.6 (2010.12) Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major

https://bugs.freedesktop.org/show_bug.cgi?id=57350 Marcin Slusarz <marcin.slusarz at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|dri-devel at lists.freedesktop |nouveau at lists.freedesktop.o |.org |rg QA Contact|

Hi, With 3.13-rc1 and 3.13-rc2 kernel crashes/BUGs while loading nouveau: [ 657.654915] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Integer], ACPI requires [Package] (20131115/nsarguments-95) [ 657.655099] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) [ 657.655270] checking

The issue was recorded in fd.o bug 27501, not 25701. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drivers/gpu/drm/nouveau/nvkm/subdev/fb/rammcp77.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/fb/rammcp77.c b/drivers/gpu/drm/nouveau/nvkm/subdev/fb/rammcp77.c index 0a0e44b..017a91d 100644 ---

Hi, I am changing from proprietary nvidia drivers to Nouveau drivers in my mediacenter. I run a Gentoo linux in this hardware and I am facing an out of signal screen just after the boot (when the nouveau module is loaded). If I blacklist this module and modprobe it in the prompt, the screen gets out of signal in my 1080p TV in this moment. I tried recompile the kernel enabling and disabling a

Hello, I've just been hit by this old bug which is still present in 4.14: https://bugs.freedesktop.org/show_bug.cgi?id=80675 On MCP79 (ION), when stolen memory is set to 32MB in BIOS, console is blank but X11 works. When the stolen memory is increased to 64MB, console works fine. Bisected it to this: 4f6029da58ba9204c98e33f4f3737fe085c87a6f is the first bad commit commit

Fixes "No Signal" via HDMI from NVIDIA Corporation ION VGA (rev b1) Ref. "drm/nouveau/disp/g94: implement workaround for dvi issue on fx380" https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2a4bd8a The last working Fedora kernel 4.8.0-0.rc0.git3.1.fc25 Patched and tested with: $ modinfo -n nouveau

On Wed, Oct 19, 2016 at 07:58:06PM +0200, Pierre Moreau wrote: > For example, my laptop (which also has an NVAC) has been triggering the > no-signal message on external monitors way before Ben???s patch landed, > but only for some adapters. I haven???t tried Ben???s patch yet, nor > yours, but I will certainly do it, and see what effect each of them has. The external DP port on your

Hi Robert, After trying to write a proper patch for Nouveau, we realised we were missing a few pieces of information. ----- Mail original ----- > Hi Robert, > > Thanks a lot for your response! > > ----- Mail original ----- > > On Wed, Oct 22, 2014 at 12:55:23AM +0200, pierre.morrow at free.fr > > wrote: > > [...] > > > After some investigation, I found

On 01:15 am - Oct 21 2016, Lukas Wunner wrote: > On Thu, Oct 20, 2016 at 10:08:28AM +0200, Lukas Wunner wrote: > > On Wed, Oct 19, 2016 at 07:58:06PM +0200, Pierre Moreau wrote: > > > For example, my laptop (which also has an NVAC) has been triggering the > > > no-signal message on external monitors way before Ben???s patch landed, > > > but only for some

With a new kernel, mind grabbing a dmesg with drm.debug=0x1e nouveau.debug=debug (or maybe even =trace)? Maybe also see if fbcon/fbdev have any debug things that can be turned on? Sounds like things are generally working, just the fbcon -> nouveaufb path seems somehow buggered. Another thing to try would be nouveau.atomic=1 On Fri, Nov 17, 2017 at 9:26 AM, Ondrej Zary <linux at

I think you want kernel 4.10, or cherry-pick upstream commit 7dfee6827780d4228148263545af936d0cae8930. On Sun, Mar 12, 2017 at 11:27 AM, Marcelo Ribeiro <mbribeiro at gmail.com> wrote: > Hi, I am changing from proprietary nvidia drivers to Nouveau drivers in my > mediacenter. > > I run a Gentoo linux in this hardware and I am facing an out of signal > screen just after the

On Wed, Dec 4, 2013 at 6:01 AM, Bruno Pr?mont <bonbons at linux-vserver.org> wrote: > Hi, > > With 3.13-rc1 and 3.13-rc2 kernel crashes/BUGs while loading nouveau: > [ 657.654915] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM: Argument #4 type mismatch - Found [Integer], ACPI requires [Package] (20131115/nsarguments-95) > [ 657.655099] ACPI Warning: \_SB_.PCI0.IXVE.IGPU._DSM:

Hi, With drm-nouveau-next branch on top of 3.13-rc2 and a few sound commits I get following errors in kernel log (repeating much more often). (once there was a corrupted fbcon with matrix-like strings of unrecognizable glyph-strings hanging down from screen top border) These errors do stop once I switch to Xorg. [ 13.825627] nouveau E[ PFB][0000:02:00.0] trapped write at 0x0000408280 on

Hi HPA et al, When moving from syslinux 4.06 to 5.01, I found serial output isn't working. The issue reproduces simply [1] and I get back serial output when I move back to syslinux 4.06. I also see a regression in booting locally with 'localboot 0' which give a generic 'failed' error message; likely reproducible there also. Let me know if you need more information and

Dear All, After recently taking a little dive into the NVAC clock tree, I was wondering what that net would look like on cards I expect to be similar. In this case I'm looking for MMIOtraces of NVAA and NVAF, which is marketed as the 8x00 mGPU, 9x00 mGPU, 320M, ION and/or some nForce IGP. If there is anyone who could provide me with an MMIO trace for any of these cards that would be

Hey all, I've just pushed out the initial Nouveau support for $subject \o/ As the atomic modesetting transition is basically a rewrite of the KMS portion of the driver, I would be very grateful for any additional testing that people could provide (even as simple as just booting and making sure you get a display is valuable). There's a Linux tree at

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 >>

Hello Ilia, > > [ 7.569394] nouveau [ DEVICE][0000:02:00.0] BOOT0 : 0x0ac080b1 > > [ 7.569460] nouveau [ DEVICE][0000:02:00.0] Chipset: MCP79/MCP7A (NVAC) > > [ 7.569530] nouveau [ DEVICE][0000:02:00.0] Family : NV50 > > [ 7.571151] nouveau [ VBIOS][0000:02:00.0] checking PRAMIN for image... > > [ 7.633082] nouveau [ VBIOS][0000:02:00.0]