mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ottavio Campana <ottavio@campana.vi.it>
To: linux-kernel@vger.kernel.org
Subject: noapic and usb, linux 2.4.20
Date: Thu, 17 Apr 2003 22:05:06 +0200	[thread overview]
Message-ID: <20030417200506.GA20466@campana.vi.it> (raw)

[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]

I'm trying to  have usb working on my  pc, based on a dual  athlon and a
motherboard GA-7DPXDW with linux 2.4.20 with  the patch for xfs from sgi
and the patch for the sensors.

I was reading the linux-usb faq and I found: 
> Sometimes a  BIOS fix will be  available for your motherboard,  and in
> other cases  a more recent  kernel will have a  Linux fix. You  may be
> able to  work around this  by passing the  noapic boot option  to your
> kernel,  or (when  you're using  an add-in  PCI card)  moving the  USB
> adapter to some  other PCI slot. If you're using  a current kernel and
> BIOS,  report this  problem  to the  Linux-kernel  mailing list,  with
> details about your motherboard and BIOS.

So I'm  writing hoping  to be  helpful. Usb  works, but  I have  to pass
noapic to  the kernel.  Otherwise I get  "device not  accepting address"
when I plug a device in the usb port. The motherboard has been bought in
september. I remember the older mobos  had the southbridge b1, which had
a faulty usb. My mobo has got the southbridge b2, which works.

Is there anything useful I can do?

Can you please explain me what "noapic" does? I think it changes the way
interrupts are  handled, but I'm  not sure. Do  I miss something  when I
pass noapic to the kernel?

Bye

PS: can you please cc your answer to my mailbox? Thank you.

-- 
Non c'è più forza nella normalità, c'è solo monotonia.

[-- Attachment #2: Type: application/pgp-signature, Size: 244 bytes --]

             reply	other threads:[~2003-04-17 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 20:05 Ottavio Campana [this message]
2003-04-17 20:53 ` Randy.Dunlap

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=20030417200506.GA20466@campana.vi.it \
    --to=ottavio@campana.vi.it \
    --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

all inboxes | Powered by JetHome®