| 1 |
On Sun, Jun 10, 2001 at 10:35:08PM +0200, Erik Van Reeth wrote: |
| 2 |
|
| 3 |
> I had a system with only kernel 2.4.4-ac9 in place, which boots perfectly. I |
| 4 |
> did a new kernel build via "ebuild ../sys-kernel/linux/linux-2.4.5.5.ebuild |
| 5 |
> qmerge". A new /lib/modules/2.4.5-ac5 directory was made. I added a new |
| 6 |
> entry to menu.lst to be able to boot the old kernel if the new one didn't |
| 7 |
> worked. Only all the *.dep files under /lib/modules/2.4.4-ac9 are being |
| 8 |
> changed with modules.dep being empty (0 bytes). So booting the older kernel |
| 9 |
> gives problems in loading modules. Also after booting kernel 2.4.5-ac5, the |
| 10 |
> modules.* are automatic generated but in the wrong directory. They were |
| 11 |
> created under 2.4.4-ac9 instead of 2.4.5-ac5. Manually doing a depmod -a |
| 12 |
> solved this behaviour. Is there some reason for this behaviour or am i doing |
| 13 |
> something wrong here ? |
| 14 |
|
| 15 |
No, there is no good reason for this behavior; the modules initscript appears |
| 16 |
to be broken. We want to fix this soon. |
| 17 |
|
| 18 |
-- |
| 19 |
Daniel Robbins <drobbins@g.o> |
| 20 |
President/CEO http://www.gentoo.org |
| 21 |
Gentoo Technologies, Inc. |
Archives