http://bugzilla.kernel.org/show_bug.cgi?id=10436 ------- Comment #3 from marco@xxxxxxxxxx 2008-04-10 12:21 ------- Created an attachment (id=15724) --> (http://bugzilla.kernel.org/attachment.cgi?id=15724&action=view) dmidecode output I'm afraid dmi data isn't much of help. As you can see at http://www.lm-sensors.org/ticket/2298 this problem already occurred with sensors-detect, due to a non-standard address in the SuperIO chip. Maybe asking VIA a BIOS containing a motherboard identifier string would help? However I have two questions for you: 1) Why does it work using udma4 with the previous 2.6.22? 2) In the BIOS at "ATA(PI) 80 pin Cable Detection" I can select "Host & Device", "Host" and "Device". Which one should I choose? Which one could/should be better? About the second (hardware related) issue, I simply had this drive laying around, so I gave a try, but I'll buy a new sata II one and use AHIC. So let me know if you find something useful in the dmidecode output, otherwise feel free to close this bug. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- 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
