9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] slow performance
Date: Sun,  1 Apr 2007 14:05:29 -0400	[thread overview]
Message-ID: <7eef3c376c0dd2cdb90d2de6e0aef086@coraid.com> (raw)
In-Reply-To: <e510e47e0704011035y72815d42k7885763aa1c59375@mail.gmail.com>

you are using vesa mode because monitor=vesa.  you need to set
your monitor.  information on doing that is in vgadb(6).  once your
monitor information is set properly, the correct driver should be used.

to check for dma, "cat /dev/sdC0/ctl".  you will see dma x dmactl y.
x describes the dma capabilities of the drive, y describes which dma
capabilities are being used.  so if x is nonzero but y is zero then
"echo -n dma on > /dev/sdC0/ctl" will turn dma on.  this can be 
done automatically through plan9.ini.  "man plan9.ini" for more info.

- erik

On Sun Apr  1 13:35:05 EDT 2007, ph.rpguo@gmail.com wrote:

> % cat '#v/vgactl'
> type vesa
> size 1024x768x32 x8r8g8b8
> blank time 30 idle 0 state on
> hwaccel on
> hwblank off
> panning off
> addr p 0xd0000000 v 0xe0000000 size 0x4000000
> % echo $vgasize - $monitor
> 1024x768x32 - vesa
> 
> My video card is a GeForce Fx5200, with 128mb of memory.
> About the driver... i have never instaled a driver for it, if there is one,
> the system installed it to me. And how can i see if my HD is doind DMA or
> not?


  reply	other threads:[~2007-04-01 18:05 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-01 12:08 erik quanstrom
2007-04-01 12:35 ` pedro henrique antunes de oliveira
2007-04-01 14:39   ` Uriel
2007-04-01 15:11   ` C H Forsyth
2007-04-01 17:35     ` pedro henrique antunes de oliveira
2007-04-01 18:05       ` erik quanstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-02  9:14 phao
2007-04-02  9:31 ` Anselm R. Garbe
2007-04-02  9:38   ` Charles Forsyth
2007-04-02  9:42     ` C H Forsyth
2007-04-02  9:45     ` Anselm R. Garbe
2007-04-02 12:49       ` pedro henrique antunes de oliveira
2007-03-31 16:41 pedro henrique antunes de oliveira
2007-03-31 16:48 ` Lorenzo Fernando Bivens de la Fuente
2007-03-31 16:48 ` Charles Forsyth
2007-03-31 16:57   ` pedro henrique antunes de oliveira
2007-03-31 16:55 ` W B Hacker
2007-03-31 17:12   ` Uriel
2007-03-31 19:27     ` W B Hacker
2007-03-31 23:20       ` erik quanstrom
2007-03-31 23:35         ` pedro henrique antunes de oliveira
2007-04-01  1:40           ` erik quanstrom
2007-03-31 17:15   ` Charles Forsyth
2007-03-31 18:50 ` Armando Camarero
2007-03-31 21:05   ` C H Forsyth
2007-03-31 23:25     ` pedro henrique antunes de oliveira
2007-04-01  1:32       ` erik quanstrom
2007-04-01  9:22       ` Charles Forsyth
2007-04-01  9:52         ` pedro henrique antunes de oliveira
2007-04-01  9:56           ` pedro henrique antunes de oliveira
2007-04-01 18:24 ` ron minnich
2007-04-01 19:11   ` pedro henrique antunes de oliveira
2007-04-01 19:26     ` geoff
2007-04-01 19:57       ` pedro henrique antunes de oliveira
2007-04-01 20:07         ` Charles Forsyth
2007-04-01 20:11           ` pedro henrique antunes de oliveira
2007-04-01 20:26             ` Charles Forsyth
2007-04-01 21:13             ` ISHWAR RATTAN
2007-04-02  1:52               ` pedro henrique antunes de oliveira

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=7eef3c376c0dd2cdb90d2de6e0aef086@coraid.com \
    --to=quanstro@coraid.com \
    --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).