Thanks for your reply. There are a couple of problems with this. There would be a conflict with the NFS servers' IP addresses because both use the same IP address. This allows my laptop to connect to either of them when needed without having to flip the NFS server IP address back and forth on the laptop. It would also require the laptop to connect to both NFS servers at the same time which looks to be possible but that would again require flipping an Ethernet configuration I normally use to connect to the Internet to the NFS network and back. The NFS (static IP) and Internet (dhcp) networks each have their own Gb network hardware and the Internet configuration would have to be changed back and forth to make that work. A second alternative would be to connect the two NFS servers to each other which I think would mean one would have to be reconfigured as a NFS client while the files are synchronized and then flipped back to a server for normal use. The laptop does not have a built in Ethernet interface, the hardware for both is provided by two USB-3 to Gb Ethernet adapters so a separate connection using the USB-3 transfer cable only when needed would actually simplify things. The modules I need already exist and could easily be compiled when the rest of the kernel and modules are compiled. In an interesting turn I checked the current version of Raspberry Pi OS which uses a 6.12.47 kernel (close enough?) to see if I could use their modules but they were not available there either, usbpl was. As far as I can tell there is no reason to compile and include the ubspl module without them.

Success!, THANK YOU!

Thanks for the reply. I seem to be on the right track but a problem has cropped up. Here is the output from xrandr and the command you suggested:

:~$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
   1920x1080     59.98*+  39.98 
   1680x1050     59.98 
   1280x1024     59.98 
   1440x900      59.98 
   1280x800      59.98 
   1280x720      59.98 
   1024x768      59.98 
   800x600       59.98 
   640x480       59.98 
HDMI-A-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 458mm x 258mm
   1920x1080     60.00*+
   1680x1050     59.88 
   1600x900      60.00 
   1280x1024     60.02 
   1440x900      59.90 
   1280x800      59.91 
   1280x720      60.00 
   1024x768      60.00 
   800x600       60.32 
   640x480       59.94 
   720x400       70.08

:~$ xrandr --output HDMI-A-0 --auto --right-of "Screen 0:"
xrandr: cannot find output "Screen 0:"
:~$ xrandr --output HDMI-A-0 --auto --right-of Screen 0:
xrandr: unrecognized option '0:'
Try 'xrandr --help' for more information.
:~$ xrandr --output HDMI-A-0 --auto --right-of Screen
xrandr: cannot find output "Screen"
:~$ xrandr --output HDMI-A-0 --auto --right-of "Screen 0"
xrandr: cannot find output "Screen 0"

Any ideas?

Thanks for the reply. I will look into that but if it is not there now it was also not there when it was working. This was not a new install, the SATA SSD I'm trying to boot from now is exactly the same one it was working with before. And before I tried to boot from it again I ran e2fsck on all the partitions on that drive booting it from a hard drive I use with by motherboard test stand and there were no errors. That is the really frustrating part, I've done very similar things before with no problems so it should have just worked. The other thing that is very odd is that I can enter in text at the log in prompt from the same SATA SSD drive when a graphics card and keyboard is installed using the original install inittab that was saved before I modified it to boot from the serial terminal.

I finally got back to trying using interface names other than ethN  and it does indeed fix the problem I was seeing. Thanks !

Here are the details:

This is the new setup in the 70-persistent-net.rules file

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:01:29:d3:0f:01", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="ethr0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="04:4b:80:08:80:03", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="ethr1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:e9:bd:1c:b7", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="ethr2"

and this is the new /etc/network/interfaces

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug ethr1
iface ethr1 inet dhcp

# The distributed compile/cluster network interface
allow-hotplug ethr0
iface ethr0 inet static
address 192.168.10.109
netmask 255.255.255.0

# The first test interface
allow-hotplug ethr2
iface ethr2 inet static
address 192.168.69.96
netmask 255.255.255.0

and the network interfaces wired interface name in wicd preferences was changed to ethr1