Trying install again

[Bikerbob]

Hello Uwe.

Remember not a linux guy.

I just did the 24.04.01 update from the piscsi release. used option 1 to update install and web ui - it works fine can access web ui

I am using a pi zero2 w - so the above is a bullseye 64bit build.

I would now like to install scsi2pi 5.0

Am I better to install into this image? or should I download bookworm pi os 64bit and try and install software after?

James

[uweseimet]

My recommendation is not to use bullseye but bookworm. bullseye support for SCSI2Pi will presumably end after the next OS release for the Pi (Debian trixie), which can be expected in autumn.

Please take notice of https://github.com/PiSCSI/piscsi/issues/1481.

Since you are migrating from PiSCSI, before installing SCSI2Pi ensure that PiSCSI (the emulation, not just the web UI) is working properly.

[Bikerbob]

My recommendation is not to use bullseye but bookworm. bullseye support for SCSI2Pi will presumably end after the next OS release for the Pi (Debian trixie), which can be expected in autumn.

Please take notice of https://github.com/PiSCSI/piscsi/issues/1481.

Since you are migrating from PiSCSI, before installing SCSI2Pi ensure that PiSCSI (the emulation, not just the web UI) is working properly.

Well I can just install the pi os lite bookworm - from raspberrypi.com - this would give me a base OS install.
Would I then go through the process of installing PiSCSI? then use your install guide to up date that? https://www.scsi2pi.net/en/installation.html

I assume an install of the PiSCSI is required before SCSI2PI? or can I install SCSI2PI and then add the web UI? which is what I use.

[uweseimet]

The answers to these questions are available on the PiSCSI wiki and the SCSI2Pi website. Please thoroughly read the installation instructions.

Please understand that this forum is not meant to duplicate information that is already available elsewhere.

[Bikerbob]

not to be belligerent Uwe, but if the information was so easy to digest; would I still be trying to do this after almost 6 months?

I am trying to get it working.. have done several times as you know from other threads..

I like to support the people who support the Atari community, as you know I have paid for your HDdriver since 2016. You might find that if you gave people a little more of a hand or push; where maybe its clear to you but others dont possess the same skill set, that you might have more users. I could not find one person on the piscsi discord that said they have installed your version of the software - no one on Atari Forum. So I come here as a last resort.

Sorry that I bother you, trying to use your software.

[uweseimet]

I am sorry, but IMO the instructions on the PiSCSI wiki are quite clear. It must have been hundreds of users who have installed PiSCSI with the help of the Wiki. Or with help from the PiSCSI Discord channel. I have recommended several times to install PiSCSI first and to ensure that it is working properly. My impression is that you are asking for help and then ignoring any recommendation. Otherwise PiSCSI at least would already be up and running. Installing PiSCSI is not a precondition for SCSI2Pi, but installing it first is what everybody who needs a lot of support should do, just because there is the wiki and the Discord channel. SCSI2Pi is backwards compatible with PiSCSI for a good reason: More or less everything that applies to PiSCSI is also valid for SCSIPi, with a lot of new functionality on top.
Regarding bullseye, I already recommended in the discussion on the SCSI2Pi GitHub site not to use it anymore. But apparently you still do.

Wrt SCSI2Pi the installation works as described on https://www.scsi2pi.net/en/installation.html, essentially by installing a Debian package with the apt package manager. That's the standard installation method for a Debian-based Linux, there is nothing special about it. In addition to the binaries. a sample configuration file and a system service (the counterpart to the piscsi service) are installed.
The SCSI2Pi website provides details on all this. It also shows how to use/enable the s2p system service, for instance. Furthermore it provides configuration examples, examples on how to use s2p and some of its tools on the command line, and a lot of other information.

In case you are not familiar enough with Linux, there is plenty of information on the internet, and you should accept that you may have to get familiar with it up to a certain degree. If you do not want to do that you should consider using other SCSI emulation solutions, at least as long as you do not need some of the features only offered by SCSI2Pi.

[Bikerbob]

piscsi has never been an issue.. has always worked from day 1 - my ONLY issue is getting SCSI2Pi installed and working after the fact.

bullseye vs bookworm - the piscsi group does not want to move fwd with a pre-built image of bookworm, because they dont feel there is anything in bookworm that benefits piscsi.

So if I wanted to follow your recommendation and go to bookworm - I would have to build piscsi first - load it into a raw image of pi os bookworm and then add SCSI2PI. I have attempted it - not successfully.

Anyway.. I appreciate your response. I am a bulldog when it comes to projects. I like to finish. I wanted to run your software - so I go back again and again and try more, read more, etc.

I have a working piscsi in bullseye. Beyond that, I have not been able to successfully get further.

[uweseimet]

In this case I suggest you just continue using PiSCSI. Especially if you are not familiar with Linux, having access to support in the respective Discord group is very likely something that has benefits.