| 1 |
My /usr partition in on the / partition. |
| 2 |
|
| 3 |
I just use initrd, i've compiled kernel with genkernel. |
| 4 |
|
| 5 |
I'm trying to look row for row if there's some diff. |
| 6 |
|
| 7 |
|
| 8 |
Il 15/07/2014 17:34, Alexander Kapshuk ha scritto: |
| 9 |
> On 07/14/2014 05:18 PM, Gmail wrote: |
| 10 |
>> Hi, i've upgraded kernel from 3.12.13 to 3.12.20. |
| 11 |
>> I've make a oldconfig as usual, but with new kernel the boot blocks |
| 12 |
>> at the begining to the ramdisk loading. |
| 13 |
>> I've tried with other 3.12.2x with the same negative results. |
| 14 |
>> I use grub2 with systemd. |
| 15 |
>> |
| 16 |
> Is your '/usr' partition housed on a filesystem of its own, or does it |
| 17 |
> reside on the '/' partition? |
| 18 |
> |
| 19 |
> http://wiki.gentoo.org/wiki/Initramfs/HOWTO |
| 20 |
> "For systems where all necessary files and tools reside on the same |
| 21 |
> file system, the |init| application can perfectly control the further |
| 22 |
> boot process. But when multiple file systems are defined (or more |
| 23 |
> exotic installations are done), this might become a bit more tricky: |
| 24 |
> |
| 25 |
> * When the /usr partition is on a separate file system, tools and |
| 26 |
> drivers that have files stored within /usr cannot be used unless |
| 27 |
> /usr is available. If those tools are needed to make /usr |
| 28 |
> available, then we cannot boot up the system. |
| 29 |
> |
| 30 |
> * If the root file system is encrypted, then the Linux kernel will |
| 31 |
> not be able to find the |init| application, resulting in an |
| 32 |
> unbootable system. |
| 33 |
> |
| 34 |
> The solution for this problem has since long been to use an /initrd/ |
| 35 |
> (initial root device)." |
| 36 |
> |
| 37 |
> Did you run a diff on your 3.12.13/.config and 3.12.13/.config, to |
| 38 |
> make sure you didn't overlook anything to do with the systemd-related |
| 39 |
> config options? |
| 40 |
> |
| 41 |
> |
Archives