Cadence IC5141 good on RHEL3?

H

HEB

Guest
Hi,All:

3 question:

1.
Did anyone install IC5141 on RHEL3? Any major or minor problem?
I like to use IC5141, but am not sure of the OS ( RH7.3 is kinds of old)...

2.
Did Assura306-50 and LDV51 supported on RHEL3?

3.
also, for the USR1, USR2 and USR3 on base IC5033:
when install the patches, should I do USR1, then USR2, and then USR3.
or I can just run USR3 and assume it cover all the previous USR1 and 2?

Thanks.

OldMan
 
Hi,

1.
Did anyone install IC5141 on RHEL3? Any major or minor problem?
I like to use IC5141, but am not sure of the OS ( RH7.3 is kinds of old)...
We use IC5141 on OpenAccess Database and Linux RHEL3.
We see some issues with Library Manager dd* SKILL commands and with
the new Stream Out/In interface XSTREAM. But this are no major or
show stopping bugs and they are related to IC5141 and OpenAccess
and not to the Operating System.
Which means we see this issues on Solaris too.
There is also a issue with the graphics display which is
slow in real 24 bit mode.
If you install IC5141 I suggest to wait for USR1 it's announced
for end of November. But be aware Cadence split the streams,
there is a new stream containing the simulators for IC5141 USR1.

2.
Did Assura306-50 and LDV51 supported on RHEL3?
LDV51 yes, Assura306-50 no idea we use 3.1.2.

3.
also, for the USR1, USR2 and USR3 on base IC5033:
when install the patches, should I do USR1, then USR2, and then USR3.
or I can just run USR3 and assume it cover all the previous USR1 and 2?
USR3 covers all the previous USR's.

Bernd
 
IC5141 is officially supported on RHEL3, and I've been running it on my laptop
with no problems.

Graphics performance that Bernd mentioned is not a generic one, it is
dependent on Linux graphics drivers. Some work well (with appropriate
parameter settings), some are pretty lousy (it's the fault of the graphics
drivers usually, which unfortunately tend to have worse support on Linux for
some manufacturers).

Assura 306 is rather old, so not sure if it works on RHEL3. However, I would
definitely recommend 3.1.2 or later, since that is the first release where the
Assura databases were cross-platform compatible, and so you can submit on one
platform, and look at results on another (a little/big-endian issue). DFII
databases have been platform independent for ever; it was just the assura vdb
and vldb databases.

I have been quite happily running IC5033, IC5141, IUS53, ICC11241, ASSURA 313,
USIM41, USIM42, NEOCKT31, and a few other streams on my RHEL3 laptop
for a while now, with no trouble.

The simulator stream that Bernd refers to is MMSIM60 - the MMSIM stream (out
shortly) will contain spectre and ultrasim, and allows it to be released with
a shorter release cycle than the environments in the IC stream. My
understanding is that P0 spectre bug fixes will still continue in the current
IC streams, but future IC releases will not have the simulators in as well.
Whilst initially this might appear a little concerning, the fact that
simulator new features and performance improvements will be accessible sooner
is a good thing, I think.

Regards,

Andrew.

On Tue, 16 Nov 2004 12:38:04 +0100, "@xignal-A%&HY%$v#&G=.de"
<""bernd.fischer\"@xignal-A%&HY%$v#&G=.de"> wrote:

Hi,

1.
Did anyone install IC5141 on RHEL3? Any major or minor problem?
I like to use IC5141, but am not sure of the OS ( RH7.3 is kinds of old)...

We use IC5141 on OpenAccess Database and Linux RHEL3.
We see some issues with Library Manager dd* SKILL commands and with
the new Stream Out/In interface XSTREAM. But this are no major or
show stopping bugs and they are related to IC5141 and OpenAccess
and not to the Operating System.
Which means we see this issues on Solaris too.
There is also a issue with the graphics display which is
slow in real 24 bit mode.
If you install IC5141 I suggest to wait for USR1 it's announced
for end of November. But be aware Cadence split the streams,
there is a new stream containing the simulators for IC5141 USR1.

2.
Did Assura306-50 and LDV51 supported on RHEL3?
LDV51 yes, Assura306-50 no idea we use 3.1.2.

3.
also, for the USR1, USR2 and USR3 on base IC5033:
when install the patches, should I do USR1, then USR2, and then USR3.
or I can just run USR3 and assume it cover all the previous USR1 and 2?
USR3 covers all the previous USR's.

Bernd
 
Hi, Bernd and Andrew:

Thanks for the detail reply. I'll check out the newer assura.


OldMan



Andrew Beckett <andrewb@DcEaLdEeTnEcTe.HcIoSm> wrote in
news:03skp09h9c1nnoalkuqh8fu87f89nm44u6@4ax.com:

IC5141 is officially supported on RHEL3, and I've been running it on
my laptop with no problems.

Graphics performance that Bernd mentioned is not a generic one, it is
dependent on Linux graphics drivers. Some work well (with appropriate
parameter settings), some are pretty lousy (it's the fault of the
graphics drivers usually, which unfortunately tend to have worse
support on Linux for some manufacturers).

Assura 306 is rather old, so not sure if it works on RHEL3. However, I
would definitely recommend 3.1.2 or later, since that is the first
release where the Assura databases were cross-platform compatible, and
so you can submit on one platform, and look at results on another (a
little/big-endian issue). DFII databases have been platform
independent for ever; it was just the assura vdb and vldb databases.

I have been quite happily running IC5033, IC5141, IUS53, ICC11241,
ASSURA 313, USIM41, USIM42, NEOCKT31, and a few other streams on my
RHEL3 laptop for a while now, with no trouble.

The simulator stream that Bernd refers to is MMSIM60 - the MMSIM
stream (out shortly) will contain spectre and ultrasim, and allows it
to be released with a shorter release cycle than the environments in
the IC stream. My understanding is that P0 spectre bug fixes will
still continue in the current IC streams, but future IC releases will
not have the simulators in as well. Whilst initially this might appear
a little concerning, the fact that simulator new features and
performance improvements will be accessible sooner is a good thing, I
think.

Regards,

Andrew.

On Tue, 16 Nov 2004 12:38:04 +0100, "@xignal-A%&HY%$v#&G=.de"
""bernd.fischer\"@xignal-A%&HY%$v#&G=.de"> wrote:

Hi,

1.
Did anyone install IC5141 on RHEL3? Any major or minor problem?
I like to use IC5141, but am not sure of the OS ( RH7.3 is kinds of
old)...

We use IC5141 on OpenAccess Database and Linux RHEL3.
We see some issues with Library Manager dd* SKILL commands and with
the new Stream Out/In interface XSTREAM. But this are no major or
show stopping bugs and they are related to IC5141 and OpenAccess
and not to the Operating System.
Which means we see this issues on Solaris too.
There is also a issue with the graphics display which is
slow in real 24 bit mode.
If you install IC5141 I suggest to wait for USR1 it's announced
for end of November. But be aware Cadence split the streams,
there is a new stream containing the simulators for IC5141 USR1.

2.
Did Assura306-50 and LDV51 supported on RHEL3?
LDV51 yes, Assura306-50 no idea we use 3.1.2.

3.
also, for the USR1, USR2 and USR3 on base IC5033:
when install the patches, should I do USR1, then USR2, and then
USR3. or I can just run USR3 and assume it cover all the previous
USR1 and 2?
USR3 covers all the previous USR's.

Bernd
 
for assura 313, when I open a layout and run the DRC I got a mesage
saying that the Database exist ... and if I want to overwrite it. I
say ok. The DRC passes and I answer that I do not want to see the
result. then I run the DRC for the second time and The form if I
want to overwirite the database, I answer yes. But this time assura
(or the interface) goes grayed. I need to kill icfb from the command
line. This behaviour is consistant. I opened a case but did not
get any answer yet.
Maybe your Assura issue is related to this topic
http://groups.google.de/groups?hl=de&lr=&threadm=6dbebd05.0409210711.7dee8969%40posting.google.com

Here Assura didn't release some run files if the run directory was
mounted via nfs.

Bernd
 
Andrew Beckett wrote:
IC5141 is officially supported on RHEL3, and I've been running it on my laptop
with no problems.
Have ever got a "X Error of failed request" type of error? This error is
very annoying when it happens because all windows of the icfb session
get closed.

Graphics performance that Bernd mentioned is not a generic one, it is
dependent on Linux graphics drivers. Some work well (with appropriate
parameter settings), some are pretty lousy (it's the fault of the graphics
drivers usually, which unfortunately tend to have worse support on Linux for
some manufacturers).

Assura 306 is rather old, so not sure if it works on RHEL3. However, I would
definitely recommend 3.1.2 or later, since that is the first release where the
Assura databases were cross-platform compatible, and so you can submit on one
platform, and look at results on another (a little/big-endian issue). DFII
databases have been platform independent for ever; it was just the assura vdb
and vldb databases.

I have been quite happily running IC5033, IC5141, IUS53, ICC11241, ASSURA 313,
for assura 313, when I open a layout and run the DRC I got a mesage
saying that the Database exist ... and if I want to overwrite it. I
say ok. The DRC passes and I answer that I do not want to see the
result. then I run the DRC for the second time and The form if I
want to overwirite the database, I answer yes. But this time assura
(or the interface) goes grayed. I need to kill icfb from the command
line. This behaviour is consistant. I opened a case but did not
get any answer yet.
 
Erik Wanta wrote:
We have the same assura 313 RHEL3 DRC problem where we can't run
twice. We have SR33036430 open on the subject. Are you running
update 2?
more /etc/redhat-release
Red Hat Enterprise Linux WS release 3 (Taroon Update 2)
---
In my case it called LTS 3.0.1 but it is based on
Red Hat Enterprise Linux AS release 3 (Taroon Update 1)
So I am running update 1.

But the latest here is LTS 3.03 and is based on Scientific linux
(SL303). I did not rush into upgarde yet for fear of problems. But
I will do it some time in the future.
What annoys me more is the X error which is not predictible. For
Assura I ran it many times and can reproduce the error. So, I am
just dumping assura and using Diva instead. Moreover in my case,
Assura extractor does not extract correctly the AS and AD of the
pmos. So all this makes assura sit on the back burner.
 
Setting ASSURA_UI_NONMEMDATA to 1 seems to allow us to run 2 Assura
DRC runs from the GUI on RHEL2 update 2 or 3. See Solution No.
11052212.
---
Erik


erikwanta@starband.net (Erik Wanta) wrote in message news:<84018314.0411231811.647371c7@posting.google.com>...
We are unable to run 2 DRC runs with assura 313 and RHEL3 update 2 or
update 3. Does anyone else have this problem? Any ideas on what the
problem might be?

I am writing to local /tmp so I don't think it is the nfs issue where
.nfs files weren't getting deleted.

On the second DRC submission Cadence locks up and nothing runs.
---
Erik

"A. B." <b@f.g> wrote in message news:<cnl1g2$hvj$1@info4.fnal.gov>...
Erik Wanta wrote:
We have the same assura 313 RHEL3 DRC problem where we can't run
twice. We have SR33036430 open on the subject. Are you running
update 2?
more /etc/redhat-release
Red Hat Enterprise Linux WS release 3 (Taroon Update 2)
---
In my case it called LTS 3.0.1 but it is based on
Red Hat Enterprise Linux AS release 3 (Taroon Update 1)
So I am running update 1.

But the latest here is LTS 3.03 and is based on Scientific linux
(SL303). I did not rush into upgarde yet for fear of problems. But
I will do it some time in the future.
What annoys me more is the X error which is not predictible. For
Assura I ran it many times and can reproduce the error. So, I am
just dumping assura and using Diva instead. Moreover in my case,
Assura extractor does not extract correctly the AS and AD of the
pmos. So all this makes assura sit on the back burner.
 
On Wed, 17 Nov 2004 12:27:06 -0600, "A. B." <b@f.g> wrote:

Andrew Beckett wrote:
IC5141 is officially supported on RHEL3, and I've been running it on my laptop
with no problems.

Have ever got a "X Error of failed request" type of error? This error is
very annoying when it happens because all windows of the icfb session
get closed.
Nope, I've not seen that for a while.

Graphics performance that Bernd mentioned is not a generic one, it is
dependent on Linux graphics drivers. Some work well (with appropriate
parameter settings), some are pretty lousy (it's the fault of the graphics
drivers usually, which unfortunately tend to have worse support on Linux for
some manufacturers).

Assura 306 is rather old, so not sure if it works on RHEL3. However, I would
definitely recommend 3.1.2 or later, since that is the first release where the
Assura databases were cross-platform compatible, and so you can submit on one
platform, and look at results on another (a little/big-endian issue). DFII
databases have been platform independent for ever; it was just the assura vdb
and vldb databases.

I have been quite happily running IC5033, IC5141, IUS53, ICC11241, ASSURA 313,

for assura 313, when I open a layout and run the DRC I got a mesage
saying that the Database exist ... and if I want to overwrite it. I
say ok. The DRC passes and I answer that I do not want to see the
result. then I run the DRC for the second time and The form if I
want to overwirite the database, I answer yes. But this time assura
(or the interface) goes grayed. I need to kill icfb from the command
line. This behaviour is consistant. I opened a case but did not
get any answer yet.
Actually, I did see this a couple of days ago whilst preparing an example -
but didn't reproduce it after that (I probably wasn't doing the same thing
twice, so perhaps that's why?). I think in my case it was just a one off,
but didn't explore enough to find out if it was really reproducable.

Regards,

Andrew.
 
We have the same assura 313 RHEL3 DRC problem where we can't run
twice. We have SR33036430 open on the subject. Are you running
update 2?
more /etc/redhat-release
Red Hat Enterprise Linux WS release 3 (Taroon Update 2)
---
Erik

"A. B." <b@f.g> wrote in message news:<cng4tv$vm$1@info4.fnal.gov>...
Andrew Beckett wrote:
IC5141 is officially supported on RHEL3, and I've been running it on my laptop
with no problems.

Have ever got a "X Error of failed request" type of error? This error is
very annoying when it happens because all windows of the icfb session
get closed.


Graphics performance that Bernd mentioned is not a generic one, it is
dependent on Linux graphics drivers. Some work well (with appropriate
parameter settings), some are pretty lousy (it's the fault of the graphics
drivers usually, which unfortunately tend to have worse support on Linux for
some manufacturers).

Assura 306 is rather old, so not sure if it works on RHEL3. However, I would
definitely recommend 3.1.2 or later, since that is the first release where the
Assura databases were cross-platform compatible, and so you can submit on one
platform, and look at results on another (a little/big-endian issue). DFII
databases have been platform independent for ever; it was just the assura vdb
and vldb databases.

I have been quite happily running IC5033, IC5141, IUS53, ICC11241, ASSURA 313,

for assura 313, when I open a layout and run the DRC I got a mesage
saying that the Database exist ... and if I want to overwrite it. I
say ok. The DRC passes and I answer that I do not want to see the
result. then I run the DRC for the second time and The form if I
want to overwirite the database, I answer yes. But this time assura
(or the interface) goes grayed. I need to kill icfb from the command
line. This behaviour is consistant. I opened a case but did not
get any answer yet.
 
We are unable to run 2 DRC runs with assura 313 and RHEL3 update 2 or
update 3. Does anyone else have this problem? Any ideas on what the
problem might be?

I am writing to local /tmp so I don't think it is the nfs issue where
..nfs files weren't getting deleted.

On the second DRC submission Cadence locks up and nothing runs.
---
Erik

"A. B." <b@f.g> wrote in message news:<cnl1g2$hvj$1@info4.fnal.gov>...
Erik Wanta wrote:
We have the same assura 313 RHEL3 DRC problem where we can't run
twice. We have SR33036430 open on the subject. Are you running
update 2?
more /etc/redhat-release
Red Hat Enterprise Linux WS release 3 (Taroon Update 2)
---
In my case it called LTS 3.0.1 but it is based on
Red Hat Enterprise Linux AS release 3 (Taroon Update 1)
So I am running update 1.

But the latest here is LTS 3.03 and is based on Scientific linux
(SL303). I did not rush into upgarde yet for fear of problems. But
I will do it some time in the future.
What annoys me more is the X error which is not predictible. For
Assura I ran it many times and can reproduce the error. So, I am
just dumping assura and using Diva instead. Moreover in my case,
Assura extractor does not extract correctly the AS and AD of the
pmos. So all this makes assura sit on the back burner.
 

Welcome to EDABoard.com

Sponsor

Back
Top