On Tue, 4 Dec 2018, Martin Husemann wrote:
On Tue, Dec 04, 2018 at 07:17:59PM +, Mike Pumford wrote:
One thing that surprised me was that I was testing with the USB install
image but instead of landing in sysinst I ended up at a a login prompt which
was unexpected. Could this be because the
On 04/12/2018 20:22, Manuel Bouyer wrote:
On Tue, Dec 04, 2018 at 07:17:59PM +, Mike Pumford wrote:
On 03/12/2018 22:47, Manuel Bouyer wrote:
Hello,
I synced our mpii(4) driver with the latest OpenBSD one and commited to HEAD.
I tested it with a SAS2 controller (I don't have SAS3 ones)
On Tue, Dec 04, 2018 at 07:17:59PM +, Mike Pumford wrote:
>
>
> On 03/12/2018 22:47, Manuel Bouyer wrote:
> > Hello,
> > I synced our mpii(4) driver with the latest OpenBSD one and commited to
> > HEAD.
> > I tested it with a SAS2 controller (I don't have SAS3 ones), so it would be
> > good
On Tue, Dec 04, 2018 at 07:26:09PM +, Mike Pumford wrote:
>
>
> On 04/12/2018 19:17, Mike Pumford wrote:
> o this tests one the cards you have brought in. I do have some other
> > 12G hosts but I think they are the same chip. They would be more awkward
> > to test with as they are serial cons
On 04/12/2018 19:31, Mike Pumford wrote:
On 04/12/2018 19:25, Martin Husemann wrote:
On Tue, Dec 04, 2018 at 07:17:59PM +, Mike Pumford wrote:
One thing that surprised me was that I was testing with the USB install
image but instead of landing in sysinst I ended up at a a login
prompt
On 04/12/2018 19:25, Martin Husemann wrote:
On Tue, Dec 04, 2018 at 07:17:59PM +, Mike Pumford wrote:
One thing that surprised me was that I was testing with the USB install
image but instead of landing in sysinst I ended up at a a login prompt which
was unexpected. Could this be because
On 04/12/2018 19:17, Mike Pumford wrote:
o this tests one the cards you have brought in. I do have some other
12G hosts but I think they are the same chip. They would be more awkward
to test with as they are serial console only machines that have only
ever been tested running linux.
Just lo
On Tue, Dec 04, 2018 at 07:17:59PM +, Mike Pumford wrote:
> One thing that surprised me was that I was testing with the USB install
> image but instead of landing in sysinst I ended up at a a login prompt which
> was unexpected. Could this be because the USB disk that was my root device
> ended
On 03/12/2018 22:47, Manuel Bouyer wrote:
Hello,
I synced our mpii(4) driver with the latest OpenBSD one and commited to HEAD.
I tested it with a SAS2 controller (I don't have SAS3 ones), so it would be
good if someone could test a SAS3 with some drives (the command setup is
different between
On 03/12/2018 22:47, Manuel Bouyer wrote:
Hello,
I synced our mpii(4) driver with the latest OpenBSD one and commited to HEAD.
I tested it with a SAS2 controller (I don't have SAS3 ones), so it would be
good if someone could test a SAS3 with some drives (the command setup is
different between
Hello,
I synced our mpii(4) driver with the latest OpenBSD one and commited to HEAD.
I tested it with a SAS2 controller (I don't have SAS3 ones), so it would be
good if someone could test a SAS3 with some drives (the command setup is
different between SAS2 and SAS3, this is the code path I can't te
On 30/11/2018 08:50, Stephen Borrill wrote:
I cannot easily attach drives to it (it has external ports only, and I
would need to drag it to our datacenter to connect it to something).
Let's see what Mike Pumford's PCI IDs are.
Wasn't able to check as I need to take a live USB stick in as t
On Fri, Nov 30, 2018 at 08:50:29AM +, Stephen Borrill wrote:
> On Thu, 29 Nov 2018, Manuel Bouyer wrote:
> > On Thu, Nov 29, 2018 at 03:56:37PM +, Stephen Borrill wrote:
> [snip]
> > > The other missing driver is handled by mpii in OpenBSD (SAS3408). Our mpii
> > > doesn't yet support any S
On Thu, 29 Nov 2018, Manuel Bouyer wrote:
On Thu, Nov 29, 2018 at 03:56:37PM +, Stephen Borrill wrote:
[snip]
The other missing driver is handled by mpii in OpenBSD (SAS3408). Our mpii
doesn't yet support any SAS3 cards.
[ 1.048805] vendor 1000 product 00af (SAS mass storage, revisi
On Thu, Nov 29, 2018 at 11:41:41PM +, Mike Pumford wrote:
>
>
> On 29/11/2018 18:16, Manuel Bouyer wrote:
>
> > Do you have drives connected to this controller ?
> > If so I can probably come up with a patch this week-end.
> > The SAS3 has a sighly different interface, but from looking at th
On 29/11/2018 18:16, Manuel Bouyer wrote:
Do you have drives connected to this controller ?
If so I can probably come up with a patch this week-end.
The SAS3 has a sighly different interface, but from looking at the OpenBSD
driver it's all in a single function.
I've got access to a spare LSI
On Thu, Nov 29, 2018 at 03:56:37PM +, Stephen Borrill wrote:
> On Mon, 26 Nov 2018, Stephen Borrill wrote:
> > Thanks Manuel!
> >
> > [ 1.048805] mfii0 at pci11 dev 0 function 0: "RAID 930-8i 2GB
> > Flash", firmware 50.3.0-1075, 2048MB cache
> > [ 1.048805] mfii0: interrupting at ioap
On Mon, 26 Nov 2018, Stephen Borrill wrote:
Thanks Manuel!
[ 1.048805] mfii0 at pci11 dev 0 function 0: "RAID 930-8i 2GB Flash",
firmware 50.3.0-1075, 2048MB cache
[ 1.048805] mfii0: interrupting at ioapic4 pin 2
[ 1.048805] scsibus0 at mfii0: 64 targets, 8 luns per target
[ 2.
Thanks Manuel!
[ 1.048805] mfii0 at pci11 dev 0 function 0: "RAID 930-8i 2GB Flash",
firmware 50.3.0-1075, 2048MB cache
[ 1.048805] mfii0: interrupting at ioapic4 pin 2
[ 1.048805] scsibus0 at mfii0: 64 targets, 8 luns per target
[ 2.161214] scsibus0: waiting 2 seconds for device
19 matches
Mail list logo