Bug 9406 - Missing uevents from the kernel when the adi joystick module is loaded
Summary: Missing uevents from the kernel when the adi joystick module is loaded
Status: RESOLVED OBSOLETE
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: 2007-11-19 08:32 UTC by Christopher Brown
Modified: 2014-03-29 19:32 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.31
Subsystem:
Regression: Yes
Bisected commit-id:

Attachments
Output of "udevmonitor --env" for the working kernel (2.13 KB, text/plain)
2008-01-28 14:31 UTC, Bjoern Rasmussen 		Details
utput of "udevmonitor --env" for the non-working kernel (360 bytes, text/plain)
2008-01-28 14:33 UTC, Bjoern Rasmussen 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Christopher Brown 2007-11-19 08:32:33 UTC 
Most recent kernel where this bug did not occur: 2.6.18-1.2200.fc5
Distribution: Fedora 7
Hardware Environment: Logitech Wingman Extreme Digital
Software Environment: 
Problem Description: Due to missing uevents from the kernel when the adi joystick module is loaded, the /dev/input/js0 file is not created and hardware therefore unusable.

Steps to reproduce: Attach said hardware via gameport and boot system.
Comment 1 Christopher Brown 2007-11-19 08:35:38 UTC 
For more information please see:

https://bugzilla.redhat.com/show_bug.cgi?id=252193
Comment 2 Dmitry Torokhov 2007-11-19 14:17:11 UTC 
Do you see input devices corresponding to the joystick reported in dmesg? Also, if you build the driver as a module, do you see any erors reported at modprobe time?
Comment 3 Bjoern Rasmussen 2007-11-20 13:29:27 UTC 
Nothing in dmesg, no errors when modules are loaded.

I ran udevmonitor both for a working and non-working kernel.  This probably gives you some hints.  See the link above for attachments of the output!

Thanks for your help!
Comment 4 Bjoern Rasmussen 2008-01-28 14:23:10 UTC 
I'll enclose above mentioned attachments to this bug.  By the way, problem still exists in Fedora 8 with the newest kernel update (uname -a: "Linux host.domain 2.6.23.14-107.fc8 #1 SMP Mon Jan 14 22:07:11 EST 2008 x86_64 x86_64 x86_64 GNU/Linux").
Comment 5 Bjoern Rasmussen 2008-01-28 14:31:21 UTC 
Created attachment 14630 [details]
Output of "udevmonitor --env" for the working kernel
Comment 6 Bjoern Rasmussen 2008-01-28 14:33:00 UTC 
Created attachment 14631 [details]
utput of "udevmonitor --env" for the non-working kernel
Comment 7 Bjoern Rasmussen 2010-02-23 20:01:21 UTC 
Updated my system (yum update) a couple of days ago.  Current kernel is
now kernel-2.6.31.12-174.2.19.fc12.x86_64.  Still no remedy.
Comment 8 Bjoern Rasmussen 2010-11-24 20:34:53 UTC 
Updated my system (yum update) today.  Current kernel is now kernel-2.6.35.6-48.fc14.x86_64.  Still no remedy.
Comment 9 Tibor Misuth 2014-02-23 17:03:42 UTC 
The bug is still present in 3.13 kernel. 
It was marked as Resolved / obsolete that is not 100% correct. Shall I file a new bug to track it, or can this one be reopened.
I'd like my Logitech Wingman Extreme working in Linux.

Thanks for help
Comment 10 Alan 2014-02-23 20:22:29 UTC 
New bug is I think best..
Comment 11 Bjoern Rasmussen 2014-03-29 19:32:08 UTC 
Tibor, did you file a new bug? Can you please add a link to it here?

I can confirm that there has been no change in this matter, since I opened this bug https://bugzilla.redhat.com/show_bug.cgi?id=252193 at Red Hat Bugzilla, back in 2007!

My kernel:

$ uname -r
3.12.9-301.fc20.x86_64
Note You need to log in before you can comment on or make changes to this bug.