From: Sid Boyce <g3vbv@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: mcp55 forcedeth woes
Date: Wed, 15 Apr 2009 02:56:50 +0100 [thread overview]
Message-ID: <49E53EE2.2030903@blueyonder.co.uk> (raw)
Yan Seiner wrote:
> There is a newer bios, 1702, that may address these issues - at least teh
> writeup for the 17xx bios for the m2n32 talks about a network lockup fix.
> I haven't tried yet. These are the most stable boards I've found; one of
> mine runs 6 SATA drives locally, 9 via eSATA, 2 dual DVI video cards, and
> 2 15K scsi drives, all without a hitch. It never glitches - except for
> the d*mn network, this board is a piece of perfection.
For the M2N-SLI-Deluxe I found only 1701 which causes oops when booting
any kernel on 64X2 6000 and for the M2N32-SLI 2205 which I haven't tried
so far.
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
next reply other threads:[~2009-04-15 3:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 1:56 Sid Boyce [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-13 22:13 mcp55 forcedeth woes Yan Seiner
2009-04-13 23:45 ` Andrew Morton
2009-04-15 13:54 ` Yan Seiner
[not found] ` <200904132100.58056.gene.heskett@verizon.net>
[not found] ` <49E3EF9F.6090600@seiner.com>
[not found] ` <200904132224.13716.gene.heskett@verizon.net>
2009-04-14 14:35 ` Yan Seiner
2009-04-14 16:34 ` John Stoffel
2009-04-14 16:47 ` Yan Seiner
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=49E53EE2.2030903@blueyonder.co.uk \
--to=g3vbv@blueyonder.co.uk \
--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