From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <4452495F.1050403@free.fr>
Date: Fri, 28 Apr 2006 18:57:03 +0200
From: Philippe Anel <xigh@free.fr>
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051014)
MIME-Version: 1.0
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] nvidia vs. dual processors
References: <109ac0651a6dafda49be3a6ac2baa04a@quanstro.net>
In-Reply-To: <109ac0651a6dafda49be3a6ac2baa04a@quanstro.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 4a8ff6dc-ead1-11e9-9d60-3106f5b1d025

erik quanstrom wrote:

>i've been having problems with aux/vga when running
>on a dual processor machine.  before the recient update
>to aux/vga, the machine would get stuck in /sys/src/9/pc/vganvidia.c/^waitforidle.
>the iprints would be painfully slow and the machine would became
>unusable afterwards.  even "aux/vga -p" would exhibit this.
>various three-fingered salutes would impress nobody.
>
>after the recient update, "aux/vga -p" works but "monitor=vesa aux/vga -p"
>puts the machine into a fairly unusable state as soon as the output hits
>the bottom of the window.  the cursor makes big jumps, lags many seconds
>and doesn't quite track rio's idea of the cursor location.  i coudn't
>manage to select a window to to do fshalt, so i rebooted. (via the keboard.)
>
>
realmode (and vesa) is not compatible with mp.
what happens with another monitor= value ?

>(this doesn't happen if i boot *nomp=1.)
>
>i think vganvidia.c/^nvidiahwscroll is conflicting with the vesa requests in aux/vga.
>
>in an unrelated problem. *nomp or not, the screen is shifted to the left 1".
>(it works fine at the same video mode on linux.)  i'm not sure what the problem
>might be.  any ideas?
>
>
what happens with the *good* monitor= value ?

>- erik
>
>
>
>