Hum ... I posted the bug with an older version of the kernel and mixed up the kernel versions while posted the bugreport.

I tried with all the following versions of the kernel :
> * 2.6.30-1-686 #1 SMP

> * 2.6.26-1-686 #1 SMP (but it warns me at boot time that the kernel is
> two old for this version of udev - no sysfs)
> * 2.6.29-2-686 #1 SMP
I'm sure at least the 2.6.26 used to have no problem when I used it at the time, but it does not now. Maybe it's not the kernel itself ...



2009/11/3 Ben Hutchings <ben@decadent.org.uk>

On Tue, Nov 03, 2009 at 01:51:08PM +0100, Thomas Douillard wrote:

> Package: linux-image-2.6-amd64

> Severity: normal

[...]

> Kernel: Linux 2.6.29-2-686 (SMP w/2 CPU cores)

[...]



This kernel version is no longer in Debian. *Please upgrade to the current

version and test whether that fixes the problem.



Ben.



--

Ben Hutchings

Hoare's Law of Large Problems:

* * * *Inside every large problem is a small problem struggling to get out.

On Tue, Nov 03, 2009 at 10:03:38PM +0100, Thomas Douillard wrote:
> Hum ... I posted the bug with an older version of the kernel and mixed up
> the kernel versions while posted the bugreport.
>
> I tried with all the following versions of the kernel :
>
> > * 2.6.30-1-686 #1 SMP
> > * 2.6.26-1-686 #1 SMP (but it warns me at boot time that the kernel is
> > two old for this version of udev - no sysfs)
> > * 2.6.29-2-686 #1 SMP
>
> I'm sure at least the 2.6.26 used to have no problem when I used it at the
> time, but it does not now. Maybe it's not the kernel itself ...

recent and supported is 2.6.31 please provide test result of it.
thanks



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

2009/11/3 maximilian attems <max@stro.at>

On Tue, Nov 03, 2009 at 10:03:38PM +0100, Thomas Douillard wrote:

> Hum ... I posted the bug with an older version of the kernel and mixed up

> the kernel versions while posted the bugreport.

>

> I tried with all the following versions of the kernel :

>

> > * 2.6.30-1-686 #1 SMP

> > * 2.6.26-1-686 #1 SMP (but it warns me at boot time that the kernel is

> > two old for this version of udev - no sysfs)

> > * 2.6.29-2-686 #1 SMP

>

> I'm sure at least the 2.6.26 used to have no problem when I used it at the

> time, but it does not now. Maybe it's not the kernel itself ...



recent and supported is 2.6.31 please provide test result of it.

thanks


Hello, I compiled my own 2.6.31 since it is still not in the debian repositories for my processor, and the results are exactly the same as in the previous versions. Do I need to select some parameters for the kernel before building it ?


Thomas

The 2.6.31-1-686 kernel is now on unstable (the bug is attributed to the wrong kernel, if the architecture is involved), so I installed it, and the result is always the same ...

2009/11/9 Thomas Douillard <thomas.douillard@gmail.com>

2009/11/3 maximilian attems <max@stro.at>


On Tue, Nov 03, 2009 at 10:03:38PM +0100, Thomas Douillard wrote:

> Hum ... I posted the bug with an older version of the kernel and mixed up

> the kernel versions while posted the bugreport.

>

> I tried with all the following versions of the kernel :

>

> > * 2.6.30-1-686 #1 SMP

> > * 2.6.26-1-686 #1 SMP (but it warns me at boot time that the kernel is

> > two old for this version of udev - no sysfs)

> > * 2.6.29-2-686 #1 SMP

>

> I'm sure at least the 2.6.26 used to have no problem when I used it at the

> time, but it does not now. Maybe it's not the kernel itself ...



recent and supported is 2.6.31 please provide test result of it.

thanks


Hello, I compiled my own 2.6.31 since it is still not in the debian repositories for my processor, and the results are exactly the same as in the previous versions. Do I need to select some parameters for the kernel before building it ?



Thomas

On Mon, 2009-11-16 at 14:23 +0100, Thomas Douillard wrote:
> The 2.6.31-1-686 kernel is now on unstable (the bug is attributed to
> the wrong kernel, if the architecture is involved), so I installed it,
> and the result is always the same ...

I'm sorry we didn't respond to this message sooner.

This doesn't really look like a bug in the kernel. Have you tried
plugging the mouse into a different port? If you have another OS
installed on this computer, does the mouse work under that?

Ben.

--
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption] would be
development of an easy way to factor large prime numbers. - Bill Gates

2010/1/3 Ben Hutchings <ben@decadent.org.uk>

On Mon, 2009-11-16 at 14:23 +0100, Thomas Douillard wrote:

> The 2.6.31-1-686 kernel is now on unstable (the bug is attributed to

> the wrong kernel, if the architecture is involved), so I installed it,

> and the result is always the same ...



I'm sorry we didn't respond to this message sooner.



This doesn't really look like a bug in the kernel. *Have you tried

plugging the mouse into a different port? *If you have another OS

installed on this computer, does the mouse work under that?



Ben.

*I don't really use this computer these days but I can answer yes and yes again to your questions. Is it possible to recategorise the bug to udev or hal ?

Thomas

-------- Forwarded Message --------
From: Thomas Douillard <thomas.douillard@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Subject: Re: Bug#554158: linux-image-2.6-amd64: USB Dell "optical whell mouse" unrecognised
Date: Wed, 6 Jan 2010 13:55:52 +0100



2010/1/3 Ben Hutchings <ben@decadent.org.uk>
On Mon, 2009-11-16 at 14:23 +0100, Thomas Douillard wrote:
> The 2.6.31-1-686 kernel is now on unstable (the bug is attributed to
> the wrong kernel, if the architecture is involved), so I installed it,
> and the result is always the same ...


I'm sorry we didn't respond to this message sooner.

This doesn't really look like a bug in the kernel. Have you tried
plugging the mouse into a different port? If you have another OS
installed on this computer, does the mouse work under that?

Ben.

I don't really use this computer these days but I can answer yes and yes again to your questions.




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Update : the mouse works after an update, it was probably not a kernel bug since it works whichever is the version of the kernel.
The bug can be closed.

Thomas