On Friday 02 Sep 2005 09:13, Chris Clayton wrote:
Hi again,
> Hi,
>
> I posted this to LKML and here a few days ago, but it doesn't seem to have
> arrived on this list (maybe because I wasn't subscribed) and I've had no
> responses from LKML. Anyway, here goes again...
>
> I've built and installed 2.6.13 from unpatched kernel.org sources and my USB
> keyboard has started to behave very strangely when I boot my system.
>
> When I get to the login prompt, I only get to type a few key presses before
> the
> characters stop appearing on the screen. If I unplug the keyboard and plug it
> in
> again, the keyboard springs back into life and works perfectly until I reboot,
> when the problem always occurs again. This same keyboard worked fine with
> 2.6.12.5 and still does.
Don't know why I didn't think of this before, but I've upgraded my laptop to
2.6.13 and tried to boot that with this keyboard attached. The laptop locks up
during the boot at a point where the /etc/hotplug/*.rc scripts are being run.
With 2.6.12.5, the laptop boots fine. So it appears that 2.6.13 includes a
change that breaks handling of this keyboard.
The keyboard does work during the early part of the laptop boot because I can
use the {up,down} arrow and enter keys at the lilo menu. Similarly, I can select
options from the config.sys menu on my desktop (I've still got Win98SE on that
and boot Linux through linld).
Ideas anyone? Please.
>
> One perhaps important fact is that the keyboard also contains two USB ports.
> It
> is labelled Gateway and has a model ID of SK-9926. There are no devices
> plugged
> into the ports. I don't have another USB keyboard, so I can't check whether
> the
> presence of these ports is material. lsusb shows it as:
>
> Bus 005 Device 003: ID 0443:001c Gateway, Inc.
> Bus 005 Device 002: ID 0443:001d Gateway, Inc.
> <snip>
>
> I've rebuilt both kernels with USB debugging turned on and attach dmesg dumps
> taken immediately after login. I also attach the output from lsusb -v from
> each
> kernel. The dump from 2.6.12.5 ends immediately after a message about my
> ieee1394 card, but the one from 2.6.13 continues with a USB error message
> (line 276 of the dump). As far as I can see, this message is coming from
> hub_irq()
> of drivers/usb/core/hub.c (line 314), but I have no idea why.
>
> I'm more than happy to provide additional diagnostics and try any patches, but
> please cc me as I'm not subscribed to either list.
>
> Thanks
>
> Chris
>
>
> -------------------------------------------------------
>
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
