9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] vga and ethernet
Date: Tue, 31 Jul 2001 06:08:35 +0200	[thread overview]
Message-ID: <20010731060835.Q7181@cackle.proxima.alt.za> (raw)
In-Reply-To: <000e01c11972$b05c7520$0691e1cf@q3m5e0>; from Dean Ash on Mon, Jul 30, 2001 at 10:41:31PM -0500

On Mon, Jul 30, 2001 at 10:41:31PM -0500, Dean Ash wrote:
>
> So I've got p9 up and running at work. I'm very happy. 2 problems have
> arisen though. 1. aux/vga doesn't want to change my resolution. I set my
> monitor to the multisync75 hz. the original error I was getting with aux/vga
> was that the vgadb didn't have the resolution I wanted in the db. I'm
> looking to get my resolution up to 1024x768x8 or 1152x864x8. well I put in
> these resolutions in the vgadb and now aux/vga doesn't report and error but
> it also doesn't do anything

I can't exactly be very helpful here, but perhaps you need to be more
specific.

> my second problem is getting a network connection. ip/config times out when
> I let it go for DHCP using ip/config -G also times out. I'm wondering if I
> need to do something with ether0. the man pages talk about using bind i.e.
> bind -a '#10' /net but the -a wants a directory to bind to /net. the problem
> is I don't know what #10 is so I can't figure out if it represents my
> ether0. anyhelp or pointers to a place to look would be appreciated.
>
That's #l0 ("ell-zero") not #10.  "L" for Lance, "0" for the first
device of its type.

++L


  reply	other threads:[~2001-07-31  4:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-31  3:41 Dean Ash
2001-07-31  4:08 ` Lucio De Re [this message]
2001-07-31 12:04 presotto
2001-07-31 19:07 [9fans] vga and Ethernet Dean Ash
2001-08-01 16:53 [9fans] vga and ethernet baldwin
2001-08-01 17:59 ` andrey mirtchovski
2001-08-03  9:05   ` Ralph Corderoy
2001-08-04  1:09     ` Boyd Roberts
2001-08-01 17:09 Dean Ash

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=20010731060835.Q7181@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).