| 1 |
Hi, |
| 2 |
|
| 3 |
I had a system with only kernel 2.4.4-ac9 in place, which boots perfectly. |
| 4 |
I did a new kernel build via "ebuild |
| 5 |
../sys-kernel/linux/linux-2.4.5.5.ebuild qmerge". |
| 6 |
A new /lib/modules/2.4.5-ac5 directory was made. I added a new entry to |
| 7 |
menu.lst to be able to boot the old kernel if the new one didn't worked. |
| 8 |
Only all the *.dep files under /lib/modules/2.4.4-ac9 are being changed |
| 9 |
with modules.dep being empty (0 bytes). So booting the older kernel gives |
| 10 |
problems in loading |
| 11 |
modules. |
| 12 |
Also after booting kernel 2.4.5-ac5, the modules.* are automatic generated |
| 13 |
but in the wrong |
| 14 |
directory. They were created under 2.4.4-ac9 instead of 2.4.5-ac5. |
| 15 |
Manually doing a depmod -a solved this behaviour. |
| 16 |
Is there some reason for this behaviour or am i doing something wrong here ? |
| 17 |
|
| 18 |
Greetz |
| 19 |
Erik |
Archives