I know this is the already the second place you have been directed to,
but you may have more luck in freebsd-scsi. (cc'd there)
On Thu, Sep 04, 2003 at 02:42:30PM -1000, Richard Puga wrote:
> I do have the ips driver working with the IBM ServerRaid 5i. However it
> only works if I boot
> of an I
I have come across the following issues with 5.1 and the IBM blades.
They are likely to apply to 4.x too.
The HS20 has a serial port, but it is only available as a header on board.
The HS20 also has an AT keyboard controller but that seems not to be physically
available anywhere.
IBMs BladeCen
HS 20 is IBMs Serverwork GC-LE dual Xeon blade, it managment chassis contains
usb floppy, cdrom, and usb to PS2 adapter for keyboard and mouse, these are
only ever avilable to one blade at a time.
I had a quick try to install from 5.1 iso this fails as the BTX loader can
not see the CD once loade
Can anyone tell me if the vpd driver functions for IBM x Series servers
as well as thinkpads?
-- --
Visit our Internet site at http://www.reuters.com
Get closer to the financial markets with Reuters Messaging - for more
informa
On Wed, Nov 24, 1999 at 01:31:44PM +, Nick Hilliard wrote:
> > Why do we need to smite the Linux database servers? With threads in their
> > current state they already outperform Linux's native threads by ~50x for
> > things like sending mail. I would assume that the differences in database
On Tue, Oct 26, 1999 at 11:06:15AM -0400, Greg Lehey wrote:
> On Tuesday, 26 October 1999 at 11:26:47 +0100, Geoff Buckingham wrote:
> > On Sun, Oct 24, 1999 at 09:58:11AM -0600, Greg Lehey wrote:
> >>
> >> Indeed. It's quite easy to put all cylinder groups on
On Sun, Oct 24, 1999 at 09:58:11AM -0600, Greg Lehey wrote:
>
> Indeed. It's quite easy to put all cylinder groups on a single
> spindle; I've seen reports of up to 80% degradation under these
> circumstances.
>
> > Where sequential read/write performance is not critical you can stripe at
> > c
> MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec
> %CPU
>40 16341 99.1 20746 38.3 20307 52.7 14187 100.0 94033 98.2
> 9744.2 99.8
>
> v.s.
>
> Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done...
> ---Sequential Output--
In article ,
Kenneth Wayne Culver writes:
> As we probably all know, Q3 test is out for Linux. I tested it on FreeBSD,
> with great results. I just downloaded the correct glide libraries from the
> site suggested by Carmac (Q3 programmer) and installed those, and then I
> added the appropr
Previously on Wed, Apr 21, 1999 at 12:31:03PM -0700, Matthew Dillon wrote:
:
: I think the existing release schedule is pretty good. Any faster and
: we might as well not have two branches at all. We really need a
: -current branch in order to make and test radical changes, and the
:
Previously on Sun, Feb 14, 1999 at 09:37:01PM -0500, tc...@staff.circle.net
wrote:
: I've been trying to track down a regular, but not
: manually reproducible crash in 3.0-BETA (19990205).
:
: I can't get a crashdump due to a DSCHECK negative
: number bug. I think my swap space of 3+GB is
: too
Hopefully this isn't becoming a democracy, but just in case, the verbose
reporting is a valued feature here.
--
Geoff Buckingham
Demon Internet
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Previously on Wed, Jan 27, 1999 at 11:48:16AM +0100, Poul-Henning Kamp wrote:
:
:
: If there is interest, this code will be merged to 3.1 as well.
:
I would like to express interest at this point.
--
Geoff Buckingham
Demon Internet
To Unsubscribe: send mail to majord...@freebsd.org
with
Previously on Thu, Jan 21, 1999 at 06:09:41PM +, Geoff Buckingham wrote:
: On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with
: 768MB RAM) poking about in the code adding:
:
: options "VM_KMEM_SIZE=(24*1024*1024)"
Previously on Thu, Jan 21, 1999 at 01:53:44PM -0800, Mike Smith wrote:
: > On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with
: > 768MB RAM) poking about in the code adding:
: >
: > options "VM_KMEM_SIZE=(24*1024*1024)"
: > options "VM_KMEM_SIZE_MAX
On tuesday I crashed a machine after it ran out of kvm. (dual PII 400 with
768MB RAM) poking about in the code adding:
options "VM_KMEM_SIZE=(24*1024*1024)"
options "VM_KMEM_SIZE_MAX=(128*1024*1024)"
seems like a good way foward. Is it?
--
GeoffB
To Unsubscribe: send mail to m
16 matches
Mail list logo
