Created attachment 31042 [details] xorg log with modedebug on When I log in to my GNOME desktop, the mouse pointer disappears. This issue has appeared after distribution upgrade to latest Xorg/intel drivers, so I am quite sure that it is not related to the desktop environment. It goes like this: - GDM starts (mouse pointer visible) - I log in (mouse pointer disappears) - I change resolution (pointer reappears) - I revert to my favourite resolution (it disappears again) - I open a terminal window, I close a Firefox tab - sometimes (quite rarely though) the pointer appears again - I launch Lgeneral game that supports mouse and has its own mouse pointer -- the mouse pointer appears. This works every time (so this is the first thing I do after I log in). Generally, when the pointer appears, it alway stays unless I play with the resolution. My system's config: Archlinux 2.6.31.5 xorg-server 1.7.1.901 xf86-video-intel 2.9.1 I use UMS since KMS is broken, probably because of my old CRT.
I am also having this problem after an upgrade from openSUSE 11.1 to 11.2. Cursor is not visible but I can move it. If the screensaver runs, then I will get the cursor back. If I switch to vt1 and back to X, the cursor will show up. xorg-x11 7.4 X.Org X Server 1.6.5 GNU/Linux 2.6.31.5-0.1-default (II) Loading /usr/lib/xorg/modules//drivers/intel_drv.so (II) Module intel: vendor="X.Org Foundation" compiled for 1.6.5, module version = 2.9.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 5.0 (II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM (II) UXA(0): Driver registered support for the following operations: (II) solid (II) copy (II) composite (RENDER acceleration) (==) intel(0): Backing store disabled (==) intel(0): Silken mouse enabled (II) intel(0): Initializing HW Cursor (II) intel(0): Fixed memory allocation layout: (II) intel(0): 0x00000000-0x00000fff: power context (4 kB) (II) intel(0): 0x0077f000: end of stolen memory (II) intel(0): 0x0077f000-0x0fffffff: DRI memory manager (254468 kB) (II) intel(0): 0x10000000: end of aperture (II) intel(0): BO memory allocation layout: (II) intel(0): 0x0077f000: start of memory manager (II) intel(0): 0x0079f000-0x01932fff: front buffer (18000 kB) X tiled (II) intel(0): 0x0279f000-0x0279ffff: overlay registers (4 kB) (II) intel(0): 0x027a0000-0x027a9fff: HW cursors (40 kB) (II) intel(0): 0x10000000: end of memory manager
Gentoo downstream bug with a few users who can reproduce : http://bugs.gentoo.org/291582 Cheers
I don't know if it's the same problem but in my case the mouse pointer doesn't re-appear if I close and then open my notebook lid Intel i915 xf86-video-intel-2.9.1 xorg-server-1.6.3.901
Hi I was forced to update today to x11-base/xorg-server with goes along with x11-drivers/xf86-video-intel-2.9.1 which produces a invisible mouse again. I thought this problem was already fixed ? When will it be? What shall I do? Linux gentoo 2.6.28-hardened-r7 (also tried a much newer kernel) Xfce Version 4.6.1 I can reproduce this BUG if needed and provied more INFO just tell me what. greetings
I have the same Problem here. xf86-video-intel-2.9.1 xorg-drivers-1.6 xorg-server-1.6.5-r1 xorg-cf-files-1.0.2 For more informations just ask :)
I solved the problem for xfce 4.6.1 with removeing .config/xfce4/xfconf/xfce-perchannel-xml/displays.xml and restarting X server. Works only for me when I set 60Hz for display otherways the mouse is still invisible. so just a crappy workaround hoppe you have more luck post it here. share your solutions.
This has been reported in the openSUSE tracker, too. Many users have this issue. See http://bugzilla.novell.com/show_bug.cgi?id=555915 .
(In reply to comment #7) > This has been reported in the openSUSE tracker, too. Many users have this > issue. > See http://bugzilla.novell.com/show_bug.cgi?id=555915 . > Sorry, I posted the wrong address. The correct one is: https://bugzilla.novell.com/show_bug.cgi?id=544930
Hmm, this wouldn't have been a flushing side-effect fixed by commit e7b526bb852cdd67b24e174da6850222f8da41b1 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Wed Jun 2 08:30:48 2010 +0100 drm/i915: Move non-phys cursors into the GTT Cursors need to be in the GTT domain when being accessed by the GPU. Previously this was a fortuitous byproduct of userspace using pwrite() to upload the image data into the cursor. The redundant clflush was removed in commit 9b8c4a and so the image was no longer being flushed out of the caches into main memory. One could also devise a scenario where the cursor was rendered by the GPU, prior to being attached as the cursor, resulting in similar corruption due to the missing MI_FLUSH. Fixes: Bug 28335 - Cursor corruption caused by commit 9b8c4a0b21 https://bugs.freedesktop.org/show_bug.cgi?id=28335 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reported-and-tested-by: Jeff Chua <jeff.chua.linux@gmail.com> Tested-by: Linus Torvalds <torvalds@linux-foundation.org> Reported-by: Andy Isaacson <adi@hexapodia.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> in 2.6.35-rc2? Seems like a long shot, but I have no other suggestions for a disappearing cursor at present.
Dumping the registers with intel_reg_dumper would be useful to check the CURABASE and CURAPOS. From the description that the mice stay invisible until reset, my guess is that CURACNTL is bogus. Another patch that may have fixed this as a side-effect: commit 3707bfcbff8a72aafcc4f0549c9d6f5fe5c09838 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Wed Jul 7 13:25:58 2010 +0100 drm/i915: Unset cursor if out-of-bounds upon mode change (v4) The docs warn that to position the cursor such that no part of it is visible on the pipe is an undefined operation. Avoid such circumstances upon changing the mode, or at any other time, by unsetting the cursor if it moves out of bounds. "For normal high resolution display modes, the cursor must have at least a single pixel positioned over the active screen.” (p143, p148 of the hardware registers docs). Fixes: Bug 24748 - [965G] Graphics crashes when resolution is changed with KMS enabled https://bugs.freedesktop.org/show_bug.cgi?id=24748 v2: Only update the cursor registers if they change. v3: Fix the unsigned comparision of x,y against width,height. v4: Always set CUR.BASE or else the cursor may become corrupt. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reported-by: Christian Eggers <ceggers@gmx.de> Cc: Christopher James Halse Rogers <chalserogers@gmail.com> Cc: stable@kernel.org Besides missing flushed, invalid registers, it may be a case of the cursor self-refresh programming being broken, again something that has been altered since the original bug was filled.
Ping? Can anyone confirm the existence of this bug on the upstream stack? Excluding 855GM users!
Timeout.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.