public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: NVMe drive and grub
Date: Thu, 16 Jun 2016 06:11:10 +0000	[thread overview]
Message-ID: <9C788EAD-5BB1-4257-B78E-F5F213B311C2@antarean.org> (raw)
In-Reply-To: <10782500.05jPFbMMXn@andromeda>

On June 16, 2016 7:43:10 AM GMT+02:00, "J. Roeleveld" <joost@antarean.org> wrote:
>On Thursday, April 07, 2016 07:41:35 PM Remy Blank wrote:
>> peter@prh.myzen.co.uk wrote on 2016-04-07 17:24:
>> > I have a new box with an NVMe SSD drive attached to the PCI bus via
>an M.2
>> > interface. The drive shows up as /dev/nvme0n1, with partitions
>> > /dev/nvme0n1p1, /dev/nvme0n1p2, ...
>> > 
>> > After following the instructions in the handbook for a UEFI system,
>I get
>> > as far as a kernel panic. Grub finds the kernel and starts it, but
>it
>> > seems to be passing a null root device name.
>> > 
>> > Can anyone offer some advice to help me get past this?
>> 
>> Make sure you have BLK_DEV_NVME compiled into your kernel (not as a
>> module), and that you pass the right device name as a root FS to the
>> kernel. It might also help to use a very recent kernel.
>> 
>> FWIW, I'm writing this from a laptop that boots from two NVMe devices
>in
>> RAID 1 configuration, with kernel 4.4.5.
>> 
>> -- Remy
>
>Remy (and others),
>
>I have been trying to get Gentoo to boot from an NVME device, but I am
>getting 
>stuck.
>
>The kernel-config I use will boot when the root-device is on a spinning
>sata-
>disk and I can see the NVME device.
>When using the same config with the root-partition on the NVME, it
>fails, 
>complaining it can't find the root-partition.
>
>The NVME driver is loaded into the kernel (not module).
>
>Does anyone have a working config for a 4.4.6 kernel or any other
>version that 
>is currently in portage?
>
>Along with the boot-options being used?
>
>Many thanks,
>
>Joost

Ignore this.
Got it working, had to enable UEFI first for the NVME device in bios....

Problem caused by silly BIOS devs at ASUS....

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.


  reply	other threads:[~2016-06-16  6:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 15:24 [gentoo-user] NVMe drive and grub peter
2016-04-07 15:56 ` Jeremi Piotrowski
2016-04-08 12:21   ` Peter Humphrey
2016-04-08 13:25     ` Poison BL.
2016-04-07 17:41 ` [gentoo-user] " Remy Blank
2016-06-16  5:43   ` J. Roeleveld
2016-06-16  6:11     ` J. Roeleveld [this message]
2016-06-16  8:28       ` Peter Humphrey
2016-06-16 10:31         ` J. Roeleveld
2016-06-16 12:03           ` Peter Humphrey
  -- strict thread matches above, loose matches on Subject: below --
2016-04-08  9:01 peter
2016-04-08 19:23 ` Remy Blank

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9C788EAD-5BB1-4257-B78E-F5F213B311C2@antarean.org \
    --to=joost@antarean.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox