Anton Graham <[EMAIL PROTECTED]> writes:
> This is my first dalliance with the 2.4 series kernels (and my first
> binary kernel install in a while), so please forgive (and correct) any
> misconceptions:
>
> 1) The /usr/sbin/detectloader script doesn't seem to work. In a cursory
> examination of it, it appears that it should print either LILO or GRUB.
> With GRUB installed (whether on the /boot partition (/dev/hda1) or on
> the MBR) it prints nothing. I have initscripts-5.27-8mdk and
> perl-5.600-11mdk
chmou?
> 2) The modules are scrambled.
>/lib/modules/2.4.0-0.12mdk/{block,cdrom,fs,ipv4,misc,net,scsi,video}
> are all empty. The modules that should be there are a subtree named
> kernel. There is also a symlink build that seems to point to titi's RPM
> build directory.
from Documentation/Changes :
@@ -138,7 +145,15 @@
Upgrade to recent modutils to fix various outstanding bugs which are
seen more frequently under 2.3.x, and to enable auto-loading of USB
-modules.
+modules. In addition, the layout of modules under
+/lib/modules/`uname -r`/ has been made more sane. This change also
+requires that you upgrade to a recent modutils.
+
+Mkinitrd
+--------
+
+These changes to the /lib/modules file tree layout also require that
+mkinitrd be upgraded.
I'm fixing it
> This made the generation of an initrd problematic because mkinitrd
> cannot find the modules. Adding /kernel/fs to the end of the kernel
> name allowed generation of the image.
> 3) ALSA header files are in the modules directory as well (under
> 2.4.0-0.12mdk/include/linux) I don't think anything is going to look
> for them there :p
a bad effect from mainstream kernel changes. arghh...
