David Brownlee | 6 Mar 2009 02:04
Picon

Re: Screen corruption under Xen DOM0 in firefox

On Thu, 5 Mar 2009, Matthew Mondor wrote:

> David Brownlee <abs <at> absd.org> wrote:
>
>>  	I'm trying Xen on my NetBSD 5.0 laptop and one thing I've
>>  	moticed is that the Firefox window seems to suffer corruption
>>  	when focus is gained/lost (this is under gnome on a Thinkpad
>>  	T60p using the radeonhd driver on a ATI MOBILITY FireGL V5250
>>
>>  	An example is at:
>>  	http://mono.org/abs/xen-x11-corruption.png
>>
>>  	Note that the 'Tools' on the menu bar has been garbled, as has
>>  	part of the webpage.
>>
>>  	Has anyone else seem anything similar?
>
> Under a desktop with an ATI radeon card I had some corruption with native
> firefox 3, but which only happened under some specific pages/tabs, so it
> seemed like a gecko bug to me...  I've not had any such problem with
> firefox 2 however.  No idea if this is related or not to your problem
> though.  The type of corruption I observed appeared different too.

 	Interesting - I can reproduce it on firefox2 and thunderbird
 	on this system but not on openoffice (for example). Did you
 	see your issues on xen or straight i386? Were you using
 	a radeon or radeonhd driver? Thanks

--

-- 
 		David/absolute       -- www.NetBSD.org: No hype required --
(Continue reading)

Matthew Mondor | 6 Mar 2009 04:19

Re: Screen corruption under Xen DOM0 in firefox

On Fri, 6 Mar 2009 01:04:04 +0000 (GMT)
David Brownlee <abs <at> NetBSD.org> wrote:

>  	Interesting - I can reproduce it on firefox2 and thunderbird
>  	on this system but not on openoffice (for example). Did you
>  	see your issues on xen or straight i386? Were you using
>  	a radeon or radeonhd driver? Thanks

The radeon driver on plain i386 (although i686 compiled system), sorry
if the previous post lacked this information.  I also haven't
encountered any other such corruption problem than under firefox 3.

Other odd problems I had on netbsd-5 base xorg were:

xscreensaver 3D modules under DRI, but these might well be related to
xscreensaver-specific bugs (some modules such as glmatrix appear to
have an invisible texture, and so only work with -wireframe or
-no-texture).  Moreover I can run xscreensaver modules fine manually,
but when xscreensaver activates them itself they appear to be
unaccelerated (I didn't look yet into why).

When exiting X11 or switching to a console text terminal, the text is
now black on black, until I run a command such as "vbetool post", which
is not ideal as it also restores the hardware cursor and interferes
with the display.  I also had this problem with the rage128 driver on
xorg, although not at all with netbsd-4's xfree86.
--

-- 
Matt

(Continue reading)


Gmane