Hello Philip, On Thu, Jan 09, 2025 at 03:31:05PM +0000, Philip Pemberton wrote: > (Repeating myself here, ata4 / ata_port=4 is the DVD drive; ata_port=3 is > the Zip drive) > > There's quite a lot on the ATA buses, so if it helps -- > ata1: Samsung 860 SSD > ata2: WD 500GB mechanical hard drive > ata3: Spare port / Zip drive > ata4: DVD writer > ata5: Not used > ata6: Not used > > There are a couple of SATA disks and a SAS tape drive on an LSI SAS card but > they seem to go through the "scsi" and "mpt2sas" driver route. > > > > Note that for ATAPI, it also looks like your SATA driver needs special support. > > See e.g. libahci.c which does a bunch of extra stuff if it is an ATAPI device, > > e.g.: > > https://github.com/torvalds/linux/blob/v6.13-rc6/drivers/ata/libahci.c#L1699-L1702 > > https://github.com/torvalds/linux/blob/v6.13-rc6/drivers/ata/libahci.c#L1638-L1643 > > > > Same for the libata-sff driver: > > https://github.com/torvalds/linux/blob/v6.13-rc6/drivers/ata/libata-sff.c#L2672-L2684 > > https://github.com/torvalds/linux/blob/v6.13-rc6/drivers/ata/libata-sff.c#L295-L297 > > https://github.com/torvalds/linux/blob/v6.13-rc6/drivers/ata/libata-sff.c#L687-L715 > > > > > > Which SATA driver are you using? > > It looks like it's "ahci" or "libahci". > > > > Are you saying that it does come up and work eventually? > > > > When we see the "disable device" print, it is usually a sign that we have > > given up, and thus remove the device. > > No, it tries to connect three times, then gives up and disables the device. Unfortunately, so far I do not think that we have enough information to do much about this issue. We know that the "SATA-to-PATA adatper + Zip drive" combo worked on some other PC (that might have used another SATA HBA) with an ancient kernel. I think my first recommendation would be to try to build an ancient kernel on your current PC, and see if the same "SATA-to-PATA adatper + Zip drive" combo then works. If it does work, then I think the best bet is to use PCI passthrough and do an git bisection (which can be automated). Or, do the opposite, see if the latest kernel with other PC still handles the Zip drive properly, if it doesn't, then perhaps the best thing is to to the bisection on this other PC. You could look at this guide for inspiration: https://github.com/floatious/qemu-bisect-doc Kind regards, Niklas
