Hi Alan,
OK, you convinced me; I'll install the new kernel (though, never done
it before, so of course, I have a question).
Google found http://www.kernel.org which has 2.6.34 (latest stable)
available as "Full source - 65MB" and a "Patch - 8MB." As I'm
upgrading current 2.6.18 kernel, can I download/use the Patch ? Also,
if you know of a good doc with 'how to upgrade kernel' steps, I'd be
most appreciative!
thank you.
shane.//
Quoting Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>:
On Tue, 22 Jun 2010 shane000@xxxxxxxxxxxxxx wrote:
> Hi Alan,
> Thank you for reply. I can certainly appreciate the amount of
> differences that might be in 2.6.34 compared to 2.6.18.
>
> However, my 'problem' is the O/S I'm using is Oracle Enterprise
> Linux(5.5) which has a lot of RedHat stuff, but then bundled and
> packaged under Oracle brand.
> And the OEL5.5 latest available kernel is 2.6.18, so not sure if I
> should (or could) go outside oracle to obtain and try install newer
> kernel package.
Well, you can always try using a new kernel just for testing. If it
works then you can go back to Oracle and say "This _is_ a software bug
because a newer kernel works okay." Or if it doesn't work then we'll
be able to track down the problem without having to deal with a
four-year old kernel containing some unknown extensions; if there's a
fix then perhaps the fix will work with Oracle's kernel too.
> Additional research and data I found on my system might help shed
some light:
> > I saved the 'dmesg' output to text and searched for relevant lines
> > (copied here):
> <snippet from dmesg.txt>
> drivers/usb/input/hid-core.c: v2.6:USB HID core driver
> ...
> input: No brand 2Port KVMSwicther as /class/input/input2 <<
> misspelled exactly as in dmesg
> input: USBHID v1.10 Keyboard [No brand 2Port KVMSwictch] on
> usb-0000:00:0f.2-1.3
> drivers/usb/input/hid-core.c: couldn't find an input interrupt endpoint
>
> <output from $ lsusb>
> Bus 001 Device 005: ID 105d:55a2 Uni Class Technology Co., 2Port
> KVMSwitcher << note, spelled correctly in this output
> Bus 001 Device 002: ID 058f:9254 Alcor Micro Corp. Hub
> Bus 001 Device 001: ID 0000:0000
> Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
> Bus 001 Device 004: ID 046d:c016 Logitech, Inc. M-UV69a/HP M-UV96
> Optical Wheel Mouse
>
> I included this data as the 'lsusb' output does identify the correct
> keyboard and mouse, but also names the KVM switch (even though the
> actual manufacturer is TrendNet TK-207 model); but odd that the 'dmesg'
> output says "No brand"
The information that dmesg reports comes directly from the device,
whereas some of the information in lsusb comes from a separate
database.
> Not sure if there is a correlation, but just my observations.
> Would this "tell" anything to someone who understands this all?
No.
> I can't find it now, but one google hit suggested a possible fix is to
> run (as root): mount usbfs
> > there wasn't much info on this, suggestion, so I've not tried it yet
> > would you recommend it ?
The Oracle system probably has done that for you already.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
