On 1/13/06, Bill Marquette <[EMAIL PROTECTED]> wrote:
> On 1/11/06, Bill Marquette <[EMAIL PROTECTED]> wrote:
> > On 12/9/05, Srebrenko Sehic <[EMAIL PROTECTED]> wrote:
> > The ciss driver works fine (no idea about speeds at this time, more on
> > that in a second).
> > The onboard broadcom nics do
On 1/13/06, Bill Marquette <[EMAIL PROTECTED]> wrote:
> I wanted to followup on the network connectivity issue I mentioned
> with the DL385. I obviously didn't try hard enough. After moving the
> machine to another location and using a crossover cable to connect it
> to another OpenBSD box instea
On 1/11/06, Bill Marquette <[EMAIL PROTECTED]> wrote:
> On 12/9/05, Srebrenko Sehic <[EMAIL PROTECTED]> wrote:
> The ciss driver works fine (no idea about speeds at this time, more on
> that in a second).
> The onboard broadcom nics do show up, but I can't seem to get link on them
> pci-x connected
On 12/9/05, Srebrenko Sehic <[EMAIL PROTECTED]> wrote:
>
> 5) DL385, SCSI/RAID/SmartArray P600/6i/6400 = showstopper, OpenBSD
> can't see the raiser board and hence the RAID controller seated in it
> (tested on amd64/3.8-STABLE and -current)
I can confirm this is still the case on a snapshot from
On Fri, 09 Dec 2005 10:24:02 -0800, Ted Unangst wrote:
> try disabling softdep to see if it changes things.
(I dunno if anybody still sees this; but finally I tried the same machine
as in the parallel thread
("Interesting ! - Just for the discussion, here are those on the ML350;
running bsd: ...)
On Fri, 09 Dec 2005 12:30:46 +0100, Pete Vickers wrote:
> [EMAIL PROTECTED] /tmp> dd if=/dev/zero of=junk.data bs=1m count=500
> 500+0 records in
> 500+0 records out
> 524288000 bytes transferred in 68.774 secs (7623327 bytes/sec)
> [EMAIL PROTECTED] /tmp>
>
> [EMAIL PROTECTED] /tmp> dd if=/dev/z
Srebrenko Sehic wrote:
On 12/9/05, Uwe Dippel <[EMAIL PROTECTED]> wrote:
So you probably saw mine as well, Proliant 350.
I have no solution yet, but a few more boxes rolling in that need more
than that single Broadcom on-board piece.
Is this a HP problem or an OpenBSD problem ? I'll try Linux
On 12/9/05, Srebrenko Sehic <[EMAIL PROTECTED]> wrote:
> On 12/9/05, Pete Vickers <[EMAIL PROTECTED]> wrote:
>
> > for my DL145 (pretty new) I get a reasonable-ish disk I/O of ~60Mb/s
> > ( with CPU at 99% idle)
> >
> > [EMAIL PROTECTED] /root> dd if=/dev/rwd0a of=/dev/null bs=1m count=1000
> > 100
On 9. des. 2005, at 11.33, Srebrenko Sehic wrote:
On 12/9/05, Pete Vickers <[EMAIL PROTECTED]> wrote:
for my DL145 (pretty new) I get a reasonable-ish disk I/O of ~60Mb/s
( with CPU at 99% idle)
[EMAIL PROTECTED] /root> dd if=/dev/rwd0a of=/dev/null bs=1m count=1000
1000+0 records in
1000+0 r
On 12/9/05, Pete Vickers <[EMAIL PROTECTED]> wrote:
> for my DL145 (pretty new) I get a reasonable-ish disk I/O of ~60Mb/s
> ( with CPU at 99% idle)
>
> [EMAIL PROTECTED] /root> dd if=/dev/rwd0a of=/dev/null bs=1m count=1000
> 1000+0 records in
> 1000+0 records out
> 1048576000 bytes transferred i
On 9. des. 2005, at 10.01, Srebrenko Sehic wrote:
2) DL145 (G2), SATA/nForce4 = works, but the disk is slow and the CPU
spends 100% of time in kernel with heavy disk activity. (tested on
i386/3.8-STABLE)
for my DL145 (pretty new) I get a reasonable-ish disk I/O of ~60Mb/s
( with CPU at 9
On 12/9/05, Uwe Dippel <[EMAIL PROTECTED]> wrote:
> So you probably saw mine as well, Proliant 350.
> I have no solution yet, but a few more boxes rolling in that need more
> than that single Broadcom on-board piece.
>
> Is this a HP problem or an OpenBSD problem ? I'll try Linux on the next
> box
On Wed, 07 Dec 2005 21:40:49 -0500, Daniel Ouellet wrote:
> Not sure if anyone was able to see the PCI-x slot in the HP 145 G2 yet.
> I did research the archive before and it did say the PCI-Express wasn't
> available
So you probably saw mine as well, Proliant 350.
I have no solution yet, but a
On 12/7/05, Daniel Ouellet <[EMAIL PROTECTED]> wrote:
> Hmmm,
>
> May be I don't understand the differences what so ever, but shouldn't
> the dmesg of the regular bsd and bsd.mp detect the same hardware?
>
> Here is the dmesg from the bsd.mp one.
the interrupt routing code is pretty much totally d
Hmmm,
May be I don't understand the differences what so ever, but shouldn't
the dmesg of the regular bsd and bsd.mp detect the same hardware?
Here is the dmesg from the bsd.mp one.
I just find it interesting and curious at the same time.
OpenBSD 3.8 (GENERIC.MP) #504: Sat Sep 10 16:02:38 M
15 matches
Mail list logo
