Hi Rich,
That screenshot is very useful :)
The last time I saw something like that was using Xsun or an old version of
Xvnc. In both cases the issue was that I was running an Xserver that didn't
support the XRENDER extension.
Could you verify this by running:
/usr/openwin/bin/xdpyinfo | grep RENDER
Would this happen to be the case for you?
If you are running on x86/amd64 it is usually much better to use the Xorg
xserver since that is where the main focus is w.r.t. the latest X extensions.
Thanks,
Darren.
Rich Teer wrote:
> On Tue, 4 Mar 2008, Darren Kenny wrote:
>
>> Hi Rich,
>
> Hi Darren,
>
>> Are you using the i386 or amd64 downloads, AFAIK you must use the amd64
>> download
>> if you're using that chipset (which AFAIK the Ultra 20 is...)
>
> Yep, I'm using the amd64 version (just re-downloaded and installed, to be
> 100% sure).
>
>> My downloaded file is called:
>>
>> VirtualBox-opensolaris-amd64-1.5.51-r28040-beta1.bz2
>> ^^^^^
>
> Yep, that's the one I have.
>
>> Also, if you are using /usr/bin/VirtualBox you don't need to set PATH and
>> LD_LIBRARY_PATH since they are set in that script already.
>
> Yep, got that. I wish the VirtualBox guys would learn about the -R flag
> (and stop using mixed case executable names!).
>
> Unfortunately, despite installing with no errors, it still doesn't work
> for me. I've attached a screenshot show the black boxes I get when I
> run VirtualBox. I get the same results on my Ultra 20 and Ferrari 3400
> (both running build 81), and some Intel Dual Core Duo machine at work,
> running build 70 (or thereabouts).
>
> Does anyone have any other ideas? I plan to install a new build of Nevada
> soon, but judging from the feedback I've seen here, it'll probably have no
> effect...
>
