| 1 |
On 07/15/2014 06:38 PM, Gmail wrote: |
| 2 |
> My /usr partition in on the / partition. |
| 3 |
> |
| 4 |
> I just use initrd, i've compiled kernel with genkernel. |
| 5 |
> |
| 6 |
> I'm trying to look row for row if there's some diff. |
| 7 |
> |
| 8 |
> |
| 9 |
> Il 15/07/2014 17:34, Alexander Kapshuk ha scritto: |
| 10 |
>> On 07/14/2014 05:18 PM, Gmail wrote: |
| 11 |
>>> Hi, i've upgraded kernel from 3.12.13 to 3.12.20. |
| 12 |
>>> I've make a oldconfig as usual, but with new kernel the boot blocks |
| 13 |
>>> at the begining to the ramdisk loading. |
| 14 |
>>> I've tried with other 3.12.2x with the same negative results. |
| 15 |
>>> I use grub2 with systemd. |
| 16 |
>>> |
| 17 |
>> Is your '/usr' partition housed on a filesystem of its own, or does |
| 18 |
>> it reside on the '/' partition? |
| 19 |
>> |
| 20 |
>> http://wiki.gentoo.org/wiki/Initramfs/HOWTO |
| 21 |
>> "For systems where all necessary files and tools reside on the same |
| 22 |
>> file system, the |init| application can perfectly control the further |
| 23 |
>> boot process. But when multiple file systems are defined (or more |
| 24 |
>> exotic installations are done), this might become a bit more tricky: |
| 25 |
>> |
| 26 |
>> * When the /usr partition is on a separate file system, tools and |
| 27 |
>> drivers that have files stored within /usr cannot be used unless |
| 28 |
>> /usr is available. If those tools are needed to make /usr |
| 29 |
>> available, then we cannot boot up the system. |
| 30 |
>> |
| 31 |
>> * If the root file system is encrypted, then the Linux kernel will |
| 32 |
>> not be able to find the |init| application, resulting in an |
| 33 |
>> unbootable system. |
| 34 |
>> |
| 35 |
>> The solution for this problem has since long been to use an /initrd/ |
| 36 |
>> (initial root device)." |
| 37 |
>> |
| 38 |
>> Did you run a diff on your 3.12.13/.config and 3.12.13/.config, to |
| 39 |
>> make sure you didn't overlook anything to do with the systemd-related |
| 40 |
>> config options? |
| 41 |
>> |
| 42 |
>> |
| 43 |
> |
| 44 |
Did the output you got when generating 'grub.cfg' look similar to this? |
| 45 |
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?style=printable&full=1#genkernel |
| 46 |
|
| 47 |
Code Listing 2.3: Generating GRUB2 configuration |
| 48 |
|
| 49 |
# grub2-mkconfig -o /boot/grub/grub.cfg |
| 50 |
Generating grub.cfg ... |
| 51 |
Found linux image: /boot/vmlinuz-3.12.20-gentoo |
| 52 |
Found initrd image: /boot/initramfs-genkernel-x86-3.12.20-gentoo |
| 53 |
done |
| 54 |
|
| 55 |
The output of the command must mention that at least one Linux image is |
| 56 |
found, as those are needed to boot the system. If you use initramfs or |
| 57 |
used genkernel to build the kernel, the correct initrd image should be |
| 58 |
detected as well. If this is not the case, go to /boot and check the |
| 59 |
contents using the ls command. If the files are indeed missing, go back |
| 60 |
to the kernel configuration and installation instructions. |
Archives