All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 15758] Invisible mouse pointer on NV4E (C51)
Date: Wed, 31 Dec 2008 11:57:38 -0800 (PST)	[thread overview]
Message-ID: <20081231195738.D38B1130057@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-15758-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>

http://bugs.freedesktop.org/show_bug.cgi?id=15758





--- Comment #4 from Ronald <ronald645-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>  2008-12-31 11:57:37 PST ---
Hello everyone,

I'm facing the same problem (invisible cursor) in this bugreport with my card
[1]. It happens whenever I use xrandr or switch VT's (also s2disk is affected).
Unloading and reloading the modules does not 'cure' it. However, it seems that
adding HWcursor with parameter 0 to the device section in xorg[2].conf seems to
work around this. I have build my own vanilla kernel[3] and pulled the drivers
from git[4]. I would like to help to solve this problem (if possible). I fairly
know my way around and this system is not important for stuff like e.g.
homework...

1: Charlie:~# lspci -v -v -s 00:05.0
00:05.0 VGA compatible controller: nVidia Corporation C51 [Geforce 6150 Go]
(rev a2) (prog-if 00 [VGA controller])
        Subsystem: Hewlett-Packard Company Presario V6133CL
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 18
        Region 0: Memory at b2000000 (32-bit, non-prefetchable) [size=16M]
        Region 1: Memory at c0000000 (64-bit, prefetchable) [size=256M]
        Region 3: Memory at b1000000 (64-bit, non-prefetchable) [size=16M]
        [virtual] Expansion ROM at 50000000 [disabled] [size=128K]
        Capabilities: [48] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0
Enable-
                Address: 0000000000000000  Data: 0000

2: X.Org X Server 1.4.2
Release Date: 11 June 2008
Build Operating System: Linux Debian (xorg-server 2:1.4.2-9)

3. Linux Charlie 2.6.28 #1 Sun Dec 28 17:27:07 CET 2008 i686 GNU/Linux

4. drm-58d557c73b9e4ad1964fd083abeec74875c141cb
xf86-video-nouveau-5d281a2439de1e8c1848b6b700f30476575966e0


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2008-12-31 19:57 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 18:36 [Bug 15758] New: Invisible mouse pointer on NV4E (C51) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-15758-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-04-29 19:18   ` [Bug 15758] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-15 17:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-06-16 13:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-12-31 19:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2009-01-03  3:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-22 12:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-22 23:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-23 21:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-26 19:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-01-26 19:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-07 20:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-07 20:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-07 23:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-08  9:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-08 12:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-02-08 14:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-04 22:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-05  9:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-07 10:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-02-24  5:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-02-24  6:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-02-24 11:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-23 13:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-23 14:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-23 14:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-08  4:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-08  4:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-19  8:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-19 16:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-08-26 10:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-19  8:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-25 16:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-25 19:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-20  1:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-04 11:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-05  6:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-22 22:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-23  7:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-24  0:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-24  6:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-24 14:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-24 16:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-25 17:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-02-25 17:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-19 15:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081231195738.D38B1130057@annarchy.freedesktop.org \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.