9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: [9fans] nvidia vs. dual processors
Date: Fri, 28 Apr 2006 11:06:31 -0500	[thread overview]
Message-ID: <109ac0651a6dafda49be3a6ac2baa04a@quanstro.net> (raw)

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.)

(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?

- erik


             reply	other threads:[~2006-04-28 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28 16:06 erik quanstrom [this message]
2006-04-28 16:57 ` Philippe Anel
2006-04-28 17:01 erik quanstrom
2006-04-28 17:07 ` andrey mirtchovski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=109ac0651a6dafda49be3a6ac2baa04a@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).