855gm and kernel 2.6.35-22.34 mouse cursor invisible

Bug #660380 reported by Vladimir Psenicka
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: linux-image-generic

Bug still present in latest kernel 2.6.35-22.34, after installing Leann Ogasawara older kernel (2.6.35-22-generic #32+lp614176) cursor is visible again.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.32+lp614176
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.32+lp614176-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ladas 1083 F.... lxpanel
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801DBICH4'/'Intel 82801DB-ICH4 with AD1981B at irq 11'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 28
   Simple ctrls : 20
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 1VHT28WW-1.04'
   Mixer name : 'ThinkPad EC 1VHT28WW-1.04'
   Components : ''
   Controls : 2
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
   Playback channels: Mono
   Limits: Playback 0 - 14
   Mono: Playback 10 [71%] [off]
Date: Thu Oct 14 10:35:39 2010
HibernationDevice: RESUME=UUID=1ea19439-217c-4552-91b7-e93b6d8b50dc
InstallationMedia: Lubuntu 10.10 "Maverick Meerkat" - i386 (20101010)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: IBM 18342LG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=b52de3db-4c68-4673-abe8-cc3daa4117f8 ro quiet splash
ProcEnviron:
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38
RfKill:

SourcePackage: linux
dmi.bios.date: 12/08/2006
dmi.bios.vendor: IBM
dmi.bios.version: 1WET90WW (2.10 )
dmi.board.name: 18342LG
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr1WET90WW(2.10):bd12/08/2006:svnIBM:pn18342LG:pvrThinkPadR50e:rvnIBM:rn18342LG:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 18342LG
dmi.product.version: ThinkPad R50e
dmi.sys.vendor: IBM

Revision history for this message
Vladimir Psenicka (vladimir-psenicka) wrote :
Revision history for this message
Veleno (veleno) wrote :

My 2 cents (filed bug report 661037, until I found this).
I'm experiencing the same issue stated in bug 614176: mouse cursor is invisible (but active), a suspend/resume usually brings the pointer back.
So far:
- pointer visible in Leann Ogasawara's 2.6.35-22.32+lp614176 (http://people.canonical.com/~ogasawara/lp614176/i386/)
- no joy with Brian Rogers' 2.6.35-ppa21+v9+pollparam.30, stuck at splash screen. (https://launchpad.net/~brian-rogers/+archive/graphics-fixes).

Revision history for this message
Vladimir Psenicka (vladimir-psenicka) wrote :

I can't see if suspend/resume because it isn't working on my R50e. After suspend I can't resume notebook (black screen and system is not responding)

Revision history for this message
Veleno (veleno) wrote :

Problem still in place with today's kernel update 2.6.35-22.35.

Revision history for this message
Veleno (veleno) wrote :

Tested with today's current mainline build, cursor is now visible.
Please notice that actual mainline is 2.36 and today's kernel from repos is 2.35.

http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/

veleno@alustriel:~$ uname -a
Linux alustriel 2.6.36-999-generic #201010180905 SMP Mon Oct 18 10:24:46 UTC 2010 i686 GNU/Linux
veleno@alustriel:~$ sudo dpkg --list |grep 201010180905
ii linux-headers-2.6.36-999 2.6.36-999.201010180905 Header files related to Linux kernel version 2.6.36
ii linux-headers-2.6.36-999-generic 2.6.36-999.201010180905 Linux kernel headers for version 2.6.36 on x86/x86_64
ii linux-image-2.6.36-999-generic 2.6.36-999.201010180905 Linux kernel image for version 2.6.36 on x86/x86_64

Revision history for this message
Veleno (veleno) wrote :

Issue still gone with 2.6.36-999-generic #201010201332 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
Still present with 2.6.35-22.35.
Both using latest xserver-xorg-video-intel driver 2:2.13.0+git20101020~glasen~maverick~ppa1 from
https://launchpad.net/~glasen/+archive/intel-driver
Will try also 855gm-fix-dkms 0.8.0~glasen~maverick~ppa1 (DKMS Source for the 855gm-fix kernel module) for 2.6.35-22.35 from
https://launchpad.net/~glasen/+archive/855gm-fix

Revision history for this message
Veleno (veleno) wrote :

Tried with DKMS from 855gm-fix-dkms 0.8.0~glasen~maverick~ppa1: issue still present in 2.6.35-22.35.

Revision history for this message
Veleno (veleno) wrote :

Mouse cursor shows on following daily builds:
- 2.6.36-997-generic #201010211126 (http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/)
- 2.6.36-020636-generic #201010210905 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.36-maverick/)

Used on both: xserver-xorg-video-intel driver 2:2.13.0+git20101020~glasen~maverick~ppa1.
Not used: 855gm-fix-dkms 0.8.0~glasen~maverick~ppa1 (errors during compiling on both versions, that's the reason of 2.6.36-020636-generic's choice).

Revision history for this message
Veleno (veleno) wrote :

Done daily standard updates (apt-get update/upgrade cycle) and removed any mainline build.
Rebuilt dkms modules against 2.6.35-22-generic: mouse pointer is now visible with 2.6.35-22.35.
The DKMS modules rebuilding process was embedded in the removal of other kernels (done via apt-get remove), the system is actually using 855gm-fix and ipheth in dkms.

Revision history for this message
Jim Rees (rees) wrote :

This is what fixed it for me:
http://lkml.org/lkml/2010/9/24/108

affects: linux-meta (Ubuntu) → linux (Ubuntu)
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Vladimir Psenicka, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.