public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: amd74xx (nforce) driver problem ?
Date: Mon, 01 Aug 2005 12:10:47 -0600	[thread overview]
Message-ID: <42EE65A7.50201@shaw.ca> (raw)
In-Reply-To: <4wEt8-4Qk-1@gated-at.bofh.it>

Sonny Rao wrote:
> NFORCE2: IDE controller at PCI slot 0000:00:09.0
> NFORCE2: chipset revision 162
> NFORCE2: not 100% native mode: will probe irqs later
> NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
> NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
>     ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
>     ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
> 
> 
> Shouldn't the driver set the channel to UDMA100 after it detects the BIOS
> set up the chip improperly, or am I mistaken about this behavior?  Isn't
> that the "workaround" or does that mean something else?

I think the workaround is something else. I get that message as well on 
nForce4 (Asus A8N-SLI Deluxe). The drives are definitely set to auto in 
the BIOS (only optical drives are on the PATA controller).

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2005-08-01 18:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4wEt8-4Qk-1@gated-at.bofh.it>
2005-08-01 18:10 ` Robert Hancock [this message]
2005-08-01  9:06 amd74xx (nforce) driver problem ? Sonny Rao
2005-08-05 12:27 ` Vojtech Pavlik

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=42EE65A7.50201@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@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