Jordan Crouse wrote: > > As background, I'm using syslinux 3.36 as my loader here - I've used this > exact same version for a very long time, so I don't blame it in the least. > Something is getting confused in the early kernel, and whatever that > something is, a still unknown change in a newer version of the BIOS > fixed it. The search goes on. >
OK, we should put printf's in arch/i386/boot/memory.c and see what actually gets read out from the BIOS. This could either be a BIOS problem or a bug in memory.c (or a bug elsewhere in the code that the change in memory.c triggers, but that seems less likely.) -hpa P.S. Are you guys in the Bay Area by any chance? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/