9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] CPU/Auth/Fileserver confusion
Date: Sun, 19 Dec 2004 11:08:17 -0500	[thread overview]
Message-ID: <a6f304ec7f3468a8f165b39085e2c8a5@plan9.bell-labs.com> (raw)
In-Reply-To: <20041219123152.GA17425@SDF.LONESTAR.ORG>

On Sun Dec 19 09:50:39 EST 2004, heiko.dudzus@gmx.de wrote:
> I got another piece of hardware and made a CPU/Auth und fossil based
> fileserver out of my Plan 9 box. The Wiki page and andreys LANL setup
> page were helpful.
> 
> If I start the terminal standalone, I can cpu to the CPU server and
> can import its filesystem with 9fs.
> 
> The next step was to boot a 9pc kernel on terminal locally and get
> root fs from the server. I can login as user und the dossrv of the
> lib/profile gets executed. But nothing more and rio doesn't start and
> there are messages like:
> 
> fifo stat 0 scrio dc000000 scr80283a04 pc 80176803
> 
> I spent the night with it and really don't find out what the problem
> is.
> 
> Any help or hints appreciated,
> Heiko :-(

That sounds like there's a problem with the acceleration of your
video card. I can only find that print in the neomagic driver, and
it's commented out in the source. Check you have up to date source
for the kernel.

When bringing up a terminal with new hardware, it's often best to
not start aux/vga (and subsequently, rio) automatically. Comment out
the vgasize and monitor lines in plan9.ini, boot it, it should come
up to a shell prompt, then you can play with aux/vga manually, e.g.

	aux/vga -p>/tmp/x

will log in x what the curent state of the vga card is and you can
look there to see if aux/vga found any problems (unknown card, etc.);

	aux/mouse ps2

for example will make sure you have a mouse if you get the graphics
working (chnage the argument to what you have);

	aux/vga -m monitor -lpv resolution>/tmp/y

will try to start the graphics with the monitor type and size you
choose (e.g. -m t23 -lpv 1024x768x16) and also log progress and
problems in /tmp/y.

--jim


  parent reply	other threads:[~2004-12-19 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-19 12:31 Heiko Dudzus
2004-12-19 14:06 ` Heiko Dudzus
2004-12-19 16:08 ` jmk [this message]
2004-12-19 18:51   ` Heiko Dudzus

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=a6f304ec7f3468a8f165b39085e2c8a5@plan9.bell-labs.com \
    --to=jmk@plan9.bell-labs.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).