Bug 158059 - Kernel 2.6.11-1.1312_FC4 breaks input from both synaptics and mouse
Kernel 2.6.11-1.1312_FC4 breaks input from both synaptics and mouse
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-05-18 05:33 EDT by Bojan Smojver
Modified: 2015-01-04 17:19 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-18 17:27:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
X configuration file (3.01 KB, text/plain)
2005-05-18 05:33 EDT, Bojan Smojver
no flags Details
dmesg output of the 1305 kernel (14.29 KB, text/plain)
2005-05-18 17:20 EDT, Bojan Smojver
no flags Details

  None (edit)
Description Bojan Smojver 2005-05-18 05:33:00 EDT
Description of problem:
After the upgrade to this development kernel (from 1305), mouse input does not
work any more (although both devices are configured - see xorg.conf), only
touchpad does.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run X on this kernel with the attached xorg.conf on HP ZE4201 notebook.

Actual results:
Mouse doesn't work.

Expected results:
Both the touchpad and mouse should work, as they do with previously released
kernel, 1305.

Additional info:
Comment 1 Bojan Smojver 2005-05-18 05:33:00 EDT
Created attachment 114498 [details]
X configuration file
Comment 2 Dave Jones 2005-05-18 16:26:25 EDT
there are no changes betweem 1305 and 1312 that could explain this.
Can you paste a diff -u output between dmesg output of both kernels ?
They should be identical as far as the input layer is concerned.
The only changes were e1000 driver, slab poison detector, scsi geometry, serial
console, max num of cpus on x86-64, and updated audit patches.

was there an X update as well perhaps ? Maybe something changed there.
Comment 3 Bojan Smojver 2005-05-18 17:20:02 EDT
Created attachment 114535 [details]
dmesg output of the 1305 kernel
Comment 4 Bojan Smojver 2005-05-18 17:27:07 EDT
Just booted 1312 and both devices work.

So, the official cause of this bug is drug induced state of the reporter :-(

I have no idea now why it didn't want to work the first time I booted 1312...
Obviuosly, not a bug. Sorry for wasting resources before the release.

Note You need to log in before you can comment on or make changes to this bug.