From: Stian Jordet <liste@jordet.nu>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB not working with 2.5.69, worked with .68
Date: 06 May 2003 01:07:02 +0200 [thread overview]
Message-ID: <1052176021.1092.7.camel@chevrolet.hybel> (raw)
In-Reply-To: <20030505215141.GB3111@kroah.com>
man, 05.05.2003 kl. 23.51 skrev Greg KH:
> On Mon, May 05, 2003 at 10:54:20PM +0200, Stian Jordet wrote:
> >
> > I have read somewhere that the USB device not accepting new address
> > means that the host-controller doesn't get an interrupt, and that this
> > often is because of ACPI. It's just the same with acpi disabled (and in
> > 2.5.68 it did work with and without acpi).
>
> Hm, can you look at /proc/interrups and verify that the usb controller's
> interrupt count is going up? It really sounds like the interrupt isn't
> getting through to the usb controller driver.
*argh* I hate this. Earlier I only tried to disable acpi, I had to
disable MPS1.4 in the BIOS as well. Now it works. But, I can't turn my
computer off without acpi. This worked with 2.5.68, so something has
changed, but I guess you aren't the one to blame, then.
Thanks for answering, and sorry I didn't find this out earlier. But it
works with acpi in 2.5.68, that's what's bugging me :)
Best regards,
Stian
A little off-topic rant about my motherboard:
I have a ASUS CUV266-DLS motherboard. Dual P3, integrated SCSI and
ethernet. Since it is smp, I have to use ACPI to power it off.
* With kernel 2.5.69, and ACPI enabled, usb doesn't work.
* With earlier ACPI enabled kernels, and secondary ide disabled in bios,
usb doesn't work.
* Without ACPI, no kernel will boot with secondary ide enabled.
It's not easy..
next prev parent reply other threads:[~2003-05-05 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 20:54 USB not working with 2.5.69, worked with .68 Stian Jordet
2003-05-05 21:51 ` Greg KH
2003-05-05 23:07 ` Stian Jordet [this message]
2003-05-06 4:56 ` Jurriaan
2003-05-06 13:22 ` 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=1052176021.1092.7.camel@chevrolet.hybel \
--to=liste@jordet.nu \
--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).