On Friday 28 December 2001 12:02, Erik Steffl wrote:

> > Did you try with usbcore and usb-uhci in the kernel rather than
> > modules?
>   no, I guess I'll try that (and using alternative uhci driver)

In my experience, the alternate UHCI driver doesn't work very well;
YMMV, of course.

>   the problem is I cannot figure out how to change the IRQs - I have
> abit VH6-II motherboard that has very confusing setup [...]

You will probably have to swap your PCI cards around; your motherboard's 
manual should provide you with a description of which slot is connected to 
which interrupt (if you have more than 4 PCI slots, some of them will 
share an interrupt; also, slot 1 usually shares an interrupt with the AGP 
slot) and which slot is sharing an interrupt with the on-board USB 
controllers.

>   btw I checked the /proc/interrupts - the count does not change when I
> plug in/unplug USB device - is this the ultimate error? [...]

I guess so.

>   what should I see when it works? is it the irq problem, or, if it's
> not clear yet, hot to make sure whether it's irq problem or not?

I think the messages you posted are printed only if you enable "Verbose 
USB debug messages" in your kernel setup, as I don't see them here now but 
I remember seeing them when I configured my USB stuff; however, you should 
definitely see some more messages that tell you about the new device being 
connected and being claimed by a device driver. Like this:

Dec 27 16:41:53 athlon kernel: hub.c: USB new device connect on bus1/2,
  assigned device number 2
Dec 27 16:41:53 athlon kernel: input0: USB HID v1.10 Mouse [Logitech
  Trackball] on usb1:2.0

I'm not sure how you can make sure this is the problem except by resolving 
it. 8-/

-- 
Ciao,
    Flavio Stanchina
    Trento - Italy

"The best defense against logic is ignorance."
http://spazioweb.inwind.it/fstanchina/

_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to