public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pedro Venda <pjlv-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: CUR-DLS blacklisted? + IRQ trouble
Date: Sun, 15 Feb 2004 14:29:17 +0000	[thread overview]
Message-ID: <402F823D.6070702@mega.ist.utl.pt> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi everyone,

i have two questions to which i haven't found answers anywhere, so i am
asking here.

- - i have an ASUS CUR-DLS motherboard (dual P3) and the 2.4 and 2.6
kernels both say: "ASUS CUR-DLS detected: force use of acpi=ht" when
starting disabling ACPI. i must do a acpi=force in order to be able to
use it, which consequences i don't know. i looked through the acpi
documentation and this board is NOT on the blacklist. i am asking why
does the kernel disable ACPI on my mb by default? what's wrong with it?
are there any known problems?

- - on the same machine, i have 2 nics. one of them is onboard (intel
eepro/100) and the other is a realtek 8139. they used to work ok with
some versions of the kernel, but now they only work together without
ACPI. with acpi, the realtek displays the famous SIOCIFADDR "device is
busy...". is this normal? what can be happening here?

thanks for your time.
regards,
pedro.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAL4I9eRy7HWZxjWERAl2jAJ9RTPnvBG2dkUuyAeCKunGPXppAJACgyNWc
6dcQRdyMzFUpnr+nZXwwJmM=
=Zyfj
-----END PGP SIGNATURE-----


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click

             reply	other threads:[~2004-02-15 14:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-15 14:29 Pedro Venda [this message]
     [not found] ` <402F823D.6070702-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org>
2004-02-18  4:47   ` CUR-DLS blacklisted? + IRQ trouble Len Brown
     [not found]     ` <1077079669.4948.24.camel-D2Zvc0uNKG8@public.gmane.org>
2004-02-18 19:58       ` Pedro Venda
2004-02-22 23:08       ` Pedro Venda
     [not found]         ` <4039365B.6090105-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org>
2004-02-23 19:24           ` Randy.Dunlap
     [not found]             ` <20040223112406.116f381e.rddunlap-3NddpPZAyC0@public.gmane.org>
2004-02-24  1:40               ` Pedro Venda
     [not found]                 ` <403AAB98.4050508-aHmAgkVUFT6Joy8PIJZ9VA@public.gmane.org>
2004-02-24 11:21                   ` Stefan Seyfried

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=402F823D.6070702@mega.ist.utl.pt \
    --to=pjlv-ahmagkvuft6joy8pijz9va@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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