On Tue, 19 Feb 2008, Andrew Buehler wrote: > With those two problems out of the way, what is left is the hard-drive > issue, and that is also halfway fixed by enabling ACPI. Specifically, it > is "fixed" in that the kernel sees the hard drive and I can mount it, > but it is not fixed in that the program we need to use in this > environment does not see the drive. What do you mean by "does not see the drive"? > I have a config from a boot disc running 2.6.5 (that's not a typo) under > which the program in question *does* see the drive, but there are > massive differences between that config and the one I am using now, and > narrowing the critical difference down is likely to be somewhat > difficult - particularly since some of the "differences" are merely > renamed config symbols (i.e. the CONFIG_SCSI_SATA_*->CONFIG_SATA_* > switchover), and I have limited ability to tell which without intensive > investigation. Are there any established techniques for simplifying this > kind of comparison? The only established technique is to run various kernels intermediate between the one that works and the one that fails. Alan Stern - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
