I just went through the latest net install. Due to unresolved symbols in 
certain modules, I cannot load my root filesystem, which is xfs.

The problem though, is the install is not creating initrd files for the 
new kernels it installs. I installed the 10-mdksecure kernel from the 
latest working Beta 2. This kernel is supposed to use its own initrd 
which should be free from the issues of the current non-working kernel 
(-17mdk), but it appears mounting on the root fs still fails.

Any ideas? Shouldn't the newly installed kernels be creating an initrd 
corresponding to that kernel version? I read about the modules problem 
probably being fixed in -18mdk, but this doesn't seem like the only 
issue if it still tries to use the initrd from my broken (-16mdk) 
kernel, which is currently the only initrd in my /boot direectory.

-- 
Sincerely,

David Walluck
<[EMAIL PROTECTED]>


Reply via email to