Re: Cadence Tool Disaster

In comp.os.linux.setup, Fazela
<fazela@xxxxxxxxx>
wrote
on 24 Dec 2005 09:20:24 -0800
<1135444824.020083.271580@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>:
> Hello All,
> I am trying to use cadence silicon ensemble via doing an ssh to one of
> our engineering school machines through cygwin. However when I try to
> invoke
>>seultra&
> I get the folowing error
>
> ***********
> CADENCE Program Disaster:
> Pseudo color graphics card not detected.
> Session aborts.
> ***********
>
> [1] Exit 1 seultra
>
>
> I was wondering as to what the problem was and if there was some
> solution to it.
>
> Thanks,
> Fazela
>

The problem does not appear to be specific to Linux.

The first try:

$ ssh -XY user@remotehost

and then invoke 'seultra'; Cadence's tool might not
be detecting an X server at all. If you want to test
the actual X server, try 'echo $DISPLAY', then firing
up 'xeyes' or 'xedit' and see if you get a window on
your local display. If you can, you're in reasonably
good shape. You may have to wiggle /etc/ssh/sshd_config
to allow X11Forwarding, if you have root/administration
access on the remote server.

Of course xdpyinfo can tell you about the characteristics
of the server, as the remote host sees it. If the ssh
forwarding is working it's actually using a proxy on
port 6010 or localhost:10; 'echo $DISPLAY' will show this.

If the problem is truly because Cadence's tool needs a PseudoColor
(as opposed to an X server; most PC video cards are too good for
PseudoColor and support instead TrueColor or DirectColor with
24- or 32-bit capability), you might try the following command
on your box; you'll have to run it from a logged-in console (CTRL-ALT-Fn),
though you won't have to log in as root if everything's set up properly:

$ startx -- :1 -depth 8 -cc Pseudo

then invoke ssh -XY and Cadence's Silicon tool and see if that helps.
If xdpyinfo indicates PseudoColor as the top choice,
you might have a chance. Depending on your setup you might have
to invoke 'xterm -display :1' or edit $HOME/.xinitrc .

I'm not otherwise familar with Cadence's tools, so this is an
educated guess.

--
#191, ewill3@xxxxxxxxxxxxx
It's still legal to go .sigless.
.

Relevant Pages

  • Re: Apache Software Foundation Server compromised, resecured. (fwd)
    ... this was one "result" of the comromised ssh binary at sourceforge. ... a public server of the Apache Software Foundation ... > (ASF) was illegally accessed by unknown crackers. ... > exhaustive audit of all Apache source code and binary distributions ...
    (FreeBSD-Security)
  • Re: FreeBSD Crash without Errors, Warnings, or Panics
    ... I suppose I could run on stable until the driver is fixed in a release branch, but I need this box up and online, and I've always read that the stable branch is not the place for production servers. ... I'm running 6.0-RELEASE-p5 on a Toshiba built server: dual Xeon Intel motherboard with a LSILogic MegaRAID controller. ... Also, some network ports still respond, like a telnet to port 22 to test SSH will yield an SSH banner, but trying to connect with SSH just hangs. ... The box runs a web-based app and connects to a local Postgres DB which seemed to be unable to start new connections being requested by the PHP scripts. ...
    (freebsd-hackers)
  • Re: restrict ssh access
    ... > We have one ssh server which receives about 6000 failed attempts to ... > unsuccessful login attempts per client IP address? ... the remote server is also running OpenSSH. ...
    (comp.security.ssh)
  • Re: SSH as root
    ... Subject: SSH as root ... but it doesn't require having a key on the server that could be ... If they compromise a server, and the passphrase, etc. is there, they only ... private key to anyone. ...
    (SSH)
  • Re: Explanation of SSH
    ... I am still unclear on how SSH works exactly. ... Client issues SSH command and names server ... "Shopper" says "server sends back its public host and server keys ... Surely there is only one public key it sends ...
    (comp.security.ssh)