Re: [gentoo-user] system won't boot - --no-bootloader set; Skipping bootloader update ...

2020-12-11 Thread Michael
On Friday, 11 December 2020 18:56:19 GMT the...@sys-concept.com wrote:
> On 12/11/2020 11:39 AM, Michael wrote:
> > On Friday, 11 December 2020 18:24:27 GMT the...@sys-concept.com wrote:
> >> On 12/11/2020 10:45 AM, Michael wrote:
> >>> On Friday, 11 December 2020 16:42:08 GMT tedheadster wrote:
>  On Fri, Dec 11, 2020 at 9:27 AM  wrote:
> > On 12/11/2020 07:07 AM, the...@sys-concept.com wrote:
> >> Now, when I boot I get a message:
> >> 
> >> Block device UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b is not a valid
> >> root device.
> > 
> > This puzzles me. I cannot find the string "is not a valid root device"
> > (or
>  
>  sub-strings) in the source code for the Linux kernel, GRUB2, and
>  refind.
>  It
>  seems to me it should be in one of them.
>  
>  - Matthew
> >>> 
> >>> The error is indicative of the kernel driver for the / block device
> >>> missing. If it is not built in-the-kernel, but as a module, then it
> >>> should be in initramfs.
> >>> 
> >>> Copy the kernel image, System.map, .config and corresponding initramfs
> >>> to
> >>> the /boot partition, then point your boot manager to the kernel to boot
> >>> it.
> >> 
> >> How do you copy/generate initramfs in /boot directory?
> > 
> > https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel
> > https://wiki.gentoo.org/wiki/Genkernel
> > 
> > If you're using genkernel it will copy it to /boot.  Besides the Handbook
> > you may find the following reference material on boot managers/loaders
> > useful:
> > 
> > For rEFInd see here:
> > 
> > https://wiki.gentoo.org/wiki/Refind
> > 
> > For GRUB see here:
> > 
> > https://wiki.gentoo.org/wiki/GRUB2
> > 
> > For efibootmgr see here:
> > 
> > https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/
> > Bootloader#Alternative_2:_efibootmgr
> 
> After I compile kernel I usually get this message (WHY?):
> 
> * You will find the initramfs in '/boot/initramfs-5.4.72-gentoo.img'.
> 
> * WARNING... WARNING... WARNING...
> * Additional kernel parameters that *may* be required to boot properly:
> *
> * With support for several ext* filesystems available, it may be needed to
> * add "rootfstype=ext3" or "rootfstype=ext4" to the list of boot parameters.

I would have thought all modern boot loaders can read ext* filesystems, 
without needing to specify the filesystem type by passing the kernel 
parameters yourself to the boot loader.  However, I don't use genkernel to 
know how to configure/modify it so it boots with different boot managers.  If 
the details are not explained in the links I provided above, someone 
experienced in using genkernel should give some pointers.

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] system won't boot - --no-bootloader set; Skipping bootloader update ...

2020-12-11 Thread thelma
On 12/11/2020 11:39 AM, Michael wrote:
> On Friday, 11 December 2020 18:24:27 GMT the...@sys-concept.com wrote:
>> On 12/11/2020 10:45 AM, Michael wrote:
>>> On Friday, 11 December 2020 16:42:08 GMT tedheadster wrote:
 On Fri, Dec 11, 2020 at 9:27 AM  wrote:
> On 12/11/2020 07:07 AM, the...@sys-concept.com wrote:
>> Now, when I boot I get a message:
>>
>> Block device UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b is not a valid
>> root device.
>
> This puzzles me. I cannot find the string "is not a valid root device"
> (or

 sub-strings) in the source code for the Linux kernel, GRUB2, and refind.
 It
 seems to me it should be in one of them.

 - Matthew
>>>
>>> The error is indicative of the kernel driver for the / block device
>>> missing. If it is not built in-the-kernel, but as a module, then it
>>> should be in initramfs.
>>>
>>> Copy the kernel image, System.map, .config and corresponding initramfs to
>>> the /boot partition, then point your boot manager to the kernel to boot
>>> it.
>> How do you copy/generate initramfs in /boot directory?
> 
> https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel
> https://wiki.gentoo.org/wiki/Genkernel
> 
> If you're using genkernel it will copy it to /boot.  Besides the Handbook you 
> may find the following reference material on boot managers/loaders useful:
> 
> For rEFInd see here:
> 
> https://wiki.gentoo.org/wiki/Refind
> 
> For GRUB see here:
> 
> https://wiki.gentoo.org/wiki/GRUB2
> 
> For efibootmgr see here:
> 
> https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/
> Bootloader#Alternative_2:_efibootmgr

After I compile kernel I usually get this message (WHY?):

* You will find the initramfs in '/boot/initramfs-5.4.72-gentoo.img'.

* WARNING... WARNING... WARNING...
* Additional kernel parameters that *may* be required to boot properly:
*
* With support for several ext* filesystems available, it may be needed to
* add "rootfstype=ext3" or "rootfstype=ext4" to the list of boot parameters.



Re: [gentoo-user] system won't boot - --no-bootloader set; Skipping bootloader update ...

2020-12-11 Thread Michael
On Friday, 11 December 2020 18:24:27 GMT the...@sys-concept.com wrote:
> On 12/11/2020 10:45 AM, Michael wrote:
> > On Friday, 11 December 2020 16:42:08 GMT tedheadster wrote:
> >> On Fri, Dec 11, 2020 at 9:27 AM  wrote:
> >>> On 12/11/2020 07:07 AM, the...@sys-concept.com wrote:
>  Now, when I boot I get a message:
>  
>  Block device UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b is not a valid
>  root device.
> >>> 
> >>> This puzzles me. I cannot find the string "is not a valid root device"
> >>> (or
> >> 
> >> sub-strings) in the source code for the Linux kernel, GRUB2, and refind.
> >> It
> >> seems to me it should be in one of them.
> >> 
> >> - Matthew
> > 
> > The error is indicative of the kernel driver for the / block device
> > missing. If it is not built in-the-kernel, but as a module, then it
> > should be in initramfs.
> > 
> > Copy the kernel image, System.map, .config and corresponding initramfs to
> > the /boot partition, then point your boot manager to the kernel to boot
> > it.
> How do you copy/generate initramfs in /boot directory?

https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel
https://wiki.gentoo.org/wiki/Genkernel

If you're using genkernel it will copy it to /boot.  Besides the Handbook you 
may find the following reference material on boot managers/loaders useful:

For rEFInd see here:

https://wiki.gentoo.org/wiki/Refind

For GRUB see here:

https://wiki.gentoo.org/wiki/GRUB2

For efibootmgr see here:

https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/
Bootloader#Alternative_2:_efibootmgr

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] system won't boot - --no-bootloader set; Skipping bootloader update ...

2020-12-11 Thread thelma
On 12/11/2020 10:45 AM, Michael wrote:
> On Friday, 11 December 2020 16:42:08 GMT tedheadster wrote:
>> On Fri, Dec 11, 2020 at 9:27 AM  wrote:
>>> On 12/11/2020 07:07 AM, the...@sys-concept.com wrote:
 Now, when I boot I get a message:

 Block device UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b is not a valid
 root device.
>>>
>>> This puzzles me. I cannot find the string "is not a valid root device" (or
>>
>> sub-strings) in the source code for the Linux kernel, GRUB2, and refind. It
>> seems to me it should be in one of them.
>>
>> - Matthew
> 
> The error is indicative of the kernel driver for the / block device missing.  
> If it is not built in-the-kernel, but as a module, then it should be in 
> initramfs.
> 
> Copy the kernel image, System.map, .config and corresponding initramfs to the 
> /boot partition, then point your boot manager to the kernel to boot it.

How do you copy/generate initramfs in /boot directory?




Re: [gentoo-user] system won't boot - --no-bootloader set; Skipping bootloader update ...

2020-12-11 Thread thelma
On 12/11/2020 10:45 AM, Michael wrote:
> On Friday, 11 December 2020 16:42:08 GMT tedheadster wrote:
>> On Fri, Dec 11, 2020 at 9:27 AM  wrote:
>>> On 12/11/2020 07:07 AM, the...@sys-concept.com wrote:
 Now, when I boot I get a message:

 Block device UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b is not a valid
 root device.
>>>
>>> This puzzles me. I cannot find the string "is not a valid root device" (or
>>
>> sub-strings) in the source code for the Linux kernel, GRUB2, and refind. It
>> seems to me it should be in one of them.
>>
>> - Matthew
> 
> The error is indicative of the kernel driver for the / block device missing.  
> If it is not built in-the-kernel, but as a module, then it should be in 
> initramfs.
> 
> Copy the kernel image, System.map, .config and corresponding initramfs to the 
> /boot partition, then point your boot manager to the kernel to boot it.


 grep -i initramfs .config  (not showing anything)
CONFIG_INITRAMFS_SOURCE=""

After cofiguring kernel, I run:
make && make modules_install
make install
grub-install --target=x86_64-efi --efi-directory=/boot

Installing for x86_64-efi platform.
Installation finished. No error reported.

grub-mkconfig -o /boot/grub/grub.cfg

I'm using kernel:  System.map-5.4.72-gentoo

ll /boot/
total 56547
drwxr-xr-x 4 root root  512 Dec 11 08:23 EFI
-rwxr-xr-x 1 root root  4730365 Dec 11 11:01 System.map-5.4.72-gentoo
-rwxr-xr-x 1 root root  4618921 Dec 11 08:57 System.map-5.4.72-gentoo-x86_64
-rwxr-xr-x 1 root root  4451817 Dec 11 10:16
System.map-5.4.80-gentoo-r1-x86_64
-rwxr-xr-x 1 root root   121805 Dec 11 11:01 config-5.4.72-gentoo
-rwxr-xr-x 1 root root   212517 Dec 11 06:18 config-5.4.72-gentoo-x86_64
-rwxr-xr-x 1 root root   121783 Dec 11 09:48 config-5.4.72-gentoo.old
drwxr-xr-x 5 root root  512 Dec 11 11:11 grub
-rwxr-xr-x 1 root root  3573416 Dec 11 08:59
initramfs-5.4.72-gentoo-x86_64.img
-rwxr-xr-x 1 root root 10521824 Dec 11 10:26
initramfs-5.4.80-gentoo-r1-x86_64.img
-rwxr-xr-x 1 root root  9991040 Dec 11 11:01 vmlinuz-5.4.72-gentoo
-rwxr-xr-x 1 root root  9831296 Dec 11 08:57 vmlinuz-5.4.72-gentoo-x86_64
-rwxr-xr-x 1 root root  9726336 Dec 11 10:17 vmlinuz-5.4.80-gentoo-r1-x86_64

Doesn't matter which kernel I boot, the login is:
"This is (none). unknown domain 
(none) longin:

I can login as user but not as root.
It seems to me it didn't boot correctly.  Don't now what else to try.



Re: [gentoo-user] system won't boot - --no-bootloader set; Skipping bootloader update ...

2020-12-11 Thread Michael
On Friday, 11 December 2020 16:42:08 GMT tedheadster wrote:
> On Fri, Dec 11, 2020 at 9:27 AM  wrote:
> > On 12/11/2020 07:07 AM, the...@sys-concept.com wrote:
> > > Now, when I boot I get a message:
> > > 
> > > Block device UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b is not a valid
> > > root device.
> > 
> > This puzzles me. I cannot find the string "is not a valid root device" (or
> 
> sub-strings) in the source code for the Linux kernel, GRUB2, and refind. It
> seems to me it should be in one of them.
> 
> - Matthew

The error is indicative of the kernel driver for the / block device missing.  
If it is not built in-the-kernel, but as a module, then it should be in 
initramfs.

Copy the kernel image, System.map, .config and corresponding initramfs to the 
/boot partition, then point your boot manager to the kernel to boot it.

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] system won't boot - --no-bootloader set; Skipping bootloader update ...

2020-12-11 Thread tedheadster
On Fri, Dec 11, 2020 at 9:27 AM  wrote:

> On 12/11/2020 07:07 AM, the...@sys-concept.com wrote:
> > Now, when I boot I get a message:
> >
> > Block device UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b is not a valid
> > root device.
>
> This puzzles me. I cannot find the string "is not a valid root device" (or
sub-strings) in the source code for the Linux kernel, GRUB2, and refind. It
seems to me it should be in one of them.

- Matthew


Re: [gentoo-user] system won't boot - --no-bootloader set; Skipping bootloader update ...

2020-12-11 Thread thelma
On 12/11/2020 07:07 AM, the...@sys-concept.com wrote:
[snip]
>>>
>>> I bootstrap the PC and run:  genkernel --menuconfig all
>>> and finish compiling, and I get a message:
>>> -
>>> * Kernel compiled successfully!
>>> *
>>> * --no-bootloader set; Skipping bootloader update ...
>>> *
>>> * Required kernel parameter:
>>> *
>>> * root=/dev/$ROOT
>>> *
>>> * Where $ROOT is the device node for your root partition as the
>>> * one specified in /etc/fstab
>>> ---
>>>
>>> What went wrong?
>>>
>>> Here is my fstab:
>>> LABEL=boot    /boot    vfat    noauto,noatime    1 2
>>> UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b  /    ext4    noatime   
>>> 0 1
>>> LABEL=swap    none    swap    sw    0 0
> 
> Now, when I boot I get a message:
> 
> Block device UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b is not a valid
> root device.
> 
> I did not change anything in /etc/fstab

blkid /dev/nvme0n1p4
/dev/nvme0n1p4: UUID="d32946b3-2236-4998-80dd-68b7d78e0c7b" BLOCK_SIZE="4096" 
TYPE="ext4" PARTLABEL="rootfs" PARTUUID="17f9927c-a792-41fc-bff3-a50c420ee616"

So why boot can not find "/" partition ???



Re: [gentoo-user] system won't boot - --no-bootloader set; Skipping bootloader update ...

2020-12-11 Thread thelma
On 12/11/2020 03:15 AM, Dan Egli wrote:
> you didn't specify grub2 on the command line or (my preference) in
> /etc/genkernel.conf. So genkernel assumes you don't want it to fix your
> boot loader. If the kernel and ramdisk are all built, you can fix grub's
> config with grub-mkconfig -o /boot/grub/grub.cfg. For future kernel
> builds, read the paramaters in man genkernel so you know how to specify
> the boot loader, or just edit /etc/genkernel.conf and set the bootloader
> from none to grub2.
> 
> On 12/11/2020 12:54 AM, the...@sys-concept.com wrote:
>> My system will not boot.
>>
>> I installed sys-power/acpid  and wanted to double check the kernel
>> configuration.
>> I run: genkernel --menuconfig all
>> The ACPI option was enabled so I exit the menu but it started to
>> compile the kernel so I press CTRL-C (to stop it).
>>
>> Upon rebooting the X will not start no root login, just a screen with
>> login:
>> "joseph (none)"
>>
>> I bootstrap the PC and run:  genkernel --menuconfig all
>> and finish compiling, and I get a message:
>> -
>> * Kernel compiled successfully!
>> *
>> * --no-bootloader set; Skipping bootloader update ...
>> *
>> * Required kernel parameter:
>> *
>> * root=/dev/$ROOT
>> *
>> * Where $ROOT is the device node for your root partition as the
>> * one specified in /etc/fstab
>> ---
>>
>> What went wrong?
>>
>> Here is my fstab:
>> LABEL=boot    /boot    vfat    noauto,noatime    1 2
>> UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b  /    ext4    noatime   
>> 0 1
>> LABEL=swap    none    swap    sw    0 0

Now, when I boot I get a message:

Block device UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b is not a valid
root device.

I did not change anything in /etc/fstab





Re: [gentoo-user] system won't boot - --no-bootloader set; Skipping bootloader update ...

2020-12-11 Thread thelma


On 12/11/2020 03:15 AM, Dan Egli wrote:
> you didn't specify grub2 on the command line or (my preference) in
> /etc/genkernel.conf. So genkernel assumes you don't want it to fix your
> boot loader. If the kernel and ramdisk are all built, you can fix grub's
> config with grub-mkconfig -o /boot/grub/grub.cfg. For future kernel
> builds, read the paramaters in man genkernel so you know how to specify
> the boot loader, or just edit /etc/genkernel.conf and set the bootloader
> from none to grub2.

I am using "refind" (not grub)
With refind, do I need to run any special command to set-up correct kernel.
Here is my tree:  (grub is there, but I'm not using it)
tree -L 3 /boot
/boot
├── EFI
│   ├── gentoo
│   │   └── grubx64.efi
│   ├── refind
│   │   ├── BOOT.CSV
│   │   ├── icons
│   │   ├── keys
│   │   ├── refind.conf
│   │   └── refind_x64.efi
│   └── tools
├── System.map-5.4.72-gentoo-x86_64
├── System.map-5.4.72-gentoo-x86_64.old
├── System.map-5.4.80-gentoo-r1-x86_64
├── System.map-5.4.80-gentoo-r1-x86_64.old
├── config-5.4.72-gentoo
├── initramfs-5.4.72-gentoo-x86_64.img
├── initramfs-5.4.72-gentoo-x86_64.img.old
├── initramfs-5.4.80-gentoo-r1-x86_64.img
├── refind_linux.conf
├── vmlinuz-5.4.72-gentoo-x86_64
├── vmlinuz-5.4.72-gentoo-x86_64.old
├── vmlinuz-5.4.80-gentoo-r1-x86_64
└── vmlinuz-5.4.80-gentoo-r1-x86_64.old



> On 12/11/2020 12:54 AM, the...@sys-concept.com wrote:
>> My system will not boot.
>>
>> I installed sys-power/acpid  and wanted to double check the kernel
>> configuration.
>> I run: genkernel --menuconfig all
>> The ACPI option was enabled so I exit the menu but it started to
>> compile the kernel so I press CTRL-C (to stop it).
>>
>> Upon rebooting the X will not start no root login, just a screen with
>> login:
>> "joseph (none)"
>>
>> I bootstrap the PC and run:  genkernel --menuconfig all
>> and finish compiling, and I get a message:
>> -
>> * Kernel compiled successfully!
>> *
>> * --no-bootloader set; Skipping bootloader update ...
>> *
>> * Required kernel parameter:
>> *
>> * root=/dev/$ROOT
>> *
>> * Where $ROOT is the device node for your root partition as the
>> * one specified in /etc/fstab
>> ---
>>
>> What went wrong?
>>
>> Here is my fstab:
>> LABEL=boot    /boot    vfat    noauto,noatime    1 2
>> UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b  /    ext4    noatime   
>> 0 1
>> LABEL=swap    none    swap    sw    0 0
>>
>>



Re: [gentoo-user] system won't boot - --no-bootloader set; Skipping bootloader update ...

2020-12-11 Thread Dan Egli
you didn't specify grub2 on the command line or (my preference) in 
/etc/genkernel.conf. So genkernel assumes you don't want it to fix your 
boot loader. If the kernel and ramdisk are all built, you can fix grub's 
config with grub-mkconfig -o /boot/grub/grub.cfg. For future kernel 
builds, read the paramaters in man genkernel so you know how to specify 
the boot loader, or just edit /etc/genkernel.conf and set the bootloader 
from none to grub2.


On 12/11/2020 12:54 AM, the...@sys-concept.com wrote:

My system will not boot.

I installed sys-power/acpid  and wanted to double check the kernel 
configuration.
I run: genkernel --menuconfig all
The ACPI option was enabled so I exit the menu but it started to compile the 
kernel so I press CTRL-C (to stop it).

Upon rebooting the X will not start no root login, just a screen with login:
"joseph (none)"

I bootstrap the PC and run:  genkernel --menuconfig all
and finish compiling, and I get a message:
-
* Kernel compiled successfully!
*
* --no-bootloader set; Skipping bootloader update ...
*
* Required kernel parameter:
*
*   root=/dev/$ROOT
*
* Where $ROOT is the device node for your root partition as the
* one specified in /etc/fstab
---

What went wrong?

Here is my fstab:
LABEL=boot  /boot   vfatnoauto,noatime  1 2
UUID=d32946b3-2236-4998-80dd-68b7d78e0c7b   /   ext4noatime 0 1
LABEL=swap  noneswapsw  0 0



--
Dan Egli
From my Test Server