linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Dibowitz <phil@ipom.com>
To: linux-ide@vger.kernel.org
Subject: Re: IDE kernel traces in 2.6.9 - Bad IRQ ?
Date: Sun, 31 Oct 2004 03:01:32 -0800	[thread overview]
Message-ID: <4184C60C.9010407@ipom.com> (raw)
In-Reply-To: <418421E9.6000809@ipom.com>

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

Phil Dibowitz wrote:
> I just upgraded my computer, compiled a new kernel appropriately, and 
> I'm getting a ton of kernel issues surrounding the IDE driver. I tried a 
> generic debian kernel as well, but same issue. Here are the tracebacks I 
> get during boot:
> 
> Oct 30 15:56:19 rider kernel: ide0 at 0xefe0-0xefe7,0xefae on irq 5
> Oct 30 15:56:19 rider kernel: hda: max request size: 128KiB

So, it turns out if I change the IDE Configuration in my BIOS to be 
"Compatible mode" instead of "Enhanced Mode", this is fixed completely. 
All my drives work flawelessly.

Any idea what, if any, features I'm missing, or how to make linux work 
with "enhanced mode" ?

-- 
Phil Dibowitz                             phil@ipom.com
Freeware and Technical Pages              Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
  - Benjamin Franklin, 1759


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2004-10-31 11:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-30 23:21 IDE kernel traces in 2.6.9 - Bad IRQ ? Phil Dibowitz
2004-10-31 11:01 ` Phil Dibowitz [this message]
2004-10-31 11:13   ` Jeff Garzik
2004-10-31 19:14     ` Phil Dibowitz
2004-11-01 14:28       ` Ericisko
2004-11-01 17:46         ` Phil Dibowitz

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=4184C60C.9010407@ipom.com \
    --to=phil@ipom.com \
    --cc=linux-ide@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).