From: Robert Hancock <hancockr@shaw.ca>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: New question on that sata controller
Date: Sat, 15 Dec 2007 14:58:30 -0600 [thread overview]
Message-ID: <47643FF6.7030701@shaw.ca> (raw)
In-Reply-To: <fa.JX5deKXb3TDJ1pV6ig+xHviNfRI@ifi.uio.no>
Gene Heskett wrote:
> Greetings;
>
> When I asked about a sata controller earlier this week, I gave a link to it.
> Unforch (maybe) when it actually arrived, the cards box showed a silicon
> image chip, and the card had a via. So much for getting what I ordered...
>
> The required module then was sata_via, not sata_uli, and it seems to be
> working ok. However, this one claims its a raid controller according to an
> lspci -v:
>
> 01:0a.0 RAID bus controller: VIA Technologies, Inc. VT6421 IDE RAID Controller
> (rev 50)
> Subsystem: VIA Technologies, Inc. VT6421 IDE RAID Controller
> Flags: bus master, medium devsel, latency 32, IRQ 19
> I/O ports at 9400 [size=16]
> I/O ports at 9800 [size=16]
> I/O ports at 9c00 [size=16]
> I/O ports at a000 [size=16]
> I/O ports at a400 [size=32]
> I/O ports at a800 [size=256]
> [virtual] Expansion ROM at e9000000 [disabled] [size=64K]
> Capabilities: [e0] Power Management version 2
>
> I just noted that the Expansion ROM is disabled, but I didn't see any jumpers
> to enable it on the card prior to installing it. Does anyone know how this
> is supposed to work? I would like to make it directly bootable but I believe
> this has to be 'enabled' for that.
It's usually normal for it to be disabled after boot, I believe. Are you
getting anything showing up on boot indicating its BIOS is active?
>
> I cannot find any references to this particular chip in a 'make xconfig' for
> 2.6.24-rc5.
>
> Should this be a concern, or is this one a 'Just Works(TM)' chipset? This
> card has 3 sata port connectors and one ide fitted.
>
> Two rather pleasant side effects of going to the Biostar.tw site and finding a
> newer bios and installing it on an M7NCD Pro mobo are:
>
> 1: FSB now running at 400MHZ, was 333 before as it was not at all stable at
> 400 and I have been told the XP-2800 Athlon only supports 333 and AMD's site
> agrees.
>
> 2: CPU temps are down around 13F. CPU speed still the same at 2079MHZ
> according to dmesg.
>
> The reduced temps at a higher FSB indicates better interface timing, and if it
> runs the rest of the night at 400 without a self reboot or crash, I'll leave
> it there.
>
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-12-15 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.JX5deKXb3TDJ1pV6ig+xHviNfRI@ifi.uio.no>
2007-12-15 20:58 ` Robert Hancock [this message]
2007-12-15 21:24 ` New question on that sata controller Gene Heskett
2007-12-15 22:17 ` Alistair John Strachan
2007-12-15 23:15 ` Gene Heskett
2007-12-15 6:49 Gene Heskett
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=47643FF6.7030701@shaw.ca \
--to=hancockr@shaw.ca \
--cc=gene.heskett@gmail.com \
--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