Bug 13526 - no input for X
Summary: no input for X
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: Input Devices (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_input-devices
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-13 12:29 UTC by Riccardo Magliocchetti
Modified: 2009-06-13 15:49 UTC (History)
0 users

See Also:
Kernel Version: post 2.6.30 git
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
x.org log, see last line (24.48 KB, application/x-trash)
2009-06-13 12:29 UTC, Riccardo Magliocchetti
Details
latest git dmesg (not working) (28.06 KB, application/octet-stream)
2009-06-13 12:30 UTC, Riccardo Magliocchetti
Details
2.6.30-rc8 dmesg, working ok (34.39 KB, application/octet-stream)
2009-06-13 12:31 UTC, Riccardo Magliocchetti
Details
2.6.30 config (63.28 KB, application/octet-stream)
2009-06-13 12:32 UTC, Riccardo Magliocchetti
Details
2.6.30-rc8 config (62.46 KB, application/octet-stream)
2009-06-13 12:32 UTC, Riccardo Magliocchetti
Details

Description Riccardo Magliocchetti 2009-06-13 12:29:47 UTC
Created attachment 21892 [details]
x.org log, see last line

latest commit is: f3ad116588151b3371ae4e092290e4f48e62b8bb

After upgrading to latest git hal can't setup input for X, i can use sysrq keys though. 2.6.30 was fine but i have only a 2.6.30-rc8 at hand which is working fine too.

Attached the X.org log, see last line, will post dmesg and config for both kernels.
Comment 1 Riccardo Magliocchetti 2009-06-13 12:30:54 UTC
Created attachment 21893 [details]
latest git dmesg (not working)
Comment 2 Riccardo Magliocchetti 2009-06-13 12:31:34 UTC
Created attachment 21894 [details]
2.6.30-rc8 dmesg, working ok
Comment 3 Riccardo Magliocchetti 2009-06-13 12:32:07 UTC
Created attachment 21895 [details]
2.6.30 config
Comment 4 Riccardo Magliocchetti 2009-06-13 12:32:37 UTC
Created attachment 21896 [details]
2.6.30-rc8 config
Comment 5 Riccardo Magliocchetti 2009-06-13 15:49:51 UTC
The issue is simply that hal requires inotify. Closing this as invalid, sorry for the noise.

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