AMMRL: running VNMRJ 4.2 on CentOS 7

From: SHENG CAI <scai58_at_wisc.edu>
Date: Fri, 29 Apr 2022 18:49:53 +0000

Hi all,

After several weeks' effort, finally I was able to make VNMRJ 4.2 work (as
spectrometer) on CentOS 7 for our Varian Inova 500 MHz. The following is the
procedure:

  1. download CentOS 7.9-2009 (the latest version).
  2. install CentOS 7 (I am using an old Dell Precision 390 computer), choosing
      the last option (development and creative workstation).
  3. change the network interface name to eth0 (internet) and eth1 (console)
      using these instructions https://www.thegeekdiary.com/centos-rhel-7-how-to-modify-network-interface-names/
  4. Do not disable NetworkManager.
  5. add your computer hostname to /etc/hosts
  6. install all required rpm online using "yum install", such as openmotif.i686,
      atk.i686, gtk2.i686. Unlike CentOS 6, CentOS 7 won't ask for any missing rpm.
      I used a minimally installed CentOS 6 to find out all required packages and
      install them all to CentOS 7.
  7. install all rpm on the VNMRJ installation disk, such as rarpd, sharutils.
      They are in the folder /code/linux/. You have to use "--force" option to
      install tk8.4 and tcl8.4, because tk8.5 and tcl8.5 already exist. Don't
      worry about kdiff3 if you cannot install it now, because it will be automatically
      installed when you install VNMRJ later.
  8. install VNMRJ 4.2. Change to "spectrometer" in "config".
  9. connect the computer to console and run "setacq"

Now comes the tricky part. The VNMRJ still showed "inactive" after "./setacq". The
connection between the computer and console cannot be established automatically. To
make the computer recognize the console, I had to disconnect the console cable and
connect to another working computer running VNMRJ 4.2 on Redhat 5. After connection
established, I connected the cable back to the CentOS 7 computer. Now everything
worked. The problem is that whenever I rebooted the console, I had to use the
Redhat 5 computer as the "middle man" to establish connection to console again.
This is quite annoying. Does anyone have an idea to fix that? Thank you.

Sheng



  1.
Received on Fri Apr 29 2022 - 08:51:45 MST

This archive was generated by hypermail 2.4.0 : Wed Oct 25 2023 - 14:48:34 MST