9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tim Wiess <tim@nop.cx>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keyboard problems after aux/vga
Date: Sun, 19 Nov 2006 11:05:42 -0800	[thread overview]
Message-ID: <a5bd31058f3dad5d77824c21c7438f28@akira.nop.cx> (raw)
In-Reply-To: <088f98b6fd3aeadc98eebb6c96f4d8e7@coraid.com>

> vesa is tough.  the first thing i would check is if X11 runs in vesa mode
> under linux on this machine.
>
> if vesa memory isn't where the driver expects or is a different size, you are
> likely to overwrite something important.  are you trying the lowest vesa resolution?

    i've tried a variety of resolutions with the same results.
    i'll try X/vesa and see what happens....



  reply	other threads:[~2006-11-19 19:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19 17:06 Tim Wiess
2006-11-19 17:45 ` erik quanstrom
2006-11-19 19:05   ` Tim Wiess [this message]
2006-11-20  1:51     ` ron minnich
2006-11-20  3:10       ` Tim Wiess
2006-11-20  3:21         ` erik quanstrom
2006-11-20  3:57           ` lucio
2006-11-27  4:09             ` Tim Wiess
2006-11-20  4:04           ` Tim Wiess

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=a5bd31058f3dad5d77824c21c7438f28@akira.nop.cx \
    --to=tim@nop.cx \
    --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).