linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix von Leitner <felix-linuxkernel@fefe.de>
To: linux-kernel@vger.kernel.org
Subject: Re: usb broken in 2.5?
Date: Tue, 14 Jan 2003 05:09:01 +0100	[thread overview]
Message-ID: <20030114040901.GA11545@fefe.de> (raw)
In-Reply-To: <20030114025245.GA1175@fefe.de> <20030114024435.GA1293@fefe.de>

Thus spake Felix von Leitner (felix-linuxkernel@fefe.de):
> In 2.5.57 USB does not work.

[...]

> Any ideas?  On 2.5 and WOLK the kernel also says that no IRQ is know and
> that it is using ACPI to route the IRQs.

It turned out to be an ACPI issue.

Darn.  Not AGAIN!
ACPI is the biggest pile of crap to poison this earth.
I have yet to see it "just work".

I'll turn it off for good now, sorry for wasting your time with this.

  reply	other threads:[~2003-01-14 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14  2:52 "PCI BIOS passed nonexistant PCI bus 0" Felix von Leitner
2003-01-14  2:44 ` usb broken in 2.5? Felix von Leitner
2003-01-14  4:09   ` Felix von Leitner [this message]
2003-01-14 14:55   ` Greg KH
2003-01-14 19:35 Adam J. Richter

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=20030114040901.GA11545@fefe.de \
    --to=felix-linuxkernel@fefe.de \
    --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;
as well as URLs for NNTP newsgroup(s).