Macintosh-HW
/
RASCSI
mirror of https://github.com/akuker/RASCSI.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Updated Dayna Port SCSI Link (markdown)

Daniel Markstedt 2023-01-22 22:11:43 -08:00
parent e74d6e57b5
commit b6779b6b37
1 changed files with 26 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
Dayna-Port-SCSI-Link.md

@ -36,11 +36,11 @@ In this section, we're going to reconfigure the network so that eth0 is just an
|---------|--------|
| <a href="images/daynaport_wired_network_before.png"><img src="images/daynaport_wired_network_before.png" alt="Network Before" width="200"></a> | <a href="images/daynaport_wired_network_configured.png"><img src="images/daynaport_wired_network_configured.png" alt="Network After" width="200"></a> |
- Set up linux networking: In this step we will be re-configuring the network to use a bridge device named `rascsi_bridge`
- Set up linux networking: In this step we will be re-configuring the network to use a bridge device named `piscsi_bridge`
- Copy the bridge configuration to `/etc/network/interfaces.d/`
```sudo cp ~/PiSCSI/src/raspberrypi/os_integration/rascsi_bridge /etc/network/interfaces.d/```
```sudo cp ~/PiSCSI/src/raspberrypi/os_integration/piscsi_bridge /etc/network/interfaces.d/```
- Modify the `/etc/dhcpcd.conf` file to add the following line at the bottom
@ -50,24 +50,24 @@ In this section, we're going to reconfigure the network so that eth0 is just an
**NOTE**: Your IP address may change after the reboot!
- After the reboot, run `ip addr show`. You should see that eth0 does NOT have an IP address, and that rascsi_bridge DOES have an IP address assigned.
- After the reboot, run `ip addr show`. You should see that eth0 does NOT have an IP address, and that piscsi_bridge DOES have an IP address assigned.
<a href="images/daynaport_bridge_config.png"><img src="images/daynaport_bridge_config.png" alt="Example Bridge Configuration" width="400"></a>
- When you run `brctl show`, you should also see that there is a rascsi_bridge created with eth0 connected to it.
- When you run `brctl show`, you should also see that there is a piscsi_bridge created with eth0 connected to it.
```
pi@rascsi:~ $ brctl show
pi@piscsi:~ $ brctl show
bridge name bridge id STP enabled interfaces
rascsi_bridge 8000.869bacd8de6f no eth0
piscsi_bridge 8000.869bacd8de6f no eth0
```
- After you create/attach the daynaport in Rascsi, you should be able to see a "piscsi0" interface attached to the bridge. Run 'brctl show' on Linux to validate this. (Note the formatting may be garbled on your terminal)
- After you create/attach the daynaport in PiSCSI, you should be able to see a "piscsi0" interface attached to the bridge. Run 'brctl show' on Linux to validate this. (Note the formatting may be garbled on your terminal)
```
pi@rascsi:~ $ brctl show
pi@piscsi:~ $ brctl show
bridge name bridge id STP enabled interfaces
rascsi_bridge 8000.869bacd8de6f no eth0
piscsi_bridge 8000.869bacd8de6f no eth0
piscsi0
```
@ -104,7 +104,7 @@ sudo apt-get install iptables-persistent
Reboot the Pi
Note that unlike the wired configuration above, PiSCSI will stand up the rascsi_bridge interface automatically when you attach the DaynaPORT device, so there is no need to copy over the interface config file to interfaces.d .
Note that unlike the wired configuration above, PiSCSI will stand up the piscsi_bridge interface automatically when you attach the DaynaPORT device, so there is no need to copy over the interface config file to interfaces.d .
On the Mac side, in the TCP/IP or MacTCP control panel choose Manual and input:
* IP address 10.10.20.2
@ -120,21 +120,21 @@ On the Mac side, in the TCP/IP or MacTCP control panel choose Manual and input:
# Attach a DaynaPORT adapter to your PiSCSI configuration
There are four ways to accomplish this:
1. Launch 'rascsi' with parameters on the command line (when not running as a service)
2. Edit the rascsi.service configuration to attach devices on launch (when running as a service)
3. Use 'scsictl' to dynamically attach the device on a running rascsi instance
1. Launch 'piscsi' with parameters on the command line (when not running as a service)
2. Edit the piscsi.service configuration to attach devices on launch (when running as a service)
3. Use 'scsictl' to dynamically attach the device on a running piscsi instance
4. Use the [[web interface]] to attach the device
Note that by default, the DaynaPORT device will launch with parameters 'eth0,wlan0' meaning it will attempt to use eth0 first, and if unavailable then wlan0. Also, note that the default IP address / netmask is 10.10.20.1/24. So for most usecases, if you follow the automated process and use the default values, you don't have to specify any parameters when attaching the DaynaPORT device and it should work out of the box.
Ex. with rascsi / wired / DHCP, PiSCSI *not* running as a service
```sudo rascsi -ID 6 -t scdp eth0```
Ex. with piscsi / wired / DHCP, PiSCSI *not* running as a service
```sudo piscsi -ID 6 -t scdp eth0```
Ex. with scsictl / wired / DHCP, PiSCSI already running
```scsictl -i 6 -c attach -t scdp -f eth0```
Ex. with rascsi / wireless / static IP, PiSCSI *not* running as a service
```sudo rascsi -ID 6 -t scdp wlan0:10.10.20.1/24```
Ex. with piscsi / wireless / static IP, PiSCSI *not* running as a service
```sudo piscsi -ID 6 -t scdp wlan0:10.10.20.1/24```
Ex. with scsictl / wireless / static IP, PiSCSI already running
```scsictl -i 6 -c attach -t scdp -f wlan0:10.10.20.1/24```
@ -142,17 +142,17 @@ Ex. with scsictl / wireless / static IP, PiSCSI already running
## **(Optional)** Configure PiSCSI to start up with your DaynaPORT configuration
Here you have two options. Either have the PiSCSI Web UI read your *default* configuration file on startup, or hard code the launch parameters in the rascsi.service ExecStart argument. The latter is more permanent, while the former can be managed more easily through the Web UI. Also note that the Web UI configuration will override whatever is defined in rascsi.service.
Here you have two options. Either have the PiSCSI Web UI read your *default* configuration file on startup, or hard code the launch parameters in the piscsi.service ExecStart argument. The latter is more permanent, while the former can be managed more easily through the Web UI. Also note that the Web UI configuration will override whatever is defined in piscsi.service.
- Web UI configuration option:
Once you've attached your DaynaPORT device with just the right parameters, you can save that as a PiSCSI Web UI configuration file. If you name it *default* (~/.config/rascsi/default.json) that configuration will be loaded when the Web UI starts up for ultimate convenience!
Once you've attached your DaynaPORT device with just the right parameters, you can save that as a PiSCSI Web UI configuration file. If you name it *default* (~/.config/piscsi/default.json) that configuration will be loaded when the Web UI starts up for ultimate convenience!
- rascsi.service ExecStart option:
Modify your service startup script to automatically add the DaynaPort at startup. To do this, open `/etc/systemd/system/rascsi.service` with a text editor. Modify the ExecStart line to add the ID and device. For example:
- piscsi.service ExecStart option:
Modify your service startup script to automatically add the DaynaPort at startup. To do this, open `/etc/systemd/system/piscsi.service` with a text editor. Modify the ExecStart line to add the ID and device. For example:
```ExecStart=/usr/local/bin/rascsi -ID 6 -t scdp eth0```
```ExecStart=/usr/local/bin/piscsi -ID 6 -t scdp eth0```
- If you modified the rascsi.service file, you will need to run `sudo systemctl daemon-reload` and `sudo service rascsi restart`
- If you modified the piscsi.service file, you will need to run `sudo systemctl daemon-reload` and `sudo service piscsi restart`
@ -176,8 +176,8 @@ MacTCP is your only option if you want to get your Mac with a 68000 or 68020 CPU
- Download [MacTCP 2.0.6](https://macintoshgarden.org/apps/mactcp-206) and apply the unofficial 2.1 patch, then move it into the "Control Panels" folder under the System Folder (SSW 7.0+) or in the root of the System Folder (SSW 6.0.x or earlier)
- Download and install the [DaynaPort 7.5.3 Drivers](https://macintoshgarden.org/apps/daynaport-drivers)
- Reboot your Macintosh
- Open up the MacTCP control panel and configure it with a static IP address matching the rascsi_bridge configuration on your PiSCSI
-- Example below for when rascsi_bridge is set to 10.10.20.1, and using Google Public DNS servers
- Open up the MacTCP control panel and configure it with a static IP address matching the piscsi_bridge configuration on your PiSCSI
-- Example below for when piscsi_bridge is set to 10.10.20.1, and using Google Public DNS servers
- Reboot your Macintosh again
- Test your network connection with [MacTCP Ping](https://macintoshgarden.org/apps/mactcp-ping) by f.e. pinging a DNS server (8.8.8.8)
@ -199,7 +199,7 @@ MacTCP is your only option if you want to get your Mac with a 68000 or 68020 CPU
| You may get a warning about a later version of a file with a corrupted name. You can ignore this. | <a href="images/daynaport_installer_3.jpg"><img src="images/daynaport_installer_3.jpg" alt="DaynaPort Installer 3" width="600"></a> |
| Once the install is complete, reboot the Macintosh. | <a href="images/daynaport_installer_4.jpg"><img src="images/daynaport_installer_4.jpg" alt="DaynaPort Installer 4" width="600"></a> |
**Tip: A bootstrap .HDA image with all of the needed drivers is available [Macintosh Garden](https://macintoshgarden.org/apps/rascsi-68kmla-edition)**
**Tip: A bootstrap .HDA image with all of the needed drivers is available [Macintosh Garden](https://macintoshgarden.org/apps/rascsi-reloaded)**
**Optional** Its recommended to also install the diagnostics utilities. These can help in troubleshooting. To install these, run the `diagnostics.sea` file included with the driver installer.