9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Successful install+update?
Date: Fri, 16 Apr 2004 09:12:21 +0200	[thread overview]
Message-ID: <4aee4b4fec725290801663b323136933@plan9.escet.urjc.es> (raw)
In-Reply-To: <90be826f65f335ab5fc4e7bf5f28293d@plan9.ucalgary.ca>

[-- Attachment #1: Type: text/plain, Size: 121 bytes --]

I see. Actually we had both a cursor/speed problem and the
message. But I now see how the message went away.

thanks

[-- Attachment #2: Type: message/rfc822, Size: 2378 bytes --]

From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Successful install+update?
Date: Fri, 16 Apr 2004 01:06:43 -0600
Message-ID: <90be826f65f335ab5fc4e7bf5f28293d@plan9.ucalgary.ca>

> I don't understand why this did fix your problem; although
> I'd like to. Maybe I'm wrong regarding the nvidia thing.

vganvidia.c was updated on the 6th (or 7th) of April and the 'fifo
stat...' message disappeared from it:

/n/dump/2004/0415/sys/src/9/pc/vganvidia.c:385,458 c /n/dump/2004/0407/sys/src/9/pc/vganvidia.c:263,264
[big snip]
---
> 	if(x >= 1000000)
> 		iprint("fifo stat %d scrio %.8lux scr %p pc %luX\n", *fifofree, scr->io, scr, getcallerpc(&scr));


so your troublesome kernels must be older ones...  i haven't
recompiled since (though i must now, to get geoff's ipv6 changes in)
so i don't know whether my cards will experience any problems with the
changed vganvidia.c...

hth, andrey

      reply	other threads:[~2004-04-16  7:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16  1:07 Thomas Miller
2004-04-16  6:49 ` Fco.J.Ballesteros
2004-04-16  7:06   ` andrey mirtchovski
2004-04-16  7:12     ` Fco.J.Ballesteros [this message]

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=4aee4b4fec725290801663b323136933@plan9.escet.urjc.es \
    --to=nemo@lsub.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).