public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jim Gifford <maillist@jg555.com>
Cc: Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problem with uhci_usb
Date: Tue, 13 Apr 2004 09:32:07 -0700	[thread overview]
Message-ID: <20040413163207.GA7198@kroah.com> (raw)
In-Reply-To: <26e601c420e5$4087ae90$d100a8c0@W2RZ8L4S02>

On Mon, Apr 12, 2004 at 04:24:07PM -0700, Jim Gifford wrote:
> cat /proc/interrrupts - output
> 
>            CPU0       CPU1
>   0:  139683637         37    IO-APIC-edge  timer
>   1:        510          1    IO-APIC-edge  i8042
>   2:          0          0          XT-PIC  cascade
>   3:      94944          1    IO-APIC-edge  serial
>   4:        168          1    IO-APIC-edge  serial
>   7:          0          0    IO-APIC-edge  parport0
>   8:          0          1    IO-APIC-edge  rtc
>   9:     466512          0   IO-APIC-level  megaraid
>  11:    1163951          1   IO-APIC-level  eth0, eth1, eth2, eth3
>  15:      24533          1   IO-APIC-level  aic7xxx, aic7xxx

Hm, no usb driver there...

> 00:13.0 USB Controller: OPTi Inc. 82C861 (rev 10) (prog-if 10 [OHCI])

Looks like a OHCI controller...

> Modules Loaded         uhci_hcd usbcore videodev hfs vfat fat isofs
> zlib_inflate floppy ext2 nfsd exportfs lockd sunrpc parport_pc lp parport
> ipt_TOS ipt_TCPMSS ipt_state ipt_REJECT ipt_LOG ipt_limit iptable_mangle
> iptable_nat ip_conntrack_irc ip_conntrack_ftp ip_conntrack iptable_filter
> ip_tables af_packet bonding 8250 serial_core tulip crc32 rtc supermount unix
> aic7xxx megaraid sd_mod scsi_mod

Yup, no ohci module either.  How about building the usb ohci module
(ohci-hcd) and trying that?  It should fix your problem.

Hope this helps,

greg k-h

      reply	other threads:[~2004-04-13 19:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-12 23:24 Problem with uhci_usb Jim Gifford
2004-04-13 16:32 ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040413163207.GA7198@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maillist@jg555.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox