Bug 162838

Created attachment 116560 [details]
dmesg

Created attachment 116561 [details]
messages

Created attachment 116562 [details]
Xorg.0.log

[This comment has been added as a mass update for all FC4 kernel bugs.
 If you have migrated this bug from an FC3 bug today, ignore this comment.]

Please retest your problem with todays 2.6.12-1.1398_FC4 update.

If your problem involved being unable to boot, or some hardware not being
detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE*
installing any kernel updates.
If in doubt, you can recreate this file using..

mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak
mv /etc/modprobe.conf /etc/modprobe.conf.bak
kudzu


Thank you.

I am up to date with yum and still intermittently get the same problem.

`uname -r`:
> 2.6.12-1.1398_FC4smp

I forgot to mention that it is a PS2 mouse.

Since it either works from the start or is broken from the start I guess that it
is some kind of initialization issue. That is also supported by the fact that
all I have to do to get the mouse working is `shutdown -r now`, and the fact
that the same hardware worked on FC3 and Windows.

This is a clean install of FC4, with no hand-edits of /etc/sysconfig/hwconf or
/etc/modprobe.conf.

(I prefer to fresh install and just keep my /home partition.)

This bug is still present in the most recently released FC4 kernel.

`uname -r`
> 2.6.12-1.1447_FC4smp

PS. I made the Bug Summary more descriptive of the actual problem.

I have the same problem. I had the mouse problem initially when I updated the
kernel. But somehow a reboot solved the problem. However, I just updated the
kernel to the latest 2.6.12-1.1456_FC4 and the mouse completely stopped working.
The mouse is a wireless USB mouse that is plugged into a ps2 adaptor.

Unfortunately 2.6.12-1.1456 also made my problem a lot worse.
Now I sometimes have to boot the system four times before the mouse will work.
I have also now seen the mouse start working, then after moving 1 inch die.

I changed the severity to High since the problem now happens on most boots.

Mass update to all FC4 bugs:

An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (2.6.13.2). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.

Please retest with this update, and update this bug if necessary.

Thanks.

`uname -r`:
> 2.6.13-1.1526_FC4smp

I was hopeful, but alas, on the second boot the mouse was unresponsive.

Mass update to all FC4 bugs:

An update has been released (2.6.14-1.1637_FC4) which rebases to a new upstream
kernel (2.6.13.2). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.

Please retest with this update, and update this bug if necessary.

Thanks.

`uname -r`
>2.6.14-1.1637_FC4smp

Still here. I noticed from the fedora list that others have similar problems
when they use kvm switches, but this is without a kvm switch.

I am willing to test or send logs if it will help. Currently I don't reboot very
often to avoid the bug, but this is far from ideal.

My power bill (and wife) will be happier when this is fixed.

`uname -r`
>2.6.14-1.1653_FC4smp

The mouse now works! I am not sure if the new kernel or some other package fixed
the bug, but since the bug never got any attention I will remain happy that it
is gone.

Thanks to all the unknown soul who fixed the problem.

PS. I hope I set the status correctly.

Created attachment 608684 [details]
output of dmesg

Created attachment 608685 [details]
output of lscpi command

Created attachment 608687 [details]
contents of /var/log/messages