Re: Raon Everun (Microchip multifunction HID)
Alan Stern <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 5 Oct 2007, Bill Gribble wrote: > Alan Stern writes: > > To start, try building a kernel without all the HID debugging, but do > > enable CONFIG_USB_DEBUG. Then post the dmesg output showing what > > happens during startup. > > Ok, done. Here's dmesg output with CONFIG_USB_DEBUG. The builtin > keyboard never worked during this boot/shutdown cycle. I believe the > EXPHID0x25 device is the keyboard/mouse/touchscreen/gamepad. Yes, it is. It looks like you didn't plug in your external keyboard during the test -- but you must have used it to collect the dmesg log. Okay, the log doesn't show anything particularly suspicious. The next step is to use usbmon. There are instructions in the kernel source file Documentation/usb/usbmon.txt. What you will have to do is this: echo -n 1-4 >/sys/bus/usb/drivers/usb/unbind That will unbind all the drivers from the EXPHID0x25 device. Then start up the usbmon monitoring for bus 1, and while it is running do: echo -n 1-4 >/sys/bus/usb/drivers/usb/bind That will rebind all the drivers, and the usbmon log will capture all the traffic that occurs. Then with usbmon still running, type some characters on the builtin keyboard. Maybe also try using the other things. Finally, stop usbmon and post the log. We'll see what it reveals. Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel