1 |
Just filed bug 824282. |
2 |
|
3 |
In the past, I've always done "make kernel, make kernel_modules, make |
4 |
install, make modules_install, genkernel initramfs ...". |
5 |
|
6 |
This worked fine, and I then ran grub-mkconfig, sorted out grub.cfg, and |
7 |
all was well. |
8 |
|
9 |
My new setup, I have a /boot WHICH I WANT TO SORT OUT MYSELF! I got |
10 |
thoroughly confused because genkernel was finding /boot in fstab, |
11 |
mounting it by default, and sticking the initramfs there. So of course, |
12 |
grub-mkconfig screwed up because the kernel was in the /boot directory, |
13 |
but the initramfs was in the /boot partition! |
14 |
|
15 |
So I told genkernel not to mount the boot partition ... |
16 |
|
17 |
WAH WAH WAH FATAL ERROR YOU WON'T LET ME MOUNT BOOT SULK SULK SULK. |
18 |
|
19 |
If I tell it not to mount boot then that's my lookout, not for genconfig |
20 |
to nanny me and sulk! |
21 |
|
22 |
|
23 |
And it gets worse. I've always done "make modules_install, genkernel |
24 |
initramfs". Which now seems to be an unsupported option. genkernel is |
25 |
now looking in /var/tmp/genkernel/... for the modules - no surprise the |
26 |
modules aren't there! The error says "did you forget to compile the |
27 |
kernel" - no I didn't - it is compiled, the modules are installed, I |
28 |
just didn't use genkernel to do it. |
29 |
|
30 |
Why oh why does everything change ... for the worse ... now let's see if |
31 |
allowing it to mount the boot partition makes it work properly ... |
32 |
|
33 |
and allowing it to mount boot made everything work perfectly afaict ... |
34 |
what a mess ... |
35 |
|
36 |
Cheers, |
37 |
Wol |