Axel Thimm wrote:
On Fri, Apr 27, 2007 at 09:46:44PM -0400, Kevin J. Cummings wrote:
> OK, so I plug my wireless USB mouse into my laptop, and I see the
> following messages in my logs:
>
>> Apr 27 21:08:32 kjclap kernel: usb 1-1: new low speed USB device using uhci_hcd
and address 2
>> Apr 27 21:08:32 kjclap kernel: Device driver usbdev1.2_ep00 lacks bus and class
support for being resumed.
>> Apr 27 21:08:32 kjclap kernel: usb 1-1: configuration #1 chosen from 1 choice
>> Apr 27 21:08:32 kjclap kernel: input: HID 062a:0000 as /class/input/input8
>> Apr 27 21:08:32 kjclap kernel: input: USB HID v1.10 Mouse [HID 062a:0000] on
usb-0000:00:1d.0-1
>> Apr 27 21:08:32 kjclap kernel: Device driver usbdev1.2_ep81 lacks bus and class
support for being resumed.
> and my mouse doesn't work. It used to work! Can someone please shed
> some light on the messages, and explain why it doesn't even work after
> rebooting the machine?
>
> kernel-suspend2-2.6.20-1.2933_1.fc6.cubbi_suspend2
>
> I've recently booted 2.6.20-1.2944_1.fc6.cubbi_suspend2 and it didn't
> work there either. This laptop came with
> 2.6.19-1.2895_1.fc6.cubbi_suspend2 installed initially. As far as I can
> tell, this may have broken with the 2.6.20-1.2933 kernel and I didn't
> notice it until recently (I don't always use the mouse with this laptop).
That sounds interesting, I didn't knew that OEMs were using cubbi
kernels.
Mine is. I once tried googling the cubbi kernels, but besides a couple
of discussions about them, I found more information about Care Bears
than Linux Kernels.
My OEM is shipping an ASUS motherboard in their laptop. I've been told
by them that they require the cubbi_suspend2 stuff in order for some of
my hardware to work correctly, including suspend and hibernate.
Being that this is my first laptop, I'm kinda learning about Linux
Laptops as I go along (but I've been running Linux desktops since Linux
version 0.12).
Any information as to why the cubbi_suspend2 kernels exist and why they
are necessary would be appreciated here. I assumed (probably
incorrectly) that they were used on most laptops. Image my surprise
last night to discover the are shunned by people here!
If you want to see whether this is a bug with the cubbi kernel or
the
Fedora vanilla kernel it is based on, why not install the
corresponding vanilla kernel and see if it's broken there, too?
I wasn't sure if I *could* even boot a stock FC kernel and have it run,
or even a vanilla Linux Kernel. I may give it a try later tonight or
tomorrow night when I have more time.
Maybe you need the cubbi kernel for using the laptop in general, but
the Fedora kernel should at least boot up, so you can test the
mouse. Of course, if the Fedora kernel does not even boot on your
hardware, you can't compare at all, so asking whether a similar USB
issue has been fixed in the Fedora kernels will also not really help
you.
I'll report back what I find. Thanks for the kind words.
Assuming that you can boot into the Fedora kernel rpm, then check if
your mouse is broken there, as well. If it is then you should comment
and post output based on the Fedora kernel, not the cubbi one.
I will.
If it is not, then the problem lies in the diff between the Fedora
kernel and this one, and you should really not take it up with Fedora
resources. Depending on what the vendor did, e.g. get the kernel from
ATrpms, Matthias or rebuild himself, you should direct the issue to
the last rebuilder.
My OEM mirrors the mhensler repos themselves. I'm not sure if they are
even the same that you provide or not. They also provide kernel modules
for my ATI Mobile Radeon X1600 video (but I haven't seen one for the
2944 kernel yet). They also provide quite few special installation
scripts for other features such as my ipw3945 wireless, and some general
stuff for expanded video support, software which makes my win-modem
work. I've installed MythTVfrontend so I can view my recordings on my
laptop if I so choose to. Unfortunately, the USB webcam doesn't work yet.
FWIW the cubbi kernels don't usually have special hardware
support, so
since the vendor says that you can only use these for the specific
laptop brand it may be that the OEM picked the kernel rpm added some
patches and rebuilt it under the same name. That would be really bad
and the vendor should be notified to use a different scheme.
I have no clue (yet, I want to learn). I'm still having a few problems
like my wireless isn't stable (doesn't always connect), and I think I
may have broken something in my video configuration (while fglrx is
installed and mostly works, my fullscreen video is *very* slow). So
far, the vendor has been unsuccessful in solving these problems, but I
probably broke them the day I received the laptop by installing some of
my favorite repos and doing a couple of "updates" before figuring out
what I broke by doing so.
So, I thought I'd post here about them one at a time as I get them
"fixed". I thought I'd start with my USB mouse problem. Big misteak
apparently. B^)
--
Kevin J. Cummings
kjchome(a)rcn.com
cummings(a)kjchome.homeip.net
cummings(a)kjc386.framingham.ma.us
Registered Linux User #1232 (
http://counter.li.org)