From: Jason Cribbins <jason.cribbins@mgmservers.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-ide@vger.kernel.org, jgarzik@pobox.com
Subject: Re: VIA VT8251 on Asus A8V-MV
Date: Mon, 21 Nov 2005 21:03:34 -0500 [thread overview]
Message-ID: <43827C76.3000703@mgmservers.com> (raw)
In-Reply-To: <20051121235516.GA8515@midnight.suse.cz>
Can you explain the situation in the following URL?
http://forums.viaarena.com/messageview.aspx?catid=28&threadid=68455&STARTPAGE=1
Also as I try to install fedora it reports that it is unable to find any
installed HDs. I have found an OpenBSD patch that does get it to work
there but nothing for Linux that works as of right now.
My BIOS has the controller set to SATA mode right now and its not
visible. Even if I set it to RAID mode or AHCI modes I get the same
result using fedora core4 and what ever kernel comes bundled with their
installer.
Vojtech Pavlik wrote:
>On Sun, Nov 20, 2005 at 09:52:28AM -0500, Jason Cribbins wrote:
>
>
>
>>I was wondering if its possible to find someone to create a driver
>>support for the Via VT8251 South Bridge chipset which appears to have
>>been around for about a year now. I am unable to get any form of Linux
>>to see my HDs connected to that on board controller. Although I have
>>successfully used it in non-raid mode on FreeBSD. I need this for
>>fedora if possible.
>>
>>Is something like this possible? And if so would it cost anything?
>>
>>
>
>The vt8251 is supported for quite some time by the IDE driver and its
>vt82cxxx.c chipset driver.
>
>
>
next prev parent reply other threads:[~2005-11-22 2:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 14:52 VIA VT8251 on Asus A8V-MV Jason Cribbins
2005-11-21 23:55 ` Vojtech Pavlik
2005-11-22 2:03 ` Jason Cribbins [this message]
2005-11-22 2:16 ` Jeff Garzik
2005-11-22 3:09 ` Andrew Joyce
2005-11-22 7:29 ` 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=43827C76.3000703@mgmservers.com \
--to=jason.cribbins@mgmservers.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=vojtech@suse.cz \
/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.