Processed: Re: Bug#689748: More info nouveau.noaccel=1 makes it much worse.

2013-03-12 Thread Debian Bug Tracking System
Processing control commands: > merge 686611 -1 Bug #686611 [xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: Distorted graphics with GeForce 4200Go (NV28) Bug #595447 [xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: Bad graphics on GeForce4 Ti 4200 Go AGP Bug #689748 [xserver-xorg

Bug#689748: More info nouveau.noaccel=1 makes it much worse.

2013-03-12 Thread Sven Joachim
Control: merge 686611 -1 On 2013-03-11 21:07 +0100, The Eclectic One wrote: > With the noaccel=1 option, the "random dots" symptom I previously described > and the illegible fonts are back to an extreme degree making all displays > totally unreadable. Moving the cursor, now a square fuzzy blob,

Bug#689748: More info nouveau.noaccel=1 makes it much worse.

2013-03-12 Thread Julien Cristau
On Mon, Mar 11, 2013 at 20:07:41 +, The Eclectic One wrote: > [32.143] (II) LoadModule: "glx" > [32.143] (II) Loading /usr/lib/xorg/modules/linux/libglx.so > [32.794] (II) Module glx: vendor="NVIDIA Corporation" > [32.794] compiled for 4.0.2, module version = 1.0.0 > [32.7

Bug#689748: More info nouveau.noaccel=1 makes it much worse.

2013-03-11 Thread The Eclectic One
Hello again, With the system updated today (03/09/13), standard wheezy kernel, with /etc/default/grub changed as follows: GRUB_CMDLINE_LINUX_DEFAULT="quiet nouveau.noaccel=1" and after running update-grub, the screens became totally unreadable. Both the main display and the secondary screen con

Bug#689748: More info, with nouveau.modeset=0 display stays dark permanently, also kernel 3.7

2013-02-26 Thread Julien Cristau
On Tue, Feb 26, 2013 at 09:38:09 +0100, Sven Joachim wrote: > On 2013-02-26 08:13 +0100, Julien Cristau wrote: > > > On Tue, Feb 26, 2013 at 07:07:48 +0100, Sven Joachim wrote: > > > >> Have you tried booting with nouveau.noaccel=1 yet? That seems to be the > >> only way to obtain stability on N

Bug#689748: More info, with nouveau.modeset=0 display stays dark permanently, also kernel 3.7

2013-02-26 Thread Sven Joachim
On 2013-02-26 08:13 +0100, Julien Cristau wrote: > On Tue, Feb 26, 2013 at 07:07:48 +0100, Sven Joachim wrote: > >> Have you tried booting with nouveau.noaccel=1 yet? That seems to be the >> only way to obtain stability on N4VE. >> > Sounds like we should make that the default in the kernel then

Bug#689748: More info, with nouveau.modeset=0 display stays dark permanently, also kernel 3.7

2013-02-25 Thread Julien Cristau
On Tue, Feb 26, 2013 at 07:07:48 +0100, Sven Joachim wrote: > Have you tried booting with nouveau.noaccel=1 yet? That seems to be the > only way to obtain stability on N4VE. > Sounds like we should make that the default in the kernel then? Cheers, Julien signature.asc Description: Digital sig

Bug#689748: More info, with nouveau.modeset=0 display stays dark permanently, also kernel 3.7

2013-02-25 Thread Sven Joachim
On 2013-02-25 23:38 +0100, The Eclectic One wrote: > So, replacing > GRUB_CMDLINE_LINUX_DEFAULT="quiet" > > with > > GRUB_CMDLINE_LINUX_DEFAULT="quiet nouveau.modeset=0" > > and running update-grub leaves the main screen dark. Without that > option, at some point the nvidia hardware is set up so

Bug#689748: More info, lock-ups sometimes not as severe

2013-02-23 Thread The Eclectic One
Hello again, Something has changed after the latest upgrade of the nouveau driver. Whereas before the machine wouldn't even turn off unless the power button was held for about 10 seconds, it is now the case that (sometimes) a quick press of the off button is caught and the machine shuts down clea

Bug#689748: More info: "unknown LVDS configuration bits, please report"

2013-02-04 Thread Sven Joachim
On 2013-02-02 22:44 +0100, The Eclectic One wrote: > Just noticed, on reboot after a lock up, the message in the subject line. > Looking back at the original bug report, dmesg data was included by > reportbug, but it was garbled (no new lines) so might have escaped notice. > > This is the complete

Bug#689748: More info: "unknown LVDS configuration bits, please report"

2013-02-02 Thread The Eclectic One
Hello again, Just noticed, on reboot after a lock up, the message in the subject line. Looking back at the original bug report, dmesg data was included by reportbug, but it was garbled (no new lines) so might have escaped notice. This is the complete line, with the 2 previous ones: [5.72306

Bug#689748: More info: glx failed, new Xorg.0.log

2013-01-16 Thread Sven Joachim
On 2013-01-16 22:24 +0100, The Eclectic One wrote: > As of January 15, 2013, with a totally up-to-date wheezy system, > tried to run openscad and it didn't work > > Xlib: extension "GLX" missing on display ":0". > Xlib: extension "GLX" missing on display ":0". > Xlib: extension "GLX" missing on

Bug#689748: More info: glx failed, new Xorg.0.log

2013-01-16 Thread The Eclectic One
Hello again, As of January 15, 2013, with a totally up-to-date wheezy system, tried to run openscad and it didn't work Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on display ":0". Xlib: extension "GLX" missing on

Bug#689748: More info, another backtrace

2013-01-12 Thread The Eclectic One
Hello again, On January 12, 2013, after an update (that upgraded dozens of kde libraries) and a reboot, I was quickly paging through a pdf document with evince and the system locked up again. After a hard power-off (holding the power button down for 5-10 seconds - the only way to regain access)

Bug#689748: More info

2012-12-27 Thread The Eclectic One
Hello again, As of December 26, 2012, with up-to-the-minute wheezy, installed xtide, which is available in a wheezy package. It has the same illegible font problem as gbuffy (as reported in the previous bug report addendum). So, this is not a gbuffy or old library problem... Any further test a

Bug#689748: More info

2012-12-21 Thread The Eclectic One
Hello again, As of December 21, 2012, with wheezy updated just now, the following still occurs: Moving any window (click on the title bar and drag) locks up the system instantly. As I currently have no other machines connected to a local network, I can't get in through ssh. All I can do is a h

Bug#689748: More info

2012-12-13 Thread The Eclectic One
Hello again, Due to circumstances beyond my control, I haven't been able to continue testing for the last few weeks. I recently did an upgrade where about 500 packages were updated, including xserver-xorg-video-nouveau and the kernel. Something has been fixed as the problem is now not repeatabl

Bug#689748: More info, sid dbg package.

2012-11-03 Thread Sven Joachim
Hello, sorry for not having responded earlier. On 2012-10-09 03:30 +0200, The Eclectic One wrote: > Hello, > > Per this page: > > http://wiki.debian.org/DebianUnstable#How_do_I_backport_a_sid_package_to_testing_or_stable.3F > > I did the following: > > added > deb-src http://ftp.us.debian.org/de

Bug#689748: More info, sid dbg package.

2012-10-08 Thread The Eclectic One
Hello, Per this page: http://wiki.debian.org/DebianUnstable#How_do_I_backport_a_sid_package_to_testing_or_stable.3F I did the following: added deb-src http://ftp.us.debian.org/debian/ sid main contrib non-free to /etc/apt/sources.list then: apt-get update apt-get build-dep xserver-xorg-video-