1 |
peter@××××××××××××.uk wrote on 2016-04-08 11:01: |
2 |
> Remy Blank <remy.blank@×××××.com> wrote : |
3 |
> |
4 |
>> peter@××××××××××××.uk |
5 |
>> wrote on 2016-04-07 17:24: |
6 |
>>> I have a new box with an NVMe SSD drive attached to the PCI bus via an M.2 |
7 |
>> interface. The drive shows up as /dev/nvme0n1, with partitions /dev/nvme0n1p1, |
8 |
>> /dev/nvme0n1p2, ... |
9 |
>>> |
10 |
>>> After following the instructions in the handbook for a UEFI system, I get as |
11 |
>> far as a kernel panic. Grub finds the kernel and starts it, but it seems to be |
12 |
>> passing a null root device name. |
13 |
>>> |
14 |
>>> Can anyone offer some advice to help me get past this? |
15 |
>> |
16 |
>> Make sure you have BLK_DEV_NVME compiled into your kernel (not as a |
17 |
>> module), and that you pass the right device name as a root FS to the |
18 |
>> kernel. It might also help to use a very recent kernel. |
19 |
> |
20 |
> Yes, I have that compiled in, and the kernel is 4.1.15-r1. |
21 |
> |
22 |
>> FWIW, I'm writing this from a laptop that boots from two NVMe devices in |
23 |
>> RAID 1 configuration, with kernel 4.4.5. |
24 |
> |
25 |
> Now, that's just showing off :-) |
26 |
|
27 |
Now now, I was merely providing evidence that what you are trying to do |
28 |
actually works. |
29 |
|
30 |
... But yeah, it's fast :) |
31 |
|
32 |
-- Remy |