From: "David C. Rankin" <drankinatty@suddenlinkmail.com>
To: kernel <linux-kernel@vger.kernel.org>
Subject: Re: Upgrade to recent 2.6.35 & 2.6.36 kernel causing boot failure with nv dmraid
Date: Thu, 04 Nov 2010 01:12:38 -0500 [thread overview]
Message-ID: <4CD24ED6.1030005@suddenlinkmail.com> (raw)
In-Reply-To: <4CD24A64.3080503@suddenlinkmail.com>
On 11/04/2010 12:53 AM, David C. Rankin wrote:
> I don't know exactly what you might need to look at or what additional data
> you want, but just let me know and I'm happy to get it for you.
Just FYI, the BIOS is current for the board and information on both can be found at:
http://www.msi.com/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1443
direct download:
http://www.msi.com/index.php?func=downloadfile&dno=12299&type=bios
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
next prev parent reply other threads:[~2010-11-04 6:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 5:53 Upgrade to recent 2.6.35 & 2.6.36 kernel causing boot failure with nv dmraid David C. Rankin
2010-11-04 6:12 ` David C. Rankin [this message]
2010-11-05 9:59 ` David C. Rankin
2010-11-09 17:48 ` David C. Rankin
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=4CD24ED6.1030005@suddenlinkmail.com \
--to=drankinatty@suddenlinkmail.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