Solaris 10 Display Screen Video Vanishes / Weird Mouse Issue

Solaris 10 Display Screen Video Vanishes / Weird Mouse Issue

Post by Questma » Sat, 13 May 2006 04:49:48



Good afternoon --

First:

I browsed the last couple of years' headers, and I saw one thing that
I'm going to try, but nobody ever said if it worked about this problem:

I've got two boxes - a 220R and a 420R - and both have PGX32-type Raptor
cards - and both have the problem where when the display goes to
"sleep", it can never be awakened again.

Has anyone found a conclusive fix for this problem?  Does commenting out
the "dtlogin stop" functionality in init.d/dtlogin work?

Is this related to "bug 6222319"?  If so, is there a patch?

Second:

When the display IS on and I'm working on the console, when I move the
mouse, the screen flickers on and off!!!  This is very annoying, as you
can imagine, and it makes it difficult to get anything done on console.

Has anyone experienced this behavior before?

Many thanks for any help,
Rick

 
 
 

Solaris 10 Display Screen Video Vanishes / Weird Mouse Issue

Post by Martin Pau » Sat, 13 May 2006 19:19:37



> I've got two boxes - a 220R and a 420R - and both have PGX32-type Raptor
> cards - and both have the problem where when the display goes to
> "sleep", it can never be awakened again.

> Has anyone found a conclusive fix for this problem?  Does commenting out
> the "dtlogin stop" functionality in init.d/dtlogin work?

> Is this related to "bug 6222319"?  If so, is there a patch?

Looks more like bugId 5093310. A workaround might be to disable
power management for the card (xset dpms).

If you haven't done so yet, I would install the most recent driver
patch for your OS release before trying anything else:

  $ pca -l /PGX32/
  Patch  IR   CR RS Age Synopsis
  ------ -- - -- -- --- ------------------------------------------------
  107714 -- < 25  S 961 PGX32 2.5.1: PGX32 Graphics Patch
  107715 -- < 26  S 436 PGX32 2.6: PGX32 Graphics Patch
  107716 -- < 27 RS 477 SunOS 5.7: PGX32 Graphics Patch
  107851 -- < 26  S 490 PGX32 2.1: Graphics Patch
  109154 -- < 21 RS 479 SunOS 5.8: PGX32 Graphics
  110126 -- < 03    999 Hardware/PROM: PGX32 firmware Update
  112601 -- < 10 RS  86 SunOS 5.9: PGX32 Graphics
  119309 -- < 03    386 SunOS 5.10: PGX32 Graphics

Quote:> When the display IS on and I'm working on the console, when I move the
> mouse, the screen flickers on and off!!!  This is very annoying, as you
> can imagine, and it makes it difficult to get anything done on console.

Might be fixed in a patch, too. E.g. 110126 mentions:

  4325135 PGX32 <-> 21" (Century) monitor gives jittered image

hth,

mp.
--
Systems Administrator | Institute of Scientific Computing | Univ. of Vienna

 
 
 

Solaris 10 Display Screen Video Vanishes / Weird Mouse Issue

Post by Questma » Fri, 19 May 2006 00:18:52




>>I've got two boxes - a 220R and a 420R - and both have PGX32-type Raptor
>>cards - and both have the problem where when the display goes to
>>"sleep", it can never be awakened again.

>>Has anyone found a conclusive fix for this problem?  Does commenting out
>>the "dtlogin stop" functionality in init.d/dtlogin work?

>>Is this related to "bug 6222319"?  If so, is there a patch?

> Looks more like bugId 5093310. A workaround might be to disable
> power management for the card (xset dpms).

> If you haven't done so yet, I would install the most recent driver
> patch for your OS release before trying anything else:

>   119309 -- < 03    386 SunOS 5.10: PGX32 Graphics

Martin,

This solution worked perfectly!  This solved the problem both on the
220R and 420R.

For anyone having this issue, I recommend using Patch 119309!

Quote:

>>When the display IS on and I'm working on the console, when I move the
>>mouse, the screen flickers on and off!!!  This is very annoying, as you
>>can imagine, and it makes it difficult to get anything done on console.

> Might be fixed in a patch, too. E.g. 110126 mentions:

>   4325135 PGX32 <-> 21" (Century) monitor gives jittered image

> hth,

> mp.

This one, however, is not solving the problem.  I'll post a new thread
detailing it better since I think that I did not explain it properly.

Rick