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
(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 m
(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=47bdd59a9967ee8dd2bcc47
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 bi
(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 l
(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 y
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:
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
Bu
*** 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:
http
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
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"
* A
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 notific
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
13 matches
Mail list logo
