fatal XIO - newbie

Hello forum,

I am quite a new user to that ray tracer. Just got a hold of the book and
installed the ray tracer in my Linux system.

Unfortunately i am getting the following error when i run one of the most
primitive commands:

···

****************************
sajjad@sajjad:~/Radiance/chapt1$ rview -vp 2.25 .375 1 -vd -.25 .125 -.125
-av .5 .5 .5 test.oct
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server
":0.0"
      after 24518 requests (24518 known processed) with 0 events remaining.
sajjad@sajjad:~/Radiance/chapt1$ rview -vp 2.25 .375 1 -vd -.25 .125 -.125
-av .5 .5 .5 test.oct
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server
":0.0"
      after 24515 requests (24515 known processed) with 0 events remaining.
sajjad@sajjad:~/Radiance/chapt1$

**************************

The scene is rendered though in the window , but after window resize event
it does not and the error pops up in the command line

Any idea why and how to get around that error?

Regards
Sajjad

I've never run across this error before. It sounds like a communication problem between rvu and the X11 server, or an unsupported request. Has anyone else seen this? Does it happen every time you resize the window?

-Greg

···

From: ami guru <[email protected]>
Date: April 23, 2009 7:47:52 AM PDT

Hello forum,

I am quite a new user to that ray tracer. Just got a hold of the book and installed the ray tracer in my Linux system.

Unfortunately i am getting the following error when i run one of the most primitive commands:

****************************
sajjad@sajjad:~/Radiance/chapt1$ rview -vp 2.25 .375 1 -vd -.25 .125 -.125 -av .5 .5 .5 test.oct
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 24518 requests (24518 known processed) with 0 events remaining.
sajjad@sajjad:~/Radiance/chapt1$ rview -vp 2.25 .375 1 -vd -.25 .125 -.125 -av .5 .5 .5 test.oct
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 24515 requests (24515 known processed) with 0 events remaining.
sajjad@sajjad:~/Radiance/chapt1$

**************************

The scene is rendered though in the window , but after window resize event it does not and the error pops up in the command line

Any idea why and how to get around that error?

Regards
Sajjad

Greg Ward wrote:

I've never run across this error before. It sounds like a communication problem between rvu and the X11 server, or an unsupported request. Has anyone else seen this?

Definitely no, I've never seen this before. If I'm gonna get an error from the X11 server, I don't get an rvu window at all.

Hi ami.

Hello forum,

I am quite a new user to that ray tracer. Just got a hold of the book and
installed the ray tracer in my Linux system.

Unfortunately i am getting the following error when i run one of the most
primitive commands:

****************************
sajjad@sajjad:~/Radiance/chapt1$ rview -vp 2.25 .375 1 -vd -.25 .125 -.125
-av .5 .5 .5 test.oct
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server
":0.0"
      after 24518 requests (24518 known processed) with 0 events remaining.

A bit of googling showed that this is not an error that's unique to
rview/rvu (or Radiance in general).

I would think it's a problem with the graphics card driver (ATI was mostly
reported). You could try
to disable the 3D acceleration (won't affect rview/rvu, but other things
like blender) or use a standard
driver and see if that helps when you run rvu. If that's your problem
upgrade/downgrade to a different
driver version or replace the graphics card with another type/chip.

Regards,
Thomas

···

On Thu, Apr 23, 2009 at 3:47 PM, ami guru <[email protected]> wrote:

Hello forum,

Thanks for the feedback on the issue.

If that is the problem of the graphics card then i think i am not on the
positive side.

I have ATI X1600 built-in my system

Sajjad

···

---------- Forwarded message ----------
From: Thomas Bleicher <[email protected]>
Date: Fri, Apr 24, 2009 at 10:29 PM
Subject: Re: [Radiance-general] fatal XIO - newbie
To: Radiance general discussion <[email protected]>

Hi ami.

On Thu, Apr 23, 2009 at 3:47 PM, ami guru <[email protected]> wrote:

Hello forum,

I am quite a new user to that ray tracer. Just got a hold of the book and
installed the ray tracer in my Linux system.

Unfortunately i am getting the following error when i run one of the most
primitive commands:

****************************
sajjad@sajjad:~/Radiance/chapt1$ rview -vp 2.25 .375 1 -vd -.25 .125 -.125
-av .5 .5 .5 test.oct
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server
":0.0"
      after 24518 requests (24518 known processed) with 0 events remaining.

A bit of googling showed that this is not an error that's unique to
rview/rvu (or Radiance in general).

I would think it's a problem with the graphics card driver (ATI was mostly
reported). You could try
to disable the 3D acceleration (won't affect rview/rvu, but other things
like blender) or use a standard
driver and see if that helps when you run rvu. If that's your problem
upgrade/downgrade to a different
driver version or replace the graphics card with another type/chip.

Regards,
Thomas

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

The free ATI drivers in X.org are actually fairly mature and stable. I personally would not ever go for nVidia.

If you are using a distro which default-enables Compiz desktop effects, such as Ubuntu, try disabling them:

System > Preferences > Appearance > Visual Effects

Ubuntu defaults to a setting which give you semi-tranparent windows, smooth animations when launching apps or switching desktop. It's called 'Normal' in the control panel, When set to 'Extra', all the whizz-bang is enabled, leaving OSX and Windows 7 in the dust.

Try setting it to 'None', and see if your problem goes away. I had a similar problem on an Ubuntu box with nVidia card some time ago. rvu would launch, but then get stuck for up to 30 seconds. The fix described aboved sorted the problem.

Axel