From: Michael Guntsche <mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org>
To: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Network failures with ACPI enabled (kernel 2.4, 2.6) PROBLEM FOUND!!!!!!
Date: Tue, 30 Dec 2003 23:22:26 +0100 [thread overview]
Message-ID: <20031230232226.7cf97fb3.mike@it-loops.com> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE0CC8953-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
On Tue, 30 Dec 2003 16:17:47 -0500
"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
> Can you put the xircom in the slot where the broadcom lived and
> See if it too gets IRQ5 and fails with the EPP set to OFF?
>
> Doing so would suggest that this failure is device independent
> and IRQ related.
Sorry, I can't do that since the broadcom network card is build-in.
I tried to get the pcmcia subsystem to assign IRQ 5 to the Xircom
which didn't work.
> It may be I/O port ranges rather than IRQs at the bottom of this one.
But why is it working when the parport is turned on?
Shouldn't it be the other way around, if there is a resource
conflict?
Michael
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next prev parent reply other threads:[~2003-12-30 22:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 21:17 Network failures with ACPI enabled (kernel 2.4, 2.6) PROBLEM FOUND!!!!!! Brown, Len
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE0CC8953-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2003-12-30 22:22 ` Michael Guntsche [this message]
2003-12-31 23:46 ` Nate Lawson
-- strict thread matches above, loose matches on Subject: below --
2003-12-30 22:36 Brown, Len
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE0CC8954-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2003-12-30 23:17 ` Michael Guntsche
[not found] ` <20031231001716.76cb2e8d.mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org>
2003-12-30 23:46 ` Michael Guntsche
[not found] ` <20031231004648.531549af.mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org>
2003-12-31 6:21 ` Len Brown
[not found] ` <1072851661.2363.228.camel-D2Zvc0uNKG8@public.gmane.org>
2003-12-31 16:23 ` Michael Guntsche
[not found] ` <20031231172328.5ae00921.mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org>
2004-01-03 21:06 ` Pavel Machek
2003-12-31 23:02 ` Nate Lawson
2003-12-30 0:08 Network failures with ACPI enabled (kernel 2.4, 2.6) Michael Guntsche
2003-12-30 15:57 ` Michael Guntsche
2003-12-30 17:48 ` Len Brown
2003-12-30 18:23 ` Michael Guntsche
[not found] ` <20031230192301.5d17d418.mike-Z92qn3yYq0hWk0Htik3J/w@public.gmane.org>
2003-12-30 20:45 ` Network failures with ACPI enabled (kernel 2.4, 2.6) PROBLEM FOUND!!!!!! Michael Guntsche
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=20031230232226.7cf97fb3.mike@it-loops.com \
--to=mike-z92qn3yyq0hwk0htik3j/w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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