On 12/22/06, I wrote > I have a 666MHz Via Epia-ML motherboard (using a Via Eden, I > think). I am booting it from a CompactFlash card attached by an > IDE-CF adapter. Everything works fine under 2.6.18. Under 2.6.19, > 2.6.19.1 and 2.6.20-rc1, the master device on ide0 is not seen. [...] Argh! This was my mistake. It is not a new kernel bug. Somehow, I inadvertently activated CONFIG_BLK_DEV_HD_IDE, which runs a much older IDE driver on hda only. This older IDE hard disk driver apparently does not detect any of the flash disks that I tried. which I suppose might be a bug, but I don't if anybody should care. Indeed, I'm curious to know if there is any hardware that needs or benefits CONFIG_BLK_DEV_HD_IDE in recent kernels. That is to say, what is it that the regular IDE driver does not handle well enough? If there is no longer any benefit to CONFIG_BLK_DEV_HD_IDE, then maybe that code should be deleted. I have verified that deactivating CONFIG_BLK_DEV_HD_IDE on 2.6.20-rc2 fixes the problem for me. I believe the reason that the offending kernels previously worked with the same flash disks in the ide0/master slot of another computer that I have is that the computer on which it worked also has two SATA drives, which are now labelled by the kernel, starting around 2.6.19, as "hda" and "hdc", bumping the flash card to "hde", which I think resulted in it being controlled by the non-ancient IDE driver, since CONFIG_BLK_DEV_HD_IDE only applies to hda. By the way, I did diff my .config files initially when researching this bug, but the configuration options from 2.6.18 to 2.6.19 changed enough that I missed this misconfiguration of mine. I'm not even sure how I made this mistake. In any case, I apologize for what was basically a false alarm. Adam Richter - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
