Bug 118755 - ps2 mouse disabled after Suse 9.1 to 10 RC1 upgrade
Summary: ps2 mouse disabled after Suse 9.1 to 10 RC1 upgrade
Status: RESOLVED FIXED
: 118166 (view as bug list)
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: RC 1
Hardware: i586 SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Marcus Schaefer
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-26 06:27 UTC by William Laxson
Modified: 2005-10-18 10:42 UTC (History)
3 users (show)

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
y2logs (524.05 KB, application/x-gtar)
2005-09-27 05:23 UTC, William Laxson
Details
Hardware Info text file (170.72 KB, text/plain)
2005-09-27 05:27 UTC, William Laxson
Details
New and old config files (20.00 KB, application/x-tar)
2005-10-12 16:07 UTC, Stefan Nordhausen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description William Laxson 2005-09-26 06:27:11 UTC
Before upgrade all system components working fine.

Performed automatic upgrade from 9.1 to 10 RC1.  After CD1 installation complete
and reboot, ps2 mouse (Microsoft 2 button) on ps2 mouse port did not work.  
Completed installation with keyboard shortcuts, then used YAST via keyboard
shortcuts to probe mouse configuration.  YAST reports no mouse selected. 
Selected PS2 mouse from list and saved and restarted GUI, and mouse started
working correctly once again.

Whitebox PC:

CPU:  AMP Athlon Xp 2500+
Video:  GE Force TI 4200 W/AGP 8X
Main Memory 512 MB
Comment 1 Michael Radziej 2005-09-26 13:49:30 UTC
Please attach the complete /var/log/YaST2 directory and hwinfo.
See http://www.opensuse.org/Bug_Reporting_FAQ#YaST
Comment 2 Steffen Winterfeldt 2005-09-26 14:29:26 UTC
Sorry, but yast does the update. There were some major changes meanwhile, like 
xfree->xorg and static /dev -> udev & hotplug. No idea how this affects 
updates. 
 
You better start practicing for the sles9 -> sles10 move. :-) 
Comment 3 Michael Radziej 2005-09-26 14:47:23 UTC
Hmm, then I hope the yast2-update maintainer is the right one ;-)
Comment 4 Jiri Srain 2005-09-26 14:58:55 UTC
Mouse is Marcus's playground. 
Comment 5 William Laxson 2005-09-27 05:23:14 UTC
Created attachment 50897 [details]
y2logs 

Log files as requested
Comment 6 William Laxson 2005-09-27 05:27:22 UTC
Created attachment 50898 [details]
Hardware Info text file

HW Info as requested.
Comment 7 Marcus Schaefer 2005-09-27 14:01:58 UTC
*** Bug 118166 has been marked as a duplicate of this bug. ***
Comment 8 Marcus Schaefer 2005-09-28 12:34:30 UTC
To know what happened here I need the original X11 configuration file 
from your 9.1 installation. Without this information I cannot do much 
Comment 9 Stefan Nordhausen 2005-10-11 20:31:53 UTC
Also had a dead mouse (USB Logitech) after update from 9.2 to 10.0 final.
Marcus, exactly which files from the original config do you need? I still have a
complete image of the original partition, so that wouldn't be a problem for me.
Comment 10 Marcus Schaefer 2005-10-12 10:37:22 UTC
cool, in that case please provide the old configuration from your partition 
which is named /etc/X11/XF86Config and the new file of your current  
configuration which has been relinked to /etc/X11/xorg.conf 
 
You should know that my code isn't called in case of update so I assume 
some kind of post install scripts... well let's compare the files 
 
Thanks 
Comment 11 Stefan Nordhausen 2005-10-12 16:05:31 UTC
Ok.... I think I'll need to buy a new backup-device. *grrr* But good I found out
before it is too late.

Fortunately, the system itself made backup copies of XF86Config in 2004, which
match the backup copies it must have made during update. So the data is not
lost. I'll attach both versions.
Comment 12 Stefan Nordhausen 2005-10-12 16:07:10 UTC
Created attachment 53849 [details]
New and old config files
Comment 13 Marcus Schaefer 2005-10-18 10:42:56 UTC
Thanks, I added an update path to fix that problem