From: Mario Mikocevic <mozgy@hinet.hr>
To: Ryan Butler <rbutler@adiis.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Few Qs regarding COMPAQ Proliant 6500
Date: Thu, 12 Apr 2001 09:00:42 +0200 [thread overview]
Message-ID: <20010412090042.A31070@danielle.hinet.hr> (raw)
In-Reply-To: <20010411132734.B24141@danielle.hinet.hr> <20010411133411.C24141@danielle.hinet.hr> <3AD45F53.2060208@adiis.net>
In-Reply-To: <3AD45F53.2060208@adiis.net>; from rbutler@adiis.net on Wed, Apr 11, 2001 at 08:42:43AM -0500
Hi,
> >> Any pointers ? Patches to apply ?
> >
> > Don't you people hate to followup yourself ..
> >
> > Anyway it's updated RH70 on 2.4.3 kernel !
>
> You didn't mention what type of 6500 it is? PPro? PII? PIII? How man
> processors installed?
COMPAQ Proliant 6500 (P11), two PIII ->
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping : 3
cpu MHz : 499.870
cache size : 1024 KB
Latest BIOS flashed (11/08/2000) and with 4.90 smartstart set as Linux.
> We use almost exclusively proliants where I work, most 3000's, but we do
> have a 6500 that is a quad PPro 200. I have spoke with Compaq and they
> didn't believe there was any driver
> for the LCD screen nor were they going to contribute to one (this was
> about a year ago.)
Well, I was hoping that that is changed !:)
> The 6500 also used to freeze up a lot under NT4, but since switching to
> linux we have experienced no ill effects with it.
We have here 14 6500 and few 800 and all of them (except that one) work
fine so far.
ps
any other relevant info avaiable on request
TIA
--
Mario Mikočević (Mozgy)
My favourite FUBAR ...
prev parent reply other threads:[~2001-04-12 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-11 11:27 Mario Mikocevic
2001-04-11 11:34 ` Mario Mikocevic
2001-04-11 13:42 ` Ryan Butler
2001-04-12 7:00 ` Mario Mikocevic [this message]
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=20010412090042.A31070@danielle.hinet.hr \
--to=mozgy@hinet.hr \
--cc=linux-kernel@vger.kernel.org \
--cc=rbutler@adiis.net \
/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
all inboxes | Powered by JetHome®