Greg,
Something strange with 2.5.56. My usb mouse is no longer working
after boot. I can get it to work by repluging it. Here is my
dmesg ang the init.d/local that should make sure the modules needed
are loaded. Before tring to replug I unloaded and reloaded hid and
psmouse to see if this would fix things (it did not).
I suspect the changeset below:
[email protected], 2003-01-09 10:29:40-08:00, [email protected]
which got added just before .56 - I have been tracking bk fairly
closely and all was working up to the version of 55bk built at 8am
on the 9th.
Ideas?
Ed Tomlinson
I'm getting a "Bad file descriptor" right now... (was just trying to pull 2.5.57)
Regards
Josh
On Mon, Jan 13, 2003 at 02:06:15PM -0500, Pete Zaitcev wrote:
> > I suspect the changeset below:
> >
> > [email protected], 2003-01-09 10:29:40-08:00, [email protected]
>
> linux.bkbits.net:8080/linux-2.5 says "Cannot find the project root".
> Can you send the patch, or refer to it somehow? BK is a wonderful
> tool, but only when it works.
>
> -- Pete
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
> I suspect the changeset below:
>
> [email protected], 2003-01-09 10:29:40-08:00, [email protected]
linux.bkbits.net:8080/linux-2.5 says "Cannot find the project root".
Can you send the patch, or refer to it somehow? BK is a wonderful
tool, but only when it works.
-- Pete
On Sun, Jan 12, 2003 at 10:42:01PM -0500, Ed Tomlinson wrote:
> Greg,
>
> Something strange with 2.5.56. My usb mouse is no longer working
> after boot. I can get it to work by repluging it. Here is my
> dmesg ang the init.d/local that should make sure the modules needed
> are loaded. Before tring to replug I unloaded and reloaded hid and
> psmouse to see if this would fix things (it did not).
>
> I suspect the changeset below:
>
> [email protected], 2003-01-09 10:29:40-08:00, [email protected]
>
> which got added just before .56 - I have been tracking bk fairly
> closely and all was working up to the version of 55bk built at 8am
> on the 9th.
Hm, that single changeset only modified the ehci driver, which should
not bother your USB mouse at all, unless it's a USB 2.0 mouse :)
It looks like from your logs that the usb core saw a bunch of devices.
What does /proc/bus/usb/devices look like after booting, when your mouse
is not working? The log also shows that a usb mouse was found by the
hid driver and bound to it, so I don't know why it wouldn't be working.
thanks,
greg k-h
On January 13, 2003 08:23 pm, Greg KH wrote:
> On Sun, Jan 12, 2003 at 10:42:01PM -0500, Ed Tomlinson wrote:
> > Greg,
> >
> > Something strange with 2.5.56. My usb mouse is no longer working
> > after boot. I can get it to work by repluging it. Here is my
> > dmesg ang the init.d/local that should make sure the modules needed
> > are loaded. Before tring to replug I unloaded and reloaded hid and
> > psmouse to see if this would fix things (it did not).
> >
> > I suspect the changeset below:
> >
> > [email protected], 2003-01-09 10:29:40-08:00, [email protected]
> >
> > which got added just before .56 - I have been tracking bk fairly
> > closely and all was working up to the version of 55bk built at 8am
> > on the 9th.
>
> Hm, that single changeset only modified the ehci driver, which should
> not bother your USB mouse at all, unless it's a USB 2.0 mouse :)
>
> It looks like from your logs that the usb core saw a bunch of devices.
> What does /proc/bus/usb/devices look like after booting, when your mouse
> is not working? The log also shows that a usb mouse was found by the
> hid driver and bound to it, so I don't know why it wouldn't be working.
I used tar on my sysfs mount point (this did not work cleanly...) and have
attached the tar and the dmesg log from the boot. The last message in
the log, which is from hid, was produced after the tar, when I replugged
the mouse.
Kernel is now 2.5.58.
Ed Tomlinson
On Tue, Jan 14, 2003 at 08:44:17AM -0500, Ed Tomlinson wrote:
>
> I used tar on my sysfs mount point (this did not work cleanly...) and have
> attached the tar and the dmesg log from the boot. The last message in
> the log, which is from hid, was produced after the tar, when I replugged
> the mouse.
>
> Kernel is now 2.5.58.
Ok, I think I've duplicated this here, and have a patch from Pat Mochel
that might fix it, but need to test. I'll let you know what I find (if
you want, go add a bug at bugme.osdl.org for this to get updates on the
status of this problem.)
thanks,
greg k-h