linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: gaxt <gaxt@rogers.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2 - Strange Terminal Problems- Gramofile UPDATE - Scheduler?
Date: Mon, 28 Jul 2003 15:48:31 -0400	[thread overview]
Message-ID: <3F257E0F.8030107@rogers.com> (raw)
In-Reply-To: <3F257CC3.1030209@rogers.com>

gaxt wrote:
> in 260-test1-mm2-O8+O9 gramofile worked fine
> 
> in 260-test2 gramofile loads but when you press on "start recording" 
> where you are supposed to get an ASCII equalizer changing with the music 
> input, you get a blank screen. Same in an xterm as in a virtual terminal.
> 

Hm. Well, closing down Wine (running Galciv) seems to have resolved the 
problem for some reason. Scheduler problems???


      reply	other threads:[~2003-07-28 19:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-27 20:42 2.6.0-test2 - VFS: Cannot open root device "NULL" or sda1 Henrik Storner
2003-07-28  2:28 ` Yifang Dai
2003-07-28  4:23   ` gaxt
2003-07-28 22:46     ` Henrik Storner
2003-07-28 19:42   ` 2.6.0-test2 - Strange Terminal Problems- Gramofile gaxt
2003-07-28 19:48     ` gaxt [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=3F257E0F.8030107@rogers.com \
    --to=gaxt@rogers.com \
    --cc=linux-kernel@vger.kernel.org \
    /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).