On 2010-07-01, Marco Peereboom ma...@peereboom.us wrote:
It seems that the sun X4100 works now with amd64 GENERIC.MP. I'd like
to get some test reports from folks in the field.
You have to checkout a kernel using cvs because all niceness isn't in
snaps yet.
Thanks,
/marco
If someone
On 6/30/10 9:27 PM, Marco Peereboom wrote:
It seems that the sun X4100 works now with amd64 GENERIC.MP. I'd like
to get some test reports from folks in the field.
You have to checkout a kernel using cvs because all niceness isn't in
snaps yet.
Just for the archive, but Marco already have
Microsystems Sun Fire X4100 Server
Bah I had been testing on a non M2 version. Well at least this one
works even though it used to have issues as well.
On Thu, Jul 01, 2010 at 11:16:45PM -0400, Daniel Ouellet wrote:
On 6/30/10 9:27 PM, Marco Peereboom wrote:
It seems that the sun X4100 works now
@ 0xf8fb0 (65 entries)
bios0: vendor American Megatrends Inc. version 080010 date 08/10/2005
bios0: Sun Microsystems Sun Fire X4100 Server
Bah I had been testing on a non M2 version. Well at least this one
works even though it used to have issues as well.
On Thu, Jul 01, 2010 at 11:16:45PM -0400
It seems that the sun X4100 works now with amd64 GENERIC.MP. I'd like
to get some test reports from folks in the field.
You have to checkout a kernel using cvs because all niceness isn't in
snaps yet.
Thanks,
/marco
Hi,
The new snapshots for March 7 on Sun X4100 M2 crash right away on boot
and go directly to bbd.
This was running with the March 4 snapshots.
Below you see the dmesg, the trace and the ps.
The dmesg is from an other server running an earlier version of the OS
as I didn't keep the bsd
More updates on this.
I tested the new snapshots as well that just hit the tree a few minutes ago.
March 8, 2010 at 11:59 mts
and it is also still broken, but trace give different results, so here
it is as well, but I had to do two screen shut this time as it didn't
fit all on one screen for
On Mon, Mar 08, 2010 at 03:59:31PM -0500, Daniel Ouellet wrote:
Hi,
The new snapshots for March 7 on Sun X4100 M2 crash right away on boot
and go directly to bbd.
This was running with the March 4 snapshots.
Below you see the dmesg, the trace and the ps.
The dmesg is from an other
= 3757592576 (3583MB)
avail mem = 3657285632 (3487MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 04/11/07, BIOS32 rev. 0 @ 0xf0010,
SMBIOS rev. 2.3 @ 0xfbd50 (70 entries)
bios0: vendor American Megatrends Inc. version 0ABJX039 date 04/11/2007
bios0: Sun Microsystems Sun Fire X4100 M2
acpi0
On Dec 5, 2009, at 7:02 PM, Daniel Ouellet wrote:
This is an old issue and not new, but I tried the latest snapshot in case
the situation have changed to no avail.
I git a little bit more details however after letting it reboot constantly
may be 40 times or so.
Then it jam and was able to
:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 3756982272 (3582MB)
avail mem = 3650658304 (3481MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xfbd50 (70 entries)
bios0: vendor American Megatrends Inc. version 0ABJX039 date 04/11/2007
bios0: Sun Microsystems Sun Fire X4100 M2
Marco Peereboom wrote:
I did test i386 on it and that seemed to work ok but I did not run it
for more than a few builds. amd64 UP seems fine too.
For the i386.mp or single kernel, it does run fine. I run it for two
years so far no problem. The i386.mp needed to be rebooted twice with
4.6 on
I have some output from the serial port but it is completely nonsensical
which points to mem corruption or bad dma or something. I farted around
with IPI to see if the error was at that level but could not find
anything. Also tried some other things that I suspected were biting the
Dell R610 but
/sys/arch/amd64/compile/GENERIC
real mem = 3756982272 (3582MB)
avail mem = 3650658304 (3481MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xfbd50 (70 entries)
bios0: vendor American Megatrends Inc. version 0ABJX039 date 04/11/2007
bios0: Sun Microsystems Sun Fire X4100 M2
acpi0 at bios0
of it and was also able to reproduce the problem as well
on his X4100 too.
http://marc.info/?l=openbsd-techm=120122281409313w=2
Any chance that may be that might be fix for the final release of 4.3?
Best,
Daniel
Snaps will be a while since Theo is out hiking.
On Sat, Jan 19, 2008 at 07:27:24AM +0100, Rolf Sommerhalder wrote:
On Jan 19, 2008 5:04 AM, Jonathan Gray [EMAIL PROTECTED] wrote:
Try this diff:
Great, that fixed it, thank you.
Now, will you commit it so that it will be included in a next
Hello misc,
after a successful upgrade of a X4100 M2 to the latest snapshot, the
server fails to reboot after having issued the reboot(8) command as
root. This was working fine before with the snapshot which was from
early December (also i386 .mp, ACPI enabled manually back then, which
is now
On Fri, Jan 18, 2008 at 05:17:26PM +0100, Rolf Sommerhalder wrote:
Hello misc,
after a successful upgrade of a X4100 M2 to the latest snapshot, the
server fails to reboot after having issued the reboot(8) command as
root. This was working fine before with the snapshot which was from
early
On Jan 19, 2008 5:04 AM, Jonathan Gray [EMAIL PROTECTED] wrote:
Try this diff:
Great, that fixed it, thank you.
Now, will you commit it so that it will be included in a next snapshot?
Ok got my x4100 out of storage. What was the mpi issue again that
someone was seeing?
Sorry for the broadcast but I couldn't find that email.
On Thu, 27 Dec 2007, Marco Peereboom wrote:
Ok got my x4100 out of storage. What was the mpi issue again that
someone was seeing?
Sorry for the broadcast but I couldn't find that email.
I think this is the thread you're looking for:
http://marc.info/?l=openbsd-miscm=119623820305056w=2
Marco Peereboom wrote:
Ok got my x4100 out of storage. What was the mpi issue again that
someone was seeing?
Sorry for the broadcast but I couldn't find that email.
4100 M2
Any time you put a amd64.mp kernel on that box and you try to do heavy
access to the SAS drives, the server
Kyle George wrote:
On Thu, 27 Dec 2007, Marco Peereboom wrote:
Ok got my x4100 out of storage. What was the mpi issue again that
someone was seeing?
Sorry for the broadcast but I couldn't find that email.
I think this is the thread you're looking for:
http://marc.info/?l=openbsd-miscm
Marco Peereboom wrote:
Yesterday I dug up a whole lot of stuff and I was able to see my x4100.
Next time I should be able to get it home. Sorry for the delay.
Please Marco, don't be sorry. Just for you agree to look into this is
already very much appreciated!
Anything I can do to help
Yesterday I dug up a whole lot of stuff and I was able to see my x4100.
Next time I should be able to get it home. Sorry for the delay.
On Fri, Nov 30, 2007 at 02:21:54AM -0500, Daniel Ouellet wrote:
Stuart Henderson wrote:
On 2007/11/28 21:00, Daniel Ouellet wrote:
Stuart Henderson wrote
Ant feedback on this part?
So, is it possible based on the logs I sent that it is in the DMA part
of the mp kernel here?
Still digging, but wanted to get some feedback as if it was possible or
am I looking totally in the wrong direction.
Fine if you tell me I am full of sh*t too. (;
Just
Marco Peereboom wrote:
I will dig my x4100 out of storage any day now. Last time I used it it
was stable on i386 and amd64.
Only amd64.mp is not stable ( and only in writing to the disk) , amd64
is stable as well as either i386 kernel are stable. And in case it does
make a difference, it's
I will dig my x4100 out of storage any day now. Last time I used it it
was stable on i386 and amd64.
On Wed, Nov 28, 2007 at 10:51:00PM +1000, David Gwynne wrote:
this diff cannot affect the behavior of your system. the code below deals
with domain validation on SPI mpi variants while
Stuart Henderson wrote:
On 2007/11/28 16:47, Daniel Ouellet wrote:
I don't know x4100 m2, is this an optional card, or meant to always
be there?
No there isn't any cards that I added or anything. The difference you see is
that the server also have RAID controller built in and as such will show
asking for an X4100 on
http://www.openbsd.org/want.html to work on RAID, not to mention
a couple of other requests for amd64 boxes (Europe/N.America) to
work on large memory support. ;-)
(I'm half-joking here, but I think it doesn't hurt to remind misc@
readers that developers are better able
On 2007/11/28 21:00, Daniel Ouellet wrote:
Stuart Henderson wrote:
Well, it's certainly a bit odd that amd64 doesn't detect the ipmi, and i386
does... I don't really have any other clues though :(
Ah. It's not odd at all...
revision 1.139
date: 2006/06/01
Stuart Henderson wrote:
On 2007/11/28 21:00, Daniel Ouellet wrote:
Stuart Henderson wrote:
Well, it's certainly a bit odd that amd64 doesn't detect the ipmi, and i386
does... I don't really have any other clues though :(
Ah. It's not odd at all...
revision 1.139
X4100 M2
acpi0 at mainbus0: rev 2
acpi0: tables DSDT FACP APIC SPCR SLIT OEMB HPET IPET SRAT SSDT
acpi0: wakeup devices PS2K(S0) PS2M(S0) USB0(S0) USB1(S0) MAC_(S5)
P0P1(S0) P0P2(S0) P0P3(S0) P0P4(S0) P0P5(S0) IO4B(S0) BR5B(S0) BR5C(S0)
BR5D(S0) BR5E(S0) IOB2(S0) BR2B(S0) BR2C(S0) BR2D(S0) BR2E(S0
Hi,
I need some help here to narrow this down more or may be someone might
find the answer quickly.
I have pinpoint the crash/reboot for the Sun X4100 to the usage of the
Ultra160: enable dual xfers, even if I think it is U360, but I could
be wrong. Couldn't find the specs just yet. In any
this diff cannot affect the behavior of your system. the code below
deals with domain validation on SPI mpi variants while the x4100 uses
SAS mpi. the code you patched isnt run on your machine.
do you have these crashes on all x4100s running amd64 mp, or only on
this one machine?
dlg
David Gwynne wrote:
this diff cannot affect the behavior of your system. the code below
deals with domain validation on SPI mpi variants while the x4100 uses
SAS mpi. the code you patched isnt run on your machine.
Not sure I understand your statement, but as a test, I did exactly that
and I
On 29/11/2007, at 4:51 AM, Daniel Ouellet wrote:
David Gwynne wrote:
this diff cannot affect the behavior of your system. the code below
deals with domain validation on SPI mpi variants while the x4100
uses SAS mpi. the code you patched isnt run on your machine.
Not sure I understand your
David Gwynne wrote:
On 29/11/2007, at 4:51 AM, Daniel Ouellet wrote:
David Gwynne wrote:
this diff cannot affect the behavior of your system. the code below
deals with domain validation on SPI mpi variants while the x4100 uses
SAS mpi. the code you patched isnt run on your machine
David Gwynne wrote:
On 29/11/2007, at 4:51 AM, Daniel Ouellet wrote:
David Gwynne wrote:
this diff cannot affect the behavior of your system. the code below
deals with domain validation on SPI mpi variants while the x4100 uses
SAS mpi. the code you patched isnt run on your machine
On 2007/11/28 15:38, Daniel Ouellet wrote:
David Gwynne wrote:
this diff cannot affect the behavior of your system. the code below deals
with domain validation on SPI mpi variants while the x4100 uses SAS mpi.
the code you patched isnt run on your machine.
Not sure I understand your
/openbsd-tech/2007/11/23/441182
Just to be clear:
Sun X4100 M2 with i386 kernel is stable so far.
Sun X4100 M2 setup with RAID1 with i386 kernel is stable so far.
Sun X4100 M2 with i386.mp kernel is stable so far.
Sun X4100 M2 setup with RAID1 with i386.mp kernel is stable so far.
Sun X4100 M2
Stuart Henderson wrote:
On 2007/11/28 16:47, Daniel Ouellet wrote:
I don't know x4100 m2, is this an optional card, or meant to always
be there?
No there isn't any cards that I added or anything. The difference you see is
that the server also have RAID controller built in and as such will show
On 2007/11/28 16:47, Daniel Ouellet wrote:
I don't know x4100 m2, is this an optional card, or meant to always
be there?
No there isn't any cards that I added or anything. The difference you see is
that the server also have RAID controller built in and as such will show
different DMESG
Stuart Henderson wrote:
Well, it's certainly a bit odd that amd64 doesn't detect the ipmi, and i386
does... I don't really have any other clues though :(
Looking in all my dmesg and all 4 servers, I sure can confirm this.
i386 bring it as:
ipmi0 at mainbus0: version 1.5 interface KCS iobase
David Gwynne wrote:
this diff cannot affect the behavior of your system. the code below
deals with domain validation on SPI mpi variants while the x4100 uses
SAS mpi. the code you patched isnt run on your machine.
Not sure I understand your statement, but as a test, I did exactly
that and I
Hi,
You may have seen a few posts from me on this box. I continue to try to
isolate the problem as much as possible with it and it's now narrow to a
more specific setup in the current kernel, but still this box WILL NOT
be stable what so ever if use with the amd64.mp kernel.
I am running
Just for the records.
Here is what help some for the stability in BIOS:
* Hotplug USB FDD Support[Disabled] *
* Hotplug USB CDROM Support [Disabled] *
Everything is default, or as F9 would put it when you load optimum
setting in BIOS. Then you only need to
OK,
To follow on this and to try to isolate more problem, I did the
following tests.
- Setup two boxes, both Sun X4100 M2.
- The source box is using i386.mp version 4.2
- The destination box is using amd64.mp version 4.2 (same with current)
- Configure public IP's on the em0 interface of both
The latest snapshot (13. Sept). of amd64 bsd.mp with ACPI enabled runs
stable on two X4100 M2 which are identically configured (single SAS
disk only, no RAID-1 yet, with current BIOS/SP/SAS Firmware from Sun).
As Daniel already observed with a snapshot that is two days older,
booting is much
Rolf Sommerhalder wrote:
The latest snapshot (13. Sept). of amd64 bsd.mp with ACPI enabled runs
stable on two X4100 M2 which are identically configured (single SAS
disk only, no RAID-1 yet, with current BIOS/SP/SAS Firmware from Sun).
Be caution and with reserved! Not stable if you do not add
I did observe similar behaviour on four X4100 M2 as well (two with one
socket dual-core, two with two sockets dual-core Opterons) using amd64
bsd.mp snapshots from 23 and 28 Aug..
Currently, amd64 bsd.mp snapshot 28. Aug is running stable on those
four servers, although using a single SAS disk
Rolf Sommerhalder wrote:
I did observe similar behaviour on four X4100 M2 as well (two with one
socket dual-core, two with two sockets dual-core Opterons) using amd64
bsd.mp snapshots from 23 and 28 Aug..
Currently, amd64 bsd.mp snapshot 28. Aug is running stable on those
four servers, although
In article [EMAIL PROTECTED], Daniel Ouellet wrote:
So, I am not sure what testing you did, unless you built your own. new
Snapshots was just release now, witch I will be happy to test tonight
and see the results and report back.
If you guys could test out my ACPI diff I posted to
rev. 2.3 @ 0xfbd50 (70 entries)
bios0: vendor American Megatrends Inc. version 0ABJX039 date 04/11/2007
bios0: Sun Microsystems Sun Fire X4100 M2
acpi0 at mainbus0: rev 2
acpi0: tables DSDT FACP APIC SPCR SLIT OEMB HPET IPET SRAT SSDT
acpitimer at acpi0 not configured
acpimadt0 at acpi0 addr
: Sun Microsystems Sun Fire X4100 M2
acpi0 at mainbus0: rev 2
acpi0: tables DSDT FACP APIC SPCR SLIT OEMB HPET IPET SRAT SSDT
acpitimer at acpi0 not configured
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Dual-Core AMD Opteron(tm) Processor 2216
Tobias Weingartner wrote:
In article [EMAIL PROTECTED], Daniel Ouellet wrote:
So, I am not sure what testing you did, unless you built your own. new
Snapshots was just release now, witch I will be happy to test tonight
and see the results and report back.
If you guys could test out my
Hi,
Quick updates on this one.
My problem is now solved and I got very nice help from some gentlemen
working at Sun that step in off list to help me out and all is now
finally work.
Nice to see some good guys following misc@ and be interested to make
sure Sun hardware (some of them anyway)
On Fri, Sep 07, 2007 at 02:13:52AM -0400, Daniel Ouellet wrote:
Hi,
Not sure if I am missing something, most likely it's not implemented yet,
but I was looking to see if I could check anything about a RAID 1 setup on
Sun X4100 M2 so that it can be monitor somehow. I am not making progress
Henning Brauer wrote:
bio is not implemented for mpi (yet).
bioctl in 4.2 onwards shows some inquiry data (vendor model fw serial)
for non-bio-capable disks. i. e. it falls back from bioctl -i to bioctl
-q if teh disk doesn't support bio.
Thanks Henning!
Jonathan Gray wrote:
mpi(4) currently has no bioctl support.
The 2 port LSI SAS RAID (mfi(4)) supports bioctl, however
sun don't sell any machines with this interestingly enough.
Thanks! That's what I figure, but wanted to check in case I wasn't
looking at the right place. Oh well. May be
-current should fix ipmi.
On Thu, May 24, 2007 at 07:40:07AM -0400, Kenneth R Westerback wrote:
On Thu, May 24, 2007 at 05:31:26AM -0400, Daniel Ouellet wrote:
Hi,
Here is some weird dmesg on a new install on a Sun X4100 X2 brand new
out of the box.
Hopefully it is helpful
Hi,
Here is some weird dmesg on a new install on a Sun X4100 X2 brand new
out of the box.
Hopefully it is helpful to clear some errors and may be as well to know
if I should do anything special.
I am just starting to test these to put them in productions soon, but I
may hold back a bit
On Thu, May 24, 2007 at 05:31:26AM -0400, Daniel Ouellet wrote:
Hi,
Here is some weird dmesg on a new install on a Sun X4100 X2 brand new
out of the box.
Hopefully it is helpful to clear some errors and may be as well to know
if I should do anything special.
I am just starting
(3669556K)
avail mem = 3223740416 (3148184K)
using 22937 buffers containing 375971840 bytes (367160K) of memory
User Kernel Config
UKC enable acpi
251 acpi0 enabled
UKC quit
Continuing...
mainbus0 (root)
bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xfbd40 (70 entries)
bios0: Sun Microsystems Sun Fire X4100
The system seems to run stable until I put load on the multiport fiber
adapter. I recompiled the entire operating system with no issues.
Try moving the adapter to another port. Also, some fixes went into
-current recently fixing some em(4) issues. You could be hitting a
bug.
Did you get
I have deployed several X4200 on 3.9 (with mpi(4) backported from
4.0). AFAIK, X4200 == X4100. It just has some more PCI slots.
When booting, RTC BIOS diagnostic error 2 is displayed, I'm not sure if
that's relevant.
You might want to investigate that. Not sure, but I don't remember
seeing
On Thu, 16 Nov 2006, Srebrenko Sehic wrote:
When booting, RTC BIOS diagnostic error 2 is displayed, I'm not sure if
that's relevant.
You might want to investigate that. Not sure, but I don't remember
seeing that error on the X4200 boxes I had tested. BIOS update might
be relevant. Perhaps
I just installed OpenBSD 4.0-stable on a Sun x4100 server. The server has
an IPMI virtual console accessed remotely via a Java application which
pretends to be a USB keyboard/mouse.
While I had no problems with the virtual console during the installation
process, once the actual operating system
We are trying to update our border firewall with a new Sun x4100 server,
but unfortunately whenever we put load on it it rudely dies :(.
The server has four onboard Intel gigabit ethernet copper ports. We have
also installed an Intel single mode fiber adapter, and an Intel dual-port
multimode
#ifdef DIAGNOSTIC
if (scd-sc_in_rep_size != cc)
printf(%s: bad input length %d != %d\n,USBDEVNAME(sc-sc_dev),
scd-sc_in_rep_size, cc);
#endif
A more correct fix is to change the line to something like this. It's
still not the most correct fix, but
On 8/10/06, Russell McGregor [EMAIL PROTECTED] wrote:
Having said that, I will still try loading an amd64 snapshot and see
if that boots MP.
Unless something changed after 3.9, it both boots and runs MP fine,
also under heavy load. I tested on x4200, but it should be the same
for 4100.
Have
Hello,
I am doing some testing on a Sun x4100 on loan to us from a vendor, I
have loaded up a snapshot from about 20060803 and everything seems to
run fine from the standard /bsd kernel image, but it panics when
trying to boot bsd.mp. I updated src with a CVS checkout earlier
today and rebuilt
On 8/9/06, Russell McGregor [EMAIL PROTECTED] wrote:
I am doing some testing on a Sun x4100 on loan to us from a vendor, I
have loaded up a snapshot from about 20060803 and everything seems to
run fine from the standard /bsd kernel image, but it panics when
trying to boot bsd.mp. I updated src
I am doing some testing on a Sun x4100 on loan to us from a vendor, I
have loaded up a snapshot from about 20060803 and everything seems to
run fine from the standard /bsd kernel image, but it panics when
trying to boot bsd.mp. I updated src with a CVS checkout earlier
today and rebuilt
I suggest you try amd64 on the box. That should work fine.
dlg@ told me that there are interrupt issues with amd64.
I need to handle high throughput on several interfaces and filter them
with pf, and I believe that I would experience difficulties in that
situation.
Having said that, I will
I have not put -current on this system. Would making this machine public and
available to developers be of any use? I would also include ilom access.
Thoughts?
Nick
Er, rather I have put current on the x4100. Hmmm... I must still be brain
dead from work...
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Nick Shank
Sent: Thursday, June 08, 2006 6:54 PM
To: misc@openbsd.org
Subject: Re: OpenBSD 3.9 on a Sun Fire x4100
: misc@openbsd.org
Subject: Re: OpenBSD 3.9 on a Sun Fire x4100
Hi Nick,
On Mon, Jun 05, 2006 at 09:51:13PM -0700, [EMAIL PROTECTED] wrote:
| I have been looking high and low for instructions on how to get 3.9
| running on an x4100. Not finding any, I decided to play w/ it myself. I
| was able
On 06/06/2006, at 2:51 PM, [EMAIL PROTECTED] wrote:
Hi all,
I have been looking high and low for instructions on how to get 3.9
running on an x4100. Not finding any, I decided to play w/ it
myself. I
was able to make it work. While I have included the entire dmesg,
here
Hi all,
I have been looking high and low for instructions on how to get 3.9
running on an x4100. Not finding any, I decided to play w/ it myself. I
was able to make it work. While I have included the entire dmesg, here is
the interesting (for the SAS controller, anyway) bit:
mpi0 at pci2 dev 3
Hi Nick,
On Mon, Jun 05, 2006 at 09:51:13PM -0700, [EMAIL PROTECTED] wrote:
| I have been looking high and low for instructions on how to get 3.9
| running on an x4100. Not finding any, I decided to play w/ it myself. I
| was able to make it work. While I have included the entire dmesg, here
On Monday 15 May 2006 17.07, Peter Huncar wrote:
Hi misc
I got this: http://www.sun.com/servers/entry/x4100 from SUN to test it,
tried to install 3.9release a minute ago without success, the disks (SAS
- LSI adapter) were not detected. Unfortunately, I'm not able to donate
this HW
Hi misc
I got this: http://www.sun.com/servers/entry/x4100 from SUN to test it,
tried to install 3.9release a minute ago without success, the disks (SAS
- LSI adapter) were not detected. Unfortunately, I'm not able to donate
this HW :(
It detects the scsibus and device sd0 (as offline
I just came across an interesting white paper with lots more detail:
http://www.computerworld.com/x64/pdfs/
Sun_Fire_X4100_and_4200_WP_v14.pdf
Sam
right now. It's a SAS variant of the chips supported by
the mpt driver. According to marco it isn't as trivial as adding
the pci ids to the driver to make it work either. I'll gladly
accept a donation of a x4100 or x4200 to make it work ;)
The only other interesting thing in these machines
From: Henning Brauer [EMAIL PROTECTED]
* Daniel Ouellet [EMAIL PROTECTED] [2005-09-29 22:20]:
I was looking at the HP DL-145 G2 with SCSI on them and I also saw the
new Sun X4100.
Looking at the less then complete technical information on the Sun
server, I don't see the details of the chip set
Henning Brauer wrote:
I am more curious about the 2100 actually. Finally a vendor got it and
made a (apparently) decent single-CPU amd64 1U machine with a reasonable
price tag. I am uncertain what chipset they use, might be nForce, might
I like the 2100 better, but was looking at the 4100
it work either. I'll gladly accept a
donation of a x4100 or x4200 to make it work ;)
The only other interesting thing in these machines is the ipmi
stuff and the management controller.
When you say that the onboard storage controller probably won't work, do
you mean that managing it from
the pci ids to the driver to make it work either. I'll gladly
accept a donation of a x4100 or x4200 to make it work ;)
The only other interesting thing in these machines is the ipmi
stuff and the management controller.
When you say that the onboard storage controller probably won't
work
to replace more Cisco
gear!
However, picking the best servers for this is also important.
I was looking at the HP DL-145 G2 with SCSI on them and I also saw the
new Sun X4100.
I really would need a minimum of 4x 10/100/1000 Ethernet ports in these
boxes.
So, hopefully someone will be able
Daniel Ouellet wrote:
Looking at the less then complete technical information on the Sun
server, I don't see the details of the chip set use in that server,
network card, etc. So, I can't search to see if OpenBSD may work on it
or not.
Google haven't return query with the X4100 and OpenBSD
* Daniel Ouellet [EMAIL PROTECTED] [2005-09-29 22:20]:
I was looking at the HP DL-145 G2 with SCSI on them and I also saw the
new Sun X4100.
Looking at the less then complete technical information on the Sun
server, I don't see the details of the chip set use in that server,
network card
--On 30 September 2005 01:00 +0200, Henning Brauer wrote:
reasonable price tag. I am uncertain what chipset they use, might be
nForce, might be Via. As long as both GigEs and the SATA stuff
works, and there's no other showstopper, I don't care.
93 matches
Mail list logo
