From: Greg KH <greg@kroah.com>
To: Ed Wildgoose <Ed@Wildgooses.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interrupt problem, no USB on SMP machine with 2.4.19/20/21
Date: Fri, 7 Mar 2003 14:13:43 -0800 [thread overview]
Message-ID: <20030307221343.GC21315@kroah.com> (raw)
In-Reply-To: <3E68F616.3090602@Wildgooses.com>
On Fri, Mar 07, 2003 at 07:42:14PM +0000, Ed Wildgoose wrote:
> I am running a dual intel P3 933Mhz machine with an EPOX EP-D3VA
> motherboard. This has a via VT82C693A/694x [Apollo PRO133x] chipset
>
> I cannot seem to get USB working at all on this machine. I have tried
> 2.4.19 20 and 21-ac (latest as of yesterday) with no luck. Basically
> doing insmod usb-uhci generates errors in the log:
Have you booted with "noapic" on the command line? That's the only way
a lot of VIA motherboards will get their onboard USB controller to work
properly.
thanks,
greg k-h
next prev parent reply other threads:[~2003-03-07 22:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 19:42 Interrupt problem, no USB on SMP machine with 2.4.19/20/21 Ed Wildgoose
2003-03-07 22:13 ` Greg KH [this message]
2003-03-07 23:35 ` Alan Cox
2003-03-07 23:27 ` Edward Wildgoose
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=20030307221343.GC21315@kroah.com \
--to=greg@kroah.com \
--cc=Ed@Wildgooses.com \
--cc=linux-kernel@vger.kernel.org \
/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