linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Oliver Korpilla" <Oliver.Korpilla@gmx.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: [SATA] SATA_SIL and ATI SB400 chipset
Date: Sun, 6 Mar 2005 10:35:27 +0100 (MET)	[thread overview]
Message-ID: <25661.1110101727@www58.gmx.net> (raw)

Hello!

I'm sorry to bug you like this, but I have a problem I hope you can help me
find about your SATA_SIL driver.

I have a brandnew computer for a project and its components aren't even
listed with names in lspci. AMD64 3500+, MSI RS480M2 with ATI RS480+SB400
controllers, 2GB 2.5 Dual DDR400 3200 RAM, Seagate 250 GB SATA drive with
NCQ, ... I guess you get it's rather new (we were allowed to spend a state
grant on it, so it isn't mine, I'm just building/configuring it for my
office).

The Debian AMD64 port netinstall doesn't recognize the disk, even if in IDE
controller mode in the BIOS and even when the SATA_SIL is modprobed into the
kernel.

But I've hooked a IDE-ATA harddrive with a Sarge install for i386 to it,
compiled a kernel 2.6.11 for it, and loaded your SATA_SIL driver for it,
which probed the device and allowed me to use it. It's working perfectly as
my 1st SCSI drive this way, and I compiled your driver into my kernel and it
boots perfectly from SATA.

Problem is, I want to do an install from the Sarge netinstall media to get a
full AMD64-compatible install. If I load the SATA_SIL module there, no
probing happens and my SATA drive isn't recognized, even if I modprobe the
module on the shell.

Problem seems to be that the simplified busybox version or something similar
of modprobe is used, which doesn't match modprobe's behaviour. But I guess
by giving the right parameters on loading your module I could force it into
being loaded correctly, with the same parameters it recognizes the hardware
when booted with kernel 2.6.11.

Do you agree?

Do you think, I could force your module into recognizing the hardware with
module parameters??

It would be very kind of you to help me out on this and I'd be very
grateful, especially since it works already so fine with 2.6.11 hack. But I
have several of this boxes to install, and I want them to run x86-64 native,
not i386 from another box' harddrive...

I'm not on the list, so could you CC: me if you answer.

Thanks and with kind regards,
Oliver Korpilla

-- 
SMS bei wichtigen e-mails und Ihre Gedanken sind frei ...
Alle Infos zur SMS-Benachrichtigung: http://www.gmx.net/de/go/sms

             reply	other threads:[~2005-03-06  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-06  9:35 Oliver Korpilla [this message]
2005-03-09 12:40 ` [SATA] SATA_SIL and ATI SB400 chipset Oliver Korpilla
     [not found] <Pine.LNX.4.44.0503071842240.4791-100000@coffee.psychology.mcmaster.ca>
2005-03-08 11:22 ` Oliver.Korpilla

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=25661.1110101727@www58.gmx.net \
    --to=oliver.korpilla@gmx.de \
    --cc=jgarzik@pobox.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).