• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Running checkSysConf Successfully for AMS tool.

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 12562
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Running checkSysConf Successfully for AMS tool.

RFStuff
RFStuff over 4 years ago

Dear All,

I was able to run checkSysconf for IC618 and MMSIM18.

This pointed me to the uninstalled required patches. After I installed all these patches, checkSysConf gave PASS for both IC618 and MMSIM18.

But, when I tried to run checkSysconf for INCISIVE152, I got following errors. It DOES NOT give me the Valid Release name for AMS tool.

I wonder why it is happening for AMS tool only.

Is there anyway, checkSysConf can allow me to tell the needed uninstalled packages for AMS tool like IC618 and MMSIM18.

Kind Regards,

=====================================================================
[Copyright 2002-2011] Cadence Design Systems, Inc. All rights reserved.

This program and online documentation may not be copied, modified,
re-published, uploaded, executed, or distributed in any way, in any
medium, whether in whole or in part, without prior written permission
from Cadence Design Systems, Inc.
=====================================================================


============== checkSysConf: Version 3.19 ====================

Configuration checks failed on this workstation (hp), status is: FAIL

checkSysConf cannot reliably parse your systems /etc/redhat-release file
It would appear that the file is non-standard and does not contain release
information in the standard readable format.

The contents of your /etc/redhat-release is listed below between
<RELEASE_FILE> tags.
A 'correct' release file should have only one line of content, containing
version information in a standard format.

<RELEASE_FILE>
CentOS Linux release 7.9.2009 (Core)
</RELEASE_FILE>

Please check/correct your /etc/redhat-release file and try again.
There is no OEM datafile for -r for the Linux platform.

Valid OEM images are :
foreach: No match.

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    INCISIVE152 was never supported on RedHat Enterprise 7.X releases (i.e. it was not tested or released on that platform), and certainly not CentOS equivalents (the checks have become more tolerant of CentOS recently). Even on my RHEL7.6 machine I get:


    Configuration checks failed on this workstation (lnx-andrewb-76), status is: FAIL

    checkSysConf cannot reliably parse your systems /etc/redhat-release file
    It would appear that the file is non-standard and does not contain release
    information in the standard readable format.

    The contents of your /etc/redhat-release is listed below between
    <RELEASE_FILE> tags.
    A 'correct' release file should have only one line of content, containing
    version information in a standard format.

    <RELEASE_FILE>
    Red Hat Enterprise Linux Workstation release 7.6 (Maipo)
    </RELEASE_FILE>

    Please check/correct your /etc/redhat-release file and try again.
    There is no OEM datafile for -r for the Linux platform.

    RHEL7 was pretty new at the time that INCISIVE152 was released, and so it was not part of our platform matrix in place at the time of release. IC617 did make it into RHEL7 support, but INCISIVE152 didn't.

    This is also clear if you look on http://downloads.cadence.com for INCISIVE152, you'll see that it doesn't list RHEL7.

    That said, I'm sure it should just run - and if there are any shared libraries missing, it is likely to be clear when running the simulation as it would fail. The right thing (as in another post) is to move to XCELIUM rather than using this old release on a current OS.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    INCISIVE152 was never supported on RedHat Enterprise 7.X releases (i.e. it was not tested or released on that platform), and certainly not CentOS equivalents (the checks have become more tolerant of CentOS recently). Even on my RHEL7.6 machine I get:


    Configuration checks failed on this workstation (lnx-andrewb-76), status is: FAIL

    checkSysConf cannot reliably parse your systems /etc/redhat-release file
    It would appear that the file is non-standard and does not contain release
    information in the standard readable format.

    The contents of your /etc/redhat-release is listed below between
    <RELEASE_FILE> tags.
    A 'correct' release file should have only one line of content, containing
    version information in a standard format.

    <RELEASE_FILE>
    Red Hat Enterprise Linux Workstation release 7.6 (Maipo)
    </RELEASE_FILE>

    Please check/correct your /etc/redhat-release file and try again.
    There is no OEM datafile for -r for the Linux platform.

    RHEL7 was pretty new at the time that INCISIVE152 was released, and so it was not part of our platform matrix in place at the time of release. IC617 did make it into RHEL7 support, but INCISIVE152 didn't.

    This is also clear if you look on http://downloads.cadence.com for INCISIVE152, you'll see that it doesn't list RHEL7.

    That said, I'm sure it should just run - and if there are any shared libraries missing, it is likely to be clear when running the simulation as it would fail. The right thing (as in another post) is to move to XCELIUM rather than using this old release on a current OS.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information