OPNsense 23.7 on the Netgate SG-4860-1U

[jc2it]

Recently, I was attempting to use OPNsense on a reconditioned Netgate SG-4860-1U. I ran into a few snags and it took some messing about but I was able to modify the loader.conf.local file enough to get it to boot and avoid the ichsmb0 interrupt loop noise.

Much of the following came from Here:
https://forum.opnsense.org/index.php?topic=6998.msg31097#msg31097

1. Create a USB-stick with OPNsense serial (amd64)
   https://docs.opnsense.org/manual/install.html#installation-media
   
   Use the nano version and image an SSD with it. Install it in the SG-4860-1U in the big open space.
   
2. Mount this USB stick on any other running FreeBSD device and navigate into /boot on USB-stick
   I used the existing pfsense 23.05.1-RELEASE install and did the following.
   a. Press F12 at boottime, choose to boot the pfsense install with the new SSD flashed with OPNsense nano connected.
   b. press 8 to open a shell
   c. get list of devices
      # camcontrol devlist
   d. mine showed the ssd was at /dev/ada0 so mount that.
      # mount /dev/ada0 /mnt
      # cd /mnt/boot
   
3. Edit or create (if not there) a file "loader.conf.local" and put the following lines in it:
   a. if the above commands completed without error then edit/create
     # vi loader.conf.local
   b. using vi add the following lines:

hint.ichsmb.0.disabled=1
hint.uart.0.flags=0x0
hint.uart.1.flags=0x10
comconsole_speed="115200"
comconsole_port="0x2F8"
console="comconsole"
kern.cam.boot_delay="10000"


3. Save file and unmount USB stick
   a. save file with vi:
    :x
   b. change directory and unmount
    # cd /
    # unmount /mnt
    # halt
   
4. Reboot and press F12 but this time select the SSD and voila...

NOTE:
"ichsmb0: interrupt loop, status=0x60" can be fixed by adding "hint.ichsmb.0.disabled=1" to loader.conf.local

[jc2it]

Two Questions:

Can the above be added to a detection script to avoid the boot problems in the future? What would you need to help with this?

Can the ichsmb0 interrupt loop be detected and "disabled" automagically?

ok, that was three questions...