Bug#694734: adjusting severity

2012-12-05 Thread Javier Domingo
Well, it wasn't really a black screen, just those i2c unknown messages. I will test it as soon as posible and report whatever it comes out Cheers, Javier Domingo 2012/12/5 Ben Hutchings b...@decadent.org.uk: On Tue, 2012-12-04 at 21:07 +0100, Sven Joachim wrote: Control: reassign -1 src:linux

Bug#694734: adjusting severity

2012-12-05 Thread Sven Joachim
On 2012-12-05 01:12 +0100, Ben Hutchings wrote: Could you try Julien Cristau's kernel package that uses 3.4 DRM drivers? This is a possible solution for wheezy's current poor or missing support for some recent GPUs. Works fine with my GeForce 8500 GT, I don't have any more recent GPU to test.

Bug#694734: adjusting severity

2012-12-04 Thread Sven Joachim
Control: reassign -1 src:linux Control: found -1 3.2.23-1 Control: fixed -1 3.6.4-1~experimental.1 Control: retitle -1 nouveau: black screen with GeForce GTX 560 On 2012-11-29 18:49 +0100, Sven Joachim wrote: On 2012-11-29 18:38 +0100, Javier Domingo wrote: I can't now at the moment access to

Bug#694734: adjusting severity

2012-12-04 Thread Ben Hutchings
On Tue, 2012-12-04 at 21:07 +0100, Sven Joachim wrote: Control: reassign -1 src:linux Control: found -1 3.2.23-1 Control: fixed -1 3.6.4-1~experimental.1 Control: retitle -1 nouveau: black screen with GeForce GTX 560 On 2012-11-29 18:49 +0100, Sven Joachim wrote: On 2012-11-29 18:38

Bug#694734: adjusting severity

2012-12-04 Thread Javier Domingo
This might go in another bug, but, Is there any way we can switch between one driver and another? I mean, is it possible to create an update-alternatives for graphical drivers? The various nvidia-* packages in non-free and contrib already provide such a system, but I haven't tried it. For

Bug#694734: adjusting severity

2012-12-01 Thread Sven Joachim
On 2012-11-29 18:38 +0100, Javier Domingo wrote: I can't now at the moment access to the computer, but I can attach what I sent there, the dmesg output and the Xorg.0.log output. I must say that with kernel 3.2 the computer doesn't boot, or at least it tells me about non-recognised ports and

Bug#694734: adjusting severity

2012-11-30 Thread Sven Joachim
On 2012-11-29 23:55 +0100, Javier Domingo wrote: I have been searching around freedesktop bug tracker and I found this bug: https://bugs.freedesktop.org/show_bug.cgi?id=53566 Might it be related? To your problem, no. But maybe you'll want to use the 3.4 longterm kernel to save yourself from

Bug#694734: adjusting severity

2012-11-29 Thread Helmut Grohne
Control: severity -1 important Javier Domingo wrote: nouveau driver is not recognising GTX560 The definition of critical includes affecting all users. This is not the case. A little more information such as pciids would be welcome as well. Helmut -- To UNSUBSCRIBE, email to

Bug#694734: adjusting severity

2012-11-29 Thread Javier Domingo
Oh! I thought it was that affected _all_ GTX560 users. But ok, I have compiled v3.6 and it recognises it, but goes into fallback mode, I have wrote to nouveau mailing list, but I had no answer yet, so I will create a bug, and link it here. Javier Domingo 2012/11/29 Helmut Grohne

Bug#694734: adjusting severity

2012-11-29 Thread Sven Joachim
On 2012-11-29 18:19 +0100, Javier Domingo wrote: Oh! I thought it was that affected _all_ GTX560 users. Even then the severity would be wrong, because the driver controls many other cards just fine. But ok, I have compiled v3.6 and it recognises it, but goes into fallback mode, Maybe you

Bug#694734: adjusting severity

2012-11-29 Thread Sven Joachim
On 2012-11-29 18:38 +0100, Javier Domingo wrote: I can't now at the moment access to the computer, but I can attach what I sent there, the dmesg output and the Xorg.0.log output. I must say that with kernel 3.2 the computer doesn't boot, or at least it tells me about non-recognised ports and

Bug#694734: adjusting severity

2012-11-29 Thread Javier Domingo
Hello, I have been searching around freedesktop bug tracker and I found this bug: https://bugs.freedesktop.org/show_bug.cgi?id=53566 Might it be related? BTW, I found that you were right with CONFIG_DRM_NOUVEAU. I also, may include that I found a bug in nvidia driver that I reported.