From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: erik quanstrom Date: Sun, 2 Aug 2009 17:41:19 -0400 To: 9fans@9fans.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Parallels Vesa driver question Topicbox-Message-UUID: 35f28e48-ead5-11e9-9d60-3106f5b1d025 > Erik, > > Thanks for your speedy assistance! I think the two things are closely > interrrelated via the global variable hardscreen. Reverting this file > solved the problem. I wouldn't be surprised if there were something > weird about Parallels' MTRR support, and since this isn't the current > version it's not likely to get any better. If anyone's using Parallels > 4 and not running into this issue, I'd love to know. you're welcome. but if you wouldn't mind, would you try the new source but modify it by replacing the vgavesaflush in the following diff with "0"? > > vgavesa.c:174,178 - /n/sourcesdump/2008/1101/plan9/sys/src/9/pc/ > > vgavesa.c:140,145 > > 0, > > 0, > > 0, > > - vesaflush, > > + 0, > > }; the reason for this test would be to see if the problem is with vesaflush or the mtrrs. - erik