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 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...
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
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-68b7d7
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-68b7d7
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 devic
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 de
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 ...
>>> *
>>>
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
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/gr
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 th
11 matches
Mail list logo
