It seems that the es1371 driver (which provides its own joystick port driver)
is broken in at least 2.6.11-mm4. I don't know when it broke, but it used to
work around in the 2.6.8/9 days (I haven't used the joystick in awhile). The
hardware and joystick still both work (tested in Windows).
Where do I go from here?
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
Patrick McFarland <[email protected]> wrote:
>
> It seems that the es1371 driver (which provides its own joystick port driver)
> is broken in at least 2.6.11-mm4. I don't know when it broke, but it used to
> work around in the 2.6.8/9 days (I haven't used the joystick in awhile). The
> hardware and joystick still both work (tested in Windows).
>
Please define "broken". I assume that audio still comes out, but that the
joystick doesn't work?
On Sunday 20 March 2005 07:39 pm, Andrew Morton wrote:
> Patrick McFarland <[email protected]> wrote:
> > It seems that the es1371 driver (which provides its own joystick port
> > driver) is broken in at least 2.6.11-mm4. I don't know when it broke, but
> > it used to work around in the 2.6.8/9 days (I haven't used the joystick
> > in awhile). The hardware and joystick still both work (tested in
> > Windows).
>
> Please define "broken". I assume that audio still comes out, but that the
> joystick doesn't work?
Yup, audio works fine, this is why I never noticed. Also, the external midi
interface also works fine. Digging around, /proc/asound/card0/audiopci says
"Joystick enable: off, Joystick port: 0x200".
I've also been looking through alsa's cvs for alsa-kernel, and I can't see any
changes that might have broken it.
Also, I have a usb gamepad that currently works fine.
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Sunday 20 March 2005 21:04, Patrick McFarland wrote:
> On Sunday 20 March 2005 07:39 pm, Andrew Morton wrote:
> > Patrick McFarland <[email protected]> wrote:
> > > It seems that the es1371 driver (which provides its own joystick port
> > > driver) is broken in at least 2.6.11-mm4. I don't know when it broke, but
> > > it used to work around in the 2.6.8/9 days (I haven't used the joystick
> > > in awhile). The hardware and joystick still both work (tested in
> > > Windows).
> >
> > Please define "broken". I assume that audio still comes out, but that the
> > joystick doesn't work?
>
> Yup, audio works fine, this is why I never noticed. Also, the external midi
> interface also works fine. Digging around, /proc/asound/card0/audiopci says
> "Joystick enable: off, Joystick port: 0x200".
>
> I've also been looking through alsa's cvs for alsa-kernel, and I can't see any
> changes that might have broken it.
>
I could have broken it during my gameport sysfs integration... Although I can't
see anything that could cause the breakage. Can I please see your .config?
--
Dmitry
On Sunday 20 March 2005 10:21 pm, Dmitry Torokhov wrote:
> I could have broken it during my gameport sysfs integration... Although I
> can't see anything that could cause the breakage. Can I please see your
> .config?
Here.
For the curious, what was the first kernel to be released that had your sysfs
stuff in it?
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Monday 21 March 2005 19:58, Patrick McFarland wrote:
> On Sunday 20 March 2005 10:21 pm, Dmitry Torokhov wrote:
> > I could have broken it during my gameport sysfs integration... Although I
> > can't see anything that could cause the breakage. Can I please see your
> > .config?
>
> Here.
>
Looks good, I was wondering if you had GAMEPORT=m and SND_ENS1371=y.
> For the curious, what was the first kernel to be released that had your sysfs
> stuff in it?
>
2.6.11-mm and 2.6.12-rc1. Vanilla 2.6.11 does not have it.
Could you verify that you enabled joystick port on card? What does
"cat /sys/module/snd_ens1371/parameters/joystick_port" show?
--
Dmitry
On Monday 21 March 2005 10:15 pm, Dmitry Torokhov wrote:
> Looks good, I was wondering if you had GAMEPORT=m and SND_ENS1371=y.
Yes, that would be quite silly. ;)
> > For the curious, what was the first kernel to be released that had your
> > sysfs stuff in it?
>
> 2.6.11-mm and 2.6.12-rc1. Vanilla 2.6.11 does not have it.
I'll go compile 2.6.11 to see if it works there.
> Could you verify that you enabled joystick port on card? What does
> "cat /sys/module/snd_ens1371/parameters/joystick_port" show?
0,0,0,0,0,0,0,0
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Monday 21 March 2005 22:41, Patrick McFarland wrote:
> On Monday 21 March 2005 10:15 pm, Dmitry Torokhov wrote:
> > Looks good, I was wondering if you had GAMEPORT=m and SND_ENS1371=y.
>
> Yes, that would be quite silly. ;)
>
> > > For the curious, what was the first kernel to be released that had your
> > > sysfs stuff in it?
> >
> > 2.6.11-mm and 2.6.12-rc1. Vanilla 2.6.11 does not have it.
>
> I'll go compile 2.6.11 to see if it works there.
>
> > Could you verify that you enabled joystick port on card? What does
> > "cat /sys/module/snd_ens1371/parameters/joystick_port" show?
>
> 0,0,0,0,0,0,0,0
>
Ok, it looks like setup problem. Try doing:
modprobe snd-ens1371 joystick_port=1
--
Dmitry
On Monday 21 March 2005 10:49 pm, Dmitry Torokhov wrote:
> On Monday 21 March 2005 22:41, Patrick McFarland wrote:
> > On Monday 21 March 2005 10:15 pm, Dmitry Torokhov wrote:
> > > Looks good, I was wondering if you had GAMEPORT=m and SND_ENS1371=y.
> >
> > Yes, that would be quite silly. ;)
> >
> > > > For the curious, what was the first kernel to be released that had
> > > > your sysfs stuff in it?
> > >
> > > 2.6.11-mm and 2.6.12-rc1. Vanilla 2.6.11 does not have it.
> >
> > I'll go compile 2.6.11 to see if it works there.
> >
> > > Could you verify that you enabled joystick port on card? What does
> > > "cat /sys/module/snd_ens1371/parameters/joystick_port" show?
> >
> > 0,0,0,0,0,0,0,0
>
> Ok, it looks like setup problem. Try doing:
>
> modprobe snd-ens1371 joystick_port=1
I already tried that before I mailed the great and almighty source of all
information kernely (aka the lkml). Infact, I tried both joystick=1 and
joystick_port=1 (some drivers use one, others use the other, and I wasn't
sure at the time which es1371 used).
It didn't work.
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Tue, 22 Mar 2005 07:06:07 -0500, Patrick McFarland
<[email protected]> wrote:
> On Monday 21 March 2005 10:49 pm, Dmitry Torokhov wrote:
> > On Monday 21 March 2005 22:41, Patrick McFarland wrote:
> >
> > Ok, it looks like setup problem. Try doing:
> >
> > modprobe snd-ens1371 joystick_port=1
>
> I already tried that before I mailed the great and almighty source of all
> information kernely (aka the lkml). Infact, I tried both joystick=1 and
> joystick_port=1 (some drivers use one, others use the other, and I wasn't
> sure at the time which es1371 used).
>
> It didn't work.
>
Ok, just so I know where we stand: your gameport/joystick does work in
plain 2.6.11 but does not in 2.6.11-mm4, correct? When you load the
module with "joystick_port=1" is there any messages from ens1371 in
dmesg? Have you tried specifying exact port, like
"joystick_port=0x200" or "joystick_port=0x218"? Do you see these ports
reserved in /proc/ioports? What about /sys/bus/gameport/devices/? Do
you see anything in that directory?
--
Dmitry
On Tuesday 22 March 2005 08:58 am, Dmitry Torokhov wrote:
> On Tue, 22 Mar 2005 07:06:07 -0500, Patrick McFarland
> Ok, just so I know where we stand: your gameport/joystick does work in
> plain 2.6.11 but does not in 2.6.11-mm4, correct? When you load the
> module with "joystick_port=1" is there any messages from ens1371 in
> dmesg? Have you tried specifying exact port, like
> "joystick_port=0x200" or "joystick_port=0x218"? Do you see these ports
> reserved in /proc/ioports? What about /sys/bus/gameport/devices/? Do
> you see anything in that directory?
I haven't tested it with 2.6.11 yet... real life showed up, and hasn't gone
away yet. *stab!* I'll be testing it right after I send this email.
With joystick_port=1 there are no messages from the module, I've tried a bunch
of specific ports, and it doesn't work. The ports are not reserved
in /proc/ioports. /sys/bus/gameport/devices is empty.
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Tuesday 22 March 2005 09:19 pm, Patrick McFarland wrote:
> I haven't tested it with 2.6.11 yet... real life showed up, and hasn't gone
> away yet. *stab!* I'll be testing it right after I send this email.
Nope, 2.6.11 is also broken.
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Tuesday 22 March 2005 23:41, Patrick McFarland wrote:
> On Tuesday 22 March 2005 09:19 pm, Patrick McFarland wrote:
> > I haven't tested it with 2.6.11 yet... real life showed up, and hasn't gone
> > away yet. *stab!* I'll be testing it right after I send this email.
>
> Nope, 2.6.11 is also broken.
>
Ok, so the good news is that I did not break it... Coudl you try 2.6.10 to
see when it got broken.
--
Dmitry
On Thursday 24 March 2005 01:00 am, Dmitry Torokhov wrote:
> On Tuesday 22 March 2005 23:41, Patrick McFarland wrote:
> > On Tuesday 22 March 2005 09:19 pm, Patrick McFarland wrote:
> > > I haven't tested it with 2.6.11 yet... real life showed up, and hasn't
> > > gone away yet. *stab!* I'll be testing it right after I send this
> > > email.
> >
> > Nope, 2.6.11 is also broken.
>
> Ok, so the good news is that I did not break it... Coudl you try 2.6.10 to
> see when it got broken.
Nope, 2.6.10 is broken too. Now, off to 2.6.9...
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Friday 25 March 2005 09:28 am, Patrick McFarland wrote:
> Nope, 2.6.10 is broken too. Now, off to 2.6.9...
Hrm, 2.6.9 is also broke. 2.6.8 is next. (I should be coming along a working
kernel any time now...)
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Sunday 27 March 2005 06:23 am, Patrick McFarland wrote:
> On Friday 25 March 2005 09:28 am, Patrick McFarland wrote:
> > Nope, 2.6.10 is broken too. Now, off to 2.6.9...
>
> Hrm, 2.6.9 is also broke. 2.6.8 is next. (I should be coming along a
> working kernel any time now...)
That whacky real life thing showed up again.
2.6.8 is also fubar. Now to 2.6.7....
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Wednesday 30 March 2005 11:59 pm, Patrick McFarland wrote:
> 2.6.8 is also fubar. Now to 2.6.7....
Nope, 2.6.7 is also fubar. Now to 2.6.6.
BTW, can the ALSA userland in anyway screw me here? I mean,the joystick stuff
shouldn't have anything to do with it at all... but....
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
Patrick McFarland wrote:
> On Wednesday 30 March 2005 11:59 pm, Patrick McFarland wrote:
>
>>2.6.8 is also fubar. Now to 2.6.7....
>
>
> Nope, 2.6.7 is also fubar. Now to 2.6.6.
>
> BTW, can the ALSA userland in anyway screw me here? I mean,the joystick stuff
> shouldn't have anything to do with it at all... but....
>
Any chance the joystick is just broken?
--
========================================================================
Ian Pilcher [email protected]
========================================================================
On Thursday 07 April 2005 03:52 pm, Ian Pilcher wrote:
> Any chance the joystick is just broken?
Nope.
What works:
1) _Both_ joysticks (one that uses the analog driver, the other that uses the
sidewinder driver) work fine under Win2k.
2) Sound works under both Linux and Win2k.
3) The analog joystick (I didn't have the sidewinder yet) use to work at some
point in the past on this system with a 2.6 kernel.
What doesn't work:
1) Either the analog or sidewinder joysticks using any kernel I've tested so
far, loading snd_ens1371 using either joystick=1 or joystick_port=1 (I test
both out of habit). (Loaded in the order of snd_ens1371 (which loads
gameport), joydev, and then analog or sidewinder. Putting joydev or gameport
or both before snd_ens1371 doesn't improve the situation.)
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Thursday 07 April 2005 07:17 am, Patrick McFarland wrote:
> Nope, 2.6.7 is also fubar. Now to 2.6.6.
I haven't tested 2.6.6 yet, but 2.6.12-rc2-mm3 is broken too.
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Thu, 2005-04-14 at 21:18 -0400, Patrick McFarland wrote:
> On Thursday 07 April 2005 07:17 am, Patrick McFarland wrote:
> > Nope, 2.6.7 is also fubar. Now to 2.6.6.
>
> I haven't tested 2.6.6 yet, but 2.6.12-rc2-mm3 is broken too.
>
There's no point in testing newer kernels if you have yet to find an old
2.6 kernel where it works.
Do you have any evidence that it ever worked with ALSA? I suspect it's
always been broken, and that 2.6.8 or 2.6.9 system you referred to was
using the OSS driver.
Lee
On Thursday 14 April 2005 09:26 pm, Lee Revell wrote:
> On Thu, 2005-04-14 at 21:18 -0400, Patrick McFarland wrote:
> > On Thursday 07 April 2005 07:17 am, Patrick McFarland wrote:
> > > Nope, 2.6.7 is also fubar. Now to 2.6.6.
> >
> > I haven't tested 2.6.6 yet, but 2.6.12-rc2-mm3 is broken too.
>
> There's no point in testing newer kernels if you have yet to find an old
> 2.6 kernel where it works.
I didn't explicitly test it. I just updated my usual running kernel, and it
just happens that it didn't magically start working again.
> Do you have any evidence that it ever worked with ALSA? I suspect it's
> always been broken, and that 2.6.8 or 2.6.9 system you referred to was
> using the OSS driver.
Nope, I haven't used OSS in a very very very very long time. Back when I used
2.4 (which ended when 2.6.1 was released) I used ALSA.
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Thursday 14 April 2005 09:18 pm, Patrick McFarland wrote:
> I haven't tested 2.6.6 yet, but 2.6.12-rc2-mm3 is broken too.
I just tested 2.6.6, it seems to be broken too. I wonder if this actually is a
kernel issue, I should have found a working kernel by now. I'll continue to
2.6.5.
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Wednesday 20 April 2005 12:47 am, Patrick McFarland wrote:
> I just tested 2.6.6, it seems to be broken too. I wonder if this actually
> is a kernel issue, I should have found a working kernel by now. I'll
> continue to 2.6.5.
I just tried 2.6.5 and 2.6.4. No go. Only 3 kernels left.
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Wednesday 20 April 2005 20:42, Patrick McFarland wrote:
> On Wednesday 20 April 2005 12:47 am, Patrick McFarland wrote:
> > I just tested 2.6.6, it seems to be broken too. I wonder if this actually
> > is a kernel issue, I should have found a working kernel by now. I'll
> > continue to 2.6.5.
>
> I just tried 2.6.5 and 2.6.4. No go. Only 3 kernels left.
>
Are you testing with sidewinder?
--
Dmitry
On Wednesday 20 April 2005 10:12 pm, Dmitry Torokhov wrote:
> On Wednesday 20 April 2005 20:42, Patrick McFarland wrote:
> > On Wednesday 20 April 2005 12:47 am, Patrick McFarland wrote:
> > > I just tested 2.6.6, it seems to be broken too. I wonder if this
> > > actually is a kernel issue, I should have found a working kernel by
> > > now. I'll continue to 2.6.5.
> >
> > I just tried 2.6.5 and 2.6.4. No go. Only 3 kernels left.
>
> Are you testing with sidewinder?
I test both my analog and sidewinders. Not that it matters, my analog is the
one I had first, I only got the sidewinder recently.
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
On Wednesday 20 April 2005 21:21, Patrick McFarland wrote:
> On Wednesday 20 April 2005 10:12 pm, Dmitry Torokhov wrote:
> > On Wednesday 20 April 2005 20:42, Patrick McFarland wrote:
> > > On Wednesday 20 April 2005 12:47 am, Patrick McFarland wrote:
> > > > I just tested 2.6.6, it seems to be broken too. I wonder if this
> > > > actually is a kernel issue, I should have found a working kernel by
> > > > now. I'll continue to 2.6.5.
> > >
> > > I just tried 2.6.5 and 2.6.4. No go. Only 3 kernels left.
> >
> > Are you testing with sidewinder?
>
> I test both my analog and sidewinders. Not that it matters, my analog is the
> one I had first, I only got the sidewinder recently.
>
Ok... I know that sidewinder needs its timeouts increased to about 6ms to
work with 2.6. Have you tried OSS driver - to make sure that layer above
the soundcard works?
--
Dmitry
On Wednesday 20 April 2005 10:29 pm, Dmitry Torokhov wrote:
> Ok... I know that sidewinder needs its timeouts increased to about 6ms to
> work with 2.6. Have you tried OSS driver - to make sure that layer above
> the soundcard works?
Well, thats what I've been thinking thats screwing me. Because I've been using
ALSA since my 2.4.x days (I switched over to 2.6 and 2.6.1), and I know my
analog joystick works with ALSA and 2.6 (I just don't know when the bug
appeared) and I've also upgraded my ALSA userland over the years. Infact, I'm
almost convinced that the ALSA userland is causing the bug.
--
Patrick "Diablo-D3" McFarland || [email protected]
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd
all be running around in darkened rooms, munching magic pills and listening to
repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989
At Wed, 20 Apr 2005 23:03:27 -0400,
Patrick McFarland wrote:
>
> [1 <text/plain; utf-8 (quoted-printable)>]
> On Wednesday 20 April 2005 10:29 pm, Dmitry Torokhov wrote:
> > Ok... I know that sidewinder needs its timeouts increased to about 6ms to
> > work with 2.6. Have you tried OSS driver - to make sure that layer above
> > the soundcard works?
>
> Well, thats what I've been thinking thats screwing me. Because I've been using
> ALSA since my 2.4.x days (I switched over to 2.6 and 2.6.1), and I know my
> analog joystick works with ALSA and 2.6 (I just don't know when the bug
> appeared) and I've also upgraded my ALSA userland over the years. Infact, I'm
> almost convinced that the ALSA userland is causing the bug.
Hmm, I'm not sure what you "userland" mean, but ALSA lib and utils
have nothing to do with input devices...
Takashi