linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Maciej Rutecki <maciej.rutecki@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: ATA ACPI (was Re: Linux 2.6.24-rc4)
Date: Tue, 04 Dec 2007 18:00:23 -0500	[thread overview]
Message-ID: <4755DC07.5090009@garzik.org> (raw)
In-Reply-To: <8db1092f0712041448t5a3da9ecna73730e421626450@mail.gmail.com>

Maciej Rutecki wrote:
> http://www.unixy.pl/maciek/download/kernel/2.6.24-rc4/dmidecode.txt.gz

Thanks.


>>> And may I presume that booting with libata module option 'noacpi=1'
>>> fixes the problem?
> 
> noacpi=1 kernel command line or module parameters?
> 
> First, no change:
> http://www.unixy.pl/maciek/download/kernel/2.6.24-rc4/dmesg_noacpi.txt.gz
> Kernel command line: root=/dev/sda2 ro vga=0x318 resume=/dev/sda3
> selinux=1 enforcing=1  noacpi=1


Yes, that's a module option.

_If_ libata is built into the kernel, and not a kernel module, then you 
can supply "libata.noacpi=1" on the kernel command line.  I don't think 
that works with modules.

With libata built as a module (libata.ko), you will probably need to 
edit /etc/modprobe.conf.

	Jeff



  reply	other threads:[~2007-12-04 23:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.0.9999.0712032055080.2981@woody.linux-foundation.org>
2007-12-04 20:51 ` Linux 2.6.24-rc4 Maciej Rutecki
2007-12-04 21:06   ` Linus Torvalds
2007-12-04 21:19     ` Maciej Rutecki
2007-12-04 21:23   ` ATA ACPI (was Re: Linux 2.6.24-rc4) Jeff Garzik
2007-12-04 21:25     ` Jeff Garzik
2007-12-04 21:25       ` Alan Cox
2007-12-04 21:27     ` Jeff Garzik
2007-12-04 22:48       ` Maciej Rutecki
2007-12-04 23:00         ` Jeff Garzik [this message]
2007-12-05  7:46           ` Maciej Rutecki
2007-12-10  8:42             ` Tejun Heo

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=4755DC07.5090009@garzik.org \
    --to=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    /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).