On Tue, Oct 14, 2008 at 1:18 PM, Santiago Vila <sanvila@xxxxxxx> wrote: > [ Sorry for the delay, yesterday it was a non-working day here, so > rebooting the computer was a little bit dangerous ]. > >> Ok, it seems that your drive gets puzzled after receiving a GET_CONFIGURATION >> command. Lets see whether this is the real cause of the problem. Here's a yet >> another version of the inquisitive patch :) which drops such commands. Please >> rebuild with it and send me the dmesg. Thanks. > > Hurrah! > > There is no waiting time during boot anymore, and the drive hdc now works. Ok, we see now where the problem hides. Nice! However, IIRC, you can boot 2.6.18 with the same Debian unstable setup (correct?) which means that the drive receives the same commands. So, it seems that there is something in the way the command is sent to the drive that puzzles it. I'll try to cook up a debugging patch for 2.6.18 for you to apply so that we can make sure it does execute GET_CONFIGURATION properly. Thanks a lot for your work! -- Regards/Gruss, Boris -- 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
