From: "Gabor Z. Papp" <gzp@papp.hu>
To: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: 2.4 and aacraid dmesg
Date: Wed, 22 Jun 2005 17:59:36 +0200 [thread overview]
Message-ID: <x64qbq757b@gzp> (raw)
In-Reply-To: 60807403EABEB443939A5A7AA8A7458B0152148D@otce2k01.adaptec.com
* "Salyzyn, Mark" <mark_salyzyn@adaptec.com>:
| >Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 08)
|
| Do you really need the audio card? :-) I'd toss (or disable) the audio
| system in a heart beat just to remove the annoyance of the messages.
ehaehaeh. Well, its not an enterprise server. I just prefer hw raid
over sw. The cheapest scsi hw raid card was this model, thats why I
bought to server me. Running with 2 Seagate Cheetah 10K.7 in raid1.
| Do keep the F/W up-to-date if you should run into problems.
Thanks for the hint.
| The 2200S is more than four times as fast (when stressed to the
| maximum), the 2120S was meant for 'budget' scenarios with feature
| completeness in mind.
Ideal for home usage. ;-)
| > Ah, the chip is *very* *very* *very* hot on the card, is that normal?
|
| I can put my hand on the CPU and keep it there with only a smidgen of
| concern and nary a sizzling sound. I would worry if you could cook eggs
| on it.
I can!
| Do you have a means to measure the actual temperature to add some
| objectivism?
Well, the mobo temp is around 47C, and I bet the chip is over 60.
I can't touch it. I was thinking about installing a mini fan on the
heatsink. Oh, about the heatsink, I see its something like a
"tuning", or a homebrew work. I think adaptec put the heatsink on the
chip after they discovered the cooling problem. But I can be wrong.
next prev parent reply other threads:[~2005-06-22 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-22 15:43 2.4 and aacraid dmesg Salyzyn, Mark
2005-06-22 15:59 ` Gabor Z. Papp [this message]
[not found] <60807403EABEB443939A5A7AA8A7458B0152136F@otce2k01.adaptec.com>
2005-06-22 15:25 ` Gabor Z. Papp
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=x64qbq757b@gzp \
--to=gzp@papp.hu \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
/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