Re: PCIe NVME drives not detected on Dell R6515

From: Yuri Pankov <ypankov_at_fastmail.com>
Date: Sat, 18 Apr 2020 00:39:06 +0300
Scott Long wrote:
> 
> 
>> On Apr 17, 2020, at 3:07 PM, Miroslav Lachman <000.fbsd_at_quip.cz> wrote:
>>
>> Scott Long wrote on 04/17/2020 23:04:
>>>> On Apr 17, 2020, at 2:45 PM, Miroslav Lachman <000.fbsd_at_quip.cz> wrote:
>>>>
>>>> Scott Long wrote on 04/17/2020 22:17:
>>>>>> On Apr 17, 2020, at 1:47 PM, Miroslav Lachman <000.fbsd_at_quip.cz> wrote:
>>>>>>
>>>>>> Kurt Jaeger wrote on 04/17/2020 21:44:
>>>>>>> Hi!
>>>>>>>>> pciconf -lBc pcib12
>>>>>>>>> pciconf -lBc pcib13
>>>>>>>>
>>>>>>>> Printscreen attached.
>>>>>>> Attachments are stripped from the list -- can you put them somewhere
>>>>>>> online ?
>>>>>>
>>>>>> Here it is https://ibb.co/c1dZrTf
>>>>>>
>>>>>> Miroslav Lachman
>>>>>>
>>>>> Ok, the bridges know about their downstream bus numbers, but I see nothing that suggests that they’re being probed.  The next step would be bootverbose, but that’s going to be a lot of output to collect in screen captures.
>>>>
>>>> Over 3000 lines long but I finally managed to make SOL work so I have it as text!
>>>>
>>>> https://pastebin.pl/view/90fdaafb
>>>>
>>> This helped a lot, thanks.  It looks like these PCIe buses are marked as being hotplug, and for some reason we’re not probing them.  At this point, I’d need to feed you some kernel patches that will dump out more info, but you’d have to compile them and get them onto your boot media.  Is that a possibility?
>>
>> Currently I have all machines on 11.3 (where I can rebuild kernel without problem)
>> If CURRENT is required I would need to setup some CURRENT VM in VirtualBox.
>>
>> Can you send me some link to documentation who should I create new ISO after rebuild?
>>
> 
> I don’t know of any docs for doing custom releases, and it looks like it’s harder than it used to be to insert custom patches.  That said, I recommend doing the following on your 11.x build system:
> 
> 1.  Do a clean `make buildworld` with an up-to-date tree
> 2.  change into the `release` directory that you just did the buildworld from
> 3.  `sudo make release NOPORTS= NODOC= CHROOTDIR=/usr/tmp/release SRCBRANCH="base/stable/11_at_rHEAD”`
> 
> You can set CHROOTDIR to whatever you want that has a few GB of space, but remember where you’ve set it for later steps.  This will build a release with stock sources.  Let it complete, both to prepare for the next step and to ensure that it works.  It’ll take an hour or two depending on your machine speed
> 
> 4.  Take the patch that I’ll send you shortly and apply it to $CHROOTDIR/usr/src
> 5.  `sudo make memstick NOPORTS= NODOC= SRC_UPDATE_SKIP= CHROOTDIR=/usr/tmp/release`

Just a thought - it could possibly be easier to build just the patched 
kernel and try booting it (11.3 userland should work with CURRENT 
kernel, right?), doing the kernel-toolchaing target first, and using 
INSTKERNNAME with the installkernel target to temporary select it from 
loader menu.
Received on Fri Apr 17 2020 - 19:39:12 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:23 UTC