[gentoo-user] EFI install ( continum) [ system hangs at boot ]

[gentoo-user] EFI install ( continum) [ system hangs at boot ]

[German]

Ok gentooers. I did manage to install gentoo on EFI, it boots, however hangs at "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block ( 0,0)"

Does anyone have an idea what is going on? Is that fstab, something else? I appreciate any advice. I want my laptop runs Gentoo.

-- 
German <gentgerman@gmail.com>

Re: [gentoo-user] EFI install ( continum) [ system hangs at boot ]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 558 bytes --]

On Fri, 27 Feb 2015 06:53:32 -0500, German wrote:

> Ok gentooers. I did manage to install gentoo on EFI, it boots, however
> hangs at "Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block ( 0,0)"
> 
> Does anyone have an idea what is going on?

The kernel cannot find the block device containing your root filesystem.
Either you have given the wrong root= option to the kernel or you have
not compiled in the driver your your hard disk driver.


-- 
Neil Bothwick

I'm writing a book. I've got the page numbers done.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] EFI install ( continum) [ system hangs at boot ]

[German]

On Fri, 27 Feb 2015 12:12:24 +0000
Neil Bothwick <neil@digimed.co.uk> wrote:

> On Fri, 27 Feb 2015 06:53:32 -0500, German wrote:
> 
> > Ok gentooers. I did manage to install gentoo on EFI, it boots, however
> > hangs at "Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block ( 0,0)"
> > 
> > Does anyone have an idea what is going on?
> 
> The kernel cannot find the block device containing your root filesystem.
> Either you have given the wrong root= option to the kernel

Where is this given? Can you elaborate?

 or you have
> not compiled in the driver your your hard disk driver.

I am using SSD Patriot Blaze. Is it also should be compiled somewhere in the kernel?
Why is the system boots at all?
> 
> 
> -- 
> Neil Bothwick
> 
> I'm writing a book. I've got the page numbers done.


-- 
German <gentgerman@gmail.com>

Re: [gentoo-user] EFI install ( continum) [ system hangs at boot ]

[German]

On Fri, 27 Feb 2015 12:12:24 +0000
Neil Bothwick <neil@digimed.co.uk> wrote:

> On Fri, 27 Feb 2015 06:53:32 -0500, German wrote:
> 
> > Ok gentooers. I did manage to install gentoo on EFI, it boots, however
> > hangs at "Kernel panic - not syncing: VFS: Unable to mount root fs on
> > unknown-block ( 0,0)"
> > 
> > Does anyone have an idea what is going on?
> 
> The kernel cannot find the block device containing your root filesystem.
> Either you have given the wrong root= option to the kernel

Are you talking about this?

"UEFI does not pass kernel parameters to the kernel during normal boot, so you need to hardcode them via CONFIG_CMDLINE. Example for the root partition on /dev/sda2:
KERNEL Enable built-in kernel parameters

Processor type and features  --->
    [*] Built-in kernel command line
    (root=/dev/sda2)"


 or you have
> not compiled in the driver your your hard disk driver.
> 
> 
> -- 
> Neil Bothwick
> 
> I'm writing a book. I've got the page numbers done.


-- 
German <gentgerman@gmail.com>

Re: [gentoo-user] EFI install ( continum) [ system hangs at boot ]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

On Fri, 27 Feb 2015 07:23:42 -0500, German wrote:

> > > Ok gentooers. I did manage to install gentoo on EFI, it boots,
> > > however hangs at "Kernel panic - not syncing: VFS: Unable to mount
> > > root fs on unknown-block ( 0,0)"
> > > 
> > > Does anyone have an idea what is going on?
> > 
> > The kernel cannot find the block device containing your root
> > filesystem. Either you have given the wrong root= option to the kernel
> 
> Where is this given? Can you elaborate?

After the kernel name if you are using GRUB or Gummiboot. If you are
directly loading the kerne you probably have to compile it into the
kernel with CONFIG_CMDLINE.

> > not compiled in the driver for your hard disk driver.
> 
> I am using SSD Patriot Blaze. Is it also should be compiled somewhere
> in the kernel? Why is the system boots at all?

It's the controller that needs to be compile in, which is usually AHCI
these days. This is covered in the kernel section of the handbook.


-- 
Neil Bothwick

We never really grow up; we only learn how to act in public.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] EFI install ( continum) [ system hangs at boot ]

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 672 bytes --]

On Fri, 27 Feb 2015 07:49:20 -0500, German wrote:

> > The kernel cannot find the block device containing your root
> > filesystem. Either you have given the wrong root= option to the
> > kernel  
> 
> Are you talking about this?
> 
> "UEFI does not pass kernel parameters to the kernel during normal boot,
> so you need to hardcode them via CONFIG_CMDLINE. Example for the root
> partition on /dev/sda2: KERNEL Enable built-in kernel parameters
> 
> Processor type and features  --->
>     [*] Built-in kernel command line
>     (root=/dev/sda2)"

Yes, if you are not using a boot manager.


-- 
Neil Bothwick

Top Oxymorons Number 24: New classic

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-user] EFI install ( continum) [ system hangs at boot ]

[German]

On Fri, 27 Feb 2015 14:15:04 +0000
Neil Bothwick <neil@digimed.co.uk> wrote:

> On Fri, 27 Feb 2015 07:49:20 -0500, German wrote:
> 
> > > The kernel cannot find the block device containing your root
> > > filesystem. Either you have given the wrong root= option to the
> > > kernel  
> > 
> > Are you talking about this?
> > 
> > "UEFI does not pass kernel parameters to the kernel during normal boot,
> > so you need to hardcode them via CONFIG_CMDLINE. Example for the root
> > partition on /dev/sda2: KERNEL Enable built-in kernel parameters
> > 
> > Processor type and features  --->
> >     [*] Built-in kernel command line
> >     (root=/dev/sda2)"
> 
> Yes, if you are not using a boot manager.

Hmm.. I was using some sort of boot manager, efibootmgr, however there was no word in install docs how to configure it to point to root device.. So, are you advising on gummiboot? Are people happy with it? I found gentoo wiki how to configure it, so I must give it a try. Thanks for your input, I guess the problem is solved now. On to the next install with gummi


> 
> 
> -- 
> Neil Bothwick
> 
> Top Oxymorons Number 24: New classic


-- 
German <gentgerman@gmail.com>

Re: [gentoo-user] EFI install ( continum) [ system hangs at boot ]

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1641 bytes --]

On Friday 27 Feb 2015 15:14:18 German wrote:
> On Fri, 27 Feb 2015 14:15:04 +0000
> 
> Neil Bothwick <neil@digimed.co.uk> wrote:
> > On Fri, 27 Feb 2015 07:49:20 -0500, German wrote:
> > > > The kernel cannot find the block device containing your root
> > > > filesystem. Either you have given the wrong root= option to the
> > > > kernel
> > > 
> > > Are you talking about this?
> > > 
> > > "UEFI does not pass kernel parameters to the kernel during normal boot,
> > > so you need to hardcode them via CONFIG_CMDLINE. Example for the root
> > > partition on /dev/sda2: KERNEL Enable built-in kernel parameters
> > > 
> > > Processor type and features  --->
> > > 
> > >     [*] Built-in kernel command line
> > >     (root=/dev/sda2)"
> > 
> > Yes, if you are not using a boot manager.
> 
> Hmm.. I was using some sort of boot manager, efibootmgr, however there was
> no word in install docs how to configure it to point to root device.. So,
> are you advising on gummiboot? Are people happy with it? I found gentoo
> wiki how to configure it, so I must give it a try. Thanks for your input,
> I guess the problem is solved now. On to the next install with gummi

You can still use the kernel stub to boot directly your OS, but you may need 
to specify the root fs, if it is BTRFS (not sure about others):

$ grep CONFIG_CMDLINE /usr/src/linux/.config
# CONFIG_CMDLINE_PARTITION is not set
CONFIG_CMDLINE_BOOL=y
CONFIG_CMDLINE="root=/dev/sda2 rootfstype=btrfs"
# CONFIG_CMDLINE_OVERRIDE is not set

Also the fs type should be built directly in the kernel, rather than a module.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] EFI install ( continum) [ system hangs at boot ]

[Rich Freeman]

On Fri, Feb 27, 2015 at 2:39 PM, Mick <michaelkintzios@gmail.com> wrote:
> You can still use the kernel stub to boot directly your OS, but you may need
> to specify the root fs, if it is BTRFS (not sure about others):
>
> $ grep CONFIG_CMDLINE /usr/src/linux/.config
> # CONFIG_CMDLINE_PARTITION is not set
> CONFIG_CMDLINE_BOOL=y
> CONFIG_CMDLINE="root=/dev/sda2 rootfstype=btrfs"
> # CONFIG_CMDLINE_OVERRIDE is not set
>
> Also the fs type should be built directly in the kernel, rather than a module.

Presumably you could also build an initramfs into the kernel, not that
I've ever tried it.

I think most just use gummiboot because it is far more flexible.  If
you're hard-coding all this stuff into your kernel then if anything
changes you're going to be dropping to rescue disks.

-- 
Rich

Re: [gentoo-user] EFI install ( continum) [ system hangs at boot ]

[Fernando Rodriguez]

[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]

On Friday, February 27, 2015 10:14:18 AM German wrote:
> Hmm.. I was using some sort of boot manager, efibootmgr, however there was no 
word in install docs how to configure it to point to root device.. So, are you 
advising on gummiboot? Are people happy with it? I found gentoo wiki how to 
configure it, so I must give it a try. Thanks for your input, I guess the 
problem is solved now. On to the next install with gummi
> 

Efibootmgr is not a boot manager, it's an utility to interface with the EFI 
firmware on the motherboard and you don't need to hardcode the command line on 
the kernel, look at the -u option of efibootmgr. You can even load an initrd 
with it by specifying the efi_memmap boot option. I use something like this (it 
shoulld work with any firmware because Windows uses it):

efibootmgr -p 2 -c -b 0001 -l "\EFI\Linux\vmlinuz.efi" -L "Gentoo Linux" -u 
"root=/dev/sda2 resume=/dev/sda3 quiet splash efi_memmap 
initrd=/EFI/Linux/initramfs.img"

I normally boot directly with the EFI stub because it's slightly faster and 
prettier (completely graphical) but I also have GRUB2 installed as a separate 
EFI entry for flexibility in case I need to boot another kernel or play with 
the command line at boot time.


-- 
Fernando Rodriguez

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: [gentoo-user] EFI install ( continum) [ system hangs at boot ]

[Tom H]

On Fri, Feb 27, 2015 at 5:47 PM, Fernando Rodriguez
<frodriguez.developer@outlook.com> wrote:
>
> Efibootmgr is not a boot manager, it's an utility to interface with the EFI
> firmware on the motherboard and you don't need to hardcode the command line on
> the kernel, look at the -u option of efibootmgr. You can even load an initrd
> with it by specifying the efi_memmap boot option. I use something like this (it
> shoulld work with any firmware because Windows uses it):
>
> efibootmgr -p 2 -c -b 0001 -l "\EFI\Linux\vmlinuz.efi" -L "Gentoo Linux" -u
> "root=/dev/sda2 resume=/dev/sda3 quiet splash efi_memmap
> initrd=/EFI/Linux/initramfs.img"

Interesting. I must be over-complicating things because I use the
following when I want to use the EFI stub without gummiboot:

# cat /boot/efi/efi-extra.txt \
    | iconv -f ascii -t ucs2 \
    | efibootmgr -b 0000 -c -L 3.19.0 -l vmlinuz-3.19.0 -u -@ -

where

# cat /boot/efi/efi-extra.txt
initrd=initrd.img-3.19.0
root=UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 ro
init=/lib/systemd/systemd

Re: [gentoo-user] EFI install ( continum) [ system hangs at boot ]

[Fernando Rodriguez]

On Saturday, February 28, 2015 12:50:37 PM Tom H wrote:
> On Fri, Feb 27, 2015 at 5:47 PM, Fernando Rodriguez
> <frodriguez.developer@outlook.com> wrote:
> >
> > Efibootmgr is not a boot manager, it's an utility to interface with the EFI
> > firmware on the motherboard and you don't need to hardcode the command line 
on
> > the kernel, look at the -u option of efibootmgr. You can even load an 
initrd
> > with it by specifying the efi_memmap boot option. I use something like this 
(it
> > shoulld work with any firmware because Windows uses it):
> >
> > efibootmgr -p 2 -c -b 0001 -l "\EFI\Linux\vmlinuz.efi" -L "Gentoo Linux" -u
> > "root=/dev/sda2 resume=/dev/sda3 quiet splash efi_memmap
> > initrd=/EFI/Linux/initramfs.img"
> 
> Interesting. I must be over-complicating things because I use the
> following when I want to use the EFI stub without gummiboot:
> 
> # cat /boot/efi/efi-extra.txt \
>     | iconv -f ascii -t ucs2 \
>     | efibootmgr -b 0000 -c -L 3.19.0 -l vmlinuz-3.19.0 -u -@ -
> 
> where
> 
> # cat /boot/efi/efi-extra.txt
> initrd=initrd.img-3.19.0
> root=UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 ro
> init=/lib/systemd/systemd
> 

It's a good idea to do that as it's less error prone. I don't know if you need 
iconv in the pipeline but if you put the arguments on the command line it's 
not needed. I just called my kernel vmlinuz.efi so I don't need to do that 
everytime I update it and use grub if I need to boot an alternate kernel or 
boot with different options.

-- 
Fernando Rodriguez

Re: [gentoo-user] EFI install ( continum) [ system hangs at boot ]

[Tom H]

On Mon, Mar 2, 2015 at 2:00 AM, Fernando Rodriguez
<frodriguez.developer@outlook.com> wrote:
> On Saturday, February 28, 2015 12:50:37 PM Tom H wrote:
>> On Fri, Feb 27, 2015 at 5:47 PM, Fernando Rodriguez
>> <frodriguez.developer@outlook.com> wrote:
>>>
>>> Efibootmgr is not a boot manager, it's an utility to interface with the EFI
>>> firmware on the motherboard and you don't need to hardcode the command line
> on
>>> the kernel, look at the -u option of efibootmgr. You can even load an
> initrd
>>> with it by specifying the efi_memmap boot option. I use something like this
> (it
>>> shoulld work with any firmware because Windows uses it):
>>>
>>> efibootmgr -p 2 -c -b 0001 -l "\EFI\Linux\vmlinuz.efi" -L "Gentoo Linux" -u
>>> "root=/dev/sda2 resume=/dev/sda3 quiet splash efi_memmap
>>> initrd=/EFI/Linux/initramfs.img"
>>
>> Interesting. I must be over-complicating things because I use the
>> following when I want to use the EFI stub without gummiboot:
>>
>> # cat /boot/efi/efi-extra.txt \
>>     | iconv -f ascii -t ucs2 \
>>     | efibootmgr -b 0000 -c -L 3.19.0 -l vmlinuz-3.19.0 -u -@ -
>>
>> where
>>
>> # cat /boot/efi/efi-extra.txt
>> initrd=initrd.img-3.19.0
>> root=UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 ro
>> init=/lib/systemd/systemd
>
> It's a good idea to do that as it's less error prone. I don't know if you need
> iconv in the pipeline but if you put the arguments on the command line it's
> not needed. I just called my kernel vmlinuz.efi so I don't need to do that
> everytime I update it and use grub if I need to boot an alternate kernel or
> boot with different options.

Thanks. Next time that I feel adventurous, I'll replace my gummiboot
nvram entry with a vmlinuz one without cat and iconv. I made big
changes after the last efi boot thread on this list so I'll wait a
bit. :)