In message from Greg Lindahl <lind...@pbm.com> (Thu, 20 Aug 2009
11:23:25 -0700):
On Thu, Aug 20, 2009 at 08:06:07PM +0200, Reuti wrote:
AFAIK, initrd (as the kernel itself) is "universal" for
EM64T/x86-64,
The problem is not the type of CPU, but the chipset (i.e. the
necessary
kernel module) with which the HDD is accessed.
There are 2 aspects to this:
1: /etc/modprobe.conf or equivalent
2: the initrd on a non-rescue disk is generally specialized to only
include modules for devices in (1).
Solution? Boot in a rescue disk, chroot to your system disk, modify
/etc/modprobe.conf appropriately, run mkinitrd.
Thanks, it's good idea ! The problem is (I think) just in 10.3 initrd
image.
Unfortunately it's in some inconsistence w/my source hope - move HDD
ASAP (As Simple As Possible :-)) ).
Mikhail
_______________________________________________
Beowulf mailing list, Beowulf@beowulf.org sponsored by Penguin Computing
To change your subscription (digest mode or unsubscribe) visit
http://www.beowulf.org/mailman/listinfo/beowulf
