[Bug 653714]
agpmode and modeset are not even remotely related I'm afraid. With 4.3 onward one should be using nouveau.config="NvAGP=0" as documented [1] [1] http://nouveau.freedesktop.org/wiki/KernelModuleParameters/#config -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/653714 Title: Garbage on X display w/ Dell D800 wuxga & nouveau driver (Nvidia GeForce4 Ti 4200 Go AGP rev a1 [NV28]) To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/653714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1275042]
(In reply to joro-2013 from comment #16) > Allow me to add my experiences. > > Whether the colors are garbled on PPC depends on the GL color format used > (among probably a gazillion other parameters :-). Packed (16-bit) formats > have been broken on big-endian for some time, they worked fine in mesa 10.1, > in mesa 10.3 R5G5B5A1 works, R4G4B4A4 works with alpha glitches, somewhere > in the 10.3 release cycle the format stuff got completely rewritten breaking > pretty much all packed formats on big-endian (PPC). > > Unpacked (32 bits) formats seem to be working fine. > > That's on a RV280 32 bit system. No idea whether that is also valid for NV34 > on 64-bit PPC, i.e. whether the problem is in core mesa or the radeon stuff. The report in question is (was?) about the gallium radeon driver - r600g. On the classic radeon/r200 front there was a regression caused by commit 779cabfc7d022de8b7b9bc7fdac0caffa8646c51 (which itself fixing some BE issues, circa 11.0), which was resolved in 11.0.6 and 11.1.0. If things are still off, then I'd suggest opening separate bug report and if possible bisecting it down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1275042 Title: Wrong colors with Mesa 9.2 and Mesa 10.0 on Lubuntu 14.04 PowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1275042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371636]
(In reply to comment #11) > With Gentoo vanilla binutils 2.24-r3 with two slim LTO patches and the patch > referred by Emil Velikov in Comment #3 > > https://projects.archlinux.org/svntogit/packages.git/plain/trunk/binutils-2. > 24-shared-pie.patch?h=packages/ > binutils&id=47bdd59a9967ee8dd2bcc47797855185c6471546 > > it builds fine even with LTO enabled (using a trick with calling configure > with LTO turned off and then -fno-lto -fno-use-linker-plugin removed from > each Makefile). > > So trunk binutils seems to be source of the problem. > I have to start with bisecting them. Nicely done. I hope that the problem does not end up a sheep in wolf's clothing - i.e. somewhere else. Using gcc+bintutils, to compile a third library, which links to another two compiler(ish) products... there are so many things that can be happening in there. Thank you for the great initiative :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371636 Title: [2.24.51.20140918-1ubuntu1 regression] - /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs To manage notifications about this bug go to: https://bugs.launchpad.net/arb/+bug/1371636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371636]
Building OpenCL works like a charm here. Can you try to establish which (if any) of the following components is responsible - llvm, gcc (*cough* 4.9.2_alpha) binutils or clang. I'm building it on Archlinux (llvm 3.5.0, gcc 4.9.1 (snapshot 4.9-20140903), binutils 2.24 [1], clang 3.5.0). [1] The binutils package has a patch which suspiciously looks like it should handle the issue https://projects.archlinux.org/svntogit/packages.git/plain/trunk/binutils-2.24-shared-pie.patch?h=packages/binutils&id=47bdd59a9967ee8dd2bcc47797855185c6471546 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371636 Title: [2.24.51.20140918-1ubuntu1 regression] - /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs To manage notifications about this bug go to: https://bugs.launchpad.net/arb/+bug/1371636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371636]
(In reply to comment #4) > I tested it with LLVM 3.4.2 and the same set of gcc-4.9.2 (svn) and binutils > (svn) used to open this bug report and all built fine. It may be that llvm 3.5 + mesa is "using" gcc/binutils in a slightly different way. Can you try using the same versions as the one I've listed ? This way if it works one can start looking for the combination that exhibits the problem. > So for me it looks > like that LLVM 3.5.0 came with something changed. Is it not a same name of > some function, introduced in LLVM 3.5.0 and present in Mesa before? If the function prototype has changed then a compiler warning is due. Afaict your issue is at a later stage - link time. > It seems to not be LTO issue if Kai really not uses it and with LLVM 3.4.2 > it builds with LTO for me. I would recommend disabling LTO until one is able to clearly establish the root cause. After it's sorted you can get it back on for llvm. > I checked content of ld/emultempl/elf32.em in my git replica and patch you > are reffering to is incorporated. I would recommend that you try the patch, before doing anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371636 Title: [2.24.51.20140918-1ubuntu1 regression] - /usr/bin/ld: .eh_frame_hdr refers to overlapping FDEs To manage notifications about this bug go to: https://bugs.launchpad.net/arb/+bug/1371636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196049]
(In reply to comment #3) > Do you really understand that Nvidia-based 1500-3000$ laptop may be really > killed by overheat with pretty non-binary / no-blob / GPL-friendly > opensource driver? Are you kidding? :) > The temperatures you've mentioned will not kill your laptop. > OK, Ilia. Where do yo recommend to post such report about "power management > not supported" issues? > There is not much of a benefit in (re-)posting "power management does not work", most people are aware about this and working on it one way or the other. If you really want to help, be more understanding and work with the nouveau team rather than posting annoying replies. Btw have you realised the _massive_ amount of work that PM is ? The AMD/ATI DPM code that landed in linux 3.11 is over 50kloc and all of it was done by the vendor. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196049 Title: Laptop with Nvidia GPU is hot while using xserver-xorg-video-nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1196049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921321]
Created attachment 68764 Enable the PANEL_BACKLIGHT_LEVEL GPIO Guys can you try the patch. It should apply against the latest nouveau tree -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921321 Title: nouveau: dark screen after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/921321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921321]
It appears that even the blob was experiencing the same issue [1] Affected blob 180.44, fixed in 180.60. I would expect that a specific quirk was added to handle the issue [1] http://www.bartromgens.org/wordpress/?p=274 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921321 Title: nouveau: dark screen after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/921321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 951331]
*** This bug has been marked as a duplicate of bug 41333 *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951331 Title: X does not start on GT240 To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/951331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 921321]
Did you have the chance to test a kernel that includes the following commit "drm/nouveau/gpio: reimplement as nouveau_gpio.c, fixing a number of issues" It does rework the gpio handling and initialization (among other things), that should have positive effect on your issue It is part of linux 3.3rc1 [1] as well as nouveau linux tree [2] Cheers Emil [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;h=a0b25635515ef5049f93b032a1e37f18b16e0f6f [2] http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=a0b25635515ef5049f93b032a1e37f18b16e0f6f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/921321 Title: nouveau: dark screen after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/921321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 925048]
Hello Bryce Here are some tips that will help triage the issue * Is the person using "3d" - try reproducing the issue without it Disable AIGLX in the X server (Re)move the file (or package providing it) "/usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so" * Try booting with "nouveau.nofbaccel=0" * Amend the previous option to read "nouveau.noaccel=0" Although before attempting any of the above I would recommend trying the git master branch (or as close as) of the following * [1] xf86-video-nouveau * [2] kernel * [3] mesa Note that those tips can be used for any case/issue Cheers Emil [1] http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/ [2] http://cgit.freedesktop.org/nouveau/linux-2.6/ [3] http://cgit.freedesktop.org/mesa/mesa/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/925048 Title: [GTX 580] X seems to hang a login prompt -- PFIFO errors in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/925048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754711]
According to the latest dmesg (in comment #47) Nouveau fails to "Suspend the GPU objects" due to NOMEM (-12 reported in the log), I.e. nouveau fails to vmalloc(gpuobj->size), that is needed to store current gpu objects (so that they can be restored after resume) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/754711 Title: [Dell Studio XPS 1340] Doesn't enter suspend mode To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/754711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 553789]
For anyone still experiencing this bug, here is a possible workaround (thanks to ColdFeetBob for pointing it out) Modify* /xserver/mi/mieq.c and rebuild xserver * Increase the "#define QUEUE_SIZE 512" to 1024, 2048 or 4096 [1] Note that this is *not* a proper fix as you can see in the discussion [2], and it isn't recommended for unexperienced users [1] http://www.nvnews.net/vbulletin/showpost.php?p=2398370&postcount=2 [2] https://bugs.freedesktop.org/show_bug.cgi?id=15473 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/553789 Title: [MASTER] [GT21x] X freeze/crash with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/553789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
