On Thu, 8 Sep 2005, Basel Al-Mustafa wrote:
--- Ken Moffat <[EMAIL PROTECTED]> wrote:
I've never seen it done with the path specified as
part of
CROSS_COMPILE, but I don't see why that wouldn't
work :)
I managed to build a cross compiled kernel for x86_64
under Slackware but it stops booting. Please refer to
the following thread for more detailed information:
http://www.linuxquestions.org/questions/showthread.php?s=&threadid=361463
In general terms, what happens after "freeing unused kernel memory" is
that it moves on to the init scripts. Maybe your Slackware initscripts
depend on something, such as an initrd ? Or maybe it's just a driver
issue (something compiled in, but doesn't work). Ideally, you would
have a similar working kernel to compare to, but obviously that's a
chicken-and-egg situation.
I've seen strangeness on new LFS systems if the skeletal /dev is
missing, and people with old versions of udev have reported long
delays in booting recent kernels, so it's worth checking that your
Slackware is indeed using udev (instead of e.g. devfs), and which
version.
At the moment I don't have an unused x86_64 sitting around, so I can't
reboot to try to see what happens next on mine. Maybe later, if you
can't get anywhere.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
