All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: andersen@codepoet.org
Cc: Philippe Lochon <plochon.n0spam@free.fr>, linux-kernel@vger.kernel.org
Subject: Re: P4C800E-Dlx: ICH5/S-ATA and Intel Pro onboard network incompatibility ?
Date: Sun, 05 Oct 2003 20:25:49 -0400	[thread overview]
Message-ID: <3F80B68D.8090109@pobox.com> (raw)
In-Reply-To: <20031005201638.GB4259@codepoet.org>

Erik Andersen wrote:
> When I have the Bios set to compatible mode everything works --
> except for the obvious problem that I have to put my SATA drive
> onto my promise SATA card (since the ICH5 SATA is disabled).
> 
> When I have the Bios set to Enhanced mode (so the ICH5 provides
> both SATA and PATA) then my system will wedge solid as a rock.
> 
> It turns out it was locking up while loading up the ide-scsi
> kernel module.  I have
> 
>     options ide-cd ignore='hdc'


So, things work in Enchanced mode if ide-scsi module is not loaded?

And, drivers/ide is picking up your PATA devices as expected?

As a tangent, I wonder if the latest cdrecord works in 2.4 with 
'dev=/dev/hdc' ... that would elimiante the need for ide-scsi.

	Jeff




  reply	other threads:[~2003-10-06  0:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-04 14:44 P4C800E-Dlx: ICH5/S-ATA and Intel Pro onboard network incompatibility ? Philippe Lochon
2003-10-04 18:03 ` Erik Andersen
2003-10-04 19:25   ` Jeff Garzik
2003-10-04 19:27   ` Jeff Garzik
2003-10-04 19:53     ` Erik Andersen
2003-10-05 20:16       ` Erik Andersen
2003-10-06  0:25         ` Jeff Garzik [this message]
2003-10-06  7:03           ` Erik Andersen
2003-10-06  7:52           ` Jens Axboe
2003-10-10  1:00         ` Greg Stark
2003-10-10  1:06           ` Erik Andersen
2003-10-10  1:26             ` Greg Stark
2003-10-04 20:07     ` ph75
  -- strict thread matches above, loose matches on Subject: below --
2003-10-06 13:46 Daniel Blueman
2003-10-08 18:53 P4C800E-Dlx: ICH5/S-ATA and Intel Pro onboard network incompatibility? Jon Burgess

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=3F80B68D.8090109@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=andersen@codepoet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plochon.n0spam@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.