On Jun 6, 2006, at 5:40 PM, Frans Pop wrote:
(removing all irrelevant CCs; please respect the reply-to)
On Tuesday 06 June 2006 12:18, Rick Thomas wrote:
OK, they are here:
http://www.rcthomas.org/~rbthomas/logfiles/
As there is absolutely no mention of 2.6.8 in this installation
itself,
the problem seems to be in the bootloader configuration and not in
base-installer. Are you sure that the correct initrd and kernel are
loaded?
I don't see anything in the logs about bootloader setup...
The only issue I can see in the install is the same as already
spotted by
Sven:
apt-install: Inconsistency detected by ld.so: dl-runtime.c: 76:
fixup: Assertion `((reloc->r_info) & 0xff) == 21' failed!
I would say that this is a problem in the target system (maybe
initramfs-tools) rather than in the installer as apt-install
effectively
runs in the /target chroot.
It also seems as if this error does not affect the installation
itself as
it just continues (although it might cause a broken initrd). It may be
related, but it could also be a totally unrelated issue (though
probably
worth following up).
The best way to debug this would be switching to console after base
installation, do a 'chroot /target' and try to generate the initrd
manually (with verbose options and checking the result afterwards; you
may have to mount /sys and /proc).
Anyway, the bootloader configuration should be checked to see why
it tries
to do anything with a 2.6.8 kernel which presumably comes from some
old
install.
It's an oldworld Mac (beige G3) and I use MacOS-9/BootX as the
bootloader, so I skipped the "install quik bootloader" step during
the install (used "continue without bootloader"). That's probably
why you aren't seeing anything in the logs about bootloader setup.
This machine has a partition with sarge on it. Is it trying to do
something with the 2.6.8 kernel from there? If so, why?!?
Give me detailed instructions or a pointer to the correct part for me
to RTFM, and I'll do the manual initrd generation tonight or tomorrow.
Enjoy!
Rick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]