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
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
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
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.
>
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.
--
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
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
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
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.
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
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.
--
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.
--
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.
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
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,
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
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
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
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
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...
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
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
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...
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
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
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
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
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
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
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
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
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.
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]
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
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
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. ;)
> >
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
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
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
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
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
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.
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.
>
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
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
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,
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
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
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
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
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
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).
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).
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
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
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
56 matches
Mail list logo
