Matthew Sayler wrote:
>
> I remember back in '00 when Justin Georgeson wrote:
> > motherboard, so I can't adjust what resources it uses. (at least not as far as I
> > can tell) I also have an onboard SCSI controller. One of the channels uses the
> > same IRQ as the USB controller. When I try to load the uhci module, insmod tells
> > me something about invalid parameters can cause problems, including invalid IRQ
> > and IO parameters. I presume the problem is that they share an IRQ. I have SCSI
> > device attached so I can't disable that. Anyone have any ideas?
>
> What is the exact command you give, and what is the exact error message?
>
> Matt
>
> --
> /* Matt Sayler || [EMAIL PROTECTED] || http://www.thewalrus.org
> "RFC 882 put the dot in .com" -- Christian Bauernfeind */
Funny thing. To answer your question I booted up like normal, switch to VT 1 (I
boot in runlevel 5) logged in as root, typed in modprobe -a uhci, and was given
messages similar too, but not the same as this:
Jul 31 18:09:18 dragon kernel: usb.c: registered new driver usbdevfs
Jul 31 18:09:18 dragon kernel: usb.c: registered new driver hub
Jul 31 18:09:18 dragon kernel: uhci.c: found UHCI device with no IRQ assigned.
check BIOS settings!
Jul 31 18:09:18 dragon kernel: kmem_shrink: Invalid cache addr c7f8dc20
Jul 31 18:09:18 dragon kernel: kmem_destroy: Can't free all objects c7f8dc20
Jul 31 18:09:18 dragon kernel: uhci: not all urb_priv's were freed
Jul 31 18:09:18 dragon kernel: kmem_shrink: Invalid cache addr c7f8dbc0
Jul 31 18:09:18 dragon kernel: kmem_destroy: Can't free all objects c7f8dbc0
Jul 31 18:09:18 dragon kernel: uhci: not all QH's were freed
Jul 31 18:09:18 dragon kernel: kmem_shrink: Invalid cache addr c7f8db60
Jul 31 18:09:18 dragon kernel: kmem_destroy: Can't free all objects c7f8db60
Jul 31 18:09:18 dragon kernel: uhci: not all TD's were freed
Jul 31 18:09:18 dragon kernel: usb.c: deregistering driver usbdevfs
Jul 31 18:09:18 dragon kernel: usb.c: deregistering driver hub
Jul 31 18:09:18 dragon kernel: grep uses obsolete /proc/pci interface
Jul 31 18:09:18 dragon kernel: usb.c: registered new driver usbdevfs
Jul 31 18:09:18 dragon kernel: usb.c: registered new driver hub
Jul 31 18:09:18 dragon kernel: usb.c: deregistering driver usbdevfs
Jul 31 18:09:18 dragon kernel: usb.c: deregistering driver hub
I pulled that out of /var/log/messages. So anyway this was interesting because
doing modprobe -a uhci from a gnome-terminal in X didn't give me anything like
that, just a stupid message that "insmod errors can be cause by invalid
parameters ....." So I rebooted, eneterd the BIOS setup, sure enough, the USB
was disabled. That confuses me, I have been using a USB scanner in Windows for 4
months now, and my USB mouse in Windows since last week. I thought if hardware
was disabled in the BIOS the OS shouldn't see it. So anyhow I enabled it in the
BIOS, save/exit, booted linux, and the USB modules load and detect my mouse. It
even works on the console now (it didn't work on the console when I was using it
as a PS/2 mouse bia the USB->PS/2 converter). The scroll wheel still doesn't
work for my user account (it does for other accounts), and kudzu broke my
XF86Config file adding the setup for the USB mouse. But I've fixed the
XF86Config file and no scroll wheel isn't a big deal.
So now I guess it's time to check out the kusbd and rc.usb stuff. Cool. Now if
only someone would write a driver for the Visioneer OneTouch 8100 I could use
the scanner too.
--
------------------------------------------------------------------------
; Justin Georgeson "free the mallocs" ;
; mailto:[EMAIL PROTECTED] ;
------------------------------------------------------------------------
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
