> On Jun 22, 2016, at 9:20 AM, Youzhong Yang wrote:
>
> Thanks Robert. Yes the driver failed to attach:
>
> # rem_drv nvme
> # add_drv nvme
> devfsadm: driver failed to attach: nvme
> Warning: Driver (nvme) successfully added to system but failed to attach
Here's a dtrace
> On 18 Jun 2016 at 12:14, Joshua M. Clulow wrote:
>
>> On 18 June 2016 at 12:12, Joshua M. Clulow wrote:
>> You _may_ be able to test these out on your running system, rather
>> than just rebuilding the image, with something like:
>>
>> update_drv -a -i
> On Jun 19, 2016, at 6:46 PM, Nigel W <nige...@nosun.ca> wrote:
>
> On Sun, Jun 19, 2016 at 12:33 PM, Dale Ghent <da...@elemental.org> wrote:
> One thing I'd like to see people who have ixgbe hardware (X550 and anything
> else) is RSS. A good smoke test is to open u
> On Jun 19, 2016, at 1:12 PM, Nigel W wrote:
>
> On Sat, Jun 18, 2016 at 3:43 PM, Nigel W wrote:
> I am going to try creating a machine to make sure nothing weird happens but
> it seems to be working at this point.
>
> It seems to be working well.
Godo
> On Aug 10, 2016, at 10:12 PM, Ian Collins wrote:
>
> On 11/08/16 1:08 pm, Robert Mustacchi wrote:
>> On 8/10/16 18:01 , Robert Mustacchi wrote:
>>> Okay, thanks for providing that Ian. I'm trying to think through what
>>> might cause this case and how we might better
> On Aug 10, 2016, at 10:52 PM, Robert Mustacchi <r...@joyent.com> wrote:
>
> On 8/10/16 19:46 , Dale Ghent wrote:
>> The problem stems from the card initializing at power-on and going into LPLU
>> mode immediately. When the kernel gets around to booting and
I had some initial trouble on this board as well, but in different ways, and a
restore of bios defaults fixed it. If you have the v 1.0a bios, upgrade it to
the current rev… it’s far better.
> On Jul 13, 2016, at 5:17 PM, Nigel W wrote:
>
> On Wed, Jul 13, 2016 at 2:31 PM,
> On Aug 8, 2016, at 5:33 AM, Ian Collins wrote:
>
> On 08/ 8/16 05:29 AM, Robert Mustacchi wrote:
>> On 8/6/16 13:21 , Ian Collins wrote:
>>> On 7/08/16 2:46 am, Robert Mustacchi wrote:
>>>
Hmm, okay. So what is the output of dladm show-linkprop on that device?
> On Aug 15, 2016, at 5:22 PM, Ian Collins wrote:
>
> On 13/08/16 5:58 am, Robert Mustacchi wrote:
>> Ian, Killian, are any of these in a place where we could maybe put
>> together something which dumps some of the register space and you might
>> be able to run it? I can
> On Feb 16, 2017, at 12:59 PM, Robert Mustacchi wrote:
>
> On 2/16/17 4:06 , 강경원 wrote:
>> I updated the platform image with "20170202T033902Z" and booted again.
>>
>> But the result was like below. Maybe it's nvme 1.2
>
> Yes, the PM963 is specified to be a NVMe 1.2 device
> On Jan 15, 2017, at 3:36 PM, Matthew Parsons
> wrote:
>
> I expect this is more of a beginner pkgsrc question, but the documentation I
> can find on the multi-arch images is minimal.
> (https://www.perkin.org.uk/posts/multiarch-package-support-in-smartos.html )
> On Aug 24, 2016, at 8:21 PM, 龙白滔 wrote:
>
> hi,
>
> We'd like to move a HA DB deployment to SmartOS. The old deplpyment is: a DB
> server is deployed on SAN storage, and two application servers connect to the
> DB server and synchronize access(read & write) to it.
> On Sep 14, 2016, at 10:45 AM, Rob Seastrom wrote:
>
>
> Hi folks,
>
> I'm looking at the "works for me" configurations; unfortunately there doesn't
> seem to be quite the information I'm looking for there so I figured I'd reach
> out here and see if anyone else is
> On Jan 13, 2017, at 2:47 AM, 郑圆杰 wrote:
>
> Hi,
>How to set SO_RCVTIMEO and SO_SNDTIMEO in smartos?
> Is there any syscall or kernel tunable parameter for socket timeout?
These two do appear to be missing from the setsockopt(3SOCKET) man page, but
they
> On Dec 23, 2016, at 11:00 AM, Jason Lawrence wrote:
>
> I have a Supermicro board with integrated IPMI support. Unfortunately,
> it's become inaccessible from the web interface and I need to reset the
> configuration. As understand things, this requires running a utility
I have SMCI servers that have mangled or all-zero UUIDs as well.
By "mangled", SMCI has made the extraordinarily poor choice on several of their
X10 platforms to set the first 4 fields to 0 and the last 48 bits to the MAC
address of one of the on-board ethernet PHYs, in an apparent "good
To chime in as well ... I've used a X10SDV-TLN4F as my main illumos dev box for
the past year with no problems. I used this same board to add X552/X557 support
to the ixgbe driver last year. They're fine systems.
The only thing that's currently needed for this (and a plethora of other
I'm using a 960 Pro M.2 stick currently, but on OmniOS. Getting it recognized
requires "strict-version=1" in /kernel/drv/nvme.conf to allow for this NVMe 1.2
device to be recognized, however I think the latest SmartOS image has a
Joyent-developed improvement to the nvme driver to bring in 1.2
You might be running into:
OS-6114 - illumos#7955 broke delegated datasets in lx-brand
Could anyone at Joyent weigh in on this?
+ /*
+* libshare is either not installed or we're in a branded zone. The
+* rest of the wrapper functions around the libshare calls already
+
As am I. Having spent some years in the area as child I would not mind the
travel at all :)
/dale
> On May 22, 2017, at 4:10 AM, InterNetX - Juergen Gotteswinter
> wrote:
>
> Definitely interested
>
> Juergen (located in Regensburg)
>
>
>> Am 19.05.2017 um 22:54
> On May 8, 2017, at 5:13 AM, Nicholas Lee wrote:
>
> Just upgraded to joyent_20170427T222500Z.
>
> imported and created an image from 7b5981c4-1889-11e7-b4c5-3f3bdfc9b88b -
> ubuntu-16.04 20170403.
>
> Using a delegated dataset and remounted it with the zone to /data
This is an intended change.
/usr/perl5 is intended only for the operation of illumos components which
require perl. The intention is that, over time, these perl (and probably Java,
too) components will be rewritten in C or deprecated, as appropriate.
If you require a general-purpose perl
22 matches
Mail list logo