From: Stian Jordet <liste@jordet.nu>
To: David van Hoose <davidvh@cox.net>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: ACPI conflict with USB
Date: Fri, 9 May 2003 04:06:48 +0200 [thread overview]
Message-ID: <1052446008.3ebb0d382f6af@webmail.jordet.nu> (raw)
In-Reply-To: <3EBB0A95.20902@cox.net>
Sitat David van Hoose <davidvh@cox.net>:
> Stian Jordet wrote:
> > Sitat Greg KH <greg@kroah.com>:
> >
> >
> >>On Thu, May 08, 2003 at 05:50:36PM -0500, David van Hoose wrote:
> >>
> >>>I'm wondering if there is any work towards correcting the ACPI conflict
> >>>with USB. On my system, I cannot use any USB devices due to a timeout
> >>>anytime I use ACPI with my kernel. Other people have noticed this
> >>>happening on their systems as well, so I am assuming it isn't just on my
>
> >>>system.
> >>
> >>Have you tried the latest 2.5 kernels? I think this is fixed in 2.5.69
> >>for the majority of people. Also, does booting with "noapic" work for
> >>you?
> >
> >
> > If it is supposed to have been fixed in 2.5.69, that must be the reason
> usb
> > stopped working with acpi on 2.5.69 for me. Worked fine with 2.5.68.
> >
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=105216850332081&w=2
> >
> > Only three days since I reported it, and you say it is fixed? Gee.
> >
> > David: The consensus on acpi-devel is to report it in bugzilla, and see
> what
> > happens.
>
> I'm using kernel 2.5.69-bk3 with this recent test. Booted with noapic,
> and I get thousands of lines of APIC errors. I still get the 'bulk_msg:
> timeout' with USB though.
> This hasn't ever worked for me. First tried with 2.5.54. I don't think I
> tried 2.5.68. Should I and see if it was something in a patch to 2.5.69?
Originally I never got usb to work with acpi, until one day I found out that
irq12 needed to be in use (!). If I booted with a ps/2 mouse, it worked perfect.
After some investigation, I found out that my BIOS had a setting for PS/2 mouse,
which were disabled, enabled and auto. Auto were the default. The irq 12 was
only reserved when there was a mouse at boot. If I set it at enabled, it always
reserved irq 12. After I found this out, usb worked perfect untill 2.5.69.
My motherboard is a Asus CUV266-DLS, Dual P3. Why irq12 has to be enabled, I
have never understood.
As a curiosity, I might tell you that when I boot my motherboard with MPS1.4
enabled, I have to disable the secondary ide port to get it to boot Linux. BUT,
when I do that, usb doesn't work (without acpi). So I have to use MPS1.1 and
have the secondary ide port enabled to get usb working without acpi. It was
better with 2.5.68 :( I guess this is just my motherboard being fscked up, but
other OS' boot fine, regardless of PS/2 mouse and/or secondary IDE port enabled.
Best regards,
Stian
next prev parent reply other threads:[~2003-05-09 1:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 22:50 ACPI conflict with USB David van Hoose
2003-05-09 0:22 ` Greg KH
2003-05-09 1:42 ` Stian Jordet
2003-05-09 1:55 ` David van Hoose
2003-05-09 2:06 ` Stian Jordet [this message]
2003-05-10 18:49 ` PCI problem [was Re: ACPI conflict with USB] David van Hoose
2003-05-10 19:11 ` Zwane Mwaikambo
2003-05-10 23:55 ` David van Hoose
2003-05-12 16:30 ` Greg KH
2003-05-12 17:08 ` Stian Jordet
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=1052446008.3ebb0d382f6af@webmail.jordet.nu \
--to=liste@jordet.nu \
--cc=davidvh@cox.net \
--cc=greg@kroah.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;
as well as URLs for NNTP newsgroup(s).