Bug#268759: [nv] Sarge xserver-xfree86 breaks display
On Fri, Oct 08, 2004 at 10:23:46PM -0300, Margarita Manterola wrote: > Hola Branden Robinson! > > > I realize this bug has since been resolved, but in the future, *please* use > > the "reportbug" command to file bugs, particularly against the > > xserver-xfree86 and xserver-xfree86-dbg packages. > > Uh, ok... But may I ask why? I mean, what I did wrong? I kind of like > not using reportbug :) What you did wrong was not using reportbug when I have provided information-gathering bug scripts that are automatically used by reportbug. :) > If it's because of the versions and stuff, in this particular case it > would have no effect, because I was reporting a bug from home, while the > bug was actually happening at Uni. Nope, that's not why. Please see /usr/share/bug/xserver-xfree86. :) -- G. Branden Robinson| If the jury can count higher than Debian GNU/Linux | two, the case will fail. [EMAIL PROTECTED] | -- Tom Lane, on Forgent's claim of http://people.debian.org/~branden/ |a patent on JPEG signature.asc Description: Digital signature
Bug#268759: [nv] Sarge xserver-xfree86 breaks display
Hola Branden Robinson!
> I realize this bug has since been resolved, but in the future, *please* use
> the "reportbug" command to file bugs, particularly against the
> xserver-xfree86 and xserver-xfree86-dbg packages.
Uh, ok... But may I ask why? I mean, what I did wrong? I kind of like
not using reportbug :)
If it's because of the versions and stuff, in this particular case it
would have no effect, because I was reporting a bug from home, while the
bug was actually happening at Uni.
(I had to leave in a hurry and I was not returning to the lab in a week,
so I wanted to report the bug, eventhough I was not in the machine).
--
Besitos, {o_
Marga. (')_
Bug#268759: [nv] Sarge xserver-xfree86 breaks display
On Sat, Aug 28, 2004 at 08:34:46PM -0300, Margarita Manterola wrote: > In one of the labs I administer, we just updated all our machines to the > latest Sarge and all the boxes that were using the "nv" driver had the > same problem: the mouse pointer was a big garbage square, and the video had > problems in general, lots of garbage on screen. Margarita, I realize this bug has since been resolved, but in the future, *please* use the "reportbug" command to file bugs, particularly against the xserver-xfree86 and xserver-xfree86-dbg packages. -- G. Branden Robinson| Never attribute to conspiracy that Debian GNU/Linux | which can be adequately explained [EMAIL PROTECTED] | by economics. http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Bug#268759: [nv] Sarge xserver-xfree86 breaks display (fwd)
Margarita please keep the bug in CC otherwise these information might be lost. Fabio -- fajita: step one Whatever the problem, step one is always to look in the error log. fajita: step two When in danger or in doubt, step two is to scream and shout. -- Forwarded message -- Date: Fri, 10 Sep 2004 22:50:39 -0300 From: Margarita Manterola <[EMAIL PROTECTED]> To: Fabio Massimo Di Nitto <[EMAIL PROTECTED]> Subject: Re: Bug#268759: [nv] Sarge xserver-xfree86 breaks display Hola Fabio Massimo Di Nitto! > > > It would be very nice if you could try the latest packages from sid on one > > > of the machines. The nv driver has been update quite recently and perhaps > > > it fixes this problem. Sorry i can't be more specific at the moment, but > > > it would be very nice if you could test it for us. > > I did. No change at all. > Which version from sid? I just recently uploaded -7 Ok, I just tested with -7. **Big disaster** I could not have any video, not with the nv options listed before, not without them, not with the vesa driver. I had to downgrade back to the sarge version. Since there are different machines here, I'll test it on a different one, but this is clearly RC. This is the lspci of the machine I'm sitting at right now: :00:00.0 Host bridge: nVidia Corporation nForce CPU bridge (rev b2) :00:00.1 RAM memory: nVidia Corporation nForce 220/420 Memory Controller (rev b2) :00:00.2 RAM memory: nVidia Corporation nForce 220/420 Memory Controller (rev b2) :00:00.3 RAM memory: nVidia Corporation: Unknown device 01aa (rev b2) :00:01.0 ISA bridge: nVidia Corporation nForce ISA Bridge (rev c3) :00:01.1 SMBus: nVidia Corporation nForce PCI System Management (rev c1) :00:02.0 USB Controller: nVidia Corporation nForce USB Controller (rev c3) :00:03.0 USB Controller: nVidia Corporation nForce USB Controller (rev c3) :00:06.0 Multimedia audio controller: nVidia Corporation nForce Audio (rev c2) :00:08.0 PCI bridge: nVidia Corporation nForce PCI-to-PCI bridge (rev c2) :00:09.0 IDE interface: nVidia Corporation nForce IDE (rev c3) :00:1e.0 PCI bridge: nVidia Corporation nForce AGP to PCI Bridge (rev b2) :01:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) :02:00.0 VGA compatible controller: nVidia Corporation NVCrush11 [GeForce2 MX Integrated Graphics] (rev b1) And the VGA part from the /proc/pci VGA compatible controller: PCI device 10de:01a0 (nVidia Corporation) (rev 177). IRQ 11. Master Capable. Latency=32. Min Gnt=5.Max Lat=1. Non-prefetchable 32 bit memory at 0xec00 [0xecff]. Prefetchable 32 bit memory at 0xf000 [0xf7ff]. -- Bessos, Maggie.
Bug#268759: [nv] Sarge xserver-xfree86 breaks display
Hola Fabio Massimo Di Nitto!
> > > It would be very nice if you could try the latest packages from sid on one
> > > of the machines. The nv driver has been update quite recently and perhaps
> > > it fixes this problem. Sorry i can't be more specific at the moment, but
> > > it would be very nice if you could test it for us.
> > I did. No change at all.
> Which version from sid? I just recently uploaded -7
The one that was in sid last saturday afternoon (Sep 3rd 17:00 GMT).
Your upload was after that? I had understood that the changes to the nv
driver had already been uploaded.
Anyway, I'll try again tomorrow. I only tested with one machine, and I
think that not all of them have the same nv cards.
--
Besitos, {o_
Marga. (')_
Re: Bug#268759: [nv] Sarge xserver-xfree86 breaks display
hi Margarita, On Sat, 4 Sep 2004, Margarita Manterola wrote: > Hola Fabio Massimo Di Nitto! > > > It would be very nice if you could try the latest packages from sid on one > > of the machines. The nv driver has been update quite recently and perhaps > > it fixes this problem. Sorry i can't be more specific at the moment, but > > it would be very nice if you could test it for us. > > I did. No change at all. Which version from sid? I just recently uploaded -7 Fabio -- fajita: step one Whatever the problem, step one is always to look in the error log. fajita: step two When in danger or in doubt, step two is to scream and shout.
Bug#268759: [nv] Sarge xserver-xfree86 breaks display
Hola Fabio Massimo Di Nitto!
> It would be very nice if you could try the latest packages from sid on one
> of the machines. The nv driver has been update quite recently and perhaps
> it fixes this problem. Sorry i can't be more specific at the moment, but
> it would be very nice if you could test it for us.
I did. No change at all.
This is the lspci of the machine:
:00:00.0 Host bridge: nVidia Corporation nForce CPU bridge (rev b2)
:00:00.1 RAM memory: nVidia Corporation nForce 220/420 Memory
Controller (rev b2)
:00:00.2 RAM memory: nVidia Corporation nForce 220/420 Memory
Controller (rev b2)
:00:00.3 RAM memory: nVidia Corporation: Unknown device 01aa (rev
b2)
:00:01.0 ISA bridge: nVidia Corporation nForce ISA Bridge (rev c3)
:00:01.1 SMBus: nVidia Corporation nForce PCI System Management (rev
c1)
:00:02.0 USB Controller: nVidia Corporation nForce USB Controller
(rev c3)
:00:03.0 USB Controller: nVidia Corporation nForce USB Controller
(rev c3)
:00:05.0 Multimedia audio controller: nVidia Corporation: Unknown
device 01b0 (rev c2)
:00:06.0 Multimedia audio controller: nVidia Corporation nForce
Audio (rev c2)
:00:08.0 PCI bridge: nVidia Corporation nForce PCI-to-PCI bridge
(rev c2)
:00:09.0 IDE interface: nVidia Corporation nForce IDE (rev c3)
:00:1e.0 PCI bridge: nVidia Corporation nForce AGP to PCI Bridge
(rev b2)
:01:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
:02:00.0 VGA compatible controller: nVidia Corporation NVCrush11
[GeForce2 MX Integrated Graphics] (rev b1)
This is the excerpt from /proc/pci related to the VGA device:
Bus 2, device 0, function 0:
VGA compatible controller: PCI device 10de:01a0 (nVidia Corporation) (rev
177).
IRQ 11.
Master Capable. Latency=32. Min Gnt=5.Max Lat=1.
Non-prefetchable 32 bit memory at 0xeb00 [0xebff].
Prefetchable 32 bit memory at 0xf000 [0xf7ff].
--
Besitos, {o_
Marga. (')_
Re: Bug#268759: [nv] Sarge xserver-xfree86 breaks display
Hi Margarita, On Sat, 28 Aug 2004, Margarita Manterola wrote: > In one of the labs I administer, we just updated all our machines to the > latest Sarge and all the boxes that were using the "nv" driver had the > same problem: the mouse pointer was a big garbage square, and the video had > problems in general, lots of garbage on screen. It would be very nice if you could try the latest packages from sid on one of the machines. The nv driver has been update quite recently and perhaps it fixes this problem. Sorry i can't be more specific at the moment, but it would be very nice if you could test it for us. Thanks Fabio -- fajita: step one Whatever the problem, step one is always to look in the error log. fajita: step two When in danger or in doubt, step two is to scream and shout.
Bug#268759: [nv] Sarge xserver-xfree86 breaks display
Package: xserver-xfree86 Severity: important Hi! In one of the labs I administer, we just updated all our machines to the latest Sarge and all the boxes that were using the "nv" driver had the same problem: the mouse pointer was a big garbage square, and the video had problems in general, lots of garbage on screen. This could be easily solved by adding: Option "HWCursor" "false" Option "Accel" "false" To the Device section. It's an easy fix, although it's turning off 2D acceleration :-\. These machines were working fine with the previous Sarge version of xserver-xfree86, and we never used the proprietary drivers. Apparently some changes were made to the nv driver for NVidia support, that broke in these machines. These machines are not updated periodically. Last update was done about 5 or 6 months ago. So the change probably happened some time in that span (I know it's a lot, sorry for that). I'm sorry I don't have the complete hardware information, since I'm not in the lab right now. I hope you can have a look at this, and I'll try to submit the hardware information as soon as I can. Love, Marga.
