9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Thomas Miller" <tom@insolvencyhelp.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Display problem
Date: Mon, 24 May 2004 09:41:18 -0400	[thread overview]
Message-ID: <40B1FB7E.nailPP11GCGL@insolvencyhelp.org> (raw)
In-Reply-To: <20040523212405.GB7434@dip.sun.ac.za>

Wynand Winterbach <wynand@dip.sun.ac.za> wrote:

> When I boot up, everything goes well until it starts up Rio.
>
> It prints 3 lines (where pc differs for each):
> fifo stat 0 scrio dc000000 scr 80304C74 pc 80171E9C
> fifo stat 0 scrio dc000000 scr 80304C74 pc 80171E9C
> fifo stat 0 scrio dc000000 scr 80304C74 pc 80171E9C
>
> then it prints character by character (SLOWLY):
> dossrc: serving #s/dos
>
> After this it continues in its slow char by char mode, and prints the
> previous line (the one starting with fifo).
>
> I assume this line is a debug line, and that pc is the program
> counter?
>
> Anyhow, nothing happens after that :(
>
> I have a classic Athlon, a Via KX 133 (I think) motherboard, which
> uses the 82C686 IDE chipset, and an Nvidia TNT 2 - according to the
> Wiki, this setup should work flawlessly. I tried to replace the TNT 2
> with an old ATI board (I don't know which one it is. A Rage board I
> think) - this allowed me at least to see a highly corrupted version of
> the window manager, but it was pretty useless.
>
> I'm really disappointed, since this OS seems so cool.

Hi,

I had this same problem last month with apparently
the same or similar video card.

The problem goes away when I recompile *both* kernel
and userland with the latest sources.  Recompiling
the kernel alone, even from latest sources, is
insufficient to resolve the problem here.  I confirmed
this yesterday by making a fresh install from
a fresh distribution iso downloaded yesterday.  I
still had to recompile both kernel and userland.

Here is the google archive to the 9fans discussion
last month (sorry about the long line length :-):

http://groups.google.com/groups?hl=en&amp;lr=&amp;ie=UTF-8&amp;th=68e8e91fed094a7c&amp;seekm=407F31CF.nail9O11TLQU%40insolvencyhelp.org&amp;rnum=2

I still do not understand the cause of the problem
and why it seems necessary to recompile both the
kernel and userland.  I'm glad, however, that the
recompilation fixes the problem.

I am running kfs with 9pcdisk.  According to 'X
--configure' running with XFree86 Version 4.4.0
under NetBSD-current i386, my video card is
"nVidia Corporation NV5M64 [RIVA TNT2 Model 64/
Model 64 Pro]."

HTH,

Tom



  parent reply	other threads:[~2004-05-24 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040523160016.E96CF19A7A@mail.cse.psu.edu>
2004-05-23 21:24 ` Wynand Winterbach
2004-05-23 21:51   ` Russ Cox
2004-05-23 22:04     ` boyd, rounin
2004-05-24 13:41   ` Thomas Miller [this message]
2004-05-24 14:01     ` Thomas Miller

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=40B1FB7E.nailPP11GCGL@insolvencyhelp.org \
    --to=tom@insolvencyhelp.org \
    --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).