On Mon, 2009-11-30 at 13:21 +0100, Frank Heckes wrote: > Hello Brian, Hi Frank,
> first of all thanks for your patience and answers so far. NP. > No, no I like the idea a lot, but unfortunately the kernel didn't boot > on the hardware we trying to install them (IBM pizzaboxes), even after > rebuilding the initrd, Systemmap... to extend the (initial) driver list. Hrm. Does the Suse-supplied kernel boot those machines or does it have the same problems? I just want to isolate whether this is a problem unique to our kernel build or whether it's a problem with the upstream (Suse supplied) kernel. > So I decided to built the kernel from source. Here the system boots as > it should after installing it to one of the nodes of the (test) > cluster. What do you do differently than is being done by our build? Do you change anything in the source-tree before you build? Probably it would be great to have a complete transcript of what you do once you have downloaded the kernel-lustre-source package from our download site. > And of course there's also a small piece of (childlike) curiosity, too. :-) > I fully agree. I would to the ready made RPM's if it would be possible. > (see above). Indeed. In fact rather than copying what could be some very copious data to this list, can you open a bug in our bugzilla and report back here for me (and the rest of the readers) what the ticket number is? > Here're the Makefile's first 10 lines: Unfortunately it was not enough. Once you have opened the ticket as per above, please attach the complete Makefile. b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
