This is probably due to the system using the ahci driver now rather than the
ata_piix one. This ought to be correct, but it's possible that there's a minor
bug in the ahci driver.
Could you check /proc/scsi in order to ensure that ahci is actually bound to
your devices? If so, then it's almost certainly just a cosmetic driver bug.
This is probably due to the system using the ahci driver now rather than the
ata_piix one. This ought to be correct, but it's possible that there's a minor
bug in the ahci driver.
Could you check /proc/scsi in order to ensure that ahci is actually bound to
your devices? If so, then it's almost certainly just a cosmetic driver bug.