uweseimet
commented
4 months ago Bisecting would not really help because the SCSI2Pi repository does not contain the legacy PiSCSI codebase, and due to numerous new features and cleanups it differs quite a lot from PiSCSI anyway.
I don't have an Amiga, but I might be able to figure out what's wrong if you can provide the images of your CD-ROMs. One image is enough for a start, because a step-by-step approach is best. I would also be interested in logs showing what happens when you mount/access this image with PiSCSI and with SCSI2Pi. When testing, please only attach one of the affected images, not both. When the issue is resolved for one image, the other can be addressed. Otherwise the test setup and the logs are too complicated. Having as few devices as possible when debugging make things easier.
In case you don't have time yet for providing logs but can already provide an image, this might already get me started.
SavourySnaX
When creating a new ticket please provide information on your environment.
The Pi type: Pi Zero
The Pi OS version (output of 'lsb_release -a' and 'uname -a'): Distributor ID: Raspbian Description: Raspbian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye Linux raspberrypi 6.1.21+ #1642 Mon Apr 3 17:19:14 BST 2023 armv6l GNU/Linux
The SCSI2Pi release or git revision: 3.4 Release
The computer/sampler connected to the RaSCSI/PiSCSI board: Amiga 1200 - Via Blizzard SCSI Kit IV with 8.5 Rom
Describe the issue
Tried installing the 3.4 release to see if it was a suitable replacement for the piscsi v24.04.01 release, I have a lot of devices in the config for the device. With 2 cd roms (Units 6 0 and 6 1), on the piscsi drivers the 2 cdroms are mounted and behave correctly, on the scsi2pi 3.4 release, the cd roms mount incorrectly, 1 detects as audio cd (its purely data), the other behaves even more strangely (and causes standard amiga assigns to be lost). reverting back to piscsi and the devices return to normal behaviour.
I can do further testing, if there is something specific i can enable to trace the issues i may be willing. I've only tried 3.4, I could bisect the releases if it would help. My time is limited however, so it might be a few weekends before I can do that.