Re: [gentoo-user] grub2 or kernel config - unable to properly boot [CLOSED]

Re: [gentoo-user] grub2 or kernel config - unable to properly boot [CLOSED]

[Francisco Ares]

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

2013/8/29 Francisco Ares <frares@gmail.com>

>
> 2013/8/29 Gregory Shearman <zekeyg@gmail.com>
>
>> In linux.gentoo.user, you wrote:
>> >>
>> >> search for CONSOLE in this file and find:
>> >>
>> >> #     exec >${CONSOLE} <${CONSOLE} 2>&1
>> >>
>> >> Just remove the hash at the start of the line, rebuild my initramfs
>> >> and it is ready to go.
>> >>
>> >> --
>> >> Regards,
>> >> Gregory.
>> >>
>> >>
>> >
>> > Thanks Gregory.
>> >
>> > I really would like to find that partition number limitation on
>> genkernel
>> > in the docs.
>>
>> I've never had that problem but then I've always made /boot my first
>> partition.
>>
>> > I have already had that splash screen problem, very interesting your
>> > solution. That's a big reason I love Gentoo, always learning something
>> new.
>> > Funny thing is that checking the file you've mentioned in this new
>> system,
>> > it has no hash at that line (line number 13, right?). On the other
>> working
>> > system, the same, no hash.
>>
>> No, the line is 149.
>>
>> You see, I've got this as part of my kernel command line:
>>
>> console=tty1
>>
>> The code section from the linuxrc file is part of the kernel command
>> line check as part of a bash(sh) "do" loop:
>>
>>         CONSOLE=*|console=*)
>>                 CONSOLE=${x#*=}
>>                 CONSOLE=$(basename ${CONSOLE})
>> #               exec >${CONSOLE} <${CONSOLE} 2>&1
>>
>> If you change your "console=" value on the command line then the new
>> console choice is redirected. If the hash is in place then the
>> console is not redirected and usually you get console output writing all
>> over your splash screen.
>>
>>
>> > I'm using genkernel-3.4.45.1 on both systems, perhaps not the same as
>> you.
>> >
>> > Regarding that last issue, the message complaining that the root
>> partition
>> > is not a valid block device _is still there_, only masked by the splash
>> > (which now is "verbose").
>> >
>> > I was optimistic in believing everything would work as expected once I
>> > found that detail.
>>
>> I'm not sure I can help you here. My root filesystem is on an LVM volume
>> (as are all the rest of my filesystems except for my /boot partition.
>>
>> --
>> Regards,
>> Gregory.
>>
>>
> Thanks, Gregory.
>
>
> Best regards,
> Francisco
>


For all who might  be interested, I've reinstalled/rebuilt/reemerged
everything from stage3 up during the night (I've saved the "world" file, it
helped a lot).

Now everything works.  I have a backup copy of all file system when things
were not working, and I will do another one now.  When I get some time to
spare, I will compare both and try to figure out what happened.

Thanks to all!
Francisco

[-- Attachment #2: Type: text/html, Size: 4018 bytes --]